I'm trying to recover data from a damaged SSD, I successfully

>>61773330
dam son

>>61773330
fyle systum?

File: 1482147939067.jpg (35KB, 200x200px) Image search: [Google]

35KB, 200x200px

>>61773330
>SSD
>recovery

>>61773510
ntfs....

I found the start of the second partition at 264192 with fdisk -l

then to confirm:

dd if=/dev/sdb bs=512 count=1 skip=264192 2>/dev/null | hexdump -C | head -n 1

got

>.R.NTFS ........

So, I'm creating a second image starting at that sector.

>>61773580
I believe its not physical damage, I was copying shit then I unplugged the cable by mistake.

Windows shits itself when I try to run chkdsk

>>61773607
SSDs don't suffer from physical damage. 99% of the time, the controller dies. Once the controller is dead, any data you pull from it is just random bits. SSDs dies randomly and you cannot recover them.

you're just wasting your time. recover from backups.

>>61773644
I do have backups, but they are weeks old...

And the image does seem to have valid data in it...

>>61773667
>And the image does seem to have valid data in it...
it pulls data randomly so there's bound to be some contiguous valid date. good luck figuring out bad bytes.

>>61773721
The SSD was in a usb enclosure.

I think the enclosure fucked up and messed up some sectors, maybe the partition table.

I'll try to mount the partition once the 2nd image is done copying

>>61773922
try another usb enclosure

>>61774035
I did, same issue