I have a weird problem, and I need some help. SuSE 8.2 distribution 2.4.20-4GB-athlon kernel from SuSE installation disk /boot partition is ext2, others are reiserfs 3.6 format.
After a power failure last week my system now panics while booting. It complains that it cannot open root device "hda3" on 03:03. This is a SuSE 8.2 system that was installed about a year ago. It had rebooted only two days previously. I am confident that this kernel has reiserfs support, but just to be sure, I re-installed the stock kernel off of the SuSE 8.2 distribution disks and got the same result. Here's where it gets weird: I booted the Rescue system on the installation CD, and from there I ran reiserfsck, which reported no inconsistecies. I can mount /dev/hda3 and look around; everything seems to be there. But when I try to boot a system that wants hda3 as its root, I get a kernel panic. What would cause mount to choke on a reiserfs root partition which gets a clean fsck and is mountable from the Rescue system? What could be wrong that fsck doesn't see and fix? Any insights or suggestions would be most welcome. -- John Wilkes john at wilkes dot com
