Bug#748056: systemd and devices from /etc/fstab missing

Gert Wollny gw.fossdev at gmail.com
Fri Jul 25 22:02:59 BST 2014


Today I hit the same problem (after the dist-upgrade introduced
systemd). I also had a device listed in /etc/fstab that is not always
available and I forgot to add the "noauto" option.

> Well, the system does boot, but it drops you into the emergency shell
> where you can inspect the problem.

At least for me it didn't, neither in normal boot nor in single-user boot. 
Maybe I didn't wait long enough, but if a device is simple not there, it
shouldn't take more than 20 seconds or so (IMHO) to figure out that
there is something wrong.

The only key combination that worked was Ctrl-Alt-Del, so I could at
least do a clean reboot.  I could only resolve the issue by rebooting
into another linux installation I happen to have in the very computer. 

I would guess that this is also related to #746358, i.e. what happens if
a network share is not available (e.g. because the corresponding server
is down)?

Anyway, I think dropping the user into an emergency shell is rather
harsh, a selection "retry, ignore, drop into emergency shell" would be
better.  

best regards, 
Gert 



More information about the Pkg-systemd-maintainers mailing list