Ubuntu
initramfs-tools package

Upgrading to udev 124-9 from new 8.10 installation causes crc error

Bug #333313 reported by sabby
4
Affects Status Importance Assigned to Milestone
initramfs-tools (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: udev

From a brand new install of Kubuntu 8.10, upgrading the single package udev to 124-9 causes the following kernel panic

2.24 RAMDISK: Compressed image found at 0
2.47 crc error
2.49 VFS: Cannot open root device "UUID=<uuid here>" or unknown block (0,0)
2.49 Please append a correct "root=" boot option; here are the available partitions:
2.49 Kernel panic - not syncing: VFS: Unable to mount root fs on unknown wm-block(0,0)

Downgrading back to 124-8 doesn't fix the problem, as well as copying the original version of /boot back into /boot. In addition, chaning to root=/dev/sda1 doesn't work either.

Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

This sounds like you have no initramfs

Revision history for this message
Chris Coulson (chrisccoulson) wrote :

Do you have an older kernel you can boot with (which might still have a good initramfs)?

Changed in initramfs-tools:
status: New → Incomplete
Revision history for this message
sabby (sabby) wrote :

Sorry no older kernel since it's a brand new install, would it be possible to take something off the live cd or download it off the web? Could someone tell me the step required?

Revision history for this message
sabby (sabby) wrote :

Just to add this is reproducible. I tested it 3 times, each time from brand new install with the same result.

Revision history for this message
sabby (sabby) wrote :

After more diagnosis, I found out that this was due to my system being unstable. It did pass 6hr mprime + 6hr memtest but there must be something that initramfs does that is more sensitive then that. Sorry to have wasted people's time. For info after making the system stable for 24hr run instead of 6hr everything went fine, needed to up MCH voltage a 0.1V. However, still curious to isolate a minimal case so as to perhaps submit it for inclusion as a stability test in phoronix. I usually have experience with random problem caused by instability but the fact that it always happened when updating udev threw me off the track. Someone can close this bug since it doesn't seem that I can do it. Thanks.

Revision history for this message
Chris Coulson (chrisccoulson) wrote :

Thanks sabby

Changed in initramfs-tools:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.