Bug#756103: systemd: boot fails due to fstab entry for /dev/cdrom with 'noauto'
Michael Biebl
biebl at debian.org
Sat Jul 26 16:24:32 BST 2014
Am 26.07.2014 11:28, schrieb Andrei POPESCU:
> Package: systemd
> Version: 208-6
> Severity: important
>
> Hi,
>
> Booting fails if the fstab entry for /dev/cdrom is activated, even
> though it has 'noauto'. I get (written down by hand):
>
> .... A start job is running for dev-cdrom.device
>
> then after a while
>
> [ TIME ] Timed out waiting for device dev-cdrom.device
>
> and then I'm told that I'm in emergency mode, where I can login and fix
> stuff. Unfortunately any key (combination) I tried except Ctrl-Alt-Del
> doesn't do anything (shall I report a separate bug for this?).
>
> If I comment out the fstab entry the system boots fine.
/dev/cdrom /media/cdrom0 udf,iso9660,user,noauto 0 0
Is there no /dev/cdrom device when you boot?
Please enable debug-shell.service so you can inspect the system state
during early boot on tty9.
If the device is actually missing, you should probably use "nofail" in
addition to "noauto".
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 884 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20140726/a7c6422d/attachment-0002.sig>
More information about the Pkg-systemd-maintainers
mailing list