Bug 406258

Summary:	GRUB menu.lst entry for Vista sets wrong root partition.
Product:	[openSUSE] openSUSE 11.0	Reporter:	Jacob Richards <jacob.richards5131>
Component:	Bootloader	Assignee:	Jiri Srain <jsrain>
Status:	RESOLVED WONTFIX	QA Contact:	Jiri Srain <jsrain>
Severity:	Normal
Priority:	P5 - None	CC:	sharms
Version:	Final
Target Milestone:	---
Hardware:	x86-64
OS:	openSUSE 11.0
Whiteboard:
Found By:	Customer	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	y2log from install new menu.lst that works old menu.lst device.map output of fdisk -l and mount

Description Jacob Richards 2008-07-03 17:44:32 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!

Comment 1 Jacob Richards 2008-07-03 17:45:44 UTC

Also, I know, I know, I suck for having vista, and it is my REAL problem, heheh, but I need it for work.

Comment 2 Jiri Srain 2008-07-14 07:58:47 UTC

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?

Comment 3 Steven Harms 2008-07-23 03:46:47 UTC

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.

Comment 4 Steven Harms 2008-07-23 03:48:08 UTC

Created attachment 229425 [details]
y2log from install

Comment 5 Steven Harms 2008-07-23 03:49:29 UTC

Created attachment 229426 [details]
new menu.lst that works

Comment 6 Steven Harms 2008-07-23 03:49:44 UTC

Created attachment 229427 [details]
old menu.lst

Comment 7 Steven Harms 2008-07-23 03:49:56 UTC

Created attachment 229428 [details]
device.map

Comment 8 Steven Harms 2008-07-26 16:43:41 UTC

Reinstalled from i386 with same issues, attaching output from fdisk -l

Comment 9 Steven Harms 2008-07-26 16:45:02 UTC

Created attachment 230175 [details]
output of fdisk -l and mount

Comment 10 Steven Harms 2008-07-26 16:48:42 UTC

Tested install with identical configuration on Ubuntu 8.04.1 and it generated correct menu.lst file

Comment 11 Jiri Srain 2008-07-29 08:18:33 UTC

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.