Comment # 49 on bug 1095096 from Franck Bui

(In reply to Dariusz Ostolski from comment #48)
> Hi,
> 
> I used mockup algo #3 and here are results:

Thanks Dariusz.

> 
> ls -alh /dev/disk/by-id 
> total 0
[...]
> lrwxrwxrwx 1 root root   13 Jul  3 17:04 nvme-200080d03000c85f8 ->
> ../../nvme0n1
> lrwxrwxrwx 1 root root   15 Jul  3 17:04 nvme-200080d03000c85f8-part1 ->
> ../../nvme0n1p1
> lrwxrwxrwx 1 root root   15 Jul  3 17:04 nvme-200080d03000c85f8-part2 ->
> ../../nvme0n1p2
> lrwxrwxrwx 1 root root   15 Jul  3 17:04 nvme-200080d03000c85f8-part3 ->
> ../../nvme0n1p3
> lrwxrwxrwx 1 root root   15 Jul  3 17:04 nvme-200080d03000c85f8-part4 ->
> ../../nvme0n1p4
> lrwxrwxrwx 1 root root   15 Jul  3 17:04 nvme-200080d03000c85f8-part5 ->
> ../../nvme0n1p5
> lrwxrwxrwx 1 root root   15 Jul  3 17:04 nvme-200080d03000c85f8-part6 ->
> ../../nvme0n1p6
> lrwxrwxrwx 1 root root   15 Jul  3 17:04 nvme-200080d03000c85f8-part7 ->
> ../../nvme0n1p7

So it looks like the old symlinks are back.

However I would recommend to use the ones shipped by upstream at that point.
For example, you can choose
"nvme-THNSN5512GPUK_NVMe_TOSHIBA_512GB_17BB502BKSHU" and use it in
/etc/crypttab.

Thank you a lot for helping us debug this issue.