CRC error, not able to boot from md0 (raid)

[Peter de Kraker]

I updated yesterday to the latest version of 2.6.15-26-server: 2.6.15-26.47 .
When I rebooted today the system didn't boot, but gave a kernel panic:

[quote]
RAMDISK: Compressed image found at block 0
crc error
VFS: cannot open root device "md0" or unknown-block(0,0)
Please append a correct "root=" boot option
kernel panic - not syncing: VFS: unable to mount root fs on unknown-block(0,0)
[/quote]

root=/dev/md0

With the other kernel on my system:2-6-15-23 and the same parameters for root etc. The system does boot. So it is not a problem with the syntax in the grub menu entry.

It looks like the system can't find the raid md0 drive, possibly doesn't initialize raid properly?

This is quite severe, since the only thing I did was sudo apt-get update && sudo apt-get dist-upgrade...
Fortunately I am running a non-production server, but these things may NEVER occur on a server distro.

I reported the bug (60893) and Ben Collins commented:
==
" Looks to me like the initramfs wasn't created correctly. Please boot from an older kernel, and run:

sudo update-initramfs -u -k 2.6.15-26-server

Make sure this runs without error. Note the message you see in dmesg confirms that the initramfs is not valid. If this appears to be a bug in the creation of this (e.g. not just a failure on the system like running out of disk space), open a target for this bug against initramfs-tools."
==

The command didn't gave me any errors. I also tried it with the -27 kernel, also no errors with update-initramfs but the same error when booting.

FYI: I am booting directly from raid, there is no seperate /boot ext3 partition.

[Peter de Kraker (peterdekraker)]

It looks like there are more users experiencing the same problem:
See http://ubuntuforums.org/showthread.php?t=259245

[Fabio Massimo Di Nitto (fabbione)]

I don't think booting from raid makes any difference here. The crc error comes from the kernel that can't unpack the initramfs and as a consequence the modules required to access the raid are not loaded.

[Adam Conrad (adconrad)]

Err, booting directly from the RAID using lilo or grub? If you're using lilo, it's known that after regenerating an initramfs, you may have to re-run lilo by hand.

[Peter de Kraker (peterdekraker)]

Details system:

Using GRUB
excerpts of menu.lst (1st one doesn't boot, second one does)
==
title Ubuntu, kernel 2.6.15-26-server
root (hd0,0)
kernel /boot/vmlinuz-2.6.15-26-server root=/dev/md0 ro quiet splash
initrd /boot/initrd.img-2.6.15-26-server
savedefault
boot
[..]
title Ubuntu, kernel 2.6.15-23-server
root (hd0,0)
kernel /boot/vmlinuz-2.6.15-23-server root=/dev/md0 ro quiet splash
initrd /boot/initrd.img-2.6.15-23-server
savedefault
boot
===

Fstab:
==
/dev/md0 / reiserfs notail 0 1
/dev/md1 /home reiserfs defaults 0 2
/dev/md2 none swap sw 0 0
/dev/hdd /media/cdrom0 udf,iso9660 user,noauto 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto 0 0
===

Diskspace:
/dev/md0 19G 728M 18G 4% /
varrun 506M 72K 506M 1% /var/run
varlock 506M 4.0K 506M 1% /var/lock
udev 506M 72K 506M 1% /dev
devshm 506M 0 506M 0% /dev/shm
/dev/md1 18G 4.8G 13G 27% /home

mem: 1 GB (2x512)

[divali (famillyelees)]

This is the message I get when I try to boot.
The problem started after I downloaded some new updates, including a new kernel. So I have to pick an earlier kernel and then the machine boots up ok.

RAMDISK: Compressed image found at block 0
crc error
VFS: cannot open root device "md0" or unknown-block(0,0)
Please append a correct "root=" boot option
kernel panic - not syncing: VFS: unable to mount root fs on unknown-block(0,0)

Using GRUB.

[Paul Dufresne (paulduf)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

[Pedro Villavicencio (pedro)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!.