Displaying 2 results from an estimated 2 matches for "734f353a4405".
2019 Jul 23
2
mdadm issue
...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...
2019 Jul 23
2
mdadm issue
.../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 --ex...