A colleague at work has a Kingston 240GB SSD drive which has come out of a now dead computer. We want to be able to recover some data from it (no backups sadly) however the drive won't mount properly.
I am using an Anker USB3 external HDD enclosure which I know to be working correctly. The drive has come from an Apple computer, and we are attempting recovery on another MacBook Pro.
The drive appears under DiskUtility, however is greyed out. Trying to click mount
does nothing. FirstAid also fails.
What Have We Tried?
So far, we've run diskutil repairVolume disk2s2
which gave the following output:
Repairing file system
Volume is already unmounted
Performing fsck_hfs -fy -x /dev/rdisk2s2
Checking Journaled HFS Plus volume
Invalid record count
Checking extents overflow file
Invalid record count
The volume could not be verified completely
File system check exit code is 8
Restoring the original state found as unmounted
Error: -69845: File system verify or repair failed
Underlying error: 8: Exec format error
We have also run sudo /sbin/fsck_hfs -yprd /dev/disk2s2
which returned:
/dev/rdisk2s2: starting
journal_replay(/dev/disk2s2) returned 0
Using cacheBlockSize=32K cacheTotalBlock=65536 cacheSize=2097152K.
Executing fsck_hfs (version hfs-407.50.6).
** Checking Journaled HFS Plus volume.
hfs_swap_BTNode: invalid forward link (0xFFFFFFFF)
hfs_swap_BTNode: invalid backward link (0xFFFFFFFF)
hfs_swap_BTNode: invalid node height (255)
hfs_swap_BTNode: invalid record count (0xFFFF)
Invalid record count
(4, 25511)
...repeats similar output...
Node 35746's back link is 0x0; expected 0x8c17
disk offset = 0x78f41000, size = 0x2000
Invalid sibling link
(4, 35746)
Node 35746's forward link is 0x0; expected 0x6489
disk offset = 0x78f41000, size = 0x2000
Invalid node height
(4, 35746)
Index key doesn't match first node key
Invalid index key
(4, 35746)
** The volume could not be verified completely.
volume check failed with error 7
volume type is pure HFS+
primary MDB is at block 0 0x00
alternate MDB is at block 0 0x00
primary VHB is at block 2 0x02
alternate VHB is at block 467182910 0x1bd8a53e
sector size = 512 0x200
VolumeObject flags = 0x07
total sectors for volume = 467182912 0x1bd8a540
total sectors for embedded volume = 0 0x00
CheckForClean - could not get VHB/MDB at block 467182910
CheckHFS returned -1317, fsmodified = 1
What Next?
I am hopeful that with the drive being recognised, the data is still recoverable. Before looking at paid software such as DiskWarrior, is there anything else that I can try so that I can access the disk or to repair this record count
problem.
OS Extended (Journaled)
and the correct 240GB capacity. The old computer had problems with the screen and keyboard and belongs to a friend of my colleague, so I'm several people down the chain from the original problem. I don't know the full details, but the drive was removed before the other components were repaired, and then wasn't replaced as the data was more important. Does this seem like a hardware failure, or just corrupted sectors (forgive my terminology).