Alan McKinnon wrote:
It looks like you have a problem with some reiser-related binary that is not on the / partition. There is obviously nothing wrong with hda3 as ext3 works on it. Which partition hosts the /lib and /sbin directories?
Both are on the same partition too. This goes for everything except for /boot and /home. The rest is all on / (/dev/hda3).
Unfortunately you seem to have been a victim of the off button being hit at exactly the right moment to cause maximum difficulty :-(
I fear this too yes, however after a re-format (`mkreiserfs /dev/hda3`) off the boot-cd and restore of filesystem from a backup this should have been solved. If the backup was damaged, I would have gotten errors during the initial create, the restore, and also from the current ext2 "/" partition ~ but I got no errors at all.
If all else fails you could take the long route: emerge -e system emerge -s world A drastic measure, but it would rebuild everything and almost certainly fix the problem.
I fear not actually, as I think this problem is reiserfs-related, and has to do with a corrupted journal or something, but not sure though. What is the best way to *really* format a drive before recreating a journalled filesystem (reiserfs) so that I really know it's not using an old corrupt one or something? I have other working partitions on that drive so an fdisk is not possible: ~ `cat /dev/zero > /dev/hda3` ? -- Ralph -- gentoo-user@gentoo.org mailing list
