On Sat, 2006-10-07 at 16:02 +0000, Daniel Werner wrote:
> > The weird thing is that / (/dev/hda5) shouldn't be being checked at all at
> > this point
> The root filesystem is first checked by /etc/init.d/checkroot.sh, but is
> checked again by checkfs.sh together with all other filesystems.
The line that does the fs check in checkfs.sh is like this:
log_action_begin_msg "Checking all filesystems"
fsck $spinner -T -R -A $fix $force
man fsck includes this:
-R When checking all file systems with the -A flag, skip the
root
file system (in case it’s already mounted read-write).
In other words, according to the script, the root fs should not be being
checked at this point. This suggests to me that there could be a bug in
fsck which is causing it to check the root FS when it shouldn't.
> Interestingly, during the aftermath of a power failure, I've come to
> encounter this very same message on a number of machines at work in the
> past weeks. fsck would not only complain about the root inode, but also
> about even graver inconsistencies. The ext2 filesystems were essentially
> wrecked, with no journal to recover from (*sigh*).
>
> The simplest solution to your problem is probably to boot from live CD,
> backup your root filesystem (e.g. `tar --create --one-file-system / -f
> /somewhere/else/root-backup.tar`), create a new ext3fs on hda5, then
> restore your backup. This won't tell you or me what went wrong in the
> first place, but at least it should give you a working system.
The thing is, I've actually been running that machine for over 6 months
with no other problems - all I have to do is press ctrl-D to exit the
root shell, and it boots up and runs fine. I've installed various
programs since having this problem, which I would have thought would
have caused a problem if there was really something wrong with the FS.
When I check the filesystem from a live CD, it comes up clean, as I
reported in my last email. This makes me think that there isn't actually
anything wrong with the filesystem, and the error is due to a bug in
fsck which is causing it to check the root fs when it's mounted
read-write.
> PS: You're not, by chance, having this problem using a Pyramid server,
> are you? ;)
No, it's a mostly second hand system with an AMD chip and an Elite K75SA
motherboard. I've now moved all my files onto a laptop, which I'm using
day to day, but if you need any more info to track down this bug, I can
provide it.
--
filesystem check fails on boot, but filesystem isn't bad
https://launchpad.net/bugs/48563
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
