Bug 146747 - during creation os initrd, error msg cannot stat /sbin/raidstart
Summary: during creation os initrd, error msg cannot stat /sbin/raidstart
Status: RESOLVED DUPLICATE of bug 146304
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: Installation (show other bugs)
Version: Beta 2
Hardware: x86 Other
: P5 - None : Critical (vote)
Target Milestone: ---
Assignee: Thomas Fehr
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-01-30 18:49 UTC by Clyde Kunkel
Modified: 2006-01-31 15:24 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Clyde Kunkel 2006-01-30 18:49:32 UTC 
Installing 10.1b2 from CD on LV over raid5, get error during initrd creation that cannot stat /sbin/raidstart.

Went to console 2 and verified that raidstart not present in new root or install root.

Rebooted into install CD, and during installation of packages, went to console 2 and copied raidstart from SuSE 10.0 to /mnt/sbin and /sbin.  This allowed the initrd to be completed without error msgs, but the initrd was useless and numerous errors scrolled off the screen, ie, could not find kernel modules, did not start raid, etc, and dropped to shell.

SuSE 10.0 installed nicely on LV over raid5 same system.
Comment 1 Michael Gross 2006-01-31 10:29:34 UTC 
We'll need help from the kernel maintainers.
Comment 2 Chris L Mason 2006-01-31 15:09:21 UTC 
Seems likely that raidtools simply was not installed.  This would be an installer issue.
Comment 3 Thomas Fehr 2006-01-31 15:14:06 UTC 
AFAIK raidtools package is not part of CODE10 any more
There is no installer on earth that can install nonexistant packages.

*** This bug has been marked as a duplicate of 146304 ***
Comment 4 Clyde Kunkel 2006-01-31 15:24:19 UTC 
OK, bug 146838 bit me and when I realized later that the installer was putting /boot on the LV, I copied the contents to the "real" boot parition (0x83 type).  The original comment that "the initrd was useless and numerous errors occured" was due to a typo on my part in using the SuSE10.0 initrd.  After having coffee and correcting the error, I tried to boot the system with the initrd I forced by copying raidstart from SuSE 10.0.  Raidstart worked here, but none of the LVs were seen and again dropped into a shell.  Provided yast logs and other info on 147838.


How are we to insall on systems with LVs over raid?  SuSE 10.0 does it nicely.