Bug 731480

Summary:	hibernated windows partition prevents boot
Product:	[openSUSE] openSUSE 12.1	Reporter:	Daniel Morris <danielm>
Component:	Basesystem	Assignee:	Frederic Crozat <fcrozat>
Status:	RESOLVED WONTFIX	QA Contact:	E-mail List <qa-bugs>
Severity:	Major
Priority:	P5 - None	CC:	aschnell, coolo, jsuchome, suse-beta
Version:	Final
Target Milestone:	---
Hardware:	i586
OS:	Other
Whiteboard:
Found By:	Community User	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Daniel Morris 2011-11-18 22:12:25 UTC

On updating from openSUSE 11.4 to 12.1 (zypper dup), the system wouldn't boot properly, asking for the root password early during the boot sequence. This was with the new default systemd boot scripts. 

After some troubleshooting I noticed that an old mount in /etc/fstab of an ntfs partition (windows/c) was whining as Windows had been hibernated and would need the ro flag passed as a mount option. This was benign in 11.4, maybe the nofail flag (mentioned with reference to crypto partitions in the release notes) is needed? Commenting the ntfs mount allowed the system to boot smoothly.

Comment 2 Arvin Schnell 2011-11-21 09:30:16 UTC

During an update with zypper YaST has no chance to modify fstab. So if
there are really changes required these have to made somewhere else.

Comment 3 Kun Kun Zhang 2012-03-08 13:59:54 UTC

Long time no response.So closed.Feel free to reopen it.Thanks.

Comment 4 Christian Boltz 2012-03-13 23:21:36 UTC

Nobody reassigning the bug to the package maintainer is no reason to close a bug as "noresponse". Reopening (and assigning to the package maintainer).

Arvin, feel free to reassign to someone who manages this "somewhere else" ;-)

Comment 5 Arvin Schnell 2012-03-14 09:11:56 UTC

As stated in comment #2 YaST cannot mofidy fstab if the update is done
via zypper dup.

Comment 7 Daniel Morris 2012-03-14 09:55:06 UTC

I don't think this is exclusively a YaST problem. The flakiness seems to lie in the new  systemd and it being less tolerant of non-mounting filesytems. 

On my desktop I've always mounted the opensuse iso images through /etc/fstab (locally networked machines then use these via vsftpd too) like:-

/mirrors/torrentable/openSUSE-12.1-DVD-x86_64.iso      /mirrors/opensuse-121 iso9660 loop,uid=danielm,gid=users,ro  0 2

In this case I guess that there is a race condition with the underlying mount point still being checked as systemd tries to do things in parallel? It works quite well post boot.

That line in /etc/fstab (and other lines like it) bring the boot sequence to halt, which is very frustrating when you are 30 miles away and a power outage causes the UPS to shut the system down cleanly, but it won't come back up without console intervention. 

I'd vote for some gentler means of logging problems and trying to carry on, rather than the bail-out approach.

Comment 9 Frederic Crozat 2012-03-14 10:48:25 UTC

@Daniel: please open a separate bug report for the iso mount bug (and double check if it works with systemd from 12.1 maintenance update).

I agree systemd should be a little more verbose when it goes into "rescue" mode due to a failing mount.

Comment 10 Daniel Morris 2012-03-15 08:38:19 UTC

@Frederic https://bugzilla.novell.com/show_bug.cgi?id=752291

Comment 11 Frederic Crozat 2013-03-11 16:04:31 UTC

systemd in 12.3 should be more verbose when failing. Closing as wontfix (for 12.1), since we can't improve its behavior on older release, unfortunately.