Bug#748056: systemd: can't boot properly when unable to mount a hibernated NTFS partition

[Michael Biebl]

Am 13.05.2014 22:57, schrieb Nikita Pichugin:
> Package: systemd
> Version: 204-10
> Severity: important
> 
> Dear Maintainer,
> 
> I use a dualboot machine with Debian and Windows 8. I want the windows
> partition to automount on boot, so I added it to the /etc/fstab. The problem is
> that I can't boot into Debian after a shutdown (not reboot!) from Windows: all
> I get is an emergency console. I looked into the journal log and found that
> Debian couldn't mount the windows partition, because Windows was hibernated (it
> turned out that Windows 8 use "hybrid shutdown" by default). If I turn off the
> "hybrid shutdown" in Windows, then everything works as expected.
> I think that unability to mount a partition shouldn't break the boot like that.
> I'd expect a non-critical error or warning or something like that, but
> definitely not an emergency console.

How is systemd supposed to know, if the given partition is vital for the
system to function properly?
Continuing to boot might lead to subtle failures, data loss etc which
can be hard to debug. I personally consider it a bug, that sysvinit
continued to boot in that case.

If the partition is not vital for the system, mark it as nofail [0].

Michael

[0] man fstab
-- 
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://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/attachments/20140513/334da78e/attachment.sig>