Windows 10 - The disk structure is corrupted and unreadable

I don't think you've understood what I said.

Don't clone a bad disk. It's the wrong thing to do.

Of course you'll get the same result if you make an exact copy of bad data. So don't do it.

@lxo7 my assumption was the OP is trying to boot his system from the cloned drive, hoping it would no work. I though he had already recovered what data he could. Note he refers to post #1.

In any event, he can expect some problems accessing the data on the cloned drive.

I agree the cloned drive can be used for data recovery as you say.

"Don't clone a bad disk. It's the wrong thing to do."- dalchina

Sorry, that is the right thing to do. And the right tool is to clone with ddrescue which runs on Linux.. ( Conventional Imaging/cloning software running on Windows or even Win PE may not clone a drive with bad sectors. Cloning in most cases will fail, their algorithm designed to image/clone a working drive without any fatal errors.)

@dalchina, 1. I don't think the OP is cloning his boot drive. Nowhere has he said so.

2. Even in a case of failing boot drive ddrescue was used successfully to recover the data. If I remember correctly one user was able to boot successfully from the ddrescue- cloned drive and access the lost partition in the boot drive.

Edit: I found that thread. https://www.sevenforums.com/general-discussion/381547-cant-access-partition-slow-system-file-record-segment-unreadable.html

OP: HighFlyerPL185: " have made a clone to the new drive, booted it up and it seems to run very well Every program I had installed runs fine, and I can access the lost partition! Here's a shot as requested from the Disk Manager; hoping that this is the end of the trouble...

GoKay:" Nice Did you run the ddrescue command or some other method? And did the faulty partition just showed up like that after cloning?"

HighFlyerPL185: " I ran the last command given by Jumanji, and yes, it showed up like this."

And that command given was ddrescue -d -f -r3 /dev/sda /dev/sdb recovery.log

3. Even if ddrescue fails to recover the data from the bad sectors, one can run the data recovery software safely on the cloned drive keeping aside the failing drive which we do not want to tax further.

Please take sometime and read this thread to know more about what we had discussed on ddrescue and other user experiences.
https://www.sevenforums.com/general-...-recovery.html
And also https://www.gnu.org/software/ddrescu...ue_manual.html

simrick another VIP member of this forum has said this ".....I used your dd-rescue instructions in sevenforums to recover data on a 4%-health-remaining-drive that was almost totally dead; saved my Uncle's precious data (which was *not*, of course, backed up anywhere" )"

And of course ddrescue may not always be successful in recovering the data from bad sectors - depends upon how good the bad sectors are or how bad that bad sectors are - but then point 3 above comes into relevance..

n4rvto said:

Hi guys, I just finished clone the bad drive into the new one. The result is exactly same with the bad one, I can't access the drive. What should I do next to fix the recovered bad disk (red mark) in the new disk or recover the data?
Attachment 174508

Anyway, here's the result from ddrescue:
Attachment 174509

And here's the log:
Attachment 174510

Many thanks!

1. I would like to know how you ran ddrescue . The procedure we had outlined previously is to run ddrescue from a bootable System Rescue pendrive and use the command ddrescue -d -f -r3 /dev/sdb /dev/sdc recovery.log. The command you had given is slightly different being -f -d -v -r3 /dev/sdb /dev/sda /opt /recovery.log ( I am not worried about the nomenclature of the source drive and destination drive. You must have given it as you found it.)In particular what does the /opt switch do? Please elaborate exactly how you ran ddrescue from the beginning as you would guide a newbie wanting to run it. That should be helpful for others.

2. I presume you have a desktop in which you have the faulty drive and also the now cloned HDD. Please post a full screenshot of Windows Disk Management showing all your drives as per the guidelines here Disk Management - How to Post a Screenshot of Truncated screenshots not acceptable.

3. On the cloned drive run active @ file recovery as recommended in my post #15 and report the results.

4. Also name the data recovery software/s you had run previously and if you had recovered the data already what more do you want aka why do you want any further data recovery?

We shall then try to get the juice out of the cloned drive. It is going to be an elaborate process, which may or may not succeed. In the event TestDisk finds the MFT corrupted - which is one of the many reasons why a drive can turn into RAW - and unable to repair it, you have to necessarily buy a commercial software as aforesaid. Reason why I am asking you to try that first with Active@FileRecovery. Other commercial software recommended by Christopher Granier, author of TestDisk are GetDataBack simple, Zero Assumption Recovery - both costlier than Active@FileRecovery. We know of many users who used these two - A@FR and GDB - and successfully recovered the data after TestDisk failed to repair the MFT.