Mailinglist Archive: opensuse (4054 mails)

< Previous Next >
Damn grub dual-boot problem (again)
  • From: Andrei Verovski <andreil1@xxxxxxxxxxx>
  • Date: Sun, 15 Jan 2006 23:23:57 +0200
  • Message-id: <200601152323.57763.andreil1@xxxxxxxxxxx>
Hi,

I have problem very similar to some other users with 2 disks - one for Linux
and 2nd for Win. Everything was fine with previous setup when I have 2
UltraATA HDs and lilo.

Now I have a little different setup:
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. For Win YAST bootloader setup utility
wrote bogus entries, so I edited them manually in YAST -> Boot Loader -> Edit
configuration files. Grub was installed on /dev/sda, since it is primary boot
device, /dev/hda time to time is being disconnected.

--------------------------------------------------

/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

--------------------------------------------------

/boot/grub/menu.lst

###Don't change this comment - YaST2 identifier: Original name: linux###
title SUSE LINUX 10.0
root (hd0,0)
kernel /boot/vmlinuz root=/dev/sda1 vga=771 selinux=0 resume=/dev/sda3
splash=verbose showopts
initrd /boot/initrd

###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. I have looked into mailing list and forums and have
modified grub Win entry as listed above. However, booting into Win do not
work either - just black screen and writing ¨grub error¨. Attempt to switch
to lilo fail completely - ¨lilo timestamp mismatch¨ message and no boot into
*ANY* OS.

Anyone have an idea what went wrong?

Thanks in advance

Andrei

< Previous Next >