Red Hat Bugzilla – Bug 199007
Kernel panic when updated from kernel 2.6.16-1.2289_FC6 to kernel 2.6.17-1.2396.fc6
Last modified: 2015-01-04 17:27:54 EST
Description of problem:
had kernel panic when yum-updated from kernel 2.6.16-1.2289_FC6 to kernel
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.boot into kernel 2.6.17-1.2396.fc6
md: created md2
md: runnind: <hda3><hdb3><hdc3>
md: personality for level 5 is not loaded!
md: do_md_run() retuendd -22
md: md2 stopped.
md: ... autorun DONE.
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
ERROR unmounting old /proc/bus/usb: No such file or directory
forcing unmount of /proc/bus/usb
switchroot: mount failed: No such file or directory
Kernel panic - not syncing: Attempted to kill init!
broken initrd ? Peter ?
Dave, you are correct! The problem was on the initrd image.
kernel 2.6.17-1.2336.fc6 gave me the same problem as the 2396 one, but kernel
2.6.16-1.2289-FC6 worked, so I decided to look for the raid5 personality modules.
Guess what? The name of the modules changed after kernel 2.6.16-1.2289! In that
kernel, each personality has its own module and in the subsequent kernels,
personalities 4, 5 and 6 are bundled up in one module.
mkinitrd --with=raid456 <image file> 2.6.17-1.2396.fc6
and changing the grub.conf file fixed the problem, but now smartd, acpi and some
other services don't start correctly and fail to stop.
forgot to mention my hd config:
md0 100mb raid1 comprised of hda1, hdb1 with hdc1 as hotspare
md1 3gb raid0 comprised of hda2, hdb2, hdc2
md2 500gb raid5 comprised of hda3, hdb3, hdc3
I'm reviewing this bug as part of the kernel bug triage project, an attempt to
isolate current bugs in the Fedora kernel.
I am CC'ing myself to this bug, however this version of Fedora is no longer
Please attempt to reproduce this bug with a current version of Fedora (presently
Fedora 8). If the bug no longer exists, please close the bug or I'll do so in a
few days if there is no further information lodged.
Thanks for using Fedora!