Error: Access violation at..., program terminated

[Midwestguy]

I keep getting the attached error message. ZAR gets 99.9% complete and then quits. I'm trying to recover a 500 Gig Western Digital External USB drive that was attached to a Linksys Network Storage Device. Any help would be greatly appreciated.

[Alexey V. Gubin]

1. What is the operating system you run on?
2. What is ZAR build number as indicated when you start ZAR (next to the version number)?

[Midwestguy]

I'm running Windows XP Service Pack 2. Zar is version 8.3, build 19. I changed some of the settings and reran the program. This time, it completed its analysis and crashed building the file list. Here's the new screen shot. Any help would be greatly appreciated. Thanks.

[Alexey V. Gubin]

This is an ext2 filesystem (Linux). Could you please update to the most current build available, by just re-downloading and re-installing ZAR, and then retry.

[mckennis]

I changed some of the settings and reran the program. This time, it completed its analysis and crashed building the file list.

I also got the first error on XP with ZAR 8.3 Build 19. What settings did you change to get it to complete? These 18 hour scans are tough enough without the error at 99% every time.

Thanks & good luck

[mckennis]

This is my Log

NT 5.1.2600 Service Pack 3; 2037 MB RAM
TS: Stop validation
TS: Stopped validation
Logging - shut down
Init done - logging
NT 5.1.2600 Service Pack 3; 2037 MB RAM
Open physical drive 00000100 success, 189 GB : Maxtor 6 V200E0 - Port 2, Bus 0, Target 0, LUN 0; maxLBA=398297088
Open physical drive 00000101 success, 465 GB : WD My Book ES; maxLBA=976773168
Sector 0, row 1 - 63/976751937 @ base 0 - FAT32x
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 0101
Processing volume ID 01010000
-------------------------------------
Volume information for ID 01010000
Origin : MBR/Primary
Partition type : FAT32x
Capacity : 465 GB
Number of sectors : 976751937
RAID type : Simple volume
Stripe size : 1
Rotation parameters: 0 / 0
Member 00 : 976751937 sectors at LBA 63 on device 0101
-------------------------------------
Volume information for ID 01010000
Origin : MBR/Primary
Partition type : FAT32x
Capacity : 465 GB
Number of sectors : 976751937
RAID type : Simple volume
Stripe size : 1
Rotation parameters: 0 / 0
Member 00 : 976751937 sectors at LBA 63 on device 0101
Starting raw scanner for a total of 976751937 sectors
Raw scanner starting on disk 0101 from LBA 63 to LBA 976752000
Quick scan failed, reverting to full scan mode
TS: Stop validation
TS: Stopped validation
Performance: RunTime 25s
Open physical drive 00000100 success, 189 GB : Maxtor 6 V200E0 - Port 2, Bus 0, Target 0, LUN 0; maxLBA=398297088
Open physical drive 00000101 success, 465 GB : WD My Book ES; maxLBA=976773168
Open physical drive 00000100 success, 189 GB : Maxtor 6 V200E0 - Port 2, Bus 0, Target 0, LUN 0; maxLBA=398297088
Open physical drive 00000101 success, 465 GB : WD My Book ES; maxLBA=976773168
Sector 0, row 1 - 63/976751937 @ base 0 - FAT32x
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
Processing volume ID 01010000
-------------------------------------
Volume information for ID 01010000
Origin : MBR/Primary
Partition type : FAT32x
Capacity : 465 GB
Number of sectors : 976751937
RAID type : Simple volume
Stripe size : 1
Rotation parameters: 0 / 0
Member 00 : 976751937 sectors at LBA 63 on device 0101
-------------------------------------
Volume information for ID 01010000
Origin : MBR/Primary
Partition type : FAT32x
Capacity : 465 GB
Number of sectors : 976751937
RAID type : Simple volume
Stripe size : 1
Rotation parameters: 0 / 0
Member 00 : 976751937 sectors at LBA 63 on device 0101
Starting raw scanner for a total of 976751937 sectors
Raw scanner starting on disk 0101 from LBA 63 to LBA 976752000

Bad sector encountered @LBA 583864320 disk 0101
:D"THIS LINE REPEATS RECURSIVLY INCRIMENTING UNTIL IT GETS TO 27718218"
Bad sector encountered @LBA 27718218 disk 0101
Init done - logging
NT 5.1.2600 Service Pack 3; 2037 MB RAM
TS: Stop validation
TS: Stopped validation
Logging - shut down
Init done - logging
NT 5.1.2600 Service Pack 3; 2037 MB RAM
TS: Stop validation
TS: Stopped validation
Logging - shut down

[Alexey V. Gubin]

If you set logging to "Extended - for debug purposes" in Advanced Configuration, what the last lines of log would be then?

Also, consider that it may be useful to create an image of the device, as it has bad sectors, so the recovery run is performed using the image rather than an actual device.