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

[Michael Biebl]

Am 03.07.2014 20:57, schrieb Michal Suchanek:
> Package: systemd
> Version: 204-14
> Followup-For: Bug #748056
> 
> Hello,
> 
> since this is a 'feature' I expect this is still present.
> 
> I encountered this problem when one of my drive cables went loose and
> the drive became inaccessible.
> 
> The drive was ad-hoc connected while placed physically outside of the
> computer case so this situation is forseeable but non-fatal with
> sysvinit. With systemd this renders the system non-bootable. There is no
> way to boot the system other than reconnecting the drive.

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

I do admit though, that this doesn't help for headless servers where you
only have an SSH login.

> Also candidate for big fat release note.

Nod. I guess the recommendation here is to simply mark non-critical
mounts as nofail.

We could try to make systemd smarter and determine which file systems
are vital for a successful boot and which are not. But I fear this will
be hard to get right for all corner cases.

So maybe just documenting the fact that this needs to be done by the
administrator is the best way.


Michael



-- 
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/20140703/9e5f2f7c/attachment-0002.sig>