Sign up ×
Ask Ubuntu is a question and answer site for Ubuntu users and developers. It's 100% free.

I asked this question in SuperUser one hour ago, then I know this community so I moved the question here...

I've been running Ubuntu 10.10 in a physical x86-64 machine. Today Update Manager reminded me that there are some updates to install and I confirmed the action. I should had read the update list but I didn't. I can only remember there is an update about cups. After the upgrading, Update Manager requires a restart and I confirmed too. But after the restart, the computer can't start up. There are errors in the console.

Begin: Running /scripts/init-premount ... done. 
Begin: Mounting root file system ... 
Begin: Running /scripts/local-top ... done. 
[xxx]usb 1-8: new high speed USB device using ehci_hcd and address 3 
[xxx]usb 2-1: new full speed USB device using ohci_hcd and address 2 
[xxx]hub 2-1:1.0: USB hub found [xxx]hub 2-1:1.0: 4 ports detected 
[xxx]usb 2-1.1: new low speed USB device using ohci_hcd and address 3 
Gave up waiting for root device. Common probles:
- Boot args (cat /proc/cmdline)
  - Check rootdelay=(did the system wait long enough)
  - Check root= (did the system wait for the right device?)
- Missing modules (cat /proc/modules; ls /dev) 
FATAL: Could not load /lib/modules/2.6.35-22-generic/modules.dep: No such file or directory
FATAL: Could not load /lib/modules/2.6.35-22-generic/modules.dep: No such file or directory 
ALERT! /dev/sda1 does not exist. 
Dropping to a shell! 

BusyBox v1.15.3 (Ubuntu 1:1.15.3-1ubuntu5) built-in shell (ash) 
Enter 'help' for a list of built-in commands. 


At the moment, I can't input anything in the console. The keyboard doesn't work at all. What's wrong? How can I check boot args or "root=" as suggested? How can I fix this issue? Thanks.


PS1: the /dev/sda1 is type ext4 (rw,nosuid,nodev)

PS2: the /dev/sda1 can be mounted and accessed successfully under SUSE 11 SP1 x64.

PS3: From this link, I think the keyboard doesn't work because the USB driver is not loaded at that time.

share|improve this question

closed as too localized by Marco Ceppi Oct 6 '11 at 12:35

This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. For help making this question more broadly applicable, visit the help center.If this question can be reworded to fit the rules in the help center, please edit the question.

Finally I fixed this issue. I boot in SUSE linux, and find in /dev/sda1 there are 2 vmlinuz, one for 2.6.35-22, one for 2.6.35-24. So I add a new entry for 2.6.35-24 in menu.lst manually, then try to boot in 2.6.35-24, it works. –  Landy Jan 10 '11 at 3:12

1 Answer 1

It looks like your kernel was updated... and somehow got killed. Just as your computer is booting you need to press Esc until you get the Grub boot menu which should allow you to select the previous kernel.

Assuming that the older kernel works fine, you should then run the
sudo apt-get install command to make sure it finished with all the jobs it was supposed to do and if it doesn't have anything to fix, remove the broken kernel:

sudo apt-get remove linux-image-2.6.35-22-generic

And restart to confirm the issue is gone.

share|improve this answer
Thanks Martin. But I didn't see previous kernel in Grub boot menu. There is only one line "Ubuntu 10.10 2.6.35-22-gen". And there is no difference in Grub boot menu no matter I press Esc or not. –  Landy Jan 10 '11 at 2:59
That's very bad, now you will need a new kernel... but I wonder what happened to your system to cause this major meltdown. I'm advising for you to reinstall. –  Martin Owens -doctormo- Jan 10 '11 at 4:29
Thanks Martin. At last I mount the disk in a SUSE Linux, then modify the grub to the right kernel image. It works now, although still don't know why this issue happened. :( –  Landy Jan 13 '11 at 1:12
Why did you have to manually manage your grub configuration? grub2 isn't editable in any serious way... did you just run grub-update? –  Martin Owens -doctormo- Jan 13 '11 at 3:39

Not the answer you're looking for? Browse other questions tagged or ask your own question.