kubuntu fails to load after grub menu

[Chylee]

I am using Kubuntu 8.10 with kde4

I've Install Kubuntu using the LiveCD but can not get to boot in to the os. When I start the PC, get to the grub menu and select the option to boot. The screen change to kubuntu screen then go's to text mode showing the following:

Starting up ...
Loading, Please Wait...
Gave up waiting for root device. Common problem
 - Boot args (cat /prog/cmdline)
   - Check rootdelay= (did the system wait long enough?)
   - Check root= (did the system wait for right device)
 - Missing module (cat /proc/modules; ls /dev)
ALERT! /dev/disk/by-uuid/3328a24e-ca23-4ce9-88cb-1c90e1588e5b does not exist. Dropping to shell!

BusyBox v1.10.2 (Ubuntu 1:1.10.2-1ubuntu6) built-in shell (ash)
Enter 'help' for a list of built-in commands.

(initramfs)

So I type in the commands and this is what I got

(initramfs) cat /proc/cmdline
root=UUID=3328a24e-ca23-4ce9-88cb-1c90e1588e5b ro quiet splash

(initramfs) cat /proc/modules; ls /dev
[to long to type]

I also check the /dev/disk/id-uuid directory in to see if the uuid was present and it was.

[Fred (lfesc)]

exactly the same problem
and the same check
is this due to a specific hardware configuration (I've got 3HD on my computer) ?
hd0 : / + swap
hd1 : /home
hd2 : /media/stock

[Chylee (chylee-74-gmail)]

I not sure. I believe that the point were it fail to boot, it was looking for the partition were kubuntu is installed and for some reason can not find it. It uses the uuid (Universally Unique Identifier) to identify the partition it need to continue booting. This information is pass form grub. When it can not find the partition I'm dropped into a busybox shell where I check the path of uuid and if the file exists and it does. So am not to sure what is going on there.

[Chylee (chylee-74-gmail)]

I have also posted this at kubuntu forums

http://kubuntuforums.net/forums/index.php?topic=3098319.0

[Fred (lfesc)]

I test a Kubuntu-8.10-RC disk this morning : same situation.
And not a single problem with Kubuntu-8.04.
Is this issue due to KDE-4.1 ?

[Chylee (chylee-74-gmail)]

I've try to install RC version of kubuntu and have the same problem as well.
Not sure if it is kde-4.1. As I recall it is to early in the boot sequence. I thing kde installs after the X server and the live CD works.

[Fred (lfesc)]

well
it seems to be a kernel issue
this problem occurs with kernel 2.6.24-21
everything's OK with kernel 2.6.24-19
(so I change my default option in /boot/grub/menu.lst)

[Chylee (chylee-74-gmail)]

I tried using kernel 2.6.24-19 and it did work, sort of. It loads into kde 4 login screen but I can't us the mouse or keyboard. I can use the Ctrl+Alt+Function key to go into console mode. Where I found out that there was not network. As there is no kernel 2.6.24-19 install into intrepid ibex I got the kernel for my laptop which is running kubuntu hardy.

[Chylee (chylee-74-gmail)]

I thing I found some similar bug reports

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/33269
https://bugs.launchpad.net/bugs/69356
https://bugs.launchpad.net/bugs/201483

[Daniel Arndt (danielarndt)]

Just dropping in to say that I, too, experience this problem. I guess I should try 2.6.24-19 (as a temporary fix).

In initramfs, if I type "exit", the system continues to boot normally and everything works fine. How about you?

Also, everything booted fine the first time Kubuntu loaded, and the third time. Not sure what was special about those time.

Everything worked fine on Ubuntu 8.04

[Chylee (chylee-74-gmail)]

Yes that work for me to.

[Rup.Xamqon (rupxamqon)]

I did a clean install of Kubuntu II (64bit) from the Live CD, on a PC with 2 hard disks. After restart, I experienced the same problem as Chylee and Fred.

I found http://ge.ubuntuforums.com/showthread.php?t=813090, and followed kebes' advice. I run Puppy Linux from CD, and used it to check "/etc/fstab". After backing it up, I changed the UUID listings for mountpoints to my device paths (like "/dev/sda1"). The same thing I did for "/boot/grub/menu.lst", changing UUIDs to "/dev/sda1" or to "(hd0,0)", following the examples given in the same file. I am attaching this file, in case it helps others.

With this changes written to both files, I was able finally to boot into my new Kubuntu II without other problems.

[Fred (lfesc)]

Great
Thanks Rup.Xamqon
it remains a bug for kernel but it works
[now there is a joke in our family : how to start the computer : just type EXIT ;-)]

[arturo (arturozamorafdz)]

I am getting the same error!
I am trying to install Ubuntu on a 2nd hard disk 30gb.
also tried installing ubuntu within a folder on primary disk, no luck
on Rup.Xamqon post, the link to the 'guide' its not working, help! tell me what can i do to fix this bug

i replaced the menu.lst of post above for my D:\ubuntu\install\boot\grub\menu.lst / same error.

Typing 'exit' does not continue

[Rup.Xamqon (rupxamqon)]

Try this link: http://ubuntuforums.org/showthread.php?t=813090
There are some other solutions there, maybe one helps you. Good luck!

[Andre Lohan (payne-aldervista)]

I got this bug on normal Ubuntu 8.10 desktop with a fresh installation on an old machine (pentium 4).

I chrooted into it via livecd and upgraded the system with dist-upgrade. But the problem is still the same.

The setup is this:
2x scsi drives (1 used for Ubuntu Linux other is empty)
1x ide cdrom

I unplugged the empty hard drive but with no effect. I get into busybox and the system continues to boot when i type "exit".

Kernel is 2.6.27-11-generic and i tried a dpkg-reconfigure initramfs but it did not help.

The uuids are all correct in grub and in fstab.

[Daniel Arndt (danielarndt)]

I am still living with this problem as well. I tried changing the grub.lst and fstab as suggested above with no luck. I'm going to have to take another try at it when i have some free time again.

[Kristóf Kiszel (ulysses)]

I got this bug also in Kubuntu Jaunty.

[Fred (lfesc)]

The computer with this problem has got 4 scsi drives.
If I drop into busybox each boot whith hardy, it's just 2 times out of 3 whith jaunty (it stars more quickly)
I never see this bug on the ones whith sata drives.
Is this a scsi problem (boot latency ?) ?

[Kristóf Kiszel (ulysses)]

I have an IDE drive in my laptop, not a SCSI.

[penalvch (penalvch)]

Chylee, thank you for reporting this and helping make Ubuntu better. Intrepid reached EOL on April 30, 2010.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We were wondering if this is still an issue on a supported release? If so, can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command in a supported release from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]