degraded NON-root raids never --run on boot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mdadm (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
mountall (Ubuntu) |
Invalid
|
Wishlist
|
Unassigned | ||
Bug Description
Systems with say /home on raid won't come up booting when raid was degraded during downtime.
An init script like /etc/init.
Because the proper mdadm --incremental mode command is not available (Bug #251646) a workaround needs to be used:
mdadm --remove <incomplete-
mdadm --incremental --run <arbitrary-
(See https:/
---
The possibility that large server RAIDs may take minutes until they come up, but regular ones are quick, can be handled nicely:
"NOTICE: /dev/mdX didn't get up within the first 10 seconds.
We continue to wait up to a total of xxx seconds complying to the ATA
spec before attempting to run the array degraded.
(You can lower this timeout by setting the rootdelay= parameter.)
<counter> seconds to go.
Press escape to stop waiting and to enter a rescue shell.
summary: |
- home array not run when degraded on boot + non-root raids fail to run degraded on boot |
description: | updated |
summary: |
- non-root raids fail to run degraded on boot + degraded non-root raids are not run on boot |
description: | updated |
description: | updated |
summary: |
- degraded non-root raids are not run on boot + degraded non-root raids don't appear on boot |
description: | updated |
summary: |
- degraded non-root raids don't appear on boot + degraded NON-root raids never --run on boot |
description: | updated |
Changed in mountall (Ubuntu): | |
status: | Incomplete → Triaged |
This issue has been separated out from Bug #120375 in order to track it separately.
(Don't mark this as a duplicate, like 4 others before.)