0

I have an SSD drive that was used with Windows 10 and suddenly stopped working. To recover the data, I made an image of the drive in Linux by:

ddrescue /dev/sda ssd_rescue.img ssd_rescue.log

No errors or bad blocks were found. Then, fdisk -l ssd_rescue.img gave this:

Disk ssd_rescue.img: 119,2 GiB, 128035676160 bytes, 250069680 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

No partitions found. I ran

parted
unit GB
print

No disk label found. Then,

mklabel msdos
mkpart primary ntfs 0% 100%

This set the primary partition to cover the whole disk. In fdisk, I marked this partition as boot. This is what fdisk -l ssd_rescue.img shows now:

Disk ssd_rescue.img: 119,2 GiB, 128035676160 bytes, 250069680 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
Disklabel type: dos
Disk identifier: 0x4d91e75c

Device          Boot Start       End   Sectors   Size Id Type
ssd_rescue.img1 *     2048 250068991 250066944 119,2G  7 HPFS/NTFS/exFAT

Now it looks promising. The partition is there, but I cannot mount it (the offset is the start of the partition: 2048*512=1048576):

mount -o loop,offset=1048576,ro -t ntfs ssd_rescue.img ssd/

which gives the error message:

NTFS signature is missing.
Failed to mount '/dev/loop4': Invalid argument
The device '/dev/loop4' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?

I tried also testdisk to analyze the disk with this result:

Disk ssd_rescue.img - 128 GB / 119 GiB - CHS 1953670 4 32
Current partition structure:
     Partition                  Start        End    Size in sectors

Invalid NTFS or EXFAT boot
 1 * HPFS - NTFS             16   0  1 1953663   3 32  250066944
 1 * HPFS - NTFS             16   0  1 1953663   3 32  250066944

Not sure why partition 1 is there twice. Neither Quick Search nor Deeper Search was able to fix it. Can someone, please, help me where to take it from here?

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.