I've seen three different people mentioning the problem, but could not find a bug report, so I thought I'd make one... My problem: Did a "fisher" install. / is a RAID1 partition (lots of RAID partitions actually... ) With the fisher kernel, boots fine. Updated kernel to wolverine kernel. Boot fails, "isofs_read_super: bread failed" and "Kernel panic: VFS: Unable to mount root fs on 06:01". I'm not at the computer right now, so I'm not sure of the numbers in the unable to mount message. The old kernel spews out lots and lots of debugging messages when the raid modules load and autodetect the raid arrays. The new kernel spits out nothing and does not appear to find my raid arrays. Bug 29731 references this problem, as do a couple of posts in the wolverine mailing list. System is a KT133A-based AMD T-Bird. (Asus KT133K7V or somesuch). 3 hard drives, two on the promise controller, one of the via controller. / is split over the via (hda) and the promise (hde).
$ df / Filesystem 1k-blocks Used Available Use% Mounted on /dev/md6 198313 82520 105544 44% / $ uname -a Linux hawke.oppositelock.org 2.4.1-0.1.14 #1 Thu Feb 22 23:36:02 EST 2001 i686 unknown Kernel RPM from rawhide.