[Bug 360378] Re: Gave up waiting for root device after upgrade then busybox console

[Rezty Felty]

More info as I continue to work this problem:
I have 6 different kernels on this box, as I never removed any.
The following kernels boot to a maintenance login:
2.6.24-19
2.6.24-24
2.6.24-25
2.6.24-27
They all display this error:
"init readahead main process terminated with status 5
mountall:/proc device or resource busy
root filesystem isn't mounted"
If I give the root password and log in to the maintenance shell, I can see all my files like root is mounted fine.  fstab shows that it is looking for root on /dev/hda1, and I see a block device /dev/hda1.  If I try and mount this block device, I get an "already mounted" error.  The mount command does not display /dev/hda1 mounted.  However, it shows /dev/sdc1 mounted as /, which is funny because /dev shows no sdc1.

2.6.28-18 actually boots to a login prompt.  GUI doesn't come up, but I
can log in, ssh is up, etc.  Currently working in this shell

2.6.31-20 continues to display the original error.
I have tried the pci=nomsi switch, I have tried the acpi=off switch, I have waited 10 minutes at the busybox shell and then typed exit in case it was the timeout error, no resolution yet.  I have tried running update-initramfs -k 2.6.31-20-generic -u, and still see this behavior.  I will continue trying to find a solution myself, yet remain hopeful that I get some good advice here.

-- 
Gave up waiting for root device after upgrade then busybox console
https://bugs.launchpad.net/bugs/360378
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to linux in ubuntu.