So I have 2 internal SSDs, one is my boot drive, the other is my actual main storage device. When I installed Manjaro KDE, I installed it onto my boot drive. However, now my main storage drive is showing as unformatted in KDE Partition Manager (checking via lsblk -no FSTYPE /dev/sda1 or lsblk -no FSTYPE /dev/sda2, which according to google should return the format of the partitions, literally just came back blank), despite the known 250 GB worth of data on it that showed just fine when I was running Windows. Is there any way to fix this without fishing the SSD out of my computer, copying the files to an external hard drive on a Windows PC, and reformatting the drive?
It sounds like if multiple tools return nothing, and you cannot access the files in any other way … then it is likely there actually is nothing there (did you wipe it during install?).
There may be a slight chance it is some unrecognized format, but that is unlikely.
What does the following show?
sudo fdisk -l
1 Like
Returns:
Disk /dev/sda: 465.76 GiB, 500107862016 bytes, 976773168 sectors
Disk model: WDC WDS500G2B0A
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 6C892CF0-CB8C-11EA-AD44-0028F87500CA
Device Start End Sectors Size Type
/dev/sda1 34 32767 32734 16M Microsoft reserved
/dev/sda2 32768 976773119 976740352 465.7G Microsoft Storage Spaces
Disk /dev/sdb: 119.24 GiB, 128035676160 bytes, 250069680 sectors
Disk model: SanDisk SD9SN8W1
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: FF6ADF0B-B6CD-3D4A-932D-8F4ED2D76A08
Device Start End Sectors Size Type
/dev/sdb1 4096 618495 614400 300M EFI System
/dev/sdb2 618496 214108013 213489518 101.8G Linux filesystem
/dev/sdb3 214108014 250067789 35959776 17.1G Linux swap
Disk /dev/sdc: 114.61 GiB, 123060879360 bytes, 240353280 sectors
Disk model: SanDisk 3.2Gen1
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000
Device Boot Start End Sectors Size Id Type
/dev/sdc1 * 64 6786991 6786928 3.2G 0 Empty
/dev/sdc2 6786992 6795183 8192 4M ef EFI (FAT-12/16/32)
Disk /dev/sdd: 931.48 GiB, 1000170586112 bytes, 1953458176 sectors
Disk model: Elements SE 25FE
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 31237251-69F5-426A-8693-C4BA01C39123
Device Start End Sectors Size Type
/dev/sdd1 2048 1953456127 1953454080 931.5G Microsoft basic data
sda is the problematic drive. If it got wiped, I would be shocked. It still had 250 gb worth of data on it, and I didn’t select that drive to be wiped, as far as I’m aware. And if it were wiped during install, surely that would have wiped the partitions as well?
IIRC it’s also called ReFS and there is no open source driver to mount/read those.
There seems to be a proprietary driver
I’d try to get that to that data by sticking that ssd into a windows machine and then copy the relevant parts.
If you’re knowledgable enough you could try creating a windows vm and directly passthrough the ssd to that vm. If all works well, the windows vm might be able to read that partition.
2 Likes
Didn’t even think about a VM. I’ll try thay when I get home from work.
Yup. After a little bit of fiddling, the Windows VM read it perfectly. Files are copying to an external HD now. Sucks I’ve got to reformat the SSD, but it is what it is. Thank you so much!
1 Like
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.