On Sat, 14 Nov 2020 12:15:47 -0700 Charles Curley <charlescur...@charlescurley.com> wrote:
> Or (afterthought here) did I give it the wrong UUID? A week later, I came back to this. It appears I did use the wrong UUID in /etc/crypttab. root@hawk:~# ll /dev/disk/by-uuid/ total 0 drwxr-xr-x 2 root root 180 Nov 20 10:25 ./ drwxr-xr-x 7 root root 140 Nov 20 10:24 ../ lrwxrwxrwx 1 root root 10 Nov 20 10:40 343ed59e-ae41-4733-8277-f1b77de67479 -> ../../sda5 lrwxrwxrwx 1 root root 10 Nov 20 10:36 52be92ca-795f-46ef-9c52-074fceedc53c -> ../../dm-1 lrwxrwxrwx 1 root root 9 Nov 20 10:41 57de8169-da6c-4952-b6ac-25e6c87dbf1a -> ../../md0 lrwxrwxrwx 1 root root 10 Nov 20 10:40 85936b4c-4088-4365-9c93-6a7cd8a025c6 -> ../../sda1 lrwxrwxrwx 1 root root 10 Nov 20 10:36 a3cc28cf-fb2f-4ef5-803e-2fcce7006d05 -> ../../dm-2 lrwxrwxrwx 1 root root 10 Nov 20 10:36 aef1882d-714d-41da-865e-f5cc161473e6 -> ../../dm-5 lrwxrwxrwx 1 root root 10 Nov 20 10:36 e297096c-1336-4f9f-8da0-025da7190d7b -> ../../dm-3 root@hawk:~# A quick experiment shows that this UUID for /dev/md0 is the one that works. This is also the UUID that gparted shows for /dev/md0. encryptedRaid UUID=57de8169-da6c-4952-b6ac-25e6c87dbf1a none luks As previously noted, using the device name also works, with or without a password file: encryptedRaid /dev/md0 /root/raid.encrypt.password.txt luks or encryptedRaid /dev/md0 none luks And that leaves the question of whether mdadm has a bug or whether it is showing some other UUID. Which question I am not going to pursue. -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/