Bugzilla – Bug 406258
GRUB menu.lst entry for Vista sets wrong root partition.
Last modified: 2008-07-29 08:18:33 UTC
On a Generic Intel 915GM Board with 2 Sata Drives, 1 Primary master and 1 Secondary Master, installing OpenSUSE onto the second drive with Vista on the first drive, installation will make a mistake in grub.lst, specifically, marking vista as rootnoverify(hd1,1) instead of rootnoverify(hd0,0), causing a lockup and series of loud, rather annoying beeps. =D (going from memory on the rootnoverify part.) i had to use "sudo pico /boot/grub/menu.lst" to fix this, because in yast>bootloader>other>edit configuration files> menu.lst nothing would be saved upon changing it. My first bug report for any linux so be gentle. =D Hope it helps someone. I am REALLY liking this linux stuff, and openSUSE v11 is awesome!
Also, I know, I know, I suck for having vista, and it is my REAL problem, heheh, but I need it for work.
This may be related to incorrect detection of disks order. Could you attach whole installation logs, /boot/grub/menu.lst, boot/grub/device.map and /etc/grub.conf?
Same thing happened to me, I will attach files. My disks are: sda - normal 140GB disk with 8gb windows partition sdb - 34GB disk with windows partition sdc - External USB drive with cryptofs Everything was detected correctly out of the gate, but once setup proposed grub it insisted on using sdb as the root. I tried to edit the configs by hand but it didn't work.
Created attachment 229425 [details] y2log from install
Created attachment 229426 [details] new menu.lst that works
Created attachment 229427 [details] old menu.lst
Created attachment 229428 [details] device.map
Reinstalled from i386 with same issues, attaching output from fdisk -l
Created attachment 230175 [details] output of fdisk -l and mount
Tested install with identical configuration on Ubuntu 8.04.1 and it generated correct menu.lst file
The heuristics for detecting the disks order failed, which is probably related to your BIOS. You should check the disks order during installation and correct it (to set it to the same as BIOS really sees it). YaST can never do always correct guess - when you boot different media than the disk, the boot order is always kind of messed. Sorry, but YaST cannot do anything here, you need to check the disks order manually during installation. We intend to show some warnings in the installation proposal in similar cases, but that's all that can be done.