I should have cooled down first from my frustration. Sorry for the inappropriate bugzilla comment. All Linux systems have these kinds of problems, which is why we have these bug tracking systems.
The above "touch /forcefsck" wouldn't have worked because the filesystem was read-only. In the duplicate bug attached to this one, someone tried: #mount -o remount,rw / # fsck / I tried "mount / -o remount -o rw" but I kept getting "filesystem already mounted." It was probably because I was specifying -o twice instead of once with a coma between args, maybe? I don't think this would be an issue if you ran XFS either because its fsck.xfs doesn't do anything (if you look at the source, it exits 0 right after main) and the journal playback is done on mount. I agree with the other comments that fsck shouldn't be skipped on boot; that AC vs battery shouldn't play a role in that decision. I didn't notice that it had been changed from 'wont-fix' back to 'confirmed.' Commenting out those lines in the check startup scripts fixed the problem on my laptop. -- fsck not run on boot if on battery power https://bugs.launchpad.net/bugs/219382 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
