Bug 76719 - RAID-init in rc.sysinit fails if RAID-devices have already been initialized in initrd
RAID-init in rc.sysinit fails if RAID-devices have already been initialized i...
Status: CLOSED WORKSFORME
Product: Red Hat Linux
Classification: Retired
Component: initscripts (Show other bugs)
7.3
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
Brock Organ
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-10-25 09:56 EDT by Joakim Ahlin
Modified: 2014-03-16 22:32 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-01-13 23:57:30 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Joakim Ahlin 2002-10-25 09:56:32 EDT
Description of Problem:

When RAID-arrays are started from within an initrd 
(using "raidautorun /dev/mdX" in linuxrc"), the boot fails in rc.sysinit. When 
trying to initialize the RAID arrays from within the script, it backs out with 
the error "raid device has already been started" or something. 

I have also been experiencing the "Typo in RAID setup"-bug from #71087.

Version-Release number of selected component (if applicable):

initscripts-6.67-1

How Reproducible:

Very.

Steps to Reproduce:
1. Set your lilo config to use /dev/mdX as root file system, and 
modify /etc/fstab to use the same mdX as / filesystem.
2. Run mkinitrd with raidmodule loaded
3. Reboot. Boot raid array will be initialized in initrd, and the RAID 
initialization in rc.sysinit will fail.

Actual Results:


Expected Results:


Additional Information:
Comment 1 Bill Nottingham 2002-11-12 00:04:05 EST
Hm, we've done root on raid here before, without problems. Can you post the
*exact* errors?
Comment 2 Bill Nottingham 2003-01-13 23:57:30 EST
closed, no followup

Note You need to log in before you can comment on or make changes to this bug.