[Bug 926330] New: system refuses to boot if /home is not available
http://bugzilla.suse.com/show_bug.cgi?id=926330 Bug ID: 926330 Summary: system refuses to boot if /home is not available Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening@forge.provo.novell.com Reporter: oneukum@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- If /home cannot be mounted (eg. on a RAID array or bcache and no driver in the initrd) the whole system refuses to come up. The system should be able to boot without /home -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=926330
Oliver Neukum
http://bugzilla.suse.com/show_bug.cgi?id=926330
Thomas Blume
If /home cannot be mounted (eg. on a RAID array or bcache and no driver in the initrd) the whole system refuses to come up. The system should be able to boot without /home
Hm, your example suggests that the whole device holding /home is not present. In this case, fsck would fail, even before the mount is attempted. I thought that even on System V systems, the boot would fail if an fsck fails. However, on an systemd system it will fail for sure if a device holding a mount is not present. This works as designed. If you don't want this, you need to add the nofail mount option as Bernhard already wrote. Ok, with this? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=926330
Oliver Neukum
If you don't want this, you need to add the nofail mount option as Bernhard already wrote.
Ok, with this?
Certainly, but I think that is YaST's job. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=926330
Thomas Blume
Ok, with this?
Certainly, but I think that is YaST's job.
Ok, adding yast2-maintainers to CC. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=926330
--- Comment #5 from Bernhard Wiedemann
Hm, your example suggests that the whole device holding /home is not present. In this case, fsck would fail, even before the mount is attempted. I thought that even on System V systems, the boot would fail if an fsck fails.
Just tested on SLE-11-SP3 adding to fstab /somedir /dev/vdx ext3 default 0 0 and this just boots fine. It only fails, when setting the last param to 2 to trigger a fsck and then goes into a sulogin with the rootfs mounted. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=926330
--- Comment #6 from Thomas Blume
Just tested on SLE-11-SP3 adding to fstab /somedir /dev/vdx ext3 default 0 0
and this just boots fine. It only fails, when setting the last param to 2 to trigger a fsck and then goes into a sulogin with the rootfs mounted.
Ok, but the default is 2 when adding a mountpoint via YaST. If you do it manually, you can as well just add the 'nofail' mount option. :-) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=926330
Bernhard Wiedemann
Ok, but the default is 2 when adding a mountpoint via YaST. If you do it manually, you can as well just add the 'nofail' mount option.
The problem with the nofail option is that nothing tells you about it. It would have been different, if you would have to add a "fail" option to the important entries... meaning that the default was still the same as before, but you could change it explicitly. man fstab and man mount just describes it as nofail: do not report errors if ... so nothing about the actual importance of it. Would also help, if there was a comment in the default fstab file. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=926330
Arvin Schnell
it usually helps to mark those with the "nofail" option in /etc/fstab
maybe this should be the default from yast2 disk partitioner...
No, I don't think so. For example we had bug reports with encrypted devices where the boot process continued after some time even without providing a password and users where confused because there home directory was missing. For me the problem is simply that fixing boot problems with systemd is currently to difficult (if at all possible). -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=926330
--- Comment #9 from Oliver Neukum
No, I don't think so. For example we had bug reports with encrypted devices where the boot process continued after some time even without providing a password and users where confused because there home directory was missing.
Then at least they can fix the omission. If you cannot boot, that's it. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=926330
Dr. Werner Fink
http://bugzilla.suse.com/show_bug.cgi?id=926330
Arvin Schnell
http://bugzilla.suse.com/show_bug.cgi?id=926330
Dr. Werner Fink
http://bugzilla.suse.com/show_bug.cgi?id=926330
Arvin Schnell
http://bugzilla.suse.com/show_bug.cgi?id=926330
Oliver Neukum
It should provide whatever Oliver is missing in systemd but would be available in the system.
I am not really missing a feature in systemd. This looks to me like a question of configuration. In this case systemd should wait for the attempt to mount /home to finish, but not to succeed. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=926330
Dr. Werner Fink
http://bugzilla.suse.com/show_bug.cgi?id=926330
Oliver Neukum
(In reply to Oliver Neukum from comment #14)
Hmmm ... for a not decypted /home this become infinite. Do you really think this is the solution? Also dropping into a emergency shell does not help (IMHO).
It is better than the current setup. And I think it can be done with minimal changes, like adding "nofail". Encryption is IMHO a special case. It requires interaction with people. And I don't think that a missing /home should drop me into an emergency shell. It should boot up. Ideally the GUI would immediately make obvious that the system has come up in a diminished state, but that would be a feature request. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=926330
Dr. Werner Fink
It is better than the current setup. And I think it can be done with minimal changes, like adding "nofail". Encryption is IMHO a special case. It requires interaction with people.
The problem seems to be that Arvin does not like the `nofail' option for a separate /home partition as i can read from comment #11 @Arvin: Second try: What is wrong to use "nofail" as default for a separate /home partition? At least as an option showed up to the user as further information. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=926330
Arvin Schnell
http://bugzilla.suse.com/show_bug.cgi?id=926330
--- Comment #19 from Oliver Neukum
participants (1)
-
bugzilla_noreply@novell.com