Bug 255851

Summary:	System Fails to boot after upgrade with Error 23
Product:	[openSUSE] openSUSE 10.3	Reporter:	Forgotten User YLzcEHequO <forgotten_YLzcEHequO>
Component:	Installation	Assignee:	Olaf Dabrunz <odabrunz>
Status:	RESOLVED FIXED	QA Contact:	Jiri Srain <jsrain>
Severity:	Critical
Priority:	P5 - None
Version:	Alpha 3
Target Milestone:	---
Hardware:	i586
OS:	Other
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	Y2log requested

Description Forgotten User YLzcEHequO 2007-03-19 18:30:49 UTC

After upgrading from 10.2GM to 10.3A2 I get the following error when booting:

Booting `openSUSE 10.3`
root (/dev/sda,0)
Error 23: Error wjile parshing number
Press any key to continue...

Why is this using "sda" for an IDE drive when "sda" was supposed to be for SCSI drives? and the drive in grub is listed as /dev/disk/by-id/ata-TOSHIBA_MK2017GA_X1J71256t-p->

What ever became of supporting legacy hardware? I now have a system that is unusable!

Also when booting to the "rescue system" I'm asked for an install source, then put into text mode. If I then select to boot the installed system I get a scrolling screen the starts with udevd[2036]get_(the rest of the line is not readable).

The system is also loading the ata_piix driver when it should be loading the pixx driver for my harddrive. Where can I change this?

Comment 1 Cyril Hrubis 2007-03-20 16:41:19 UTC

The "grub" problem is probably caused by yast2-bootloader module so please attach y2logs. Quick how to obtain y2log is here: http://en.opensuse.org/Bugs/YaST.

About the driver problem: There is only ata_piix driver in /lib/modules/... I'm quite confused what you wanted to do.

Please next time send one bug per report.

Comment 2 Forgotten User YLzcEHequO 2007-03-20 20:26:13 UTC

Created attachment 125577 [details]
Y2log requested

Requested Y2log files attached as tar file using czvf options.

Comment 3 Cyril Hrubis 2007-03-23 16:37:23 UTC

Please next time after answering question or attaching logs set bug status to ASSIGNED in order to help us find bugs witch was answered.

Comment 4 Stefan Fent 2007-04-10 15:44:33 UTC

Should be fixed with latest perl-Bootloader.
As there's an easy workaround for this, decreasing severity.

Comment 5 Forgotten User YLzcEHequO 2007-04-11 15:51:51 UTC

Upon further investigation I did the following in order to get the system to boot.

I changed the following lines in menu.lst:

gfxmenu (hd0,3)/boot/message

to:

gfxmenu (hd0,0)/message

Under linux and failsafe entries:

root (hd0,3)

to:

root (hd0,0)

and:

initrd /boot/initrd

to:

initrd /initrd

I also changed the "by_id" reference to the partition to /dev/sda#.

Once these changes were made the system did boot the finish the install (upgrade) process.

Comment 6 Forgotten User YLzcEHequO 2007-04-18 14:39:22 UTC

After upgrade to 10.3A3 it has become obvious that the problem resides with the upgrade process _NOT_ recognizing that I have a /boot partition. Why doesn't the upgrade process read the /etc/fstab file during the upgrade to find out what partitions are previously used? This is why when I make the changes listed in #5 that the system then boots. This error is apparent in 10.3A2 and 10.3A3.

Comment 7 Stefan Fent 2007-07-31 13:07:50 UTC

The problem here indeed is the change from hda -> sda.
This is fixed in Alpha6.