LinuxQuestions.org - [SOLVED] Strange Boot errors

- Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)

- - Strange Boot errors (https://www.linuxquestions.org/questions/linux-newbie-8/strange-boot-errors-4175468513/)

Strange Boot errors

I had a working CentOS 6.4 this morning, installed some software via yum, and now I'm getting this error when I try to boot:

Quote:

RAMDISK: EOF while reading compressed data
uncompression error
VFS: Cannot open root driver "UUID = 3643aeb8-a475-...." or unknown block (0,0)
Please append a correct "root=" boot option; here are the available partitions:
Kernel panic - not syncing: VFS: Unable to mount rootfs on unknown-block (0,0)
Pid: 1, comm: swapper Not tainted 2.6.32-279.el6.x86_64 #1

The machine has multiple boot partitions and I can boot into another and successfully mount the drive with the UUID=643aeb8-a475-.... so that partition seems okay. But somehow grub can't mount from that partition.

More info: the software I installed previous to the problems did modify the boot image: /boot/initramfs-2.6.32-279.el6.i686.img or something like that: it has a new date on the file. Could that file have been screwed? Does anyone know what might be causing this?

Quote:

VFS: Cannot open root driver "UUID = 3643aeb8-a475-...." or unknown block (0,0)

Run the blkid command to see if you actually have a partition with that uuid. Compare it to your grub.conf or grub.cfg file. Not knowing what software you installed or what else happened limits suggestions.

Yes, I ran blkid and the partition with that UUID exists. The software was a proprietary driver for a video capture card, but I don't know if that will help.

I think the problem is that that software modified /boot/initramfs-2.6.32-279.el6.i686.img and somehow corrupted it, but I'm not smart enough to know what that is.

I booted into another OS on this machine, and tried this:

Quote:

> gzip -dc /boot/initramfs-2.6.32-279.el6.i686.img | cpio -i
gzip: /boot/initramfs-2.6.32-279.el6.i686.img: unexpected end of file

so I think this must be where the problem is. If that makes sense, how can I restore /boot/initramfs-2.6.32-279.el6.i686.img?

Figured it out. Mount with Rescue Disk, create a new initramfs with dracut:

Quote:

dracut /boot/initramfs-2.6.32-279.el6.i686.img 2.6.32-279.el6.i686