Public bug reported:
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.
** Affects: initramfs-tools (Ubuntu)
Importance: Untriaged
Status: Unconfirmed
--
CRC error, not able to boot from md0 (raid)
https://launchpad.net/bugs/61382
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
