Jason Montleon wrote:
Good Afternoon,
I installed kernel-smp-2.6.18-1.2200 today and rebooted my computer. I
got a kernel panic pretty fast in the boot process. I have 3 drives in
my system. md0 is a RAID 1 /boot partition formatted ext3 of appr. 1GB
on hda and hdc. I have a 1GB swap partition on hdc. The remainder of
the space on all three drives is dedicated to md1 a RAID 5 partition
formatted ext3 of appr. 450GB. hdb is a DVD-ROM/CD-RW.
The system boots normally with kernel-smp-2.6.17-1.2187
The error message booting with kernel-smp-2.6.18-1.2200 is (and this is
typed by hand since it was the quickest manner I had to capture the
data; tried to be absolutely accurate as possible, however there may be
a slight error or two...):
Booting 'Fedora Core (2.6.18-1.2200.fc5smp)
root (hd0,0)
Filesystem type is ext2fs, partition type 0xfd
kernel /vmlinuz-2.6.18-1.18.200.fc5smp ro root=/dev/md1 rhgb quiet
[Linux-bzImage, setup=0x1e00, size=0x1b5ff2]
initrd /initrd-2.6.18-1.2200.fc5smp.img
[2Linux-initrd @ 0x37eea000, 0x105ceb bytes]
Uncompressing Linux... Ok, booting the kernel.
Red Hat nash version 5.0.32 starting
EXT3-fs: unable to read superblock
mount: error mounting /dev/root on /sysroot as ext3: Invalid argument
setuproot: moving /dev failed: No such file or directory
setuproot: error mounting /proc: No such file or directory
setuproot: error mounting /sys: No such file or directory
switchroot: mount failed: No such file or directory
Kernel panic - not syncing: Attempted to kill init!
And that's all she wrote. Any ideas?
Respectfully,
Jason
This is Bz 202596 again.
If root is on a raid 5 device, or you need raid 5 during boot, need to
run mkinitrd --with=raid456 after booting an older FC5 kernel. Module
raid5 is now raid456.
--
Regards,
Old Fart
(my reply-to address is "munged" to defeat spambots)
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
