Description of problem: booting from 2.6.20-1.2930.fc7 result in kernel panic Actual results: device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: dm-devel Reading all physical volumes. This may take a while... No volume groups found Volume group "VolGroup00" not found Unable to access resume device (/dev/VolGroup00/LogVol01) mount: could not find filesystem '/dev/root' 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! the previous kernel-2925 boots w/o problems Expected results: booting without problems Additional info: grub.conf: default=0 timeout=15 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title Fedora (2.6.20-1.2930.fc7) root (hd0,0) kernel /vmlinuz-2.6.20-1.2930.fc7 ro root=/dev/VolGroup00/LogVol00 rhgb quiet initrd /initrd-2.6.20-1.2930.fc7.img title Fedora (2.6.20-1.2925.fc7) root (hd0,0) kernel /vmlinuz-2.6.20-1.2925.fc7 ro root=/dev/VolGroup00/LogVol00 rhgb quiet initrd /initrd-2.6.20-1.2925.fc7.img
I'm getting this same error after doing a clean install and full update. My configuration looks almost identical to the above except that my root volume is "rootvg" versus "VolGroup00".
Same problem for me with 2.6.20-1.2947. I think problem is related to topic "Live CD FD7T1 won't boot on some machines" discussed on fedora-test-list.
Moving to 'devel' as discussed on https://www.redhat.com/archives/fedora-devel-list/2007-March/msg00095.html.
Martin, do you have a SCSI system? I suspect this is a dupe of bug #220470.
(In reply to comment #4) > Martin, do you have a SCSI system? I suspect this is a dupe of bug #220470. It's a Virtuall Maschine (VMWare-Server) on a SATA System. The Disc is handled like a SCSI-Disc.
Same here.. VMWare-Server image presenting a BusLogic SCSI adapter to the guest VM.
Interesting. Is it possible in that version of VMware to emulate IDE instead and disable all SCSI? (Not as a solution but as a diagnostic test.) In the meantime, I'm going to mark this as a duplicate. *** This bug has been marked as a duplicate of 220470 ***