CentOS - Jul 2019 - mdadm issue

Gordon Messmer wrote:
> On 7/23/19 11:12 AM, mark wrote:
>
>> 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.
>
>
> Can you post those files somewhere?? I'm confused by the idea that
> cryptsetup is involved in or using the same UUID as an MD RAID device.
>
Here's part of /etc/mdadm.conf
ARRAY /dev/md/root metadata=1.2 name=<server>:root
UUID=7dea42fa:c9ef035d:0a6bada5:3ba5c21f
ARRAY /dev/md/export_1 metadata=1.2 name=<server>:export_1
UUID=637ef224:91b445d8:69d48980:adc8bc70

and, from /etc/fstab, the same drives
/dev/mapper/luks-5e007234-cd4c-47c6-b305-734f353a4405 /                   
   xfs     defaults,x-systemd.device-timeout=0 0 0
/dev/mapper/luks-3da4ae38-b78a-4fb4-9c2d-b029a9b16378 /export/1 xfs
defaults 0 0

excerpt the last luks doesn't exist. They *both* say UUID, so it's *so*
simple to understand (NOT). I got the mdraid UUID from mdadm --examine
--scan.

        mark

    mark

I still don't understand how this relates to md125.? I don't see it 
referenced in mdadm.conf.? It sounds like you see it in the output from 
lsblk, but only because you manually assembled it.? Do you expect there 
to be a luks volume there?

> Am 23.07.2019 um 22:39 schrieb Gordon Messmer <gordon.messmer at
gmail.com>:
> 
> I still don't understand how this relates to md125.  I don't see it
referenced in mdadm.conf.  It sounds like you see it in the output from lsblk,
but only because you manually assembled it.  Do you expect there to be a luks
volume there?
To check:

 cryptsetup isLuks <device> && echo Success

 cryptsetup luksDump <device>

--
LF