SSD No Longer Being Recognized?

axsc · 2024-11-08 15:57:32

Hello,

I was using my PC as normal and it suddenly crashed (mouse still moved, audio was still playing, but nothing else was responsive). Upon hard rebooting my PC it booted directly to BIOS. On the BIOS main page, under "Storage", my SSD was no longer listed. I clicked Boot Options and it gave me a pop up saying, "System cannot find any bootable devices."

Here's what I tried:
1. Disabling/enabling CSM
2. Disabling/enabling secure boot
3. Changing EXPO settings from EXPO Tweaked to EXPO 1
4. Reseated SSD, using different cable and different SATA slot

None of these changed anything. I then booted into a bootable Ubuntu USB drive.
When I first booted into the USB I used fdisk -l to display my partitions. My SSD (/dev/sda) was recognized.

Opening the "Disks" utility on Ubuntu, my SSD is recognizable. However, all storage partitions' 'Partition Types' are now listed as "unknown".
When I attempt to mount the SSD I get the error:

mount: /mnt: can't read superblock on /dev/sda1.

I get the same error message regardless of which partition on the SSD I'm trying to mount.

I then try to use parted:

parted /dev/sda

(parted) p

This is the output:

Error: /dev/sda: unrecognized disk label
Model: ATA Samsung SSD 870 (scsi)
Disk /dev/sda: 1000GB
Sector size (logical/physical): 512B/512B
Partition Table: unknown
Disk Flags:

After doing all that, I did fdisk -l again, and now my SSD (/dev/sda) is no longer showing up...
lsblk does still show /dev/sda and its partitions.

I then tried testdisk, which recognizes the SSD, and chose "Analyse". This gives me an error:

Partition: Read error

The only option I can choose is [Quick Search], which I do.
After scanning it only shows the disk itself:

Disk /dev/sda - 1000 GB / 931 GB - CHS 121601 255 63

But there's nothing listed under Partition, Start, End, Size in sectors
My only options are:

Keys A: add partition, L: load backup, Enter: to continue

I press enter to continue, and it gives me an error message: No partition found or selected for recovery
I then try a Deeper Search. Again, no partitions are listed.

I then attempt to use ddrescue. Currently it's in the process of writing an image to an external drive. However, it seems this process isn't able to read/recover anything

rescued: 0 B
pct rescued: 0.00%

At this point I'm stumped. Is there any way to fix this? At the very least I'd like to be able to access my Linux partition and recover some files. I already have a replacement SSD on the way (Hynix Platinum p41 2TB). Thanks in advance.

Specs:
Mobo: ASUS B650E-F
CPU: Ryzen 7700x
GPU: ASUS 4070 Ti
SSD: Samsung 870 Evo 1TB (purchased in 2021)
RAM: TEAMGROUP T-Force Vulcan DDR5 32GB Kit (2x16GB) 5600MHz

Last edited by axsc (2024-11-08 17:32:23)

CookieMuncher · 2024-11-08 17:27:27

Your SSD is definitely dying, you might try tools like testdisk or similar but I am not sure if this can be done at home or if you need to let a professional recover the data. If it keeps disconnecting and reconnecting that will surely mess up conventional tools. Try it though, can't get worse than it is now

axsc · 2024-11-08 17:34:13

CookieMuncher wrote:

Your SSD is definitely dying, you might try tools like testdisk or similar but I am not sure if this can be done at home or if you need to let a professional recover the data. If it keeps disconnecting and reconnecting that will surely mess up conventional tools. Try it though, can't get worse than it is now

I've tried testdisk and it doesn't show any partitions (though the drive itself is visible).
I'm in the process of trying ddrescue but it's currently showing that 0 B of data has been rescued. For some reason it's not able to read anything on the drive at all.

seth · 2024-11-08 20:45:04

On the live system, check the system journal or dmesg for errors - there's certainly IO ones, maybe bus ones.
Can you connect the disk to a different motherboard?
If you're "lucky", it's the SATA controller (and maybe just the firmware) rather than the disk itself.

dd_rescue will likely not help - the thing that dies on SSDs is the controller, NAND itself at some point wears down and can no longer be written, but hold data extremely stable.
And if the SSD controller is fried, the disk becomes inaccessible and you'll have to attach the NAND modules to an equivalent controller (you realistically meaning some data rescue service) in order to access it again.

axsc · 2024-11-08 20:55:45

seth wrote:

On the live system, check the system journal or dmesg for errors - there's certainly IO ones, maybe bus ones.
Can you connect the disk to a different motherboard?
If you're "lucky", it's the SATA controller (and maybe just the firmware) rather than the disk itself.
dd_rescue will likely not help - the thing that dies on SSDs is the controller, NAND itself at some point wears down and can no longer be written, but hold data extremely stable.
And if the SSD controller is fried, the disk becomes inaccessible and you'll have to attach the NAND modules to an equivalent controller (you realistically meaning some data rescue service) in order to access it again.

Thanks for your response.
I don't have another motherboard available to me at the moment but I might be able to bring it to a friend's house later to try.

Regarding the second part of your post: what do you think the odds are of being able to recover my data if I bring it to a professional? The SSD is only 3-4 years old and it just abruptly stopped working. My BIOS doesn't recognize it, but a live USB does.
lsblk recognizes the drive and its partitions.
fdisk -l recognizes the drive and its partitions.
The Ubuntu (live USB) Disks application recognizes the drive and its partitions, but lists the partition types as "unknown".
testdisk recognizes the drive but NOT the partititions.
ddrescue recognizes the drive but cannot recover ANY data to an img file.

Is there anything you can extrapolate from this? Thank you.

seth · 2024-11-08 21:08:43

Is there anything you can extrapolate from this?

It sound like flicker (the controller responds and then fails) but why, whether it's the disk or board controller - or you're super unlucky w/ your cables - is impossasible to tell.
If the dmesg shows lots of unrelated PCI errors, it's probably more the board, but those could also be induced by the drive failure.

If the service suggests they can recover the drive, there's an extremely high likelyhood for a 100% recovery (unless you forgot to mention that the disk was briefly on fire or so ) because the storage modules themselves rarely fail for reading. It's however likely still cost quite some money.

dd_rescue is more relevant on magnetic disks, because you "often" lose sectors w/o the controller being affected at all.
But when the drives firmware* doesn't work, the entire drive fails, not just some sectors.

*You could attempt a firmware update, but on a malfunctioning device that's not a good idea and might easily turn a bus problem into a disk controller problem.
So I'd NOT! "just try" that to see what happens.

axsc · 2024-11-08 21:15:16

seth wrote:

Is there anything you can extrapolate from this?
It sound like flicker (the controller responds and then fails) but why, whether it's the disk or board controller - or you're super unlucky w/ your cables - is impossasible to tell.
If the dmesg shows lots of unrelated PCI errors, it's probably more the board, but those could also be induced by the drive failure.

I tried 'dmesg | grep sda' earlier and it gave me a whole bunch of I/O errors. You have any idea what could that be, and do you think that could be recoverable by a pro?

*You could attempt a firmware update, but on a malfunctioning device that's not a good idea and might easily turn a bus problem into a disk controller problem.
So I'd NOT! "just try" that to see what happens.

Yeah the data is pretty valuable so I unplugged it and I'm not gonna touch it myself anymore in case it's on its very last legs.

Thanks again!!

seth · 2024-11-08 21:37:26

You have any idea what could that be

IO errors
Ideally post the entire dmesg, otherwise it's impoosible to comment on this beyond what you assert it is.

do you think that could be recoverable by a pro?

This has really much more to do w/ the particular controller used and how complicated the model is to re-assemble.
The service will likely ask for brand, model and serial number and then tell you whether they offer services for that.

The error messages can hint at the broken link in the chain (but so will testing against your friends system) - if it ends up being the disk controller, that will have to be replaced, regardless whether it's an intermittent or permanent failure. You cannot reliably read the memory otherwise.

axsc · 2024-11-08 21:52:13

seth wrote:

You have any idea what could that be
IO errors
Ideally post the entire dmesg, otherwise it's impoosible to comment on this beyond what you assert it is.
do you think that could be recoverable by a pro?
This has really much more to do w/ the particular controller used and how complicated the model is to re-assemble.
The service will likely ask for brand, model and serial number and then tell you whether they offer services for that.
The error messages can hint at the broken link in the chain (but so will testing against your friends system) - if it ends up being the disk controller, that will have to be replaced, regardless whether it's an intermittent or permanent failure. You cannot reliably read the memory otherwise.

I would post the dmesg but I'm afraid of plugging it in, in case of further damage. I think at this point my best course of action is to take it to a professional. Thanks Seth!

seth · 2024-11-08 22:44:13

It's not super-likely that you aggrevate the situation merely by powering up the device and trying to access it, but you can of course combine this w/ the test against your friends system to reduce the access to a minimum.

axsc · 2024-11-08 22:53:12

seth wrote:

It's not super-likely that you aggrevate the situation merely by powering up the device and trying to access it, but you can of course combine this w/ the test against your friends system to reduce the access to a minimum.

Ok I'll give it a shot. Are there any other tests you suggest I do?

seth · 2024-11-08 23:02:16

Testing against a different SATA controller and firmware and recording the kernel log (don't grep!) will tell if and what further steps to take.
If it randomly happens to work on your friends system, secure your data from the drive immediately - this might just be temporarily if there's a degradation that's just less exposed on that system and the data rescue service will cost you much more than a new disk.

axsc · 2024-11-08 23:14:04

seth wrote:

Testing against a different SATA controller and firmware and recording the kernel log (don't grep!) will tell if and what further steps to take.
If it randomly happens to work on your friends system, secure your data from the drive immediately - this might just be temporarily if there's a degradation that's just less exposed on that system and the data rescue service will cost you much more than a new disk.

Ok, what's the best way to record the kernel log (they're often quite large aren't they)?

seth · 2024-11-09 07:42:40

Redirect it into a file on some usb key (nb. that live distros may or not offer mounts to persistent storage, but the immediate filesystem is typically transient) or the internet:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

axsc · 2024-11-09 17:10:56

seth wrote:

Redirect it into a file on some usb key (nb. that live distros may or not offer mounts to persistent storage, but the immediate filesystem is typically transient) or the internet:
sudo journalctl -b | curl -F 'file=@-' 0x0.st

I just tried it on a friend's PC. It was also not recognized by their BIOS.
Here is the journalctl: https://0x0.st/XD6K.txt
This is dmesg (no grep): https://0x0.st/XD6Z.txt
This is lsblk: https://0x0.st/XD6b.txt
This is fdisk -l:

ubuntu@ubuntu:~$ sudo fdisk -l
Disk /dev/loop0: 2.54 GiB, 2731876352 bytes, 5335696 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop1: 4 KiB, 4096 bytes, 8 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop2: 63.28 MiB, 66355200 bytes, 129600 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop3: 346.33 MiB, 363151360 bytes, 709280 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop4: 240.61 MiB, 252301312 bytes, 492776 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop5: 304 KiB, 311296 bytes, 608 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop6: 45.93 MiB, 48160768 bytes, 94064 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop7: 91.69 MiB, 96141312 bytes, 187776 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
The backup GPT table is corrupt, but the primary appears OK, so that will be used.


Disk /dev/sda: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: Samsung SSD 870 
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: 14C4BD10-045E-4D10-9BBC-5ACAB1604C70

Device           Start        End    Sectors   Size Type
/dev/sda1         2048    1050623    1048576   512M EFI System
/dev/sda5   1952602112 1953525134     923023 450.7M Microsoft basic data
/dev/sda6   1748418560 1952602111  204183552  97.4G Linux filesystem
/dev/sda100  368082944  368492543     409600   200M BIOS boot
/dev/sda101  368492544  385269759   16777216     8G Linux swap
/dev/sda102  385269760 1748418559 1363148800   650G Linux filesystem

Partition table entries are not in disk order.


Disk /dev/sdb: 58.23 GiB, 62528684032 bytes, 122126336 sectors
Disk model: Storage Media   
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: A0891D7E-B930-4513-94D9-F629DBD637B2

Device       Start       End   Sectors  Size Type
/dev/sdb1       64   9613459   9613396  4.6G Microsoft basic data
/dev/sdb2  9613460   9623527     10068  4.9M EFI System
/dev/sdb3  9623528   9624127       600  300K Microsoft basic data
/dev/sdb4  9625600 122126272 112500673 53.6G Linux filesystem


Disk /dev/loop8: 49.84 MiB, 52260864 bytes, 102072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

And this is dmesg | grep sda:

ubuntu@ubuntu:~$ sudo dmesg | grep sda
[   81.925210] sd 3:0:0:0: [sda] tag#5 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=1s
[   81.925212] sd 3:0:0:0: [sda] tag#5 Sense Key : Illegal Request [current] 
[   81.925213] sd 3:0:0:0: [sda] tag#5 Add. Sense: Unaligned write command
[   81.925215] sd 3:0:0:0: [sda] tag#5 CDB: Write(10) 2a 00 65 da ec 38 00 00 10 00
[   81.925216] I/O error, dev sda, sector 1708846136 op 0x1:(WRITE) flags 0x800 phys_seg 2 prio class 0
[   81.925220] Buffer I/O error on dev sda102, logical block 165447047, lost async page write
[   81.925227] Buffer I/O error on dev sda102, logical block 165447048, lost async page write
[   81.945178] sd 3:0:0:0: [sda] tag#8 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=1s
[   81.945180] sd 3:0:0:0: [sda] tag#8 Sense Key : Illegal Request [current] 
[   81.945181] sd 3:0:0:0: [sda] tag#8 Add. Sense: Unaligned write command
[   81.945182] sd 3:0:0:0: [sda] tag#8 CDB: Write(10) 2a 00 65 da eb 98 00 00 10 00
[   81.945183] I/O error, dev sda, sector 1708845976 op 0x1:(WRITE) flags 0x800 phys_seg 2 prio class 0
[   81.945185] Buffer I/O error on dev sda102, logical block 165447027, lost async page write
[   81.945189] Buffer I/O error on dev sda102, logical block 165447028, lost async page write
[   81.965186] sd 3:0:0:0: [sda] tag#11 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=1s
[   81.965188] sd 3:0:0:0: [sda] tag#11 Sense Key : Illegal Request [current] 
[   81.965189] sd 3:0:0:0: [sda] tag#11 Add. Sense: Unaligned write command
[   81.965190] sd 3:0:0:0: [sda] tag#11 CDB: Write(10) 2a 00 65 da ea e0 00 00 08 00
[   81.965191] I/O error, dev sda, sector 1708845792 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0
[   81.965194] Buffer I/O error on dev sda102, logical block 165447004, lost async page write
[   81.985172] sd 3:0:0:0: [sda] tag#14 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=1s
[   81.985174] sd 3:0:0:0: [sda] tag#14 Sense Key : Illegal Request [current] 
[   81.985176] sd 3:0:0:0: [sda] tag#14 Add. Sense: Unaligned write command
[   81.985177] sd 3:0:0:0: [sda] tag#14 CDB: Write(10) 2a 00 65 da ea 88 00 00 10 00
[   81.985178] I/O error, dev sda, sector 1708845704 op 0x1:(WRITE) flags 0x800 phys_seg 2 prio class 0
[   81.985180] Buffer I/O error on dev sda102, logical block 165446993, lost async page write
[   81.985184] Buffer I/O error on dev sda102, logical block 165446994, lost async page write
[   82.005157] sd 3:0:0:0: [sda] tag#17 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=1s
[   82.005159] sd 3:0:0:0: [sda] tag#17 Sense Key : Illegal Request [current] 
[   82.005160] sd 3:0:0:0: [sda] tag#17 Add. Sense: Unaligned write command
[   82.005161] sd 3:0:0:0: [sda] tag#17 CDB: Write(10) 2a 00 65 da ea 58 00 00 10 00
[   82.005162] I/O error, dev sda, sector 1708845656 op 0x1:(WRITE) flags 0x800 phys_seg 2 prio class 0
[   82.005165] Buffer I/O error on dev sda102, logical block 165446987, lost async page write
[   82.005169] Buffer I/O error on dev sda102, logical block 165446988, lost async page write
[   82.025213] sd 3:0:0:0: [sda] tag#29 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=1s
[   82.025215] sd 3:0:0:0: [sda] tag#29 Sense Key : Illegal Request [current] 
[   82.025216] sd 3:0:0:0: [sda] tag#29 Add. Sense: Unaligned write command
[   82.025218] sd 3:0:0:0: [sda] tag#29 CDB: Write(10) 2a 00 65 da ea 30 00 00 08 00
[   82.025218] I/O error, dev sda, sector 1708845616 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0
[   82.025221] Buffer I/O error on dev sda102, logical block 165446982, lost async page write
[   82.045151] sd 3:0:0:0: [sda] tag#20 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=1s
[   82.045153] sd 3:0:0:0: [sda] tag#20 Sense Key : Illegal Request [current] 
[   82.045155] sd 3:0:0:0: [sda] tag#20 Add. Sense: Unaligned write command
[   82.045156] sd 3:0:0:0: [sda] tag#20 CDB: Write(10) 2a 00 65 da e9 d8 00 00 08 00
[   82.045156] I/O error, dev sda, sector 1708845528 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0
[   82.065236] sd 3:0:0:0: [sda] tag#1 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=1s
[   82.065238] sd 3:0:0:0: [sda] tag#1 Sense Key : Illegal Request [current] 
[   82.065239] sd 3:0:0:0: [sda] tag#1 Add. Sense: Unaligned write command
[   82.065241] sd 3:0:0:0: [sda] tag#1 CDB: Write(10) 2a 00 65 da e4 f0 00 00 08 00
[   82.065241] I/O error, dev sda, sector 1708844272 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0
[   82.085187] sd 3:0:0:0: [sda] tag#23 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=1s
[   82.085189] sd 3:0:0:0: [sda] tag#23 Sense Key : Illegal Request [current] 
[   82.085190] sd 3:0:0:0: [sda] tag#23 Add. Sense: Unaligned write command
[   82.085191] sd 3:0:0:0: [sda] tag#23 CDB: Write(10) 2a 00 65 da e2 20 00 00 08 00
[   82.085192] I/O error, dev sda, sector 1708843552 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0
[   82.105186] sd 3:0:0:0: [sda] tag#25 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=1s
[   82.105188] sd 3:0:0:0: [sda] tag#25 Sense Key : Illegal Request [current] 
[   82.105189] sd 3:0:0:0: [sda] tag#25 Add. Sense: Unaligned write command
[   82.105190] sd 3:0:0:0: [sda] tag#25 CDB: Write(10) 2a 00 65 da de f0 00 00 08 00
[   82.105191] I/O error, dev sda, sector 1708842736 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0
[   84.529152] EXT4-fs (sda102): error loading journal
[   84.602583] EXT4-fs (sda6): mounted filesystem with ordered data mode. Quota mode: none.
[   84.602885] EXT4-fs (sda6): unmounting filesystem.
[   95.023749] Adding 8388604k swap on /dev/sda101.  Priority:-2 extents:1 across:8388604k SSFS
[  118.389230] sd 3:0:0:0: [sda] tag#11 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
[  118.389232] sd 3:0:0:0: [sda] tag#11 Sense Key : Illegal Request [current] 
[  118.389233] sd 3:0:0:0: [sda] tag#11 Add. Sense: Unaligned write command
[  118.389234] sd 3:0:0:0: [sda] tag#11 CDB: Synchronize Cache(10) 35 00 00 00 00 00 00 00 00 00
[  118.389236] I/O error, dev sda, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0
[  119.237271] sd 3:0:0:0: [sda] tag#8 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
[  119.237273] sd 3:0:0:0: [sda] tag#8 Sense Key : Illegal Request [current] 
[  119.237274] sd 3:0:0:0: [sda] tag#8 Add. Sense: Unaligned write command
[  119.237274] sd 3:0:0:0: [sda] tag#8 CDB: Synchronize Cache(10) 35 00 00 00 00 00 00 00 00 00
[  119.237276] I/O error, dev sda, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0
[  131.069115] sd 3:0:0:0: [sda] tag#22 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=11s
[  131.069117] sd 3:0:0:0: [sda] tag#22 CDB: Synchronize Cache(10) 35 00 00 00 00 00 00 00 00 00
[  131.069118] I/O error, dev sda, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0
[  131.069171] sd 3:0:0:0: [sda] tag#10 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
[  131.069174] sd 3:0:0:0: [sda] tag#10 CDB: Read(10) 28 00 68 36 c0 00 00 00 20 00
[  131.069175] I/O error, dev sda, sector 1748418560 op 0x0:(READ) flags 0x80700 phys_seg 4 prio class 0
[  131.069196] sd 3:0:0:0: [sda] tag#14 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
[  131.069197] sd 3:0:0:0: [sda] tag#14 CDB: Read(10) 28 00 68 36 c0 00 00 00 08 00
[  131.069197] I/O error, dev sda, sector 1748418560 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[  131.069199] Buffer I/O error on dev sda6, logical block 0, async page read
[  131.069216] sd 3:0:0:0: [sda] tag#11 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
[  131.069217] sd 3:0:0:0: [sda] tag#11 CDB: Read(10) 28 00 68 36 c0 00 00 00 08 00
[  131.069218] I/O error, dev sda, sector 1748418560 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[  131.069219] Buffer I/O error on dev sda6, logical block 0, async page read
[  131.069266] sd 3:0:0:0: [sda] tag#15 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
[  131.069267] sd 3:0:0:0: [sda] tag#15 CDB: Read(10) 28 00 68 36 c0 00 00 00 20 00
[  131.069267] I/O error, dev sda, sector 1748418560 op 0x0:(READ) flags 0x80700 phys_seg 4 prio class 0
[  131.069277] sd 3:0:0:0: [sda] tag#12 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
[  131.069279] sd 3:0:0:0: [sda] tag#12 CDB: Read(10) 28 00 68 36 c0 00 00 00 08 00
[  131.069279] I/O error, dev sda, sector 1748418560 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[  131.069281] Buffer I/O error on dev sda6, logical block 0, async page read
[  131.069289] sd 3:0:0:0: [sda] tag#16 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
[  131.069290] sd 3:0:0:0: [sda] tag#16 CDB: Read(10) 28 00 68 36 c0 00 00 00 08 00
[  131.069290] I/O error, dev sda, sector 1748418560 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[  131.069291] Buffer I/O error on dev sda6, logical block 0, async page read
[  132.391241] sd 3:0:0:0: [sda] tag#13 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
[  132.391246] sd 3:0:0:0: [sda] tag#13 CDB: ATA command pass through(16) 85 06 20 00 00 00 00 00 00 00 00 00 00 00 e5 00
[  132.391574] sd 3:0:0:0: [sda] tag#14 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
[  132.391576] sd 3:0:0:0: [sda] tag#14 CDB: ATA command pass through(16) 85 06 20 00 00 00 00 00 00 00 00 00 00 00 e5 00
[  132.392291] sd 3:0:0:0: [sda] tag#18 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
[  132.392293] sd 3:0:0:0: [sda] tag#18 CDB: Read(10) 28 00 16 f6 c0 00 00 00 20 00
[  132.392294] I/O error, dev sda, sector 385269760 op 0x0:(READ) flags 0x80700 phys_seg 4 prio class 0
[  132.392313] I/O error, dev sda, sector 385269760 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[  132.392317] Buffer I/O error on dev sda102, logical block 0, async page read
[  132.392330] I/O error, dev sda, sector 385269760 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[  132.392332] Buffer I/O error on dev sda102, logical block 0, async page read
[  132.392368] Buffer I/O error on dev sda102, logical block 0, async page read
[  132.392376] Buffer I/O error on dev sda102, logical block 0, async page read
[  132.393411] Buffer I/O error on dev sda6, logical block 0, async page read
[  132.393420] Buffer I/O error on dev sda6, logical block 0, async page read
[  155.343533] I/O error, dev sda, sector 1050496 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[  155.343535] sd 3:0:0:0: [sda] tag#23 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
[  155.343535] sd 3:0:0:0: [sda] tag#9 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
[  155.343538] sd 3:0:0:0: [sda] tag#9 CDB: Read(10) 28 00 15 f6 bf 80 00 00 08 00
[  155.343538] sd 3:0:0:0: [sda] tag#23 CDB: Read(10) 28 00 68 36 bf 80 00 00 08 00
[  155.343538] I/O error, dev sda, sector 1748418432 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[  155.343539] I/O error, dev sda, sector 368492416 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[  155.343546] sd 3:0:0:0: [sda] tag#20 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
[  155.343547] sd 3:0:0:0: [sda] tag#20 CDB: Read(10) 28 00 00 10 07 80 00 00 08 00
[  155.343548] I/O error, dev sda, sector 1050496 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[  155.343550] Buffer I/O error on dev sda1, logical block 131056, async page read
[  155.343552] sd 3:0:0:0: [sda] tag#10 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
[  155.343553] sd 3:0:0:0: [sda] tag#10 CDB: Read(10) 28 00 68 36 bf 80 00 00 08 00
[  155.343554] I/O error, dev sda, sector 1748418432 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[  155.343555] Buffer I/O error on dev sda102, logical block 170393584, async page read
[  155.343558] sd 3:0:0:0: [sda] tag#11 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
[  155.343559] sd 3:0:0:0: [sda] tag#11 CDB: Read(10) 28 00 74 70 6d 00 00 00 01 00
[  155.343560] I/O error, dev sda, sector 1953524992 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[  155.343561] Buffer I/O error on dev sda5, logical block 922880, async page read
[  155.343563] sd 3:0:0:0: [sda] tag#12 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
[  155.343564] sd 3:0:0:0: [sda] tag#12 CDB: Read(10) 28 00 15 f6 bf 80 00 00 08 00
[  155.343564] I/O error, dev sda, sector 368492416 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[  155.343565] Buffer I/O error on dev sda100, logical block 51184, async page read
[  155.343566] sd 3:0:0:0: [sda] tag#31 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
[  155.343569] sd 3:0:0:0: [sda] tag#31 CDB: Read(10) 28 00 74 62 57 80 00 00 08 00
[  155.343569] I/O error, dev sda, sector 1952601984 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[  155.343571] sd 3:0:0:0: [sda] tag#14 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
[  155.343572] sd 3:0:0:0: [sda] tag#14 CDB: Read(10) 28 00 74 70 6d 01 00 00 01 00
[  155.343572] I/O error, dev sda, sector 1953524993 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[  155.343573] Buffer I/O error on dev sda5, logical block 922881, async page read
[  155.343578] sd 3:0:0:0: [sda] tag#15 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
[  155.343579] sd 3:0:0:0: [sda] tag#15 CDB: Read(10) 28 00 74 70 6d 02 00 00 01 00
[  155.343579] I/O error, dev sda, sector 1953524994 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[  155.343580] Buffer I/O error on dev sda5, logical block 922882, async page read
[  155.343582] sd 3:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
[  155.343583] sd 3:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 74 62 57 80 00 00 08 00
[  155.343584] Buffer I/O error on dev sda6, logical block 25522928, async page read
[  155.343584] Buffer I/O error on dev sda5, logical block 922883, async page read
[  155.343588] Buffer I/O error on dev sda5, logical block 922884, async page read
[  155.343592] Buffer I/O error on dev sda5, logical block 922885, async page read
[  226.052207] sd 3:0:0:0: [sda] tag#21 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
[  226.052209] sd 3:0:0:0: [sda] tag#21 CDB: Read(10) 28 00 74 70 6d 88 00 00 18 00
[  226.052210] I/O error, dev sda, sector 1953525128 op 0x0:(READ) flags 0x80700 phys_seg 3 prio class 0
[  226.052220] sd 3:0:0:0: [sda] tag#22 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
[  226.052221] sd 3:0:0:0: [sda] tag#22 CDB: Read(10) 28 00 74 70 6d 88 00 00 08 00
[  226.052221] I/O error, dev sda, sector 1953525128 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[  226.052222] Buffer I/O error on dev sda, logical block 244190641, async page read
[  300.611890] sd 3:0:0:0: [sda] tag#30 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
[  300.611894] sd 3:0:0:0: [sda] tag#30 CDB: Read(10) 28 00 74 70 6d 00 00 00 08 00
[  300.611894] I/O error, dev sda, sector 1953524992 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[  300.611903] sd 3:0:0:0: [sda] tag#1 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
[  300.611905] sd 3:0:0:0: [sda] tag#2 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
[  300.611905] sd 3:0:0:0: [sda] tag#1 CDB: Read(10) 28 00 00 10 07 80 00 00 08 00
[  300.611906] sd 3:0:0:0: [sda] tag#2 CDB: Read(10) 28 00 74 70 6d 00 00 00 01 00
[  300.611906] I/O error, dev sda, sector 1050496 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[  300.611906] I/O error, dev sda, sector 1953524992 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[  300.611908] Buffer I/O error on dev sda5, logical block 922880, async page read
[  300.611912] sd 3:0:0:0: [sda] tag#3 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
[  300.611912] sd 3:0:0:0: [sda] tag#3 CDB: Read(10) 28 00 74 70 6d 01 00 00 01 00
[  300.611913] I/O error, dev sda, sector 1953524993 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[  300.611914] Buffer I/O error on dev sda5, logical block 922881, async page read
[  300.611919] sd 3:0:0:0: [sda] tag#6 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
[  300.611919] sd 3:0:0:0: [sda] tag#4 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
[  300.611920] sd 3:0:0:0: [sda] tag#6 CDB: Read(10) 28 00 00 10 07 80 00 00 08 00
[  300.611920] sd 3:0:0:0: [sda] tag#4 CDB: Read(10) 28 00 74 70 6d 06 00 00 01 00
[  300.611920] I/O error, dev sda, sector 1050496 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[  300.611921] I/O error, dev sda, sector 1953524998 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[  300.611921] Buffer I/O error on dev sda5, logical block 922886, async page read
[  300.611922] Buffer I/O error on dev sda1, logical block 131056, async page read
[  300.611924] sd 3:0:0:0: [sda] tag#5 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
[  300.611924] sd 3:0:0:0: [sda] tag#7 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
[  300.611925] sd 3:0:0:0: [sda] tag#5 CDB: Read(10) 28 00 74 70 6d 07 00 00 01 00
[  300.611925] sd 3:0:0:0: [sda] tag#7 CDB: Read(10) 28 00 74 70 6d 02 00 00 03 00
[  300.611926] I/O error, dev sda, sector 1953524999 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[  300.611926] I/O error, dev sda, sector 1953524994 op 0x0:(READ) flags 0x0 phys_seg 3 prio class 0
[  300.611926] Buffer I/O error on dev sda5, logical block 922887, async page read
[  300.611927] Buffer I/O error on dev sda5, logical block 922882, async page read
[  300.611928] Buffer I/O error on dev sda5, logical block 922883, async page read
[  300.611929] Buffer I/O error on dev sda5, logical block 922884, async page read
[  300.611931] sd 3:0:0:0: [sda] tag#8 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
[  300.611932] sd 3:0:0:0: [sda] tag#8 CDB: Read(10) 28 00 74 70 6d 05 00 00 01 00
[  300.611933] I/O error, dev sda, sector 1953524997 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[  300.611934] Buffer I/O error on dev sda5, logical block 922885, async page read
[  300.611995] I/O error, dev sda, sector 1952601984 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[  300.611996] sd 3:0:0:0: [sda] tag#9 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
[  300.611997] sd 3:0:0:0: [sda] tag#9 CDB: Read(10) 28 00 15 f6 bf 80 00 00 08 00
[  300.612006] Buffer I/O error on dev sda6, logical block 25522928, async page read
[  320.045745] sd 3:0:0:0: [sda] tag#17 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
[  320.045747] sd 3:0:0:0: [sda] tag#17 CDB: Read(10) 28 00 74 70 6d 00 00 00 08 00
[  320.045749] I/O error, dev sda, sector 1953524992 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[  320.045764] sd 3:0:0:0: [sda] tag#14 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
[  320.045765] sd 3:0:0:0: [sda] tag#14 CDB: Read(10) 28 00 74 70 6d 00 00 00 08 00
[  320.045766] I/O error, dev sda, sector 1953524992 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[  320.045768] Buffer I/O error on dev sda, logical block 244190624, async page read
[  320.047289] sd 3:0:0:0: [sda] tag#23 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
[  320.047291] sd 3:0:0:0: [sda] tag#23 CDB: Read(10) 28 00 74 70 6d 00 00 00 08 00
[  320.047292] I/O error, dev sda, sector 1953524992 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[  320.047297] sd 3:0:0:0: [sda] tag#10 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
[  320.047299] sd 3:0:0:0: [sda] tag#10 CDB: Read(10) 28 00 74 62 57 80 00 00 08 00
[  320.047299] I/O error, dev sda, sector 1952601984 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[  320.047302] sd 3:0:0:0: [sda] tag#26 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
[  320.047303] sd 3:0:0:0: [sda] tag#26 CDB: Read(10) 28 00 74 70 6d 00 00 00 01 00
[  320.047303] I/O error, dev sda, sector 1953524992 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[  320.047304] Buffer I/O error on dev sda5, logical block 922880, async page read
[  320.047309] sd 3:0:0:0: [sda] tag#27 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
[  320.047310] sd 3:0:0:0: [sda] tag#27 CDB: Read(10) 28 00 74 70 6d 01 00 00 01 00
[  320.047310] I/O error, dev sda, sector 1953524993 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[  320.047311] Buffer I/O error on dev sda5, logical block 922881, async page read
[  320.047313] sd 3:0:0:0: [sda] tag#15 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
[  320.047314] sd 3:0:0:0: [sda] tag#28 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
[  320.047315] sd 3:0:0:0: [sda] tag#28 CDB: Read(10) 28 00 74 70 6d 02 00 00 01 00
[  320.047315] I/O error, dev sda, sector 1953524994 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[  320.047315] sd 3:0:0:0: [sda] tag#15 CDB: Read(10) 28 00 15 f6 bf 80 00 00 08 00
[  320.047316] Buffer I/O error on dev sda5, logical block 922882, async page read
[  320.047316] I/O error, dev sda, sector 368492416 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[  320.047318] sd 3:0:0:0: [sda] tag#29 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
[  320.047319] sd 3:0:0:0: [sda] tag#29 CDB: Read(10) 28 00 74 70 6d 03 00 00 01 00
[  320.047319] sd 3:0:0:0: [sda] tag#16 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
[  320.047319] I/O error, dev sda, sector 1953524995 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[  320.047320] Buffer I/O error on dev sda5, logical block 922883, async page read
[  320.047320] sd 3:0:0:0: [sda] tag#16 CDB: Read(10) 28 00 74 62 57 80 00 00 08 00
[  320.047321] I/O error, dev sda, sector 1952601984 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[  320.047322] Buffer I/O error on dev sda6, logical block 25522928, async page read
[  320.047323] Buffer I/O error on dev sda5, logical block 922884, async page read
[  320.047326] Buffer I/O error on dev sda5, logical block 922885, async page read
[  320.047330] Buffer I/O error on dev sda5, logical block 922886, async page read
[  320.047331] Buffer I/O error on dev sda100, logical block 51184, async page read

What do you think?

seth · 2024-11-09 18:02:06

Nov 09 16:47:55 ubuntu kernel: ata4.00: status: { DRDY ERR }
Nov 09 16:47:55 ubuntu kernel: ata4.00: error: { ABRT }
Nov 09 16:47:55 ubuntu kernel: ata4.00: supports DRM functions and may not be fully accessible
Nov 09 16:47:55 ubuntu kernel: ata4.00: failed to enable AA (error_mask=0x1)
Nov 09 16:47:55 ubuntu kernel: ata4.00: supports DRM functions and may not be fully accessible
Nov 09 16:47:55 ubuntu kernel: ata4.00: failed to enable AA (error_mask=0x1)
Nov 09 16:47:55 ubuntu kernel: ata4.00: configured for UDMA/133 (device error ignored)
Nov 09 16:47:55 ubuntu kernel: ata4: EH complete
Nov 09 16:47:55 ubuntu kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Nov 09 16:47:55 ubuntu kernel: ata4.00: irq_stat 0x40000001
Nov 09 16:47:55 ubuntu kernel: ata4.00: failed command: WRITE DMA EXT
Nov 09 16:47:55 ubuntu kernel: ata4.00: cmd 35/00:08:e0:ca:da/00:00:65:00:00/e0 tag 20 dma 4096 out
                                        res 51/04:08:e0:ca:da/00:00:65:00:00/e0 Emask 0x1 (device error)

"device error"

https://bbs.archlinux.org/viewtopic.php?id=280545 - but
1. You do still seem to have access to the/a partition table though?
2. no power loss involved, right?

The partition table looks messy, though - was that the case before?
Yes.
Your valuable data is on "sda102" (the 650GB partition)?
Have you tried to mount that?
Or dd it (the partition, not the drive)?
Can you dd /dev/sda5 ? (That should run quick, it's < 500MB)
There's a windows partition… can you still boot windows?

Last edited by seth (2024-11-09 18:03:14)

axsc · 2024-11-09 18:58:08

seth wrote:

1. You do still seem to have access to the/a partition table though?

Sorry, what do you mean by this?

2. no power loss involved, right?

No, however, when it initially crashed yesterday I had to hard reboot the PC (holding the power button down)

The partition table looks messy, though - was that the case before?
Yes.

Yeah I installed all this over a decade ago. The current broken SSD was cloned in 2021. Looks like my ignorance has caught up to me.

Your valuable data is on "sda102" (the 650GB partition)?

Yes, it's all there.

Have you tried to mount that?

Yeah I tried:

mount: /mnt: can't read superblock on /dev/sda102.

Or dd it (the partition, not the drive)?
Can you dd /dev/sda5 ? (That should run quick, it's < 500MB)

I only tried to ddrescue the whole drive, but I waited long enough during that process that it should've already went through /dev/sda5

There's a windows partition… can you still boot windows?

No, nothing is mountable or bootable. BIOS does not recognize it even as storage.

seth · 2024-11-09 19:26:23

The drive firmware still responds and you can even read the partition table, but not much more

mount: /mnt: can't read superblock on /dev/sda102.

Does that result in lots of IO errors?

I only tried to ddrescue the whole drive

Don't waste any time w/ that, see whether you can read any of the relevant blocks into an image that you can then apply testdisk on.

Looks like my ignorance has caught up to me.

I don't think that the weird partitioning is any cause here - it just might have been reflective of a corrupted table.

But you might be in the position of the other user and the internal block assignment is gone.
Make sure any data rescue service charges you based on success…

axsc · 2024-11-09 22:13:39

seth wrote:

Does that result in lots of IO errors?

When I tried it, that was the only output I got.

Don't waste any time w/ that, see whether you can read any of the relevant blocks into an image that you can then apply testdisk on.

Testdisk unfortunately cannot recognize any partitions.

Make sure any data rescue service charges you based on success…

I'm planning to go to a service this week. Thanks for the tip!

seth · 2024-11-10 08:03:12

Testdisk unfortunately cannot recognize any partitions.

Don't try to operate it on the drive, you'll run into problems w/ the IO errors.
If anything, you'll need to get blocks from the drive you can salvage onto a sane medium and run data recovery tools on that.

Thanks for the tip!

It's mostly because if the internal block assignment is gone, there's little hope.

Arch Linux

#1 2024-11-08 15:57:32

SSD No Longer Being Recognized?

#2 2024-11-08 17:27:27

Re: SSD No Longer Being Recognized?

#3 2024-11-08 17:34:13

Re: SSD No Longer Being Recognized?

#4 2024-11-08 20:45:04

Re: SSD No Longer Being Recognized?

#5 2024-11-08 20:55:45

Re: SSD No Longer Being Recognized?

#6 2024-11-08 21:08:43

Re: SSD No Longer Being Recognized?

#7 2024-11-08 21:15:16

Re: SSD No Longer Being Recognized?

#8 2024-11-08 21:37:26

Re: SSD No Longer Being Recognized?

#9 2024-11-08 21:52:13

Re: SSD No Longer Being Recognized?

#10 2024-11-08 22:44:13

Re: SSD No Longer Being Recognized?

#11 2024-11-08 22:53:12

Re: SSD No Longer Being Recognized?

#12 2024-11-08 23:02:16

Re: SSD No Longer Being Recognized?

#13 2024-11-08 23:14:04

Re: SSD No Longer Being Recognized?

#14 2024-11-09 07:42:40

Re: SSD No Longer Being Recognized?

#15 2024-11-09 17:10:56

Re: SSD No Longer Being Recognized?

#16 2024-11-09 18:02:06

Re: SSD No Longer Being Recognized?

#17 2024-11-09 18:58:08

Re: SSD No Longer Being Recognized?

#18 2024-11-09 19:26:23

Re: SSD No Longer Being Recognized?

#19 2024-11-09 22:13:39

Re: SSD No Longer Being Recognized?

#20 2024-11-10 08:03:12

Re: SSD No Longer Being Recognized?

Board footer