Mailinglist Archive: opensuse (4054 mails)

< Previous Next >
Re: [SLE] Damn grub dual-boot problem (again)
  • From: Vince Littler <suse@xxxxxxxxxxxxxxxxxxxxxxxxx>
  • Date: Sun, 15 Jan 2006 22:24:14 +0000
  • Message-id: <200601152224.14424.suse@xxxxxxxxxxxxxxxxxxxxxxxxx>
On Sunday 15 January 2006 21:23, Andrei Verovski wrote:
>
> 1) SuSE Linux on /dev/sda1 - Seagate Barracuda SATA HD connected to
> Silicon Image SATA PCI Card.
> 2) Win on /dev/hda1 connected to primary UltraATA bus on m/b.
>
> BIOS was configured to boot from SATA drive first. Basically, there is no
> problem with Linux. Its just boots.
>
> --------------------------------------------------
>
> /boot/grub/device.map:
> (hd0) /dev/sda
> (hd1) /dev/hda
>
> --------------------------------------------------
>
> /etc/grub.conf
> setup --stage2=/boot/grub/stage2 (hd0,0) (hd0,0)
> setup --stage2=/boot/grub/stage2 (hd1) (hd0,0)
> quit
>
> --------------------------------------------------
>
> ###Don't change this comment - YaST2 identifier: Original name: windows###
> title Win
> map (hd0) (hd1)
> map (hd1) (hd0)
> root (hd1,0)
> rootnoverify (hd1,0)
> chainloader +1
> makeactive
>
> --------------------------------------------------
>
> With the orignal YAST setup attempt to boot into Win results ¨chainloader +
> 1¨ message and nothing else.
>
> Anyone have an idea what went wrong?

only a guess. Win is on hd(1,0), but expects to boot from hd(0,*). Correctly
you have used the map instructions, but having set the GRUB to make it appear
as though hd(0,0) is the windows drive, you actually try to boot from
hd(1,0).


< Previous Next >
References