https://bugzilla.novell.com/show_bug.cgi?id=810293
https://bugzilla.novell.com/show_bug.cgi?id=810293#c19
--- Comment #19 from Jianye Shi
I added the nofail option as you told me to and I can confirm that the machine boots now. The dm-1 entry is just mounted later in the boot process, after the multipath service has been started.
Perhaps you should add that information somewhere in the wikis or in some other place, where users usually look for help. Or is this just a workaround and there may be a fix for systemd to see that dm-1 depends on multipathd.service?
Well, I don't know the relation among nofail, systemd and multipathd.service but I think the parameter nofail is something essential. It solved the following problems: 1. landed in the emergency mode during/after installation (my own experience); 2. Network Manager not working (KDE desktop, my own experience); 3. Encrypted home partition (someone's experience, somewhere in Bugzilla). It's worth pointing out in the 2nd case as I put nofail to the fstab and saved the file and found that the status of NM from "(not connected)" to configured ("not connected" disappeared) even without rebooting. I suppose if someone updates, upgrades a system or cleanly installs a system but wants to keep his home partition untouched he might have encountered problems like above mentioned or even more. Generally speaking if one wants to keep his home partition untouched and found problems during or after installation, the suggestion to put nofail in fstab could be a help. It should be a workaround. Deep relation is still needed to dig out. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.