Boot hangs with message 'Waiting for root file system'

Bug #59930 reported by Rob Moore
4
Affects Status Importance Assigned to Milestone
linux-source-2.6.17 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: kernel-image-2.6.17-7-generic-di

Starting from Edgy knot 2, I upgraded to the generic kernel on a vmware instance and cannot boot using kernel. In single-user mode, the last message I see on the console is:

Begin: Waiting for root file system... ...

I can still boot using the older non-generic kernel.

Rob Moore (roborative)
description: updated
Revision history for this message
Alex Vaughn (aevaughn) wrote :

Do you have any kind of special configurations for your root file system? It looks as if the kernel is having trouble interacting with the file system. Perhaps adding some files to your report such as /etc/fstab. I only ask this since I am not having any trouble with a laptop, but it's just an IDE hard drive. Also, any information you can gather from the system logs on your computer may be helpful. Thanks.

Revision history for this message
Rob Moore (roborative) wrote :

I've attached the fstab per Alex (thanks for the suggestion). I'd be happy to provide any further logs or such -- please just let me know what would be helpful.

BTW, I'm actually have the same Edgy configuration running in vmware in 2 separate machines and am experiencing the same problem with each.

Revision history for this message
Rob Moore (roborative) wrote :

I experienced this problem again and discovered I'd be dropped into busybox after a wait. I receive this error: ALERT! /dev/sda1 does not exist. Dropping to shell!

If someone could give me some suggestions on commands to run to produce diagnostic info, I'd appreciate it.

Revision history for this message
Ben Collins (ben-collins) wrote : Re: [Bug 59930] Re: Boot hangs with message 'Waiting for root file system'

On Sep 13, 2006, at 7:00 PM, Rob Moore wrote:

> I experienced this problem again and discovered I'd be dropped into
> busybox after a wait. I receive this error: ALERT! /dev/sda1 does not
> exist. Dropping to shell!

Edit the grub entry (from the grub menu on boot) so that it uses /dev/
hda1 instead. This is what I consider an installer bug, because we
changed some sata drives back to ide. However, the grub menu uses
root=/dev/sda1 when it should be using root=UUID=XXX....

When you complete the boot, edit /boot/grub/menu.lst, and remove the
kopt_2_6 line, then rerun "sudo update-grub".

Revision history for this message
Rob Moore (roborative) wrote :

Thanks, Ben. That did the trick.

Revision history for this message
Ben Collins (ben-collins) wrote :

This is really an installer bug, one which I'm sure is already filed.

Changed in linux-source-2.6.17:
status: Unconfirmed → Rejected
Revision history for this message
®om (rom1v) wrote :

Same problem, if in my /etc/hosts, I put my computer name on 127.0.0.1 :

$ cat /etc/hosts
127.0.0.1 localhost rom-laptop
#127.0.1.1 rom-laptop

it resolves the problem.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

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