After pressing enter on quick search to find lost partitions, there is no response

How to use TestDisk to recover lost partition
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
Post Reply
Message
Author
Synapse
Posts: 2
Joined: 03 Aug 2019, 09:42

After pressing enter on quick search to find lost partitions, there is no response

#1 Post by Synapse » 03 Aug 2019, 09:48

Hi,

I'm trying to restore a partition that was somehow deleted on a USB 3.0 external hard drive. It was working perfectly the last time I plugged it into my Windows 10 laptop.

After choosing analyze -> quick search, it didn't update the screen, showing the progress of the search like it should, and pressing any other keys doesn't result in any response.

Is this expected behaviour, or how can I get quick search to work?

Sponsored links

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

Re: After pressing enter on quick search to find lost partitions, there is no response

#2 Post by cgrenier » 04 Aug 2019, 08:17

Can you try to clone the disk to an empty disk using ddrescue as described in https://www.cgsecurity.org/testdisk.pdf ?
Once it's done, remove the original disk and try TestDisk on the clone.
If ddrescue failed to clone the disk, there is a hardware problem with the disk, in this case, you should contact a data recovery company.

Synapse
Posts: 2
Joined: 03 Aug 2019, 09:42

Re: After pressing enter on quick search to find lost partitions, there is no response

#3 Post by Synapse » 04 Aug 2019, 14:20

Thanks for the suggestion, will try that once I get a drive that is big enough.

I left it to run, and the screen changed, now its stuck here. I suspect there're hardware problems that prevent it from reading the start of the drive.

Disk /dev/sdb - 4000 GB / 3725 GiB - CHS 486397 255 63
Analyse cylinder     2/486396: 00%
Read error at 0/25/49 (lba=1623)

  Stop

Leaving it on to see if its able to skip past this bad sector to make any more progress.

Post Reply

Who is online

Users browsing this forum: Bing [Bot] and 3 guests