> 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.
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. PS: You're not, by chance, having this problem using a Pyramid server, are you? ;) -- filesystem check fails on boot, but filesystem isn't bad https://launchpad.net/bugs/48563 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
