PDA

View Full Version : I am confused...


Martypants
21st January 2009, 11:19
I used the free version of the software, and was able to retrieve the 4 folders from my wounded external drive (a 500 gig My Book from Western Digital). My problem was an I/O error each time I tried to move files from the drive. The free version went fast, and in about 2 hours it ran its course. I was so happy that it found all the files (I saw everything in the folder tree and my 4 free folders were 100% intact), I purchased the software to retrieve all the files.

When I got the code, I unlocked it and ran ZAR again. This time, it locked up when it was only 60% into reading the files...which took about 10 hours. it showed 3 red boxes in the file ID, so I knew there were some bad spots...but this was not different than when I ran the free version (except the free version moved past them, and completed the task). The free version showed the same 3 red boxes, so I was a little confused as to the difference.
I followed the suggested steps of this forum (changing the settings to avoid the long stalling periods), but nothing happened.
So I unplugged everything and waited for 24 hours.
Plugged it all back in (using a different USB port and a tested, solid cable to be sure), and ran it again last night - but this time, it locked up after about 47%...and maybe 8 hours or so. This time there were more red boxes, so I immediately shut it down. Now I am really worried that more damage has occurred due to the long run times, and I see my chances of recovering the data fading. I am actually worse off than before. Oy.
The drive is not making noises or indicating in any other way that there is an issue...but I did not try to manually transfer files again (wanted it to relax).
I am confused, and a little dismayed. If the software worked great for the trial, why does it no longer work for me after I have paid for it? The drive has only been plugged in to run the recovery tasks, but now I am really nervous to run it again, as it seems to not help at all, in fact it seems to be doing the opposite for me.
Would love to become an evangelist for this product, if I could only get it to work as it did for me when using the free download. I feel a little gypped, and really hope you can help me to sort this out...the files on that drive are pretty important to me. is there a history or something I can tap to see what i did the first trial run? The trial run was perfect, but since I bought it, it has not worked.
Since this is a My Book hard drive, it is in a closed case, and I can't remove the drive (without destroying the case) to run it directly through eSATA or see if there is any noticeable physical damage to it (it is only USB out). The drive was never dropped, dinged or physically harmed in any way...it sits where it always has, far from anything that could bump or bruise it, so I am at a loss. Please tell me my data is not in the same boat...hate to think I spent $30 to screw up my drive, and hope you'd hate that too.
Thanks.

Alexey V. Gubin
21st January 2009, 12:17
As much as I hate it, this drive is beyond a software repair.
This is because a physical-type defect grew to the point the drive (or most likely the enclosure) now gets stuck on reading.

Since you cannot remove it from the enclosure, the only option I see left is to send the device to a data recovery lab, somebody who does physical-level repairs.

The last saved state would be of no use as the drive deteriorated to the point it locks up completely.

Martypants
21st January 2009, 16:17
As much as I hate it, this drive is beyond a software repair.
This is because a physical-type defect grew to the point the drive (or most likely the enclosure) now gets stuck on reading.

Since you cannot remove it from the enclosure, the only option I see left is to send the device to a data recovery lab, somebody who does physical-level repairs.

The last saved state would be of no use as the drive deteriorated to the point it locks up completely.

Alexey - I have some pals who are much smarter than me, and could help.
I am thinking that it could very likely be an enclosure issue - so if I can get the drive out (back to the smart pals helping me), I can likely get the data back...that my issue is actually the enclosure malfunctioning and the fact I used Fat32 instead of NFTS for the structure...is this a rational thought?
My thing is, i don't want to spend another dime unless there is a realistic chance of rescue.
And though I was grumbling, I never really thought it was the software - I am just pissed off. But, if it is an enclosure thing, i can probably get around it and get to the finish line...i simply am out of my element here, and don't want to make a mistake that GUARANTEES I won't get anything back without a healthy data recovery investment.
For the record, i thought your software was both strong and cool - love the little snide/flippant details, and your use of vernacular in the details. Kindred spirits.
I honestly had a moment when the free version pulled up all the files where I clicked save, and then decided against it, to try to retrieve at least SOME of the data...so i clicked save on my selected folders and almost immediately thought I could've saved it all if I wasn't so skittish. Is this true? If I would have saved instead of selecting files for copying, would I have been able to pull it up after I bought it and reclaim those files I saw? That issue is gnawing at me.
Your answers help - kind of like salve on a rash. It won't make it disappear, but it won't be as irritating.
Thanks-
Marty

Alexey V. Gubin
22nd January 2009, 14:30
If I would have saved instead of selecting files for copying, would I have been able to pull it up after I bought it and reclaim those files I saw?

Not likely. Looks like the drive deteriorates as read operations are performed. Copying of the files is more read-intensive then the initial analysis, so the drive would most likely start locking up early in the copy process even with a saved state input.


My thing is, i don't want to spend another dime unless there is a realistic chance of rescue.

If you can get the enclosure opened, you can still try ZAR on the same drive attached to the mainboard port. If by some coincidence you have about 1TB of free space available, then go for an image of the drive rather than a recovery. An image file occupies 500 GB, but, when created, provides unlimited number of software attempts because it does not deteriorate on reads.

Martypants
22nd January 2009, 18:07
Alexey -
I did pull the drive out (found some great info online), and learned to my dismay, it is in fact a hardware issue. The overheating bastard is simply malfunctioning at a root level. Managed to save a few more files, but it was hit and miss, and I see now the drive is not going to cooperate at all. Each pass I take makes it weaker.
But your suggestion of imaging the drive is great, because I do have access to a program that will put less stress on the drive and will do this for me...and based on what I saw today with the drive out of the crappy WD enclosure, it is my last, best hope for the most recovery. Your point about it not taxing the drive further was key...because based on what I saw today, i am going to have to do this recovery very slowly, one file at a time...and I can't afford for deterioration to occur with every pass.
So though the software didn't really work as planned, i am glad i could give you a little money. Keep offering people hope - I appreciate you didn't blow smoke up my dress at any time. You helped me...and the software was solid. Wish it would've helped, but I have it now if I need it in the future.
Thanks again - consider me your evangelist. :)