SeqOneReader Thread Error

[colossus]

I am getting this error message after ZAR 8.3 during reading sequence numbers on my 4 disk RAID 5 array (minus 1 disk - zar generates parity on 4th disk)

The Config is as follows:


4 Disk RAID 5 (500GB each) 1.5TB Array

1 drive is missing, 2 hdd's are good and the other hdd has a small amount of bad sectors.

so just to confirm the config of ZAR

3 x 500GB RAID5 checkerboard
1 x Parity drive that ZAR generates

Story:

The first disk i took out to swap with another one. i had not inserted the replacement disk yet to rebuild the parity.

during that time a second hdd developed bad sectors, causing the raid card to fail the already degraded array.



With ZAR 8.3 it does a complete quick scan fine, generates the parity data fine, then goes on to read the sequence numbers.

its at this point (13%) that the program crashes with the error

"an error has occured and it is not possible to contine execution. The program will now terminate. The error message was: Thread fault SeqOneReaderThread"

I have submitted this error report via the program.

If it is any help, I had debug logging enabled when I ran the program.


I have attached a screenshot of the problem.

The machine in question has the following specs:

AMD 3200 XP
1GB DDR RAM
160GB HDD
NVIDIA 7800 GS AGP


I hope you can help me get this issue resolved as it looks like ZAR can see the data, but just crashes with this error message!


Thanks,


James.

[Alexey V. Gubin]

We had a similar issue discussed in this thread about RAID recovery (http://z-a-recovery.com/data-recovery-forum/showthread.php?t=328&page=2) .
You should download and try http://www.z-a-recovery.com/zar-83-024.exe - the issue is believed to be resolved in this build. If it is not, make sure you allow it submit an error report.

[colossus]

Thank you very much.

I have downloaded this build and running it as we speak.

I will let you know how it goes!

James.

[colossus]

Hi Alexey,

I can confirm that this latest build has resolved the problem.

The error does not come up and I am able to recover my files!

Thank you very much.

James.

[Alexey V. Gubin]

Nice, thanks.