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

[Bas Wijnen]

On Thu, Jul 10, 2014 at 06:40:47PM +0200, Michael Biebl wrote:
> 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.

When fsck failed with this message before, I could do:
mount / -o remount,ro
fsck /

Now, and I'm guessing this is a change on the part of systemd, that
first command (remount read-only) fails with the message that the file
system is busy.  Having no bootable computer and thus no internet, I was
unable to figure out what was keeping it busy, and how I was supposed to
stop it.  This is the information that I think should be part of the
"please run fsck manually"-message, because that won't work without it.

Thanks,
Bas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20140712/41f88370/attachment-0002.sig>