[clug] grub boot problems

[Brian]

Paul,
In order to get this working I believe you need to marry up your 
device.map with what your bios actually loads.
When I installed a sata drive and one ide  and one sata compact flash 
card I had all sorts of problems trying to get things booted.
I then figured out that my bios was allocating the sata drives first 
then the ide. So my original hd0(ide) became sd2.
Once you have the 'actual' /dev order, then change your device.map to 
match and see how you go.
In the end I booted from sd0, put a chainloader into the menu.lst to 
boot the other two and changed all the /etc/fstabs accordingly.
Brian

Paul wrote:
> On 4/08/2008 5:26 PM, Brett Worth wrote:
>> Paul wrote:
>>
>>> Initially I tried
>>> root (hd2,1)
>>> but I got  Error 22: partition not valid
>>
>> I'll take a stab...
>>
>> Looks like you have a separate /boot partition so this probably should 
>> read:
>>
>> root (hd2,0)
>>
>> Then
>>
>> setup (hd2)
>>
>>> Number  Start   End     Size    Type     File system  Flags
>>>  1      32.3kB  107MB   107MB   primary  ext3         boot
>>>  2      107MB   21.6GB  21.5GB  primary  ext3
>>>  3      21.6GB  23.7GB  2147MB  primary  linux-swap
>>>  4      23.7GB  500GB   476GB   primary  ext3
>>
>> Also...
>>
>>>
>>> menu.lst
>>> splashimage=(hd0,1)/boot/grub/splash.xpm.gz
>>
>> splashimage=(hd2,0)/grub/splash.xpm.gz
>>
>>> hiddenmenu
>>> title Fedora (2.6.25.11-60.fc8) new
>>>         root (hd0,1)
>>
>> root (hd2,0)
>>
>>>         kernel /boot/vmlinuz-2.6.25.11-60.fc8 ro root=LABEL=/ rhgb quiet
>>
>> kernel /vmlinuz-2.6.25.11-60.fc8 ro root=LABEL=/ rhgb quiet
>>
>>>         initrd /boot/initrd-2.6.25.11-60.fc8.img
>>
>> initrd /initrd-2.6.25.11-60.fc8.img
>>
>> Having a separate /boot means you have to reference everything 
>> relative to the root of that partition.
>>
>> Brett
>>
>>
> 
> 
> hd2,0 doesn't work either..
> The next weird thing is that
> 
> the current menu.lst
> has root (hd0,2) and that boots the old disk which is /dev/sdb
> 
>  cat /boot/grub/device.map
> (hd0)   /dev/sda
> (hd1)   /dev/sdb
> (hd2)   /dev/sdc
> 
> 
> so I'm really confused it seems its device.map is not what is used.
>