SABnzbd Forums

Hi,

I have an other pc with SABNZB 4.3.2 installed on it.
After making the settings with the setup, i made the correct way to the maps for download.
On the my old pc the NZB works fine. The file downloaded, controlled, verified and upacked. It was taking a lot of time

But on my new pc i get this message:
Reparatie mislukt (Reparing FAILED), checksum mismatch, recovered input slice 2575
or
Reparatie mislukt (Reparing FAILED), checksum mismatch, recovered input slice 2576

I also unchecked the option DIRECT UNPACKING (direct uitpakken) but this is not helping and the error message keeps coming.

Can i getr some help?

UPDATE: after an hour i use QUICKPAR to repair the last error file and it was possible to repair the download, with quickpar an d unpack with 7zip.
The error is still there with SABNZB

Regards
Marcel

This is during the repair phase, so not during unpack.
That the same NZB works on one, but fails on another could indicate an issue with your PC. Maybe corrupt disk or memory.

What happens is that during repair it reconstructs the data and then checks the checksum for the . This should always return success, and can basically only fail due to some memory corruption.

Hi safihre,
Thank you for your quick reply. I will check the disk and memory
Regards
Marcel

Basic test:

In SABnzbd's upper right corner, click on the wrench symbol ("Status and interface options"), then click on first tab Status, click Test download 1GB.

Does that download go well (it should), or also an error (confirming you have hardware problems)

Hi Sander,
Thank you for your answer. It seems to be a memory issue. I run "mdsched.exe" . The result is a memory error. I will contact the store for a replacement and test again.
Regrads
Marcel

TIL: Windows has a built-in memory testing tool: Windows Memory Diagnostics Tool - MdSched.

Nice!

I did not know that either. Good to know!

Hi to all,
I am glad to let you know that i now know whats wrong. The memory banks are failling and need to be replaced.
Many thanks for your imput

Update: After replacing the memory, the problem still occurred. So i went back with the complete pc. And again the memory was corrupt and failed the test. After the complete check and a new set of memory banks the problem is now solved. No problems with the same nzb.

Great!