You are not logged in.
I have a wierd issue with my motherboard NVMe slots.
when I have one NVMe I place it on my first NVMe slot. It's recognized as /dev/nvme0.
But when I add another on the second slot, so there are 2 NVMe drives. The first one is recognizes as /dev/nvme1 and the second one I just added as /dev/nvme0.
Do you know what's happening ?
Motherboard: MSI MPG Z490 GAMING PLUS
I did read it three times and I still do not see, what is the issue you are experiencing.
When you insert one device, one device is being reported (“/dev/nvme0”).
When you insert two devices, two devices are being reported (“/dev/nvme0” and “/dev/nvme1”).
Everything seems fine. What is the problem?
Paperclips in avatars? | Sometimes I seem a bit harsh — don’t get offended too easily!
Offline
Not exactly.
My main NVMe is placed on the first slot on my motherboard. When alone it's refered to as nvme0
When I add another on the second slot, so I have 2 NVMe drives, the first one is refered to as nvme1 and the second one as nvme0.
In my case, my root NVMe is usually nvme0 but when I add another NVMe, my root one becomes nvme1 and the new one I added is nvme0.
Device names are random and one can’t rely on them.
For predictable names use UUIDs, PARTUUIDs, or the “/dev/disk/*” hierarchy.
Paperclips in avatars? | Sometimes I seem a bit harsh — don’t get offended too easily!
Offline
This is why I use UUIDs in my config files like fstab.
But do you understand if the problem is from Linux, the motherboard, or the drives ?
There is no problem at all. It is a normal situation. There is no specific order in which devices are expected to receive their numbers.
Paperclips in avatars? | Sometimes I seem a bit harsh — don’t get offended too easily!
Offline
Ok I see, thanks
The situation can be even more difficult.
In my case names of NVMe drives was changed after one of the kernel update (6.1->6.2, if I remember correctly). And some time later I found that they can change when I boot from rescue disk.
I do understand the reason, and why UUIDs are important, just double check every time when I do some dangerous operations with disks.
Offline