FS#62788 - [mdadm] 4.1-1 cannot boot with a degraded array

Attached to Project: Arch Linux
Opened by Austin (heptagram) - Saturday, 01 June 2019, 03:21 GMT
Last edited by freswa (frederik) - Saturday, 22 February 2020, 22:01 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

mdadm 4.1-1 won't boot a degraded array. mdadm 4.0-2 is fine.

Two months ago (March 25-ish) I upgraded a drive by powering down, swapping, booting, then adding the new drive to my md arrays. This week I tried the same procedure and the system couldn't boot because the md devices weren't being assembled. I found I'd upgraded mdadm (4.0-2 -> 4.1-1) on April 19. Downgrading mdadm 4.1-1 -> 4.0-2 allowed the system to boot and let me to complete the swap.

Here's my mkinitcpio.conf HOOKS:

HOOKS=(base udev autodetect modconf block mdadm lvm2 usr filesystems keyboard fsck)

I tried mdadm_udev and saw no difference. I switched back to mdadm because that was what I was using prior. Idea being to test one change at a time.

My /boot is on a raid1, / is on raid5+lvm. lsblk is attached.
   lsblk.txt (2.5 KiB)
This task depends upon

Closed by  freswa (frederik)
Saturday, 22 February 2020, 22:01 GMT
Reason for closing:  Duplicate
Additional comments about closing:   FS#57860 
Comment by eaut (eaut) - Thursday, 05 September 2019, 21:58 GMT
I have already posted the needed bug fix in  FS#57860 

Loading...