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
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).
Hi, Vince and Anders, Thanks a lot for advice. Now grub.conf lists: title Win map (hd0) (hd1) map (hd1) (hd0) root (hd0,0) rootnoverify (hd0,0) chainloader +1 makeactive Unfortunately, it still do not work. It prints content of grub.conf Win entry and stop at GRUB> command prompt. Really strange...
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).
Make these two (hd0,0) and I think things will start to work
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?
Andrei Verovski (aka MacGuru) wrote:
Hi, Vince and Anders,
Thanks a lot for advice. Now grub.conf lists:
title Win map (hd0) (hd1) map (hd1) (hd0) root (hd0,0) rootnoverify (hd0,0) chainloader +1 makeactive
I really don't remember anymore, I haven't had windows installed in a very long time. But if I read the grub exampled right, I think the last two lines are in the wrong order. Put makeactive before chainloader +1, I think the chainloader command should be the last thing as that is what loads the windows boot loader
Andrei Verovski wrote:
map (hd0) (hd1) map (hd1) (hd0)
With these lines you are changing the order of the disks
root (hd1,0)
So this is now the linux disk.
rootnoverify (hd1,0)
Make these two (hd0,0) and I think things will start to work
chainloader +1 makeactive
--------------------------------------------------
With the orignal YAST setup attempt to boot into Win results ¨chainloader + 1¨ message and nothing else.
Right. You don't have a chained bootloader on the linux partition, so it fails.
participants (4)
-
Anders Johansson
-
Andrei Verovski
-
Andrei Verovski (aka MacGuru)
-
Vince Littler