Am 28.09.2014 um 03:31 schrieb Jean-Philippe MENGUAL: > Dear Maintainer, > > To precise my bug, now that it's reproduced on my testing, I identify 2 > issues: > 1. If some device is mentioned in fstab and not connected, the system doesn't > start and falls in emergency. Here, I created /dev/sdc2 in fstab, > disconnected, > it refused to start, while /dev/sdc2 doesn't contain major things (not home, > not root, etc.). I consider it's a bug or something is a problem for me. > Because how is mounted every device quickly?
If /dev/sdc2 is not vital to boot your system, you should mark it as "nofail" in /etc/fstab. > 2. The bug itself: I was unable to understand why my system falled in > emergency. > Nothing in the journal, or at least nothing which is relevant. Unable to > detect > the origin of the problem, except my imagination. v215 will automatically switch to verbose mode when it a unit triggers a timeout or fails to start. See the attached screenshot. In timeout1.png, systemd is waiting for the device to show up. In timeout2.png you see that it reached the timeout and then drops you into emergency shell (timeout3.png). Does that address your issues? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
