Crash

[sander]

I've tried twice to recover a 500GB Seagate drive, once from a Firewire enclosure and once directly from the IDE bus.

Both times the program scans for about 24 hours then boom:
Access violation 0x004DBA8A (tried to write to 0x015F0FF4) Program terminated

The drive has an NTFS volume in a TVisto 3500 Multimedia enclosure (linux media player which alternately boots to a media player or an external hard drive).

I tried testdisk and a couple of other utilities, because I thought it was just the partition table was messed up, but none of them detected any problems, even though nothing can find any physical damage.

Zar gave me hope because it detects about 10% file system and about 80% random data on the sector blocks, but it just crashes when it's finished.

TIA

[Alexey V. Gubin]

What exact version and build number you try it with?
Are you certain the filesystem was NTFS?
With a drive on IDE bus, does it still take 24 hours?
Can you zip the log file, C:\Program Files\ZAR\logfile.txt and email it to me at development@z-a-recovery.com? The mailbox accepts 15MB max. If the log file is larger than that, please use ZIP feature to split the log file into parts.

[sander]

Sorry for the delay. Thank you for your help.

1. What exact version and build number you try it with?
8.3 build 26

2. Are you certain the filesystem was NTFS?
95% certain. I put ISOs on it so I needed the big file support

3. With a drive on IDE bus, does it still take 24 hours?
Yes, maybe the drive is damaged in some strange way.

4. Can you zip the log file, C:\Program Files\ZAR\logfile.txt and email it to me at development@z-a-recovery.com? The mailbox accepts 15MB max. If the log file is larger than that, please use ZIP feature to split the log file into parts.

The log file is short enough, I'll post it:
Init done - logging
NT 5.1.2600 Service Pack 2; 1535 MB RAM
Open physical drive 00000100 success, 232 GB : WDC WD2500JB-00GVA0 - Port 0, Bus 0, Target 0, LUN 0; maxLBA=488397168
Open physical drive 00000101 success, 0 B : Generic USB SD Reader; maxLBA=0
Open physical drive 00000102 success, 0 B : Generic USB CF Reader; maxLBA=0
Open physical drive 00000103 success, 0 B : Generic USB SM Reader; maxLBA=0
Open physical drive 00000104 success, 0 B : Generic USB MS Reader; maxLBA=0
Open physical drive 00000105 success, 465 GB : ST350063 0A; maxLBA=976773168
Sector 0, row 1 - 63/976768002 @ base 0 - NTFS
Sector 0, row 2 - 0/0 @ base 0 - Empty
Sector 0, row 3 - 0/0 @ base 0 - Empty
Sector 0, row 4 - 0/0 @ base 0 - Empty
Ldm: started processing of the device 0100
Ldm: started processing of the device 0105
Processing volume ID 01050000
-------------------------------------
Volume information for ID 01050000
Origin : MBR/Primary
Partition type : NTFS
Capacity : 465 GB
Number of sectors : 976768002
RAID type : Simple volume
Stripe size : 1
Rotation parameters: 0 / 0
Member 00 : 976768002 sectors at LBA 63 on device 0105
-------------------------------------
Volume information for ID 01050000
Origin : MBR/Primary
Partition type : NTFS
Capacity : 465 GB
Number of sectors : 976768002
RAID type : Simple volume
Stripe size : 1
Rotation parameters: 0 / 0
Member 00 : 976768002 sectors at LBA 63 on device 0105
Starting raw scanner for a total of 976768002 sectors
Raw scanner starting on disk 0105 from LBA 63 to LBA 976768065
Quick scan failed, reverting to full scan mode
TS: Stop validation
TS: Stopped validation
Logging - shut down
Init done - logging
NT 5.1.2600 Service Pack 2; 1535 MB RAM
TS: Stop validation
TS: Stopped validation
Logging - shut down

[Alexey V. Gubin]

We've been tracking several similar cases, and this is believed to be fixed as of build 29. Please download http://www.z-a-recovery.com/zar-83-029.exe, install and retry - should work this time.

[sander]

Thank you Alexey, that did the trick. Here's 30$ for your efforts!

[Alexey V. Gubin]

So that really fixed it. Nice.