On Thu, 13 Oct 2005, Tim Green wrote:
On 12-Oct-05 Dan Hatton wrote:
Lately (last week or so,) when I boot my machine (Debian Testing,) after either a poweroff (via shutdown -h) or reboot (via shutdown -r,) it consistently complains that the root filesystem was not cleanly unmounted, and insists on fscking that filesystem. After the reboot forced by fsck, the machine starts up just fine.
Another strategy is to re-mount root as read-only before the end.
Ah, yes; this is what my system was trying to do, but unfortunately never got round to it, because the relevant script (S60umountroot) came after K99reboot or K99halt (neither of which unmounts anything) in the run_parts sequence; S60umountroot also has all its action in its "stop" subroutine, which presumably means that, whatever the run order, it wouldn't have worked while it was named with an "S." Renaming the symlink from "S60umountroot" to "K98umountroot" got things working right again.