Boot fails with degraded mdadm raid
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mdadm (Debian) |
Fix Released
|
Unknown
|
|||
mdadm (Ubuntu) |
Fix Released
|
High
|
Dimitri John Ledkov | ||
Xenial |
Fix Released
|
High
|
Dimitri John Ledkov |
Bug Description
[Impact]
* Systems fail to boot in certain status of mdadm arrays, requiring manual recovery / array assembly
* Backport of boot logic from yakkety
[Test Case]
* Install a system with RAID1 and two hard-drives and boot the system with array in-sync
* Shutdown
* Disconnect one of the drives and thus boot, unexpectedly, degraded
* The boot should complete.
* Shutdown, and boot again, expecting degraded state.
* The boot should complete.
* Shutdown, reconnect disconnected drive, and boot again.
* The boot should complete, add the device to the array, the array should be resyncing, and results with system with array in-sync, just like at the beginning of the testcase.
[Regression Potential]
* Systems may continue to fail to boot degraded.
[Other Info]
* Original report
mdadm does not attempt to start partial md devices (incremental assembly) during initramfs and can cause system to fail to initramfs prompt if rootfs on md.
http://
Fixed in debian mdadm 3.4-2: https:/
tags: | added: regression-release xenial |
Changed in mdadm (Debian): | |
status: | Unknown → Fix Released |
Changed in mdadm (Ubuntu): | |
importance: | Undecided → High |
assignee: | nobody → Dimitri John Ledkov (xnox) |
Changed in mdadm (Ubuntu): | |
milestone: | none → ubuntu-17.02 |
description: | updated |
description: | updated |
tags: |
added: verification-done removed: verification-needed |
Status changed to 'Confirmed' because the bug affects multiple users.