Page 1 of 1
Downloads that need repair failing on Unraid Docker install but not on MacOS install
Posted: October 18th, 2025, 1:08 pm
by wapkaplet
I'm running into an odd issue with my SABNZBd docker install on Unraid. Downloads that require a repair seem to be failing somewhat regularly, even if there are enough par files to repair them. It goes through the download and verification process, and then sometimes even gets into the repair process, and then just shows RAR Corrupt.
I tried reinstalling my Docker instance, installing a clean instance, switching repositories from Linuxserver to Binhex with no luck.
However, when I download SABNZBd and install it on MacOS, the same NZB file downloads, verifies, repairs and unpacks with no problem at all.
I'm a little stumped as to what's happening. Does anyone have any ideas? Thanks in advance for any help!
Re: Downloads that need repair failing on Unraid Docker install but not on MacOS install
Posted: October 18th, 2025, 1:20 pm
by safihre
Enable Debug logging in the Status window and then after it happens again click Show Logging in the Status window.
Then check the par2cmdline output.
Re: Downloads that need repair failing on Unraid Docker install but not on MacOS install
Posted: October 18th, 2025, 6:17 pm
by sander
Same SABnzbd version?
Same newsservers settings?
If so: fault hardware (faulty RAM, faulty disk) on the docker host?
To check that: in SABnzbd open "Add NZB", select the NZB, and select "Post processing" -> Download (not +Repair etc). Let the download finish. Then go into the download directory, and run
on the files in that directory. Run on both systems, and verify the md5sum values.
You can do this for the 1000MB.nzb test reference from
https://sabnzbd.org/tests/test_download_1000MB.nzb
Example (should be exact the same for you, on both systems):
Code: Select all
sander@zwarte:~/Downloads/complete/test_download_1000MB$ md5sum *
835a1a13b7f3d8f21966db95e3f72f88 sometestfile-1GB.par2
190bed240d66af7525613318268b0667 sometestfile-1GB.part01.rar
d243306f0df83ea82077aa19c6d56f7d sometestfile-1GB.part02.rar
0fb453b4677cbedf9dbce250a97aba16 sometestfile-1GB.part03.rar
4743f47d199e1e6f6727f583526fd0bb sometestfile-1GB.part04.rar
f59982cb31da48e927b8c87143c4c5b0 sometestfile-1GB.part05.rar
0aacd9bbdf50fa1b70efd26b1b430b87 sometestfile-1GB.part06.rar
62b6254f4409152561ed050f16728d88 sometestfile-1GB.part07.rar
0188b599a284310552764348a2fcf16c sometestfile-1GB.part08.rar
7dc80d0e9f05e8983198f37e21ab33ae sometestfile-1GB.part09.rar
202824d948682a86fcd7263186dd0a87 sometestfile-1GB.part10.rar
8dee7ad88a349717bd2272846b18db80 sometestfile-1GB.part11.rar
5671a4ed841c11e518cafecd2fa1f7f5 sometestfile-1GB.vol000+001.par2
6dbe9ee239d1f38b36afbf97a788acef sometestfile-1GB.vol001+002.par2
4d1bdb27a689011bec9871354d16e465 sometestfile-1GB.vol003+004.par2
dddb7a3ee4e3e14878361a7dcda58112 sometestfile-1GB.vol007+008.par2
5385e11efd95305e9127abf59fafa00b sometestfile-1GB.vol015+016.par2
e0b26cf8ce34a1aca5308d8c97991e78 sometestfile-1GB.vol031+032.par2
eb336b25dc85b0eb9fce26dcbf92978b sometestfile-1GB.vol063+064.par2
601aacf009435c635c27c0a31a98dcb4 sometestfile-1GB.vol127+072.par2
Re: Downloads that need repair failing on Unraid Docker install but not on MacOS install
Posted: October 18th, 2025, 7:10 pm
by wapkaplet
Thanks for that. Output from the Docker:
Code: Select all
MD5 (sometestfile-1GB.par2) = 835a1a13b7f3d8f21966db95e3f72f88
MD5 (sometestfile-1GB.part01.rar) = 190bed240d66af7525613318268b0667
MD5 (sometestfile-1GB.part02.rar) = d243306f0df83ea82077aa19c6d56f7d
MD5 (sometestfile-1GB.part03.rar) = 0fb453b4677cbedf9dbce250a97aba16
MD5 (sometestfile-1GB.part04.rar) = 0dbaf6a0df99076d7ce678e94ddd3301
MD5 (sometestfile-1GB.part05.rar) = f59982cb31da48e927b8c87143c4c5b0
MD5 (sometestfile-1GB.part06.rar) = 233eb05de1987d0019741c7db333bede
MD5 (sometestfile-1GB.part07.rar) = d30848c7902035598649298e85798c79
MD5 (sometestfile-1GB.part08.rar) = 0188b599a284310552764348a2fcf16c
MD5 (sometestfile-1GB.part09.rar) = 7dc80d0e9f05e8983198f37e21ab33ae
MD5 (sometestfile-1GB.part10.rar) = 202824d948682a86fcd7263186dd0a87
MD5 (sometestfile-1GB.part11.rar) = 8dee7ad88a349717bd2272846b18db80
MD5 (sometestfile-1GB.vol000+001.par2) = 5671a4ed841c11e518cafecd2fa1f7f5
MD5 (sometestfile-1GB.vol003+004.par2) = bff699ed3dc727172de24c1df5792af7
MD5 (sometestfile-1GB.vol007+008.par2) = 3c28af340c3f3914ccb430162dd53335
MD5 (sometestfile-1GB.vol015+016.par2) = 863e57521b967e5aa596f38ea68a5d2a
MD5 (sometestfile-1GB.vol031+032.par2) = 90fad444723deb8e4adb278de6dec7da
MD5 (sometestfile-1GB.vol063+064.par2) = 8be1eee920abc1f3d16e34569020e5c2
MD5 (sometestfile-1GB.vol127+072.par2) = 5082d6e041995d59c3a48fd89e17e666
Output from the MacOS install:
Code: Select all
MD5 (sometestfile-1GB.par2) = 835a1a13b7f3d8f21966db95e3f72f88
MD5 (sometestfile-1GB.part01.rar) = 190bed240d66af7525613318268b0667
MD5 (sometestfile-1GB.part02.rar) = d243306f0df83ea82077aa19c6d56f7d
MD5 (sometestfile-1GB.part03.rar) = 0fb453b4677cbedf9dbce250a97aba16
MD5 (sometestfile-1GB.part04.rar) = 4743f47d199e1e6f6727f583526fd0bb
MD5 (sometestfile-1GB.part05.rar) = f59982cb31da48e927b8c87143c4c5b0
MD5 (sometestfile-1GB.part06.rar) = 0aacd9bbdf50fa1b70efd26b1b430b87
MD5 (sometestfile-1GB.part07.rar) = 62b6254f4409152561ed050f16728d88
MD5 (sometestfile-1GB.part08.rar) = 0188b599a284310552764348a2fcf16c
MD5 (sometestfile-1GB.part09.rar) = 7dc80d0e9f05e8983198f37e21ab33ae
MD5 (sometestfile-1GB.part10.rar) = 202824d948682a86fcd7263186dd0a87
MD5 (sometestfile-1GB.part11.rar) = 8dee7ad88a349717bd2272846b18db80
MD5 (sometestfile-1GB.vol000+001.par2) = 5671a4ed841c11e518cafecd2fa1f7f5
MD5 (sometestfile-1GB.vol001+002.par2) = 5ae45614ce3c5f9394d1aca0c9021c31
MD5 (sometestfile-1GB.vol003+004.par2) = bff699ed3dc727172de24c1df5792af7
MD5 (sometestfile-1GB.vol007+008.par2) = 3c28af340c3f3914ccb430162dd53335
MD5 (sometestfile-1GB.vol015+016.par2) = 863e57521b967e5aa596f38ea68a5d2a
MD5 (sometestfile-1GB.vol031+032.par2) = 90fad444723deb8e4adb278de6dec7da
MD5 (sometestfile-1GB.vol063+064.par2) = 8be1eee920abc1f3d16e34569020e5c2
MD5 (sometestfile-1GB.vol127+072.par2) = 5082d6e041995d59c3a48fd89e17e666
Re: Downloads that need repair failing on Unraid Docker install but not on MacOS install
Posted: October 18th, 2025, 7:16 pm
by wapkaplet
I am starting to think this is some sort of permissions issue on the Unraid system, but I can't figure out what it is. The reason why I say that is that I watched my download fail in the following manner:
1. Progress through the download as normal
2. Proceed to verification and progress through that
3. Immediately report the download as failed without attempting a repair
The SABnzbd instance made no attempt to even download any par files.
I then set the owner of my entire Download folder to root (shouldn't have to do this) and redid the download, and the following happened:
1. Progress through the download as normal
2. Proceed to verification and progress through that
3. Go back several times to fetch more par files and re-verify, but never attempt repair
4. Report the download as failed
After that attempt, I pulled all the files over to my computer and was able to repair the file successfully.
I'm really stumped here.
Re: Downloads that need repair failing on Unraid Docker install but not on MacOS install
Posted: October 18th, 2025, 7:32 pm
by sander
So ... differences ... ?
Yes:
First:
Code: Select all
$ cat docker | awk '{ print $2 " " $NF }' | tr -d "()" | sort > docker.clean
$ cat mac | awk '{ print $2 " " $NF }' | tr -d "()" | sort > mac.clean
The compare
Code: Select all
$ diff docker.clean mac.clean
5c5
< sometestfile-1GB.part04.rar 0dbaf6a0df99076d7ce678e94ddd3301
---
> sometestfile-1GB.part04.rar 4743f47d199e1e6f6727f583526fd0bb
7,8c7,8
< sometestfile-1GB.part06.rar 233eb05de1987d0019741c7db333bede
< sometestfile-1GB.part07.rar d30848c7902035598649298e85798c79
---
> sometestfile-1GB.part06.rar 0aacd9bbdf50fa1b70efd26b1b430b87
> sometestfile-1GB.part07.rar 62b6254f4409152561ed050f16728d88
13a14
> sometestfile-1GB.vol001+002.par2 5ae45614ce3c5f9394d1aca0c9021c31
Yes, differences in the rar files. Not good. So disk / RAM problem?
Comparing your mac download with my download:
Code: Select all
$ diff zwarte.clean mac.clean
14,20c14,20
< sometestfile-1GB.vol001+002.par2 6dbe9ee239d1f38b36afbf97a788acef
< sometestfile-1GB.vol003+004.par2 4d1bdb27a689011bec9871354d16e465
< sometestfile-1GB.vol007+008.par2 dddb7a3ee4e3e14878361a7dcda58112
< sometestfile-1GB.vol015+016.par2 5385e11efd95305e9127abf59fafa00b
< sometestfile-1GB.vol031+032.par2 e0b26cf8ce34a1aca5308d8c97991e78
< sometestfile-1GB.vol063+064.par2 eb336b25dc85b0eb9fce26dcbf92978b
< sometestfile-1GB.vol127+072.par2 601aacf009435c635c27c0a31a98dcb4
---
> sometestfile-1GB.vol001+002.par2 5ae45614ce3c5f9394d1aca0c9021c31
> sometestfile-1GB.vol003+004.par2 bff699ed3dc727172de24c1df5792af7
> sometestfile-1GB.vol007+008.par2 3c28af340c3f3914ccb430162dd53335
> sometestfile-1GB.vol015+016.par2 863e57521b967e5aa596f38ea68a5d2a
> sometestfile-1GB.vol031+032.par2 90fad444723deb8e4adb278de6dec7da
> sometestfile-1GB.vol063+064.par2 8be1eee920abc1f3d16e34569020e5c2
> sometestfile-1GB.vol127+072.par2 5082d6e041995d59c3a48fd89e17e666
So differences in the par2 files (I don't know why), but not in the rar riles. So your MAC and my download at least agree on the rar files.
Next step: on your docker, do a few downloads of 1000MB with only Download (not: +Repair), and then compare the md5sum between them. If they differ ... big problem on your docker system. My guess: disk or RAM.
Re: Downloads that need repair failing on Unraid Docker install but not on MacOS install
Posted: October 18th, 2025, 7:37 pm
by sander
wapkaplet wrote: ↑October 18th, 2025, 7:16 pm
I am starting to think this is some sort of permissions issue on the Unraid system, but I can't figure out what it is.
Or a caching problem?
EDIT: maybe related / useful:
https://github.com/sabnzbd/sabnzbd/disc ... nt-9583601 (of which I understand nihil)
Before md5sum-check, you can check file sizes:
Code: Select all
$ ll ~/Downloads/complete/test_download_1000MB/
total 1154768
drwxrwxr-x 2 sander sander 4096 Oct 19 01:15 ./
drwxrwxr-x 5 sander sander 12288 Oct 19 01:15 ../
-rw-rw-r-- 1 sander sander 42696 Oct 19 01:15 sometestfile-1GB.par2
-rw-rw-r-- 1 sander sander 107374182 Oct 19 01:15 sometestfile-1GB.part01.rar
-rw-rw-r-- 1 sander sander 107374182 Oct 19 01:15 sometestfile-1GB.part02.rar
-rw-rw-r-- 1 sander sander 107374182 Oct 19 01:15 sometestfile-1GB.part03.rar
-rw-rw-r-- 1 sander sander 107374182 Oct 19 01:15 sometestfile-1GB.part04.rar
-rw-rw-r-- 1 sander sander 107374182 Oct 19 01:15 sometestfile-1GB.part05.rar
-rw-rw-r-- 1 sander sander 107374182 Oct 19 01:15 sometestfile-1GB.part06.rar
-rw-rw-r-- 1 sander sander 107374182 Oct 19 01:15 sometestfile-1GB.part07.rar
-rw-rw-r-- 1 sander sander 107374182 Oct 19 01:15 sometestfile-1GB.part08.rar
-rw-rw-r-- 1 sander sander 107374182 Oct 19 01:15 sometestfile-1GB.part09.rar
-rw-rw-r-- 1 sander sander 107374182 Oct 19 01:15 sometestfile-1GB.part10.rar
-rw-rw-r-- 1 sander sander 1780 Oct 19 01:15 sometestfile-1GB.part11.rar
-rw-rw-r-- 1 sander sander 582336 Oct 19 01:15 sometestfile-1GB.vol000+001.par2
-rw-rw-r-- 1 sander sander 1121976 Oct 19 01:15 sometestfile-1GB.vol001+002.par2
-rw-rw-r-- 1 sander sander 2243836 Oct 19 01:15 sometestfile-1GB.vol003+004.par2
-rw-rw-r-- 1 sander sander 4444976 Oct 19 01:15 sometestfile-1GB.vol007+008.par2
-rw-rw-r-- 1 sander sander 8804676 Oct 19 01:15 sometestfile-1GB.vol015+016.par2
-rw-rw-r-- 1 sander sander 17481496 Oct 19 01:15 sometestfile-1GB.vol031+032.par2
-rw-rw-r-- 1 sander sander 34792556 Oct 19 01:15 sometestfile-1GB.vol063+064.par2
-rw-rw-r-- 1 sander sander 39109676 Oct 19 01:15 sometestfile-1GB.vol127+072.par2
If file sizes are different between downloads, the md5sum cannot be the same.
Re: Downloads that need repair failing on Unraid Docker install but not on MacOS install
Posted: October 18th, 2025, 8:47 pm
by wapkaplet
Swapped the RAM for another set of known good RAM. The system seems to be behaving now.
RAM made the most sense because I had gone as far as to change the share that SABnzbd was downloading and unpacking to.
Thank you very much for the needed perspective. I was so down the rabbit hole of software solutions I didn't stop to think about the obvious hardware possibility. This would explain all the random behavior I was seeing.
Here's a download test with the Docker running on different RAM:
Code: Select all
MD5 (sometestfile-1GB.par2) = 835a1a13b7f3d8f21966db95e3f72f88
MD5 (sometestfile-1GB.part01.rar) = 190bed240d66af7525613318268b0667
MD5 (sometestfile-1GB.part02.rar) = d243306f0df83ea82077aa19c6d56f7d
MD5 (sometestfile-1GB.part03.rar) = 0fb453b4677cbedf9dbce250a97aba16
MD5 (sometestfile-1GB.part04.rar) = 4743f47d199e1e6f6727f583526fd0bb
MD5 (sometestfile-1GB.part05.rar) = f59982cb31da48e927b8c87143c4c5b0
MD5 (sometestfile-1GB.part06.rar) = 0aacd9bbdf50fa1b70efd26b1b430b87
MD5 (sometestfile-1GB.part07.rar) = 62b6254f4409152561ed050f16728d88
MD5 (sometestfile-1GB.part08.rar) = 0188b599a284310552764348a2fcf16c
MD5 (sometestfile-1GB.part09.rar) = 7dc80d0e9f05e8983198f37e21ab33ae
MD5 (sometestfile-1GB.part10.rar) = 202824d948682a86fcd7263186dd0a87
MD5 (sometestfile-1GB.part11.rar) = 8dee7ad88a349717bd2272846b18db80
MD5 (sometestfile-1GB.vol000+001.par2) = 5671a4ed841c11e518cafecd2fa1f7f5
MD5 (sometestfile-1GB.vol001+002.par2) = 5ae45614ce3c5f9394d1aca0c9021c31
MD5 (sometestfile-1GB.vol003+004.par2) = bff699ed3dc727172de24c1df5792af7
MD5 (sometestfile-1GB.vol007+008.par2) = 3c28af340c3f3914ccb430162dd53335
MD5 (sometestfile-1GB.vol015+016.par2) = 863e57521b967e5aa596f38ea68a5d2a
MD5 (sometestfile-1GB.vol031+032.par2) = 90fad444723deb8e4adb278de6dec7da
MD5 (sometestfile-1GB.vol063+064.par2) = 8be1eee920abc1f3d16e34569020e5c2
MD5 (sometestfile-1GB.vol127+072.par2) = 5082d6e041995d59c3a48fd89e17e666
Re: Downloads that need repair failing on Unraid Docker install but not on MacOS install
Posted: October 19th, 2025, 5:25 am
by sander
Brrrrr. Makes clear the added value of error detecting and error correcting codes at hardware level, so Ram with ECC.
Good it's clear and solved now
Good to know: RAM test from Unraid boot with Memtest86+
https://docs.unraid.net/unraid-os/troub ... esting-ram
And I now realize:
Hypothesis: On a correct system, the download is deterministic, and repeated downloads of the same NZB (the 1000MB test file) on the same system, should have the same result. If not, the system is not correct.
So that can be done within one SABnzbd setup.