On Wed January 31 2007 14:13, Darryl Gregorash wrote:
> With this and your /etc/fstab, it is possible to rebuild grub's
> menu.lst. Your root device is /dev/sda8, and /boot is on it (ie. not a
> separate partition). In grub, this is (hd0,7). Thus
>
>        gfxmenu (/dev/sda,7)/boot/message
>
> should read
>
>        gfxmenu (hd0,7)/boot/message
<snip>
> The kernel options are correct insofar as partition references are
> concerned (ie. the root= and resume= options).

Hi Darryl,

The repaired menu.lst I posted yesterday (quoted below) seems to match your 
interpretation. One thing, though, I 'clipped out' one of the two apparent 
Windows installations thinking it could be added back later, manually or via 
the bootloader configuration module. That, and confirming the version numbers 
for his installed initrd and vmlinuz, are the only outstanding questions for 
this part of the puzzle.

> - - - - - 8< - - - - -
> # Modified by YaST2. Last modification on Sun Jan 28 20:13:54 PST 2007
> default 0
> timeout 12
> gfxmenu (hd0,7)/boot/message
>
> ###Don't change this comment - YaST2 identifier: Original name: linux###
> title openSUSE 10.2
>     root (hd0,7)
>     kernel /boot/vmlinuz-2.6.18.2-34-default root=/dev/sda8
> resume=/dev/sda7 splash=silent showopts
>     initrd /boot/initrd-2.6.18.2-34-default
>
> ###Don't change this comment - YaST2 identifier: Original name: Windows ###
> title windows 1
>    rootnoverify (hd0,0)
>    chainloader (hd0,0)+1
>
> ###Don't change this comment - YaST2 identifier: Original name: failsafe###
> title Failsafe -- openSUSE 10.2
>     root (hd0,7)
>     kernel /boot/vmlinuz-2.6.18.2-34-default root=/dev/sda8 showopts
> ide=nodma apm=off acpi=off noresume nosmp noapic maxcpus=0 edd=off 3
>     initrd /boot/initrd-2.6.18.2-34-default
>
> - - - - - 8< - - - - -

> It is possible that the grub MBR contains incorrect offsets because of
> these errors. However, correct menu.lst only and see if you can boot; we
> can re-install the grub boot record later, if that proves to be necessary.

agreed

> The only other possible source of a problem is a missing or incorrect
> stage 1.5 file embedded in the grub MBR. We'll check that if the above
> corrections do not work.

agreed

If Charles is working a full day today we many not know the results before 
late evening (EDT).

regards,

Carl
-- 
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to