Red Hat Bugzilla – Bug 316911
kernel panic vmlinux-18.104.22.168-91.fc7, can not upgrade from 22.214.171.124-73 on restored filesystem
Last modified: 2007-11-30 17:12:17 EST
Description of problem:
Version-Release number of selected component (if applicable):
When attempting to boot from vmlinux-126.96.36.199-91.fc7, the kernel fails to find
root and panics. The machine boots normally from vmlinux-188.8.131.52-76.fc7. The
only thing that makes this a little unique is that I restored this system from
backup. The backed up initrd did not work, so I created a new one by installing
a small Fedora install, and then using the same initrd to point to the regular
My root is on a LVM logical volume on RAID device /dev/md2. I might have
thought this was related to the problem, but it appears to find the logical
volume group, and the same kernel works on my DELL machine with virtually the
mount could not find filesystem '/dev/root'
Setting up other filesystems
Setting up new root fs2
setuproot: moving /dev failed: No such file or directory
no fstab.sys, mounting internal defaults
setuproot: error mounting /proc: No such file or directory
setuproot: error mounting /sys: No such file or directory
Switching to new root and running init
umounting old /dev
umounting old /proc
umounting old /sys
switchroot: mount failed. No such file or directory
Booting has failed.
Kernel panic - not syncing: Attempt to kill init!
Everytime I boot.
Steps to Reproduce:
1. Try rebooting my machine after upgrading from 184.108.40.206-76 to 220.127.116.11-91
Contents of grub.conf:
title Fedora (18.104.22.168-91.fc7)
kernel /vmlinuz-22.214.171.124-91.fc7 ro root=/dev/h6410/Fedora7
title Fedora (126.96.36.199-76.fc7)
kernel /vmlinuz-188.8.131.52-76.fc7 ro root=/dev/h6410/Fedora7
title Windows XP Pro
title Small Fedora (184.108.40.206-76.fc7)
kernel /vmlinuz-220.127.116.11-76.fc7 ro root=/dev/h6410/Fedora7small
Note: In the original system my root filesystem was /dev/sys/Fedora7. When I
restored it from backup, I placed it on raid device /dev/md2 as /dev/h6410/Fedora7.
Can you compare the working and non-working initrds? The below link has some
I compared, and it turns out the problem is /etc/mdadm.conf was missing from the
initrd-18.104.22.168-91.fc7.img file. I copied mdadm.conf from the old initrd to
/etc in my root filesystem, and then rebuild the now initrd. That solved the
So it appears the problem is that the logic for finding the root partition in
the initrd is not correct. Even though /dev/md2 was activated without having
mdm.conf, and the logical volume was found, it could not find the root partition
without access to an mdm.conf file.
Closing as notabug, it's not really posible to reconstruct exactly what happened.
I believe that should be a "WORKSFORME". As it definitely is a bug, but it
works for you, so you can not reproduce it to try and fix the problem.