External 1TB usb3 HDD recovery help

Using PhotoRec to recover lost data
Forum rules
When asking for technical support:
- Search for posts on the same topic before posting a new question.
- Give clear, specific information in the title of your post.
- Include as many details as you can, MOST POSTS WILL GET ONLY ONE OR TWO ANSWERS.
- Post a follow up with a "Thank you" or "This worked!"
- When you learn something, use that knowledge to HELP ANOTHER USER LATER.
Before posting, please read https://www.cgsecurity.org/testdisk.pdf
Locked
Message
Author
tripis
Posts: 1
Joined: 15 May 2016, 12:11

External 1TB usb3 HDD recovery help

#1 Post by tripis »

Greetings

I have an external 1TB USB3 HDD with all my mp3s in it. About a week ago I had connected the disk on my laptop tried to do "safety remove" but for some reason it just didn’t work. After 30 minutes of waiting for my hdd to be "safety removed" I just unplugged the usb. As it turned out that was a lethal mistake.

When i connected again my hdd on my windows pc i was prompted to format it. I tried to connect my drive on a linux machine as well as on a mac without luck. I got a bit of a panic so I started to research how am I going to recover. What i have done so far is:

1) Imaged the disk using ddrescue.
I successfully managed to clone the disk. However when I try to mount the image on my Linux system I get the following error:

Code: Select all

sudo mount -t ntfs -o loop,ro hdd.img ~/Desktop/workbench/mnt/
[sudo] password for ratb0y: 
NTFS signature is missing.
Failed to mount '/dev/loop0': Invalid argument
The device '/dev/loop0' 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 also opened the image file using testdisk and did a quicksearch on the image. However, when i try to list the files (p option), i get "no file found file system may be damaged"


2) Used testdisk on the physical disk.
Testdisk was able to recognize the disk including the ntfs partition. I took the risk to "write" the MBR to the disk which took alot of time (about 20 min). After that, when I plugged again the hdd on my pc I noticed that my system was able to verify the drive. Meaning, I could see my hdd device in my GUI. However, when I tried to access my drive (which means my system tried to mount it) I got the below errors on my syslog:

Code: Select all

May 15 13:15:24 beasty kernel: [69493.201921] usb 2-6: new SuperSpeed USB device number 2 using xhci_hcd
May 15 13:15:24 beasty kernel: [69493.218464] usb 2-6: New USB device found, idVendor=0480, idProduct=a200
May 15 13:15:24 beasty kernel: [69493.218467] usb 2-6: New USB device strings: Mfr=2, Product=3, SerialNumber=1
May 15 13:15:24 beasty kernel: [69493.218469] usb 2-6: Product: External USB 3.0
May 15 13:15:24 beasty kernel: [69493.218470] usb 2-6: Manufacturer: TOSHIBA
May 15 13:15:24 beasty kernel: [69493.218471] usb 2-6: SerialNumber: 20150127002059F
May 15 13:15:24 beasty kernel: [69493.220205] usb-storage 2-6:1.0: USB Mass Storage device detected
May 15 13:15:24 beasty kernel: [69493.220346] scsi host5: usb-storage 2-6:1.0
May 15 13:15:24 beasty mtp-probe: checking bus 2, device 2: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-6"
May 15 13:15:24 beasty mtp-probe: bus: 2, device: 2 was not an MTP device
May 15 13:15:25 beasty kernel: [69494.220686] scsi 5:0:0:0: Direct-Access     TOSHIBA  External USB 3.0 0    PQ: 0 ANSI: 6
May 15 13:15:25 beasty kernel: [69494.221210] sd 5:0:0:0: Attached scsi generic sg2 type 0
May 15 13:15:28 beasty kernel: [69497.025683] sd 5:0:0:0: [sdc] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
May 15 13:15:28 beasty kernel: [69497.025904] sd 5:0:0:0: [sdc] Write Protect is off
May 15 13:15:28 beasty kernel: [69497.025907] sd 5:0:0:0: [sdc] Mode Sense: 43 00 00 00
May 15 13:15:28 beasty kernel: [69497.026102] sd 5:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
May 15 13:15:28 beasty kernel: [69497.032244]  sdc: sdc1
May 15 13:15:28 beasty kernel: [69497.033560] sd 5:0:0:0: [sdc] Attached SCSI disk

May 15 13:17:06 beasty kernel: [69595.375397] sd 5:0:0:0: [sdc] FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
May 15 13:17:06 beasty kernel: [69595.375401] sd 5:0:0:0: [sdc] Sense Key : Medium Error [current] 
May 15 13:17:06 beasty kernel: [69595.375402] sd 5:0:0:0: [sdc] Add. Sense: Unrecovered read error
May 15 13:17:06 beasty kernel: [69595.375404] sd 5:0:0:0: [sdc] CDB: Read(10) 28 00 00 60 08 08 00 00 08 00
May 15 13:17:06 beasty kernel: [69595.375405] blk_update_request: critical medium error, dev sdc, sector 6293512
May 15 13:17:10 beasty kernel: [69599.214494] sd 5:0:0:0: [sdc] FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
May 15 13:17:10 beasty kernel: [69599.214497] sd 5:0:0:0: [sdc] Sense Key : Medium Error [current] 
May 15 13:17:10 beasty kernel: [69599.214499] sd 5:0:0:0: [sdc] Add. Sense: Unrecovered read error
May 15 13:17:10 beasty kernel: [69599.214501] sd 5:0:0:0: [sdc] CDB: Read(10) 28 00 00 60 08 08 00 00 01 00
May 15 13:17:10 beasty kernel: [69599.214502] blk_update_request: critical medium error, dev sdc, sector 6293512
May 15 13:17:10 beasty kernel: [69599.214505] Buffer I/O error on dev sdc1, logical block 6291464, async page read
May 15 13:17:14 beasty kernel: [69603.053589] sd 5:0:0:0: [sdc] FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
May 15 13:17:14 beasty kernel: [69603.053593] sd 5:0:0:0: [sdc] Sense Key : Medium Error [current] 
May 15 13:17:14 beasty kernel: [69603.053596] sd 5:0:0:0: [sdc] Add. Sense: Unrecovered read error
May 15 13:17:14 beasty kernel: [69603.053598] sd 5:0:0:0: [sdc] CDB: Read(10) 28 00 00 60 08 09 00 00 01 00
May 15 13:17:14 beasty kernel: [69603.053600] blk_update_request: critical medium error, dev sdc, sector 6293513
May 15 13:17:14 beasty kernel: [69603.053603] Buffer I/O error on dev sdc1, logical block 6291465, async page read
May 15 13:17:18 beasty kernel: [69606.892684] sd 5:0:0:0: [sdc] FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
May 15 13:17:18 beasty kernel: [69606.892689] sd 5:0:0:0: [sdc] Sense Key : Medium Error [current] 
May 15 13:17:18 beasty kernel: [69606.892691] sd 5:0:0:0: [sdc] Add. Sense: Unrecovered read error
May 15 13:17:18 beasty kernel: [69606.892694] sd 5:0:0:0: [sdc] CDB: Read(10) 28 00 00 60 08 0a 00 00 06 00
May 15 13:17:18 beasty kernel: [69606.892697] blk_update_request: critical medium error, dev sdc, sector 6293514
May 15 13:17:18 beasty kernel: [69606.892700] Buffer I/O error on dev sdc1, logical block 6291466, async page read
May 15 13:17:18 beasty kernel: [69606.892703] Buffer I/O error on dev sdc1, logical block 6291467, async page read
May 15 13:17:18 beasty kernel: [69606.892704] Buffer I/O error on dev sdc1, logical block 6291468, async page read
May 15 13:17:18 beasty kernel: [69606.892706] Buffer I/O error on dev sdc1, logical block 6291469, async page read
May 15 13:17:18 beasty kernel: [69606.892707] Buffer I/O error on dev sdc1, logical block 6291470, async page read
May 15 13:17:18 beasty kernel: [69606.892709] Buffer I/O error on dev sdc1, logical block 6291471, async page read
May 15 13:20:52 beasty kernel: [69821.216432] INFO: task mount.ntfs:10711 blocked for more than 120 seconds.
May 15 13:20:52 beasty kernel: [69821.216435]       Tainted: P           OE   4.2.0-27-generic #32-Ubuntu
May 15 13:20:52 beasty kernel: [69821.216436] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
May 15 13:20:52 beasty kernel: [69821.216437] mount.ntfs      D ffff88021ec16640     0 10711  10710 0x00000000
May 15 13:20:52 beasty kernel: [69821.216440]  ffff880136a07cc8 0000000000000082 ffffffff81c13500 ffff88011fb10000
May 15 13:20:52 beasty kernel: [69821.216441]  01ffffff00000011 ffff880136a08000 ffff880136a07e20 ffff880136a07e18
May 15 13:20:52 beasty kernel: [69821.216443]  ffff88011fb10000 000056057498c360 ffff880136a07ce8 ffffffff817edc37
May 15 13:20:52 beasty kernel: [69821.216444] Call Trace:
May 15 13:20:52 beasty kernel: [69821.216449]  [<ffffffff817edc37>] schedule+0x37/0x80
May 15 13:20:52 beasty kernel: [69821.216452]  [<ffffffff817f0cd9>] schedule_timeout+0x189/0x250
May 15 13:20:52 beasty kernel: [69821.216454]  [<ffffffff8139a9d5>] ? blk_queue_bio+0x325/0x330
May 15 13:20:52 beasty kernel: [69821.216457]  [<ffffffff81184fa5>] ? mempool_alloc_slab+0x15/0x20
May 15 13:20:52 beasty kernel: [69821.216459]  [<ffffffff817ee653>] wait_for_completion+0xb3/0x140
May 15 13:20:52 beasty kernel: [69821.216461]  [<ffffffff810a61d0>] ? wake_up_q+0x70/0x70
May 15 13:20:52 beasty kernel: [69821.216463]  [<ffffffff8138f8cb>] submit_bio_wait+0x6b/0x90
May 15 13:20:52 beasty kernel: [69821.216465]  [<ffffffff8139c601>] blkdev_issue_flush+0x61/0x90
May 15 13:20:52 beasty kernel: [69821.216468]  [<ffffffff81237855>] blkdev_fsync+0x35/0x50
May 15 13:20:52 beasty kernel: [69821.216469]  [<ffffffff812304bb>] vfs_fsync_range+0x4b/0xb0
May 15 13:20:52 beasty kernel: [69821.216471]  [<ffffffff8123057d>] do_fsync+0x3d/0x70
May 15 13:20:52 beasty kernel: [69821.216472]  [<ffffffff81230820>] SyS_fsync+0x10/0x20
May 15 13:20:52 beasty kernel: [69821.216473]  [<ffffffff817f1c72>] entry_SYSCALL_64_fastpath+0x16/0x75
May 15 13:20:52 beasty kernel: [69821.216475] INFO: task testdisk:10730 blocked for more than 120 seconds.
May 15 13:20:52 beasty kernel: [69821.216476]       Tainted: P           OE   4.2.0-27-generic #32-Ubuntu
May 15 13:20:52 beasty kernel: [69821.216476] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
May 15 13:20:52 beasty kernel: [69821.216477] testdisk        D ffff88021ec16640     0 10730  10729 0x00000000
May 15 13:20:52 beasty kernel: [69821.216479]  ffff880136af3ae8 0000000000000086 ffffffff81c13500 ffff8800a0fe1b80
May 15 13:20:52 beasty kernel: [69821.216480]  ffff880136af3b18 ffff880136af4000 ffff88021ec16640 7fffffffffffffff
May 15 13:20:52 beasty kernel: [69821.216481]  ffffffff817ee430 ffff880136af3c80 ffff880136af3b08 ffffffff817edc37
May 15 13:20:52 beasty kernel: [69821.216482] Call Trace:
May 15 13:20:52 beasty kernel: [69821.216484]  [<ffffffff817ee430>] ? bit_wait+0x50/0x50
May 15 13:20:52 beasty kernel: [69821.216485]  [<ffffffff817edc37>] schedule+0x37/0x80
May 15 13:20:52 beasty kernel: [69821.216487]  [<ffffffff817f0cd9>] schedule_timeout+0x189/0x250
May 15 13:20:52 beasty kernel: [69821.216488]  [<ffffffff81395c96>] ? submit_bio+0x76/0x170
May 15 13:20:52 beasty kernel: [69821.216491]  [<ffffffff8101dcc9>] ? read_tsc+0x9/0x10
May 15 13:20:52 beasty kernel: [69821.216492]  [<ffffffff817ee430>] ? bit_wait+0x50/0x50
May 15 13:20:52 beasty kernel: [69821.216494]  [<ffffffff817ed244>] io_schedule_timeout+0xa4/0x110
May 15 13:20:52 beasty kernel: [69821.216495]  [<ffffffff810bd1a4>] ? prepare_to_wait+0x54/0x80
May 15 13:20:52 beasty kernel: [69821.216497]  [<ffffffff817ee465>] bit_wait_io+0x35/0x50
May 15 13:20:52 beasty kernel: [69821.216498]  [<ffffffff817edffd>] __wait_on_bit+0x5d/0x90
May 15 13:20:52 beasty kernel: [69821.216500]  [<ffffffff81237150>] ? I_BDEV+0x20/0x20
May 15 13:20:52 beasty kernel: [69821.216501]  [<ffffffff81237c90>] ? blkdev_readpages+0x20/0x20
May 15 13:20:52 beasty kernel: [69821.216503]  [<ffffffff81181b8b>] wait_on_page_bit+0xcb/0xf0
May 15 13:20:52 beasty kernel: [69821.216504]  [<ffffffff810bd7a0>] ? autoremove_wake_function+0x40/0x40
May 15 13:20:52 beasty kernel: [69821.216506]  [<ffffffff81181db9>] wait_on_page_read+0x49/0x50
May 15 13:20:52 beasty kernel: [69821.216508]  [<ffffffff811833fd>] do_read_cache_page+0x8d/0x1b0
May 15 13:20:52 beasty kernel: [69821.216509]  [<ffffffff81183539>] read_cache_page+0x19/0x20
May 15 13:20:52 beasty kernel: [69821.216512]  [<ffffffff813aaf4d>] read_dev_sector+0x2d/0x90
May 15 13:20:52 beasty kernel: [69821.216514]  [<ffffffff8157ad90>] scsi_bios_ptable+0x50/0xe0
May 15 13:20:52 beasty kernel: [69821.216515]  [<ffffffff8157ae3b>] scsicam_bios_param+0x1b/0x170
May 15 13:20:52 beasty kernel: [69821.216517]  [<ffffffff8158ca1c>] sd_getgeo+0xac/0xc0
May 15 13:20:52 beasty kernel: [69821.216518]  [<ffffffff813a733b>] blkdev_ioctl+0x2fb/0x6c0
May 15 13:20:52 beasty kernel: [69821.216519]  [<ffffffff8123874d>] block_ioctl+0x3d/0x50
May 15 13:20:52 beasty kernel: [69821.216521]  [<ffffffff812110b5>] do_vfs_ioctl+0x295/0x480
May 15 13:20:52 beasty kernel: [69821.216524]  [<ffffffff81202da4>] ? SYSC_newfstat+0x34/0x60
May 15 13:20:52 beasty kernel: [69821.216525]  [<ffffffff81211319>] SyS_ioctl+0x79/0x90
May 15 13:20:52 beasty kernel: [69821.216526]  [<ffffffff817f1c72>] entry_SYSCALL_64_fastpath+0x16/0x75
May 15 13:22:52 beasty kernel: [69941.390293] INFO: task mount.ntfs:10711 blocked for more than 120 seconds.
May 15 13:22:52 beasty kernel: [69941.390296]       Tainted: P           OE   4.2.0-27-generic #32-Ubuntu
May 15 13:22:52 beasty kernel: [69941.390296] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
May 15 13:22:52 beasty kernel: [69941.390297] mount.ntfs      D ffff88021ec16640     0 10711  10710 0x00000000
May 15 13:22:52 beasty kernel: [69941.390300]  ffff880136a07cc8 0000000000000082 ffffffff81c13500 ffff88011fb10000
May 15 13:22:52 beasty kernel: [69941.390302]  01ffffff00000011 ffff880136a08000 ffff880136a07e20 ffff880136a07e18
May 15 13:22:52 beasty kernel: [69941.390303]  ffff88011fb10000 000056057498c360 ffff880136a07ce8 ffffffff817edc37
May 15 13:22:52 beasty kernel: [69941.390304] Call Trace:
May 15 13:22:52 beasty kernel: [69941.390309]  [<ffffffff817edc37>] schedule+0x37/0x80
May 15 13:22:52 beasty kernel: [69941.390311]  [<ffffffff817f0cd9>] schedule_timeout+0x189/0x250
May 15 13:22:52 beasty kernel: [69941.390314]  [<ffffffff8139a9d5>] ? blk_queue_bio+0x325/0x330
May 15 13:22:52 beasty kernel: [69941.390317]  [<ffffffff81184fa5>] ? mempool_alloc_slab+0x15/0x20
May 15 13:22:52 beasty kernel: [69941.390318]  [<ffffffff817ee653>] wait_for_completion+0xb3/0x140
May 15 13:22:52 beasty kernel: [69941.390321]  [<ffffffff810a61d0>] ? wake_up_q+0x70/0x70
May 15 13:22:52 beasty kernel: [69941.390323]  [<ffffffff8138f8cb>] submit_bio_wait+0x6b/0x90
May 15 13:22:52 beasty kernel: [69941.390325]  [<ffffffff8139c601>] blkdev_issue_flush+0x61/0x90
May 15 13:22:52 beasty kernel: [69941.390327]  [<ffffffff81237855>] blkdev_fsync+0x35/0x50
May 15 13:22:52 beasty kernel: [69941.390329]  [<ffffffff812304bb>] vfs_fsync_range+0x4b/0xb0
May 15 13:22:52 beasty kernel: [69941.390330]  [<ffffffff8123057d>] do_fsync+0x3d/0x70
May 15 13:22:52 beasty kernel: [69941.390331]  [<ffffffff81230820>] SyS_fsync+0x10/0x20
May 15 13:22:52 beasty kernel: [69941.390332]  [<ffffffff817f1c72>] entry_SYSCALL_64_fastpath+0x16/0x75
May 15 13:22:52 beasty kernel: [69941.390334] INFO: task testdisk:10730 blocked for more than 120 seconds.
May 15 13:22:52 beasty kernel: [69941.390335]       Tainted: P           OE   4.2.0-27-generic #32-Ubuntu
May 15 13:22:52 beasty kernel: [69941.390335] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
May 15 13:22:52 beasty kernel: [69941.390336] testdisk        D ffff88021ec16640     0 10730  10729 0x00000000
May 15 13:22:52 beasty kernel: [69941.390337]  ffff880136af3ae8 0000000000000086 ffffffff81c13500 ffff8800a0fe1b80
May 15 13:22:52 beasty kernel: [69941.390339]  ffff880136af3b18 ffff880136af4000 ffff88021ec16640 7fffffffffffffff
May 15 13:22:52 beasty kernel: [69941.390340]  ffffffff817ee430 ffff880136af3c80 ffff880136af3b08 ffffffff817edc37
May 15 13:22:52 beasty kernel: [69941.390341] Call Trace:
May 15 13:22:52 beasty kernel: [69941.390343]  [<ffffffff817ee430>] ? bit_wait+0x50/0x50
May 15 13:22:52 beasty kernel: [69941.390344]  [<ffffffff817edc37>] schedule+0x37/0x80
May 15 13:22:52 beasty kernel: [69941.390345]  [<ffffffff817f0cd9>] schedule_timeout+0x189/0x250
May 15 13:22:52 beasty kernel: [69941.390347]  [<ffffffff81395c96>] ? submit_bio+0x76/0x170
May 15 13:22:52 beasty kernel: [69941.390349]  [<ffffffff8101dcc9>] ? read_tsc+0x9/0x10
May 15 13:22:52 beasty kernel: [69941.390351]  [<ffffffff817ee430>] ? bit_wait+0x50/0x50
May 15 13:22:52 beasty kernel: [69941.390352]  [<ffffffff817ed244>] io_schedule_timeout+0xa4/0x110
May 15 13:22:52 beasty kernel: [69941.390354]  [<ffffffff810bd1a4>] ? prepare_to_wait+0x54/0x80
May 15 13:22:52 beasty kernel: [69941.390355]  [<ffffffff817ee465>] bit_wait_io+0x35/0x50
May 15 13:22:52 beasty kernel: [69941.390356]  [<ffffffff817edffd>] __wait_on_bit+0x5d/0x90
May 15 13:22:52 beasty kernel: [69941.390358]  [<ffffffff81237150>] ? I_BDEV+0x20/0x20
May 15 13:22:52 beasty kernel: [69941.390359]  [<ffffffff81237c90>] ? blkdev_readpages+0x20/0x20
May 15 13:22:52 beasty kernel: [69941.390361]  [<ffffffff81181b8b>] wait_on_page_bit+0xcb/0xf0
May 15 13:22:52 beasty kernel: [69941.390362]  [<ffffffff810bd7a0>] ? autoremove_wake_function+0x40/0x40
May 15 13:22:52 beasty kernel: [69941.390364]  [<ffffffff81181db9>] wait_on_page_read+0x49/0x50
May 15 13:22:52 beasty kernel: [69941.390365]  [<ffffffff811833fd>] do_read_cache_page+0x8d/0x1b0
May 15 13:22:52 beasty kernel: [69941.390367]  [<ffffffff81183539>] read_cache_page+0x19/0x20
May 15 13:22:52 beasty kernel: [69941.390369]  [<ffffffff813aaf4d>] read_dev_sector+0x2d/0x90
May 15 13:22:52 beasty kernel: [69941.390371]  [<ffffffff8157ad90>] scsi_bios_ptable+0x50/0xe0
May 15 13:22:52 beasty kernel: [69941.390372]  [<ffffffff8157ae3b>] scsicam_bios_param+0x1b/0x170
May 15 13:22:52 beasty kernel: [69941.390374]  [<ffffffff8158ca1c>] sd_getgeo+0xac/0xc0
May 15 13:22:52 beasty kernel: [69941.390375]  [<ffffffff813a733b>] blkdev_ioctl+0x2fb/0x6c0
May 15 13:22:52 beasty kernel: [69941.390376]  [<ffffffff8123874d>] block_ioctl+0x3d/0x50
May 15 13:22:52 beasty kernel: [69941.390378]  [<ffffffff812110b5>] do_vfs_ioctl+0x295/0x480
May 15 13:22:52 beasty kernel: [69941.390380]  [<ffffffff81202da4>] ? SYSC_newfstat+0x34/0x60
May 15 13:22:52 beasty kernel: [69941.390381]  [<ffffffff81211319>] SyS_ioctl+0x79/0x90
May 15 13:22:52 beasty kernel: [69941.390382]  [<ffffffff817f1c72>] entry_SYSCALL_64_fastpath+0x16/0x75
May 15 13:23:18 beasty kernel: [69967.417413] sd 5:0:0:0: timing out command, waited 360s
May 15 13:23:18 beasty kernel: [69967.417418] blk_update_request: I/O error, dev sdc, sector 0
May 15 13:24:20 beasty kernel: [70029.993941]  sdc: sdc1
I thought that most provably my disk was about to RIP so i went to get a smart status:

Code: Select all

smartctl -a -d sat /dev/sdc
smartctl 6.4 2014-10-07 r4002 [x86_64-linux-4.2.0-27-generic] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Toshiba 2.5" HDD MQ01UBD... (USB 3.0)
Device Model:     TOSHIBA MQ01UBD100
Serial Number:    15R3TL0TT
LU WWN Device Id: 0 000000 000000000
Firmware Version: AX001U
User Capacity:    1.000.204.886.016 bytes [1,00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Form Factor:      2.5 inches
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS (minor revision not indicated)
SATA Version is:  SATA 2.6, 3.0 Gb/s (current: 3.0 Gb/s)
Local Time is:    Sun May 15 13:41:27 2016 EEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x00)	Offline data collection activity
					was never started.
					Auto Offline Data Collection: Disabled.
Self-test execution status:      (   0)	The previous self-test routine completed
					without error or no self-test has ever 
					been run.
Total time to complete Offline 
data collection: 		(  120) seconds.
Offline data collection
capabilities: 			 (0x5b) SMART execute Offline immediate.
					Auto Offline data collection on/off support.
					Suspend Offline collection upon new
					command.
					Offline surface scan supported.
					Self-test supported.
					No Conveyance Self-test supported.
					Selective Self-test supported.
SMART capabilities:            (0x0003)	Saves SMART data before entering
					power-saving mode.
					Supports SMART auto save timer.
Error logging capability:        (0x01)	Error logging supported.
					General Purpose Logging supported.
Short self-test routine 
recommended polling time: 	 (   2) minutes.
Extended self-test routine
recommended polling time: 	 ( 241) minutes.
SCT capabilities: 	       (0x003d)	SCT Status supported.
					SCT Error Recovery Control supported.
					SCT Feature Control supported.
					SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000b   100   100   050    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0005   100   100   050    Pre-fail  Offline      -       0
  3 Spin_Up_Time            0x0027   100   100   001    Pre-fail  Always       -       2602
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       490
  5 Reallocated_Sector_Ct   0x0033   100   100   050    Pre-fail  Always       -       8
  7 Seek_Error_Rate         0x000b   100   100   050    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0005   100   100   050    Pre-fail  Offline      -       0
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       183
 10 Spin_Retry_Count        0x0033   109   100   030    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       192
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       2
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       49
193 Load_Cycle_Count        0x0032   100   100   000    Old_age   Always       -       2117
194 Temperature_Celsius     0x0022   100   100   000    Old_age   Always       -       31 (Min/Max 15/52)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       1
197 Current_Pending_Sector  0x0032   100   100   000    Old_age   Always       -       5264
198 Offline_Uncorrectable   0x0030   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   253   000    Old_age   Always       -       0
220 Disk_Shift              0x0002   100   100   000    Old_age   Always       -       61
222 Loaded_Hours            0x0032   100   100   000    Old_age   Always       -       124
223 Load_Retry_Count        0x0032   100   100   000    Old_age   Always       -       0
224 Load_Friction           0x0022   100   100   000    Old_age   Always       -       0
226 Load-in_Time            0x0026   100   100   000    Old_age   Always       -       181
240 Head_Flying_Hours       0x0001   100   100   001    Pre-fail  Offline      -       0

SMART Error Log Version: 1
ATA Error Count: 1377 (device log contains only the most recent five errors)
	CR = Command Register [HEX]
	FR = Features Register [HEX]
	SC = Sector Count Register [HEX]
	SN = Sector Number Register [HEX]
	CL = Cylinder Low Register [HEX]
	CH = Cylinder High Register [HEX]
	DH = Device/Head Register [HEX]
	DC = Device Command Register [HEX]
	ER = Error register [HEX]
	ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 1377 occurred at disk power-on lifetime: 182 hours (7 days + 14 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 06 0a 08 60 40  Error: UNC 6 sectors at LBA = 0x0060080a = 6293514

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 03 06 0a 08 60 40 00      00:01:50.216  READ DMA EXT
  25 03 01 09 08 60 40 00      00:01:46.382  READ DMA EXT
  25 03 01 08 08 60 40 00      00:01:42.548  READ DMA EXT
  25 03 08 08 08 60 40 00      00:01:38.714  READ DMA EXT
  25 03 08 80 08 00 40 00      00:01:38.714  READ DMA EXT

Error 1376 occurred at disk power-on lifetime: 182 hours (7 days + 14 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 01 09 08 60 40  Error: UNC 1 sectors at LBA = 0x00600809 = 6293513

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 03 01 09 08 60 40 00      00:01:46.382  READ DMA EXT
  25 03 01 08 08 60 40 00      00:01:42.548  READ DMA EXT
  25 03 08 08 08 60 40 00      00:01:38.714  READ DMA EXT
  25 03 08 80 08 00 40 00      00:01:38.714  READ DMA EXT
  25 03 08 00 08 60 40 00      00:01:38.410  READ DMA EXT

Error 1375 occurred at disk power-on lifetime: 182 hours (7 days + 14 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 01 08 08 60 40  Error: UNC 1 sectors at LBA = 0x00600808 = 6293512

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 03 01 08 08 60 40 00      00:01:42.548  READ DMA EXT
  25 03 08 08 08 60 40 00      00:01:38.714  READ DMA EXT
  25 03 08 80 08 00 40 00      00:01:38.714  READ DMA EXT
  25 03 08 00 08 60 40 00      00:01:38.410  READ DMA EXT
  25 03 20 00 08 00 40 00      00:01:38.408  READ DMA EXT

Error 1374 occurred at disk power-on lifetime: 182 hours (7 days + 14 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 08 08 08 60 40  Error: UNC 8 sectors at LBA = 0x00600808 = 6293512

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 03 08 08 08 60 40 00      00:01:38.714  READ DMA EXT
  25 03 08 80 08 00 40 00      00:01:38.714  READ DMA EXT
  25 03 08 00 08 60 40 00      00:01:38.410  READ DMA EXT
  25 03 20 00 08 00 40 00      00:01:38.408  READ DMA EXT
  25 03 08 00 00 00 40 00      00:00:04.552  READ DMA EXT

Error 1373 occurred at disk power-on lifetime: 182 hours (7 days + 14 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 08 08 08 60 40  Error: UNC 8 sectors at LBA = 0x00600808 = 6293512

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 08 08 08 60 40 00      00:10:32.627  READ DMA EXT
  25 00 08 08 08 60 40 00      00:10:28.526  READ DMA EXT
  25 00 08 08 08 60 40 00      00:08:14.096  READ DMA EXT
  25 00 08 08 08 60 40 00      00:08:06.874  READ DMA EXT
  e7 00 08 00 00 00 00 00      00:08:06.870  FLUSH CACHE

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

As far as I understand, the facts are:
1) MBR of disk was damaged. I recovered the MBR using testdisk but the hdd still cant be used because is dying. So, hdd is useless
2) Image of the hdd still cant be mounted because MBR is damaged (since it was cloned from the damaged hdd)

My question is:
If a get the "fixed" mbr from the physical hdd, and copy it to the image disk, will i be able to mount and browse the files inside the image?

Is there any way i could make the image file mountable and browsable?

User avatar
cgrenier
Site Admin
Posts: 5432
Joined: 18 Feb 2012, 15:08
Location: Le Perreux Sur Marne, France
Contact:

Re: External 1TB usb3 HDD recovery help

#2 Post by cgrenier »

Code: Select all

sudo losetup -f
sudo losetup /dev/loop0 hdd.img
sudo partprobe /dev/loop0
sudo fsck.ntfs /dev/loop0p1
sudo mount /dev/loop0p1 ~/Desktop/workbench/mnt/
If it still failed

Code: Select all

sudo ntfsfix /dev/loop0p1
sudo mount /dev/loop0p1 ~/Desktop/workbench/mnt/
If it doesn't work, you can always try PhotoRec to recover your data. After selecting the partition, choose [Whole] instead of [Free]

Locked