#Nzbget unraid drivers
#Nzbget unraid full

With a queue being stuck with one NZB not unpacking correctly I restarted nzbget and lo and behold everything unpacked as expected. I had the issue this morning again (seems to be every morning or early in the day at least as that's when nzbget is doing most of the work). Edit: ran scrub, it did not report any errors. Will run a scrub to see if there are any corruptions. Since when the issue started to happen? Were there updates of Unraid software recently before that?ĭifficult to tell, but could be around unRAID 6.5.x or maybe even 6.4.xĪre there any way to check disks for errors?ītrfs scrub can be done, but it's unlikely to be related to that.

#Nzbget unraid drivers

What media is used for InterDir: is this a software RAID? Can you put InterDir into a simple non-RAID disk (formatted as EXT4 which doesn't use any fancy Unraid drivers or software)?Ħ equally sized and branded SSDs in btrfs RAID10 Are there any way to check disks for errors?.Since when the issue started to happen? Were there updates of Unraid software recently before that?.What media is used for InterDir: is this a software RAID? Can you put InterDir into a simple non-RAID disk (formatted as EXT4 which doesn't use any fancy Unraid drivers or software)?.What and ChapeL (forum user) have in common? It's Unraid with docker. Once again that means the repaired files computed during repair were not written properly into disk as subsequent reading of files from disk and recompilation of checksums fails. par-repair is performed: at the end of repair the repaired files are checked and they don't have correct checksums the par-repair fails with message 'repair completed but the data files still appear to be damaged'.That means the downloaded files were not properly written into disk otherwise their checksums would fail with first quick par-check This par-check reports errors in multiple files.

#Nzbget unraid full

second par-check is performed this time in full mode where all downloaded files are read from disk and their checksums are calculated again.

another unpack is made (after par-check) which fails again.

first par-check reports files are OK and not repair is necessary that first par-check is made in quick mode (that's OK) and it relies on file checksums calculated during downloading the succeeded par-check confirms the files were downloaded correctly.

unrar fails to start properly (it hangs) or unrar reports checksum error.

no errors are reported during downloading.

The logs exhibit the very similar behaviour as reported by other user on forum in topic I'm getting numerous PAR: FAILURE errors: