Bug#754340: Unable to run fsck manually when instructed to do so

[Michael Biebl]

Am 10.07.2014 05:03, schrieb Bas Wijnen:

> My suggested solution is to document the method for remounting the root
> filesystem read-only (or the method for getting help on the commands that do
> such things) in the error message that says fsck must be run manually, or
> perhaps whenever a shell is spawned so early during boot.  This is essential to
> be able to rescue the system, and since it's changed compared to how it worked
> for decades, you can't assume that everyone knows how to do it.

Could you elaborate what you mean by that? What has changed with systemd
in that regard?
It's not like the situation is really different with sysvinit: If fsck
fails to repair a file system automatically, you'll have to do it manually.

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/20140710/ff9ca9b1/attachment-0002.sig>