grub sees 2 out of 3 systems...lucky me

[Goh Lip]

On Tue, 4 May 2010 10:09:51 -0400
Tom H <tomh0665 at gmail.com> wrote:

> >> Just tried adding /boot to the kernel and initrd lines with no
> >> other changes. Before I did that the boot sequence would start and
> >> hang with (initramfs)_. Afterward it went right back to "files not
> >> found" error. Deleted /boot from the two lines and it went back to
> >> initiating the boot sequence and hanging up. Did I leave something
> >> out?
> 
> If /boot is a separate partition from /, you must not have /boot in
> the kernel (grub1), linux (grub2), or initrd lines.
> 
> If /boot is a separate partition from / and "root=(hdx,y)" (grub1) or
> "set root=(hdx,y)" (grub2), for grub, the path to a file in /boot is
> (hdx,y)/file and not (hdx,y)/boot/file.
> 


Good thing you caught it, Tom. Did not see Bob adding back the /boot

I wrote...
> On Mon, 3 May 2010, Goh Lip wrote:
>> title		Ubuntu 8.04.4 LTS, kernel 2.6.24-27-generic
>>> root		(hd0,5)
>>> kernel		/vmlinuz-2.6.24-27-generic
>>>                    root=UUID=xxxxxxxxxxxxxx ro
>>> initrd		/initrd.img-2.6.24-27-generic
>>> quiet
>>
>>
>> (hd0,5) is the /boot, right? and let UUID=xxxxxx refer to the /boot
>> partition, (hd0,5).
>

I also wrote...
> You said you always create separate /boot partitions for all your OS, 
> therefore your menu.lst must never have the /boot/xxxxxxx in it;
> whether you 'target' the '/' or the '/boot' as the root (hd0,x).

Good catch, again Tom.

Reagrds - Goh Lip

--