Page 2 of 2

Re: Why do nvme drives change their "name" designations in 'lsblk' list on every reboot?

Posted: Sun Apr 13, 2025 10:40 pm
by Michael-IDA
@Rizlaw,

blkid is also a useful tool, it shows the current (UUIDs and LABELs) to (/nvme and /dev/sdX) mappings.

As an aside, the order my drives are listed in my fstab don't match the /nvme or /dev/sdX order at any particular boot.

Personally I use UUIDs, as {supposedly} different drives (partitions?) can have the same LABEL.

HTH,
Michael

Re: Why do nvme drives change their "name" designations in 'lsblk' list on every reboot?

Posted: Mon Apr 14, 2025 11:54 am
by atomick
I would not "LEAVE" current mount points as set. /media/S990P /media/CP3 /media/MX5D1 and /media/MX5D2

set them in the root of the file system at /
sudo mkdir /S990P as example
change the entry if made perm in /etc/fstab
toss in a Flash Drive with Data on it "Not the Live Flash" and see it gets "Auto Mounted" too

/media/Acctname/s990p if labeled , or would see the UUID of this discs number schema eg: /media/johndoe/S990P or /media/johndoe/dcad8539-b8fd-48ca-89b8-e5bb2cd7af99
thunar would do this when see on left column "if not mounted yet". usually but then odd issues have some not able to see these references.

this could cause you troubles down the line if not your OS weird Issues

ownerships can be set to your own user name and privatize the access
sudo chmod -R 740 /S990P as example owner is full read write execute , group is read only and World-Others no access.

do rest as set but highly suggest this. Confusion to adding plugin devices might really mess up. down the road.
Simply a suggestion.
Nothing should ever change up drive info on any distro when handled correctly. food for thought.
Ubuntu forms covers - Mounted a new drive and making permanent
https://askubuntu.com/questions/125257/ ... hard-drive
might provide some other information, for better performance.