Using TW, Gnome, Wayland. I successfully did a sudo zypper dup this morning. I’ve got a 2TB nvme drive in an external USB-C case. I’ve been using this external drive for about 3 months to successfully do Clonez images. Now it’s not recognized by File Mngr. It appeared in Gparted as “unallocated” so I formatted it to fat32. Now it does not appear as /dev/sda like usual, like before. It now appears as /dev/nvme1n1p3.
(My other 2 internal nvme drives are /dev/nvme1n1p and 2p.)
/dev/nvme1n1p3 is appearing in Clonez so looks like I can use it for Clonez images as usual. So that’s good.
Is there a way to convert this external nvme drive from /dev/nvme1n1p3 back to /dev/sda?
I took a bunch of screenshots so let me know if you need to see any of them.
It is quite normal for an NVME device to get a device file names in this way. The p3 part points to a partition with number 3 on it.
That is a wrong assumption. They are partition 1 and 2 of the same device.
Please interpret your lsblk listing.
There are three (3) devices: sda, sdb and nvme1n1.
Where sda seems to have no partition table and nothing that lsblk is able to detect.
And sdb has two partitions. sdb1 seems to have some file system (alas you did not use lsblk -f, else you would have seen the type) that is mounted using desktop features for usr advait. For sdb2 there is no further information.
And then you have nvme1n1 that p1 that is mounted on /boot/efi and that thus, most probably is the EFI partition of this machine. From the listings about p2 (again the file sysemtype information is missing) I assume with high probablity that it contains a Btrfs file system that is used is the root file system for your present running operating system. p3 is again mounted through the desktop for user advait.
I hope you now understand what the present situation is. Maybe you can formulate your question better that the title says “not working”.
Sorry I was still typing as an edit, but that took so much time that you already tried to answer.
But no, I need no screenshot of any so called GUI tool. And I am not interested in any information from such a tool. You showed the lsblk (but lsblk -f would have been better). And my interpretation of it is above.
Please read it and ask if you do not understand it.
I removed my USB Ventoy drive to make it simpler. See below. So looks like nvme1n1 is my main 2TB internal system nvme. And nvme0n1 is my 2TB external nvme. That sound right?
(I don’t know what sda is. I also have a 500GB spare internal nvme that I don’t use.)
Looks fine. We now see that sdb2 has a vfat file system that is not in use at the moment.
Sorry but I missed in your first lsblk listing that there is also nvme0n1 that has one large partition nvme0n1p1 with a vfat file system on it. Not in use (mounted) at the moment.
Now what is your problem with this? Four (4) mass-storage devices (two probably rotating disks, two NMVE).
sda no partitioning, no file system direct on the device, nothing interesting and the size is 0 Bytes, a bit strange, could be a memory card reader.
sdb two partitions with file systems of type exfat resp. vfat, also labeled, one mounted by the desktop for user advait.
nmve1n1 three partitions with file systems vfat, btrfs and vfat, EFI, System and mounted for user advait by the desktop.
nvme0n with one, all space taking, partition of type vfat.
Again, you are so fast answering that we are not in sync
Thus my post above (#8) is an answer to your #6.
I will now answer to your #7.
When you mean with that the sdb is gone, you are correct. Remind that the wording you, as a human being, might give to something, is not the same that it is called by the system. Also please see that the way a mass-storage device is connected (e.g. USB, CGI, whatever) is of no influence to the usage and also can not be seen in the lsblk listing.
Again, the wording “internal” and “external” in this context (of mass-storage devices) might have some meaning in a computer shop (maybe influenced by MS Windows lingo??), but the Linux system can not “see” if such a device is inside or outside of the metal case. So when you think, rightful or not, that a device in “internal” or “external”, that is fine but has no meaning to us here who can not look at the physical boxes you have in front of you.
Apart from that, as I said above, nvme1n1 has, what is called, an “EFI partition” and a partition with a Btrfs file system used as root partition. Yes, many people will call that their “system disk”. Mind that there is there a third partition with a non-Linux file system (vfat), I do not know where for.
And then there is nvme0n1 with again something non-Linux on it.
BTW those are all things that should not surprise you. I am still at a loss what your problem is.
As far as I know NVMe has something to do with the physical connection of a storage device to the system bus (see here for more information).
If you connect an NVMe-storage-device via USB-C (you need some sort of interface adapter and) your system will no longer recognize this device as NVMe-device but as usb-storage i.e. that device will not be seen as /dev/ nvmexn1 but as /dev/sdx.
Looking at the data you provided so far I agree with @hcvv that you showed 4 devices
/dev/sda (unknown, probably that NVMe connected via USB-C)
/dev/sdb (USB storage with ventoy on it, later removed)
/dev/nvme0n1 (a KINGSTON OM8PCP3512F-AI1 with 512.11 GB)
/dev/nvme1n1 (a Seagate FireCuda 520 SSD ZP2000GM30002 with 2.00 TB)
I guess your problem relates in some way to /dev/sda so could you please show the result of
The “Disks” app shows /dev/sda/ but gives no info about it. /dev/sda/ does not appear in File Manager or GParted. So I think there’s something wrong with the drive enclosure or the drive itself.
And ideas how I can determine if the problem is with the drive enclosure or the drive itself? One way is to buy another drive enclosure. Anything I can test before taking that step? I don’t have any other nvme drives.
I got it fixed. I opened the enclosure and the drive was loose. I re-secured it and now it’s working normally and fully recognized. A good reminder for me to try the simple troubleshooting tasks first.
