Is ZAR supposed to run really really slow?

[dashriprock]

Just a quick question; is it supposed to run really slow? I've been running it for nearly 16 hrs. straight and it's only 2% complete on the volume scan. (sorry, I"m running Option 2 from the main menu) At this rate, it'll be running for days, perhaps weeks. Is this normal??

Thx.

Details: I'm trying to recover a 465Gb drive. It does recognize the disk, but not any volume name. I can open the disk in Windows Explorer (ie, it lists the directory's contents) however I cannot open, copy, move, or delete any folders/files without crashing. Tried running chkdsk /f but it doesn't read in DOS. Always gives one of several different error msgs. But, it did actually run one time and then gave an error msg saying it couldn't save the log file because of not enough disc space (or something to that affect). Nothing is working at this point.

[Alexey V. Gubin]

Originally Posted by dashriprock

Just a quick question; is it supposed to run really slow? I've been running it for nearly 16 hrs. straight and it's only 2% complete on the volume scan. (sorry, I"m running Option 2 from the main menu) At this rate, it'll be running for days, perhaps weeks. Is this normal??

No.

1. On a volume map, are there any red dots visible? (which would suggest the drive is physically bad)
2. Is the drive connected directly to the motherboard, or is there some sort of USB enclosure involved?
3. What is the exact model of the disk?

[dashriprock]

Yeah, it's connected via USB. If I connect the drive (SATA) to the main board it doesn't recognize that there is a disk present. The only way I can get the drive noticed is to USB it. It's all red dots on the volume map (well, just on the first line so far). The disk is a Western Digital 500GB (SATA), WD5000KS Caviar.

Would you say that this drive is toast and needs a professional service to recover the data?

Thx for your help.

[Alexey V. Gubin]

Yeah, the drive is damaged beyond software repair, you need a lab recovery service.