errorC: 71 Diskpatch clone Help?

[vpaul]

I have a 1TB drive and know ift has some bad sectors on it from testing with iRecover and diskpatch.  In my efforts to clone this drive with Diskpatch I get this error about 1/4 of the wat through the clone process.

Diskpatch has encountered an unrecoverable error and all operations are halted to prevent damage

Address: 241275
ErrorC: 71
Error specifics-

Diskette not ready


This error comes up after about 8 hours of ruunning dispatch clone.
I also get a error that there is a MBR read error at the begining of running Diskpatch.

I have tried to save the log files but cannot see where they are saved to. I will try again to see if I can save them to a USB stick.

Any help will be very much appreciated on this error.

THANKS

[Tom]

A strange error to receive. You might want to try a clone with all logging disabled, to make sure that the only activity is the actual cloning. When starting from the DiskPatch diskette or USB key, select "DiskPatch Options" in the DP start menu (the first menu to appear with the blue background), then select the second option, "force select files location prompt". Disable logging and try again.

You can pick up the clone from where you left off, what has been cloned sofar will remain on the target disk.

The MBR read error warning will pop up whenever the MBR for any disk can not be read; this is by design because the MBR (the first sector on the disk) is the most important sector on the disk, so if it doesn't work well you should know about this. When cloning this can be ignored, unless the error comes up for the target disk.

[vpaul]

THANKS for your quick response.

Update on progress. I was able to get  a usb stick recognized and booted diskpatch. Now that I can have a place to save the log file I get past the place in the drive where it gave me the errorc: 71.  I began the clone at 502,000,000 and after a little bit of cloning I see the light on the USB stick flashing.  There are a lot of blocks skipped right now I am seeing over 10,000.

1. If this completes successful I assume I will need to re clone from the begining to get as much of the drive cloned as possible. I am not sure what has been cloned and what has not as it asks if I wish to overwrite each time and as I think I saw if you choose no it will not proceed, I will have to watch the dialog better next time. correct?

2. There are 8 partitions and as I recall one of the partitions may be NTFS with the others as FAT32.

3. Is there any way to correct the MBR error mentioned in my first message and would this help in the clone process?

4. I have had to access this drive a multitude of times trying to figure out what will best fix it and I know that the fewer accesses the better in my attempts. Should I do a 1 Pass or a 2 pass clone for the final attempt?

Thanks

[Tom]

1. If this completes successful I assume I will need to re clone from the begining to get as much of the drive cloned as possible. I am not sure what has been cloned and what has not as it asks if I wish to overwrite each time and as I think I saw if you choose no it will not proceed, I will have to watch the dialog better next time. correct?

When re-starting a clone after aborting one previously, what has been cloned so far stays on the target disk. It's not as if DiskPatch wipes everything every time a new clone operation is started, that would make no sense. If you clone a region that has been cloned before then yes, what was on the target disk gets overwritten, but that may not make a difference if the cloning on the previous run went well. So you can clone as many times as you like, the result can only get better (if for instance regions that didn't go well the first time did better the second time).

3. Is there any way to correct the MBR error mentioned in my first message and would this help in the clone process?

That is not relevant. The MBR can not be read, and that's the end of it. It's not so much an error as it is a message. The fact that the MBR can't be read is not good and that's why you are cloning now.

4. I have had to access this drive a multitude of times trying to figure out what will best fix it and I know that the fewer accesses the better in my attempts. Should I do a 1 Pass or a 2 pass clone for the final attempt?

Read the bit about cloning in the manual, it explains it perfectly well and after reading you should be able to make an informed decision on that. Basically though, always do a 2 pass.
http://www.diydatarecovery.nl/dp_manual/clone.htm

[vpaul]

Tom, Thank You for your kind replys.  From what I have read, if I started a 2 pass full clone and it aborted 1/4 of the way through the 1st pass, I should then start the 2 pass full clone over again.  If the 1st pass had completed I would be ok and have a full clone but I would not have the benefit of the second pass.

Just in testing I started a clone on a 2 pass full and it did abort on the 1st pass about 1/4 done.  When I got the USB stick to work on capturing the log I started the 1st pass just before the place where it aborted before.

In reading the link on cloning at http://www.diydatarecovery.nl/dp_manual/clone.htm I see that "if you restart step 1 after you have aborted step 1 you will have to start from the beginning again. "

I thought possibly that the first 1/4 of the clone was still on the target and then when I restarted with just a 1 pass at the sector point just before the 1/4 mark where it failed before I would then have a whole pass and possibly 1 complete 1 pass clone. Can you confirm this?

If I need, I would prefer a 2 pass full to try to recover as much data as possible but also so not want to strees the drive any more than necessary.

THANKS Again and Best to you,

Vic

[Tom]

I thought possibly that the first 1/4 of the clone was still on the target and then when I restarted with just a 1 pass at the sector point just before the 1/4 mark where it failed before I would then have a whole pass and possibly 1 complete 1 pass clone. Can you confirm this?

Yes, correct. I know this might be a bit confusing, but here's why:
The first pass creates a log of bad spots (*) that are encountered during that first pass. When the second pass runs it looks at this log and re-works the bad spots that could not be read on the first pass. For this system to work the first pass must run to completion, so in that sense, if you abort the first pass then yes, you will need to start again to get the full benefit of that two pass system (**). BUT if you abort during the first pass, what has been cloned so far stays on the target disk. So in that sense your assumption is correct. I hope this clarifies a bit.

(*) this log is kept on the target disk and is hidden from view, not something to worry about with regard to DiskPatch being able to write files.
(**) it doesn't have to run to completion for the entire disk though, just for the region you specify when starting the clone (which is the entire disk by default, but can be changed). So you can run complete 2 pass clones on sections of the disk, as long as you remember the start and end locations you entered when starting the clone.

[vpaul]

THANK YOU again. It is nice to have you as an expert in my corner.  From what I am seeing so far...

Diskpatch is still running with no crash.  The 1TB drive which is bad begun loging blocks skipped at 446,690,000 (approximate).  I had done a 2 pass full up to that point and when the loging started to kick in I believe that is when diskpatch threw an errorc: 71. Now that I have the USB stick loging the activity it seems to run fine.  This may possibly fill up the USB stick at some point and crash again, I will watch it.

On the first 2 pass full it crashed at the 446,690,000 (approximate) during the 1st pass. I had selected to do the full drive from 0 to 1,953,523, 024 (default). I then begun a 1 pass at the 446,000,000 mark and after a short bit the blocks skipped began showing on the screen and the number increases rapidly and consistently. It is still running and has been about 22 hours and I will continue to let this one pass finish.  I am thinking I can the examine the target disk with iRecover or other utilities.

Something else I am thinking is that when I first ran irecover ( I know I should have run the clone first) I was able to recover some of the data from some of the partitions.  This 1TB drive has 8 partitions, one of them may be NTFS and the others FAT32.  They are Drives C, E, F,G,H,I,J,K.  I believe I was able to recover some data from Drive K which I would guess is at the end of the drive.  Also I was able to recover some data from Drive C which I assume is at the beginning of the drive. In seeing the clone run and blocks skipped from about the 446,690,000 mark and beyond, I am thinking that I may not have ANY good data from that point on the clone.  Can you confirm this?

Also when in iRecover and I tried to recover Drive F it would run for a while, I did see some bad blocks in red and then irecover seemed to hang. I let it run for over 1 hour with no progress and the numbers at the bottom of the screen like CPU, Temp etc were either 0 (zero) or not displaying when it appeared to hang.  I aborted by doing an end task. I think it would be nice to have a bootable version of irecover to be able to eliminate the Windows XP boot up. Windows seems to have trouble booting when there is a bad disc attached as a secondary.

When this clone is complete, can you recommend any settings for irecover to possibly get past this hang when trying to recover my Drive F?

THANKS so much, I really do appreciate this help.

[Tom]

[...] Can you confirm this?

I understand your thinking but no. The only way to determine that is to try, so you'll have to see for yourself.

When this clone is complete, can you recommend any settings for irecover to possibly get past this hang when trying to recover my Drive F?

No, because when the clone is finished you'll be running iRecover on the cloned disk, and that disk should not have any read errors.

[vpaul]

Hopefully my last questions. When the clone is complete will ALL files that I can see and copy to a new drive be Good Files? If iRecover runs against the clone will I still see bad files? If so on the bad files, how will I know the difference which are good and which are bad in viewing the drive or using irecover?

I was thinking if I see a file with a name how would I tell if it is goo or bad.

Hope this makes some sense, very tired here, LOL

I restored an older backup of my drive F and was thinking that if ALL the files I can see on the clone are good then I could just copy all the files and folders from the clone to my restored F Drive. Then I would have the newer files that were recovered as well.

THANKS Again !!!  I do appreciate this help.

[Tom]

When the clone is complete will ALL files that I can see and copy to a new drive be Good Files?

I have no way of knowing that. I'm not there and I haven't worked with your disks and/or files, so there's no possible way that I can tell. As always, you'll have to try and hope for some good luck.

If iRecover runs against the clone will I still see bad files?

That is very well possible, yes. Files can still be bad because for instance only parts of files were cloned.

If so on the bad files, how will I know the difference which are good and which are bad in viewing the drive or using irecover?

By recovering as much as you can and going through the files manually. iRecover makes educated guesses on the state of the files, the only way to know for sure is to check it for yourself, as is always the case in any recovery scenario. A good pair of eyes and brains can not be replaced by algorithms.

[vpaul]

This makes sense, Thanks.

When I boot up with the clone attached WinXP wants to do a scandisk (chkdsk) at boot for one of the colned partitions, I have been afraid to allow this to run.  Should I allow the scandisk to run on the clone?

I think from this point I will copy the files to a folder on a new drive (to keep my current clone intact). Then I can test the files and move them to the origial locations if the files prove to be good.

In my pood organization of files I have important stuff scattered across all the partitions. My bad.  I am going to make a back up server just as soon as I can!!!

One other thing I am thinking and not too clear on this.  I ran the 1 pass begining about 1/4 from the begining (and it completed) to pick up where the 1st try failed on a 2 pass.  Wanting to exercise the disk as little as possible.  I see in the DPLOG the blocks skipped on this 1 pass. What would happen if I run the 2nd pass begining at the 1/4 point (same as the 1 pass). Would I possibly recover more files?

THANKS so much!!!

[Tom]

Never let chkdsk or scandisk run when working on a recovery. We explain why in all manuals and on the website.

Never change anything (if possible) on any disk that is involved in a recovery operation. The reason should be obvious.

Would I possibly recover more files?

Possibly, but probably not. Remember, what was cloned earlier stays on the target disk so re-cloning parts can potentially only make things better. You'll have to take the state of the source disk into account though: if it's in bad shape it's likely that even more source sectors can not be read compared to earlier attempts so the net profit won't be higher.

[vpaul]

I was seeing this

"Download (on a different PC) the DIY DataRecovery.nl Product CD ISO image > Burn the ISO image using your CD burn software > Insert the CD in the PC containing the disk that data needs to be salvaged from and select the option to run iRecover from the CD directly. "

at the bottom of the iRecover page.  Does this mean I can boot from a CD and run iRecover?  I burned the ISO to a cd and can boot but only get the Diskpatch running.

[Tom]

The CD boots into DiskPatch, it's not legal to distribute a working Windows on CD. What that description means is that when you insert the CD in a drive on a PC with Windows running, it will allow you to run any of our apps without having to run the setup.
Also, running iRecover on Windows PE is currently not supported, you will need a working Windows to install and run iRecover.

[vpaul]

Tom, I may have gotten all the files I am going to get with this process.  Still missing a bunch of files but I should have done a clone at the first sign.

I believe I ran diskpatch last and just the second pass.

I wanted to try a couple of utilities to learn and possible recover some more.
I ran TestDisk and after selecting the disk that is bad I get message that says "hidden sectors are present",  Have you ever seen this and is this something diskpatch or irecover may have hidden?  I am not able to see any of the 8 partitions.  I was able to see some of the partitions before.

THANKS