[CentOS] mdadm issue

mark

m.roth at 5-cent.us
Tue Jul 23 18:12:44 UTC 2019


Just rebuilt a C6 box last week as C7. Four drives, and sda and sdb for
root, with RAID-1 and luks encryption.

Layout:
lsblk
NAME                                        MAJ:MIN RM   SIZE RO TYPE 
MOUNTPOINT
sda                                           8:0    0 931.5G  0 disk
├─sda1                                        8:1    0   200M  0 part 
/boot/efi
├─sda2                                        8:2    0     1G  0 part  /boot
├─sda3                                        8:3    0 500.1G  0 part
│ └─md127                                     9:127  0   500G  0 raid1
│   └─luks-5e007234-cd4c-47c6-b305-734f353a4405
                                            253:0    0   500G  0 crypt /
├─sda4                                        8:4    0     4G  0 part
│ └─md126                                     9:126  0     4G  0 raid1
│   └─luks-9dd9aacc-e702-43d9-97c2-e7e954619886
                                            253:1    0     4G  0 crypt [SWAP]
└─sda5                                        8:5    0 426.2G  0 part
  └─md125                                     9:125  0 426.1G  0 raid1
sdb                                           8:16   0 931.5G  0 disk
├─sdb1                                        8:17   0 500.1G  0 part
│ └─md127                                     9:127  0   500G  0 raid1
│   └─luks-5e007234-cd4c-47c6-b305-734f353a4405
                                            253:0    0   500G  0 crypt /
├─sdb2                                        8:18   0     4G  0 part
│ └─md126                                     9:126  0     4G  0 raid1
│   └─luks-9dd9aacc-e702-43d9-97c2-e7e954619886
                                            253:1    0     4G  0 crypt [SWAP]
└─sdb3                                        8:19   0 426.2G  0 part
  └─md125                                     9:125  0 426.1G  0 raid1

The problem is md125. System gagged on bringing it up when I rebooted,
until I commented it out of fstab.

Now, cryptsetup gives me the same UUID as I have in /etc/mdadm.conf. The
entry in /etc/crypttab looks identical to the RAIDs for root and swap, but
nope.

I was able to d an mdadm --assemble -u $(UUID from mdadm.conf), and then a
cryptopen luks... but never got anything in /dev/mapper.

I'm still fighting - any thoughts? (No, I can't reboot again, like I did
this morning, it's now serving four important home directories from
another pair of drives with RAID 1.)

      mark



More information about the CentOS mailing list