Why nvme name changes after install.

[ozgurerdogan]

This is probably simple question. I am installing proxmox on first nvme disk which I guess should be nvme0n1 but after install I see OS disk is nvme1n1
I even tried installing pve to second this but after install I still see /dev/nvme1n1 in gui.
So how can I install PVE to nvme0n1 ?
AFAIK 0n1 is first disk and 1n1 is second disk on system.

 

[tcabernoch]

This sort of thing can be so confusing. What do you see here?

ls -alh /dev/disk/by-id/

 

[ozgurerdogan]

drwxr-xr-x 2 root root 340 Aug 17 00:32 .
drwxr-xr-x 8 root root 160 Aug 17 00:32 ..
lrwxrwxrwx 1 root root  13 Aug 17 00:32 nvme-eui.002538b331a608fd -> ../../nvme1n1
lrwxrwxrwx 1 root root  15 Aug 17 00:32 nvme-eui.002538b331a608fd-part1 -> ../../nvme1n1p1
lrwxrwxrwx 1 root root  15 Aug 17 00:32 nvme-eui.002538b331a608fd-part2 -> ../../nvme1n1p2
lrwxrwxrwx 1 root root  15 Aug 17 00:32 nvme-eui.002538b331a608fd-part3 -> ../../nvme1n1p3
lrwxrwxrwx 1 root root  13 Aug 17 00:32 nvme-eui.002538b331a608fe -> ../../nvme0n1
lrwxrwxrwx 1 root root  13 Aug 17 00:32 nvme-SAMSUNG_MZVL2512HCJQ-00B00_S675NU0W301077 -> ../../nvme1n1
lrwxrwxrwx 1 root root  13 Aug 17 00:32 nvme-SAMSUNG_MZVL2512HCJQ-00B00_S675NU0W301077_1 -> ../../nvme1n1
lrwxrwxrwx 1 root root  15 Aug 17 00:32 nvme-SAMSUNG_MZVL2512HCJQ-00B00_S675NU0W301077_1-part1 -> ../../nvme1n1p1
lrwxrwxrwx 1 root root  15 Aug 17 00:32 nvme-SAMSUNG_MZVL2512HCJQ-00B00_S675NU0W301077_1-part2 -> ../../nvme1n1p2
lrwxrwxrwx 1 root root  15 Aug 17 00:32 nvme-SAMSUNG_MZVL2512HCJQ-00B00_S675NU0W301077_1-part3 -> ../../nvme1n1p3
lrwxrwxrwx 1 root root  15 Aug 17 00:32 nvme-SAMSUNG_MZVL2512HCJQ-00B00_S675NU0W301077-part1 -> ../../nvme1n1p1
lrwxrwxrwx 1 root root  15 Aug 17 00:32 nvme-SAMSUNG_MZVL2512HCJQ-00B00_S675NU0W301077-part2 -> ../../nvme1n1p2
lrwxrwxrwx 1 root root  15 Aug 17 00:32 nvme-SAMSUNG_MZVL2512HCJQ-00B00_S675NU0W301077-part3 -> ../../nvme1n1p3
lrwxrwxrwx 1 root root  13 Aug 17 00:32 nvme-SAMSUNG_MZVL2512HCJQ-00B00_S675NU0W301078 -> ../../nvme0n1
lrwxrwxrwx 1 root root  13 Aug 17 00:32 nvme-SAMSUNG_MZVL2512HCJQ-00B00_S675NU0W301078_1 -> ../../nvme0n1

 

[tcabernoch]

Ok, I see exactly what you are talking about there.
All I did was google around. I guess it has something to do with the order things are discovered upon boot.
Question is, does this just bother you because its messy? Or is something broken?
The advice is to use persistent block identifiers, not transient ones like the /dev/whatever labels.
I saw a lotta advice to use lsblk.

 

[ozgurerdogan]

Thank you for your time. This does not bother much but I always install PVE on first disk and leave it so with no vm on it. So in case system crashes I just go for reinstall and I always keep in mind that first disk is ok to reinstall.
I was following this guide and there is section to detect detect disk:

PRIMARY_DISK=$(lsblk -dn -o NAME,SIZE,TYPE -e 1,7,11,14,15 | sed -n 1p | awk '{print $1}')
SECONDARY_DISK=$(lsblk -dn -o NAME,SIZE,TYPE -e 1,7,11,14,15 | sed -n 2p | awk '{print $1}')

I also tried not adding SECONDARY_DISK but it still shows pve on nvme1n1.

This is kinda annoyning and wierd. Did not have such thing on ssd or sata disks..

So I guess no easy way for this?