Bug 178728
Summary: | when usb raid on usb or firewire raidautorun fails | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 4 | Reporter: | Sal Scotto <sal.scotto> |
Component: | initscripts | Assignee: | Bill Nottingham <notting> |
Status: | CLOSED DUPLICATE | QA Contact: | Brock Organ <borgan> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4.0 | CC: | rvokal |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-08-01 16:36:31 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Sal Scotto
2006-01-23 20:13:08 UTC
echo "raidautorun /dev/md0" | nash --quiet This does not try to mount the device... that does not happen until later. Can you get the kernel messages when it drops you to single-user mode? Is it creating an incomplete array? when the autorun executes it does try to start md0, sicne the devices arent all present, the raid fails to start resulting in a failed array with 0 devices single since udev hasnt added the node for the usb devices yet. OK. mdadm -As later does not reassemble it once it fails, correct? mdadm -As will assemble it later on, IF you stop the raidautorun from invoking so you can finish the boot process without dropping into single user mode. The drop into single user mode should be after mdadm runs.... it shouldn't get fscked until the second invocation. correct, but when it tries to assemble not all the drives are ready , marks drives as bad, you can force a clean re-assmbly later but once you exit single user as you know it reboots, doing it all over again |