John DeDourek wrote: > Just did a rather massive yum update of an FC5 system. The update > include updating > kernel from .... to 2.6.20-1.2312.fc5 > > System is an IBM Thinkpad T42 > > The system will not boot the new kernel. Skipping the first lines (grub > stuff) the screen > shows: > Uncompressing Linux... Ok, booting the kernel. > Red Hat nash version 5.0.32 starting > Unable to access resume device (/dev/VolGroup00/LogVol01) > mount: could not find filesystem '/dev/root' > > followed by the expected messages such as "moving /dev failed" > > It almost looks like the boot things that it is coming out of "suspend" > rather than > booting the kernel, unless the wording of that message is bogus about > "unable to access resume device". Any ideas anyone? > The "unable to access resume device" is the kernel trying to see if it is a fresh boot, or a resume after hibernation. From the prospective of GRUB, they are the same. The kernel then checks the swap space for a hibernation signature, to help it decide weather to do a fresh boot, or a resume. This looks more like you have a bad Initial RAM disk. The kernel is not able to access the Logical Volumes for some reason. Mikkel -- Do not meddle in the affairs of dragons, for thou art crunchy and taste good with Ketchup!
