Bug 130696

Summary:	Add option for mkinitrd to add raid files for initrds builded for remote machines
Product:	[openSUSE] SUSE Linux 10.1	Reporter:	Thomas Renninger <trenn>
Component:	Basesystem	Assignee:	Hannes Reinecke <hare>
Status:	RESOLVED FIXED	QA Contact:	E-mail List <qa-bugs>
Severity:	Minor
Priority:	P5 - None
Version:	unspecified
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	Logs of the machine bartok after yast tries to setup partitions

Description Thomas Renninger 2005-10-26 06:56:49 UTC

An option like -r would be nice that adds raid specific binaries to the initrd even if the system itself has no raid configured.

Problem:
Building kernel/initrd on a remote machine and let another machine boot those via PXE fails on raid systems.

Are there any other binaries or whatever that could be missing (for something else than a raid) for building initrds for remote machines?

Comment 1 Hannes Reinecke 2005-12-19 10:25:05 UTC

This is not feasible in general as we need to include any controller / drive specific modules as well.

However, it's probably not a bad idea to select the any available feature from the command-line option.

Comment 2 Thomas Renninger 2006-01-18 14:49:30 UTC

Created attachment 63831 [details]
Logs of the machine bartok after yast tries to setup partitions

Be aware that this time the raid arrays were tried to be freshly installed by Frank. It seems as if Yast does not only recognise old Raid arrays, but even cannot setup new ones any more?
For details to these logs ask Frank.
The machine's name is *bartok*, it is up and running with one disk at the moment and SLES10-PRE4.

Comment 3 Hannes Reinecke 2006-03-20 16:09:10 UTC

There is now an option '-f' which lets you enable additional features.
new rpm queued for Beta9.