On 2008-11-05, Sean Keesler wrote:
> I am having issues booting my Ubuntu 8.04 box after an upgrade. It has
> been a while since I had this problem so I am not sure my memory is
> clear on how I even got here!
>
> When I boot my machine, I get watch grub
>
> Searching for Boot Record from IDE-0 OK
> GRUB Loading stage 1.5
>
> Here the system just sits for about 30 seconds and then finally says:
>
> GRUB loading, please wait
>
> I can enter the GRUB menu and see that I have the following entry:
>
> root (hd0,7)
> kernel /vmlinuz-2.6.24-21-generic
> root=UUID=ee13039d-8f86-4d78-86f2-586c1b91d875 ro
> initrd /initrd.img-2.6.24-21-generic
>
> When I boot this kernel I see:
>
> a bunch fly by:
>
> ata1:SRST failed (errno=-16)
> ata2.00: ATAPI: FX54++W, U016, max UDMA/33
> ata2.00: configured for UDMA/33
> scsi 1:0:0:0: CDROM MITSUMI CD_ROM FX43++W U01G PQ: 0 ANSI: 5
> Driver 'sr' needs updating - please use bus_type methods
> sr0: scsi3-mmc drive: 54x/54x cd/rw xa/form2 cdda tray
> Uniform CD-ROM driver Revision: 3.20
> sr 1:0:0:0: Attached scsi generic sg0 type 5
>
> and then is just hangs for a while (minutes?)
> and then:
>
> Done.
> Check root= bootarg cat /proc/cmdline
> or missing modules, devices: cat /proc/modules ls /dev
>
> ALERT! /dev/disk/by-uuid/ee13039d-8f86-4d78-86f2-586c1b91d875 does
> not exist Dropping to a shell!
>
> and then I get the BusyBox shell, from which I can do very little.
>
> I can boot from a CD and mount all of the partitions and from the
> contents I know that:
>
> /dev/sda5 is /
> /dev/sda6 is swap
> /dev/sda7 is /home
> /dev/sda8 is /boot
>
> From the script at:
> http://ubuntuforums.org/archive/index.php/t-593796.html
> I see that the UUID for sda8 is ee13039d-8f86-4d78-86f2-586c1b91d875
>
> Can anyone give me a clue why the kernel isn't loading?

It's pretty clear that your /boot partition isn't mounting. Since it
appears that grub is also having a hard time reading it, there may be
a problem. Have you tried running fsck on the /dev/sda8 partition?


--
Joe - Linux User #449481/Ubuntu User #19733
joe at hits - buffalo dot com
"Hate is baggage, life is too short to go around pissed off all the
time..." - Danny, American History X

Joe wrote:
> On 2008-11-05, Sean Keesler wrote:
>> I am having issues booting my Ubuntu 8.04 box after an upgrade. It has
>> been a while since I had this problem so I am not sure my memory is
>> clear on how I even got here!
>>
>> When I boot my machine, I get watch grub
>>
>> Searching for Boot Record from IDE-0 OK
>> GRUB Loading stage 1.5
>>
>> Here the system just sits for about 30 seconds and then finally says:
>>
>> GRUB loading, please wait
>>
>> I can enter the GRUB menu and see that I have the following entry:
>>
>> root (hd0,7)
>> kernel /vmlinuz-2.6.24-21-generic
>> root=UUID=ee13039d-8f86-4d78-86f2-586c1b91d875 ro
>> initrd /initrd.img-2.6.24-21-generic
>>
>> When I boot this kernel I see:
>>
>> a bunch fly by:
>>
>> ata1:SRST failed (errno=-16)
>> ata2.00: ATAPI: FX54++W, U016, max UDMA/33
>> ata2.00: configured for UDMA/33
>> scsi 1:0:0:0: CDROM MITSUMI CD_ROM FX43++W U01G PQ: 0 ANSI: 5
>> Driver 'sr' needs updating - please use bus_type methods
>> sr0: scsi3-mmc drive: 54x/54x cd/rw xa/form2 cdda tray
>> Uniform CD-ROM driver Revision: 3.20
>> sr 1:0:0:0: Attached scsi generic sg0 type 5
>>
>> and then is just hangs for a while (minutes?)
>> and then:
>>
>> Done.
>> Check root= bootarg cat /proc/cmdline
>> or missing modules, devices: cat /proc/modules ls /dev
>>
>> ALERT! /dev/disk/by-uuid/ee13039d-8f86-4d78-86f2-586c1b91d875 does
>> not exist Dropping to a shell!
>>
>> and then I get the BusyBox shell, from which I can do very little.
>>
>> I can boot from a CD and mount all of the partitions and from the
>> contents I know that:
>>
>> /dev/sda5 is /
>> /dev/sda6 is swap
>> /dev/sda7 is /home
>> /dev/sda8 is /boot
>>
>> From the script at:
>> http://ubuntuforums.org/archive/index.php/t-593796.html
>> I see that the UUID for sda8 is ee13039d-8f86-4d78-86f2-586c1b91d875
>>
>> Can anyone give me a clue why the kernel isn't loading?
>
> It's pretty clear that your /boot partition isn't mounting. Since it
> appears that grub is also having a hard time reading it, there may be
> a problem. Have you tried running fsck on the /dev/sda8 partition?
>
>

Thanks, Joe.

The file system mounts fine from the command line (mount -t ext3
/dev/sda8 /mnt/disk8) when I boot from a cd. fsck reports the file
system clean.

Since the kernel and the grub menu is on sda8, and the kernel starts and
gives me all of those messages I reported, I don't really get what is
happening here.

Sean

Sean Keesler wrote:
> Joe wrote:
>> On 2008-11-05, Sean Keesler wrote:
>> The file system mounts fine from the command line (mount -t ext3
> /dev/sda8 /mnt/disk8) when I boot from a cd. fsck reports the file
> system clean.
>
> Since the kernel and the grub menu is on sda8, and the kernel starts and
> gives me all of those messages I reported, I don't really get what is
> happening here.

IMHO, you should be concentrating on the error message you are receiving:

Check root= bootarg cat /proc/cmdline
>>> or missing modules, devices: cat /proc/modules ls /dev

I did a quick Google check on this error message and it would appear
that it can be generated from driver resolution problems, failing
hardware etc.

propman wrote:
> Sean Keesler wrote:
>> Joe wrote:
>>> On 2008-11-05, Sean Keesler wrote:
>>> The file system mounts fine from the command line (mount -t ext3
>> /dev/sda8 /mnt/disk8) when I boot from a cd. fsck reports the file
>> system clean.
>>
>> Since the kernel and the grub menu is on sda8, and the kernel starts
>> and gives me all of those messages I reported, I don't really get what
>> is happening here.
>
> IMHO, you should be concentrating on the error message you are receiving:
>
> Check root= bootarg cat /proc/cmdline
> >>> or missing modules, devices: cat /proc/modules ls /dev
>
> I did a quick Google check on this error message and it would appear
> that it can be generated from driver resolution problems, failing
> hardware etc.

When I boot from the CDROM, I can see that the directories for
/dev/disk/by-uuid contains symbolic links:

ubuntu@ubuntu:~$ ls -l /dev/disk/by-uuid/
total 0
lrwxrwxrwx 1 root root 10 2008-11-07 04:56
7e53ac26-8a73-49fa-b156-8f09632c5d4d -> ../../sda7
lrwxrwxrwx 1 root root 10 2008-11-07 04:56
b5ce6114-6c42-48f3-a186-5828c2ebf8b2 -> ../../sda5
lrwxrwxrwx 1 root root 10 2008-11-07 04:56
cd243cef-b2af-4a75-9c74-1f0c40430585 -> ../../sda6
lrwxrwxrwx 1 root root 10 2008-11-07 04:56
ee13039d-8f86-4d78-86f2-586c1b91d875 -> ../../sda8


However, those same symbolic links are not present when the system boots
from a kernel in /dev/sda8

So, although GRUB finds the kernel and it starts booting, something is
looking for stuff in
/dev/disk/by-uuid/ee13039d-8f86-4d78-86f2-586c1b91d875, but it doesn't
exist.

Instead I get sent to the BusyBox command line:

(initramfs) ls /dev/disk
by-path
(initramfs) ls /dev/disk/by-path
pci-0000:00:02.5-scsi-1:0:0:0

How do I fix that? What is responsible for setting up that structure?