I have an encrypted SATA SSD from a laptop that was running tumbleweed yesterday and now has hardware display errors. I have removed this drive from the laptop. I have a USB-SATA adapter+power kit that I was expecting to just be able to plug this drive into and mount with the drive password on another laptop to retrieve data.
The power and USB indicator lights on the adapter kit light up.
Plugging the USB cable into another laptop running tumbleweed and KDE produces the normal audio indicator that a drive has been plugged in, but the drive does not appear in dolphin (the KDE graphical file manager) under devices.
but one includes the line with the prompt and the command inside the copy/paste. Then everybody can see exactly what you see before you: what your working directory is, what the user is, what the user did and what the user got. Also copy/paste including the new prompt line so that we can see that the output is complete. That last one is e.g. in his case important for the lsblk listing. No story telling, but showing.
I am e.g. confused by the fact that you only seem to have that sda that is connected by you as an extra disk, but that there is no disk with the system you are running???
I was already confused earlier that the added mass storage device was enumerated as sda.
Otherwise there seem to be one partition that fills the whole of the disk and that is of type ee, said to be GPT.
I do not knowing much about encryption, but I assume the partition is encrypted and not the whole disk.
Thanks for the now complete fdisk listing, I already has a vague idea that the system was on SSD devices, but now all is clear.
Although you did not post the lsblk -f, you say that sda is not in that listing. Very strange.
The system now sees on sda a DOS partitioning table with only one partition, that uses the rest of the space on the disk. That does not concur with your impression of having root partition, swap partition and a one for /home. But maybe my lack of knowledge how YaST creates that encryption does not help. Better wait until others, like @hendersj , enter the daylight part of the globe.
From long ago I remember that installing with encryption was often done using the Logical Volume manager. I assume you do not have any /etc/fstab from the original system this was the system disk of.
It does NOT mean: show nothing when no file system detected.
It means show an lsblk listing with, apart from other columns listed by default, showing file system types when detected.
localhost:/home/matt # gdisk -l /dev/sda
GPT fdisk (gdisk) version 1.0.10
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: not present
Creating new GPT entries in memory.
Disk /dev/sda: 62514774 sectors, 238.5 GiB
Model: MZ7LN256HAJQ-000
Sector size (logical/physical): 4096/4096 bytes
Disk identifier (GUID): FCDB911E-99B8-41D4-A861-779A099CD4F4
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 5
First usable sector is 6, last usable sector is 62514768
Partitions will be aligned on 256-sector boundaries
Total free space is 62514763 sectors (238.5 GiB)
Number Start (sector) End (sector) Size Code Name
localhost:/home/matt #
Assuming you have used nvme0n1 in the same way as earlier sda, there is something wrong with sda. It should have manifested itself in the same way as nvme0n1.
fdisk interprets what it sees as the protective MBR. It looks as gdiskseems something that could be a GPT.lsblk` sees only the device with nothing particular on it.
I wonder if something happened to the device after you last used it on that laptop.
Assuming you have used nvme0n1 in the same way as earlier sda , there is something wrong with sda . It should have manifested itself in the same way as nvme0n1 .
I don’t remember whether it’s exactly the same, but that was the intention.
I ran zypper dup on a functioning Tumbleweed distribution on a Lenovo T480 laptop. It ran as normal.
You drive was partitioned for 512 bytes sector size (standard legacy disks). GPT starts in the second sector (whatever size it is) and now your drive claims to have 4K sector size, so GPT is not found.
Most likely it is your
which “optimizes” drive access. Your physical drive is likely 512e (4K physical sector and 512 bytes emulated logical sector).
May be your adapter can be configured to not do it. If not and you have enough space you can simply dd this disk into a file and create loop device over this file with losetup. It defaults to 512 sectors and in any case you can set sector size during creation.
It may work directly over /dev/sda.
Otherwise try to find other adapter that is not that “smart” or plug SATA disks directly into SATA port in your system.