https://bugzilla.novell.com/show_bug.cgi?id=408164 Summary: Problem with OpenSuse 11.0 menu.lst Generation for Suse/Windows dual OS Boot Product: openSUSE 11.0 Version: Final Platform: 64bit OS/Version: openSUSE 11.0 Status: NEW Severity: Normal Priority: P5 - None Component: Booting AssignedTo: jsrain@novell.com ReportedBy: cramer@phys.washington.edu QAContact: jsrain@novell.com Found By: Customer System is a dual processor system with two dual-core Opteron 64-bit processors, and two 250 GB SATA hard disks. Windows Vista SP1 is installed on the first physical disk (sda or hd0), with a small 10 MB FAT16 partition sda1 and Windows in the large 232.8 GB partition sda2. OpenSuse Linux 11.0 is installed on the sdb or hd1 physical disk, with a 2.0 GB swap in partition sdb1, the 20.0 GB / in partition sdb2, and the 210.8 GB /home in partition sdb2. Suse Linux installed this setup with a dual boot for grub, but incorrectly generated the grub commands for booting to the Windows OS. In particular, the /boot/grub/menu.lst file generated by the Suse 11.0 installation had a segment to implement the windows boot that looked like this: ###Don't change this comment - YaST2 identifier: Original name: windows### title windows rootnoverify (hd1,1) chainloader (hd0,1)+1 The system worked on the Suse boot but stalled on the Windows boot, displaying the last two lines above. After considerable flailing around, I found that the next to last line above pointed to the wrong physical disk. I changed it to the segment shown below, and the problem went away: ###Don't change this comment - YaST2 identifier: Original name: windows### title windows rootnoverify (hd0,1) chainloader (hd0,1)+1 There appears to be a bug in the installation program that is confused by a two disk system with this configuration. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.