Hardy kernel panic after upgrade
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Linux |
Invalid
|
Unknown
|
|||
gforge (Ubuntu) |
Triaged
|
High
|
Unassigned | ||
memtest86+ (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
I've got a problem with the new kernel. After upgrade Gutsy->Hardy which went fine reboot welcomes me with Kernel panic - not syncing: VFS: unable to mount root on unknown-block(0,0). Trying to boot Gutsy kernel ends in BusyBox. Quick look around in it showed no hard drive devices (sda/sdb/hdc/hdd in /dev). I did boot with System Rescue CD, mounted /boot and rolled back initrd to the one generated during gutsy install for 2.6.22. I successfully booted Gutsy kernel then. update-initramfs successfully actualized initrd for 2.6.22 so there has to be some problem with the kernel. I've tried to reinstall it, install 2.6.22-16-386, server and pci=nomsi option with kernel panic everytime. Ubuntu Live CD recognizes all drives correctly, but overwriting 2.6.24 kernel with the one from Live CD doesn't help. Recompilation of Hardy kernel doesnt either. This bug is also valid for vanilla 2.6.24.3 and 2.6.25 kernels. I've got lvm on software raid, but that shouldn't matter here. System installed on sata drives, and besides those two, I've got one hdd and dvd-rw on pata. Chipset is nforce2, sata controller PDC20376.
description: | updated |
description: | updated |
Changed in linux: | |
status: | Unknown → Confirmed |
Changed in linux: | |
status: | Confirmed → Invalid |
I had the same problem : sata disk on nforce2, gutsy->hardy then unable to mount root at boot.
The problem was in menu.lst: the initrd line was missing for the new kernel.
Previous kernel (from gutsy) had a valid initrd line and was working fine, but hardy kernel didn't have any initrd line.
I simply ran update-grub and the kernel booted. The only diff is the initrd line.