Bug 115529

Summary:	boot loader installation failure can cause no initrd to be created
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	Leah Cunningham <leah>
Component:	Installation	Assignee:	Jiri Srain <jsrain>
Status:	RESOLVED WORKSFORME	QA Contact:	Klaus Kämpf <kkaempf>
Severity:	Normal
Priority:	P5 - None
Version:	Beta 4
Target Milestone:	---
Hardware:	PowerPC
OS:	All
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	y2log from this system

Description Leah Cunningham 2005-09-06 22:28:06 UTC

I realize the boot loader installation is not supported, but in beta 4 a default
installation seemed to try to set it up anyway.  There was a failure (I was away
from the system, but eventually it restarted and the initrd had not been created
in /boot, though a /boot/initrd symlink was there pointing to nothing.  

I do not have the y2log from that failure, however, I can provide another y2log
from a sucessful installation where I went in and attempted to go through the
boot loader installation after the failure message, and the initrd was created
sucessfully, though the boot loader installation failed.  The initrd should be
created regardless of the boot loader installation, and probably the boot loader
installation should not be turned on by default for powermacs if it is not
working...

Comment 1 Leah Cunningham 2005-09-06 22:28:31 UTC

Created attachment 49005 [details]
y2log from this system

Comment 2 Jiří Suchomel 2005-09-07 06:59:07 UTC

What hardware are you using? "Other"?


"The initrd should be created regardless of the boot loader installation" 

well, maybe; but the code must be executed from somewhere, while this
'somewhere' may fall... this looks more like and IVNALID report. Are you able to
reproduce the behaviour?

Comment 3 Leah Cunningham 2005-09-07 16:37:24 UTC

Sorry, I meant to mark the hardware powerpc.  I think it is related to the PPC
bootloader issues.  In beta 3, the bootloader was not marked to be installed no
matter what, but that doesn't seem the case in beta4.  I can probably reproduce
it again, I saw the problem twice already.  Let me know if you want me to try to
reproduce, I can probably look at it tomorrow sometime.

Comment 4 Jiri Srain 2005-09-09 15:29:55 UTC

Provide the logs from the failing installation, please. 
 
initrd should be created during installation in any case. The log shows the 
output of mkinitrd.

Comment 5 Leah Cunningham 2005-09-15 22:06:56 UTC

I could not reproduce with RC1.  It looks like now the installer creates the
initrd, even when bootloader installation (selected by default) fails.