[Kernel issue] broken upgrade to 2.6.35-22 kernel

Asked by aleeming

New upgrade to Ubuntu 1.10 on AMD Athlon 64 3000+ Carrera Desktop. Ater required re-boot, machine frozen with message:-
"Gave up waiting for root device. Common Problems:
-Boot args (cat/proc/cmline)
-check rootdelay = (did system wait long enough?)
-check root = (did system wait for right device?)
-Missing modules (cats/proc/modules; ls/dev)

ALERT! /dev/disk/by -uud/)d5c0872 ... etc....does not exist.
Dropping to shell
..............

I can still boot to the kernel 2.6.32-25(x86_64) via 'grub' , and the rest of the upgrade is installed & working.

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu grub2 Edit question
Assignee:
No assignee Edit question
Solved by:
aleeming
Solved:
Last query:
Last reply:
Revision history for this message
delance (olivier-delance) said :
#1

Looks strange! Could you check UUID for both kernel version is same.

Revision history for this message
A. Denton (aquina) said :
#2

Maybe this will help you out...

TRON-DELTA.ORG (KB #A-30): Desaster recovery due to major drive changes regarding GRUB. The following commands can be issued to recover the system (make volumes available again) using the gub shell.

One-Time:
1] "ls -a /dev/disk/by-uuid" / "ls -slap /dev/disk/by-uuid"
2] Write down / copy the output of the command given above.
3] Then reebot and enter GRUB (ESCAPE), issue 'p' and edit.
4] Modify GRUB ("sudo nano /boot/grub/menu.lst") with UUID.

Permanent:
5] Modify fstab ("sudo nano /etc/fstab") with appr. values.
6] Issue "sudo update-grub" to enable all the changes made.
7] Issue tune2fs with switches -C1, -c<INTd> and -i<INTd>.

Good luck! ;-)

Revision history for this message
A. Denton (aquina) said :
#3

Sorry, but No. 4] belongs to the "Permanent:" section.

Revision history for this message
delance (olivier-delance) said :
#4

This solution is outdated and apply to Grub Legacy, which is replaced by Grub2 since 9.10.
The simplest is to reinstall grub:
     https://help.ubuntu.com/community/Grub2#Reinstalling%20from%20LiveCD
The problem is, usually, when you have a UUID error, you have it fro both kernels.
It's why I asked you to check UUID for both kernels, because there could be a unusual issue behind this one visible.

Revision history for this message
aleeming (aleeming) said :
#5

Reply to 'delance': When I booted 2.6.35-22 kernel the original message says "ALERT! /dev/disk/by -uuid 0d5c0872-6d76-4248-bf07-3828a84ab34a does not exist" . When I booted 2.6.32-25 and 2.6.31-21 their uuid shown in /boot/grub/menu.lst was 0d5c08772-6d76-4248-bf07-3828ab34a.; ie all quoted uuid are the same.
I have not yet tried to reinstall grub.

Revision history for this message
A. Denton (aquina) said :
#6

delance, I'm indeed using GRUB but GRUB2 has a shell to and one can assign UUIDs. I aslo think the UUIDs are correct but not updated in GRUB. So a reinstallaton of GRUB *could* help.

Revision history for this message
aleeming (aleeming) said :
#7

As always I thank you all for your advice. I have re-installed grub2 & grub-pc,activated chainload, upgraded-from-grub-legacy,etc, but on loading kernel 2.6.35-22, I have still got the original message: "Gave up waiting for root device .........etc. I can still boot from 2.6.32-25.
It is getting frustrating!!

Revision history for this message
aleeming (aleeming) said :
#8

I have tried re-installing the kernel 2.6.35-22, along with the relevant headers, but there is still no joy. I have also hit the 'e', edit key in the grub menu, to view the uuid,kernel & initid of 2.6.35-22:-
uuid 0d50872-6d76-4248-bf07-3828a8434a, which is as it should be
kernel /boot/vmlinux - 2.6.35-22 generic root = uuid=0d50872.....etc
initid /boot/initrd.img - 2.6.35 generic

I can find no obvious fault, except it will not boot to this kernel. Very frustrating

Revision history for this message
delance (olivier-delance) said :
#9

It looks like a kernel issue.
Did 2.6.35-22 kernel ever worked ?
You could raise a bug against 2.6.35-22 kernel.

Revision history for this message
aleeming (aleeming) said :
#10

I have now installed the new kernel 2.6.35-23, and deleted the troublesome 2.6.35-22. I am glad to tell you all that everything now works perfectly