Bug 116359

Summary:	Yast2 sets wrong harddisk number in GRUB
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	Jörg Rüppel <sharky-x>
Component:	Installation	Assignee:	Steffen Winterfeldt <snwint>
Status:	RESOLVED WORKSFORME	QA Contact:	Klaus Kämpf <kkaempf>
Severity:	Major
Priority:	P5 - None	CC:	jsrain
Version:	RC 1
Target Milestone:	---
Hardware:	x86-64
OS:	All
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	Yast2 Logfiles getsysinfo run without /proc/acpi tree getsysinfo run without /proc/acpi tree getsysinfo run without /proc/acpi tree

Description Jörg Rüppel 2005-09-10 20:03:52 UTC

The GRUB config file refers to hdb(hd1,x) for all my installed OSes, although
they all are installed on hda (hd0,x).

Bootet from a SuSE 10 Beta 1 CD, in Bootscreen selected Advanced Options,
XMB/CIFS install.

Pointed it to remote SMB share of RC1 CD1.
Install went through until reboot, GRUB came up, but couldn't boot anything.
Looking at the GRUB configuration revealed that all entries pointed one harddisk
number too high.

Comment 1 Jörg Rüppel 2005-09-10 20:05:22 UTC

Created attachment 49527 [details]
Yast2 Logfiles

Comment 2 Jiri Srain 2005-09-26 11:36:07 UTC

The BIOS provides wrong information (it claims that /dev/hda is 2nd disk 
regarding the order of BIOS). According to what I know, some BIOSes are 
confused if you boot from CD. 
 
Sorry, but I can't do anything about it.

Comment 3 Jörg Rüppel 2005-09-26 23:56:32 UTC

It worked for SuSE 9.3 and I think even 9.2 with the exactly same hardware, this
is actually the first time that I see this behaviour. Maybe it depends on what
cddrive I boot from? Can I test that behaviour somehow without doing complete
installs?

Comment 4 Jiri Srain 2005-09-27 07:03:10 UTC

Steffen, any idea why it had worked in older releases? 
 
According to the logs, /dev/hda is 0x81 and /dev/hdb has no ID assigned.

Comment 5 Steffen Winterfeldt 2005-09-27 08:56:57 UTC

Please start installation, at the license screen go to console 2, run 
'getsysinfo' and attach the tar file it produces.

Comment 6 Jörg Rüppel 2005-09-27 14:21:35 UTC

Created attachment 50942 [details]
getsysinfo run without /proc/acpi tree

/proc/acpi/event couldn't be copied nor deleted so I had to remove /proc/acpi
from getsysinfo

Comment 7 Steffen Winterfeldt 2005-09-27 14:38:40 UTC

Sorry, my fault: edd is not loaded that early on. Could you do that again, but 
let yast run a bit further, up to the screen where you can start the 
installation? The storage modules and edd will be loaded then. 
 
Yes, /proc/acpi/event blocks on some systems.

Comment 8 Jörg Rüppel 2005-09-27 15:09:03 UTC

Created attachment 50948 [details]
getsysinfo run without /proc/acpi tree

Comment 9 Steffen Winterfeldt 2005-09-27 15:17:58 UTC

Still not loaded. Maybe that's the problem. Could you please try 
'modprobe edd' manually? Is so, does it improve the situation (yast2 
lets you look at the grub config without actually starting the install)?

Comment 10 Jörg Rüppel 2005-09-27 15:37:47 UTC

Created attachment 50954 [details]
getsysinfo run without /proc/acpi tree

sorry last one was the same as the first

Comment 11 Steffen Winterfeldt 2006-03-27 15:44:21 UTC

The logs look very strange. If that still happens with 10.1, reopen and 
attach the log of 'hwinfo --block --log=xxx' (taken during installation).