http://bugzilla.suse.com/show_bug.cgi?id=926330 Thomas Blume changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |thomas.blume@suse.com Flags| |needinfo?(oneukum@suse.com) --- Comment #2 from Thomas Blume --- (In reply to Oliver Neukum from comment #0)

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 Thomas Blume changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |yast2-maintainers@suse.de --- Comment #4 from Thomas Blume --- (In reply to Oliver Neukum from comment #3)

...

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 #6 from Thomas Blume --- (In reply to Bernhard Wiedemann from comment #5)

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 Arvin Schnell changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|aschnell@suse.com |bnc-team-screening@forge.pr | |ovo.novell.com --- Comment #8 from Arvin Schnell --- (In reply to Bernhard Wiedemann from comment #1)

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 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(aschnell@suse.com | |) --- Comment #10 from Dr. Werner Fink --- (In reply to Arvin Schnell from comment #8) IMHO this is not a problem of systemd in the case that /home is part of the local-fs.target (former /etc/init.d/boot.localfs or $local_fs) and there are services do hard depend on local-fs.target. This is more that you get what you have requested. Btw: What is wrong adding 'nofail' to the /home partition? Or do you think that systemd should ignore hard dependencies? -- 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 changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(aschnell@suse.com | |) --- Comment #12 from Dr. Werner Fink --- (In reply to Arvin Schnell from comment #11) And how does this look like in your opinion? -- 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 changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(oneukum@suse.com) | --- Comment #14 from Oliver Neukum --- (In reply to Arvin Schnell from comment #13)

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 Oliver Neukum changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(oneukum@suse.com) | --- Comment #16 from Oliver Neukum --- (In reply to Dr. Werner Fink from comment #15)

(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 Arvin Schnell changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED Resolution|--- |FEATURE Flags|needinfo?(aschnell@suse.com | |) | --- Comment #18 from Arvin Schnell --- Feel free to make a feature request. -- You are receiving this mail because: You are on the CC list for the bug.