SABnzbd Forums

Hi all,

I'm running SABnzbd 0.7.16 on a Netgear ReadyNAS Ultra 2 and have a curious problem.

Whenever I download a DVD the fourth VOB file (VTS_01_04.VOB) is corrupted. If I download the same DVD (using the same .nzb file) on my PC, I have no problems at all.

I made sure both SABnzbd and the ReadyNAS are updated and have tried about 10 DVD's. All had the same issue.

Thanks for any tips!

Does the download verify properly (using par2 files)?
Does the nzb consist of RAR files?
Do you see a CRC error coming from unrar in the download report?

Does the download verify properly (using par2 files)?
Yes, download, verify, extract and move are without errors.
Does the nzb consist of RAR files?
Yes, rar and par files
Do you see a CRC error coming from unrar in the download report?
No, no errors at all.

Thanks for taking the time to reply though

Found it!

I don't think it's an SABnzbd issue, but a Netgear ReadyNAS issue.

Although my share settings are read/write for all, the settings for all new VTS_01_04.VOB files had different settings. Re-applying the read/write settings ensured proper working of the VOB file.

Not sure what goes wrong and which system is responsible, but at least it's working.

Cheers.

Possibly the poster messed up access rights in the RAR files.
You can have SABnzbd explicitly set the access rights.
See Config->Folders and the explanation here: http://wiki.sabnzbd.org/unix-permissions

Possibly, but no. Permission was 777 (full access for everyone). And if I'm not mistaken, all files would have the same issue, not just the 4th VOB file.

Thanks for the reply though! Appreciated.

That is weird, that would mean that SABnzbd isn't allowed to change the rights of that file.
Now SABnzbd doesn't report failure to change access rights, because on some
systems this would mean a lot of false reports. It would be very odd indeed that this one file isn't changeable.
Do the other files actually end up with full access rights?

Sorry for the extremely late reply, but it's for when other people encounter the same issue (and in fact I still have the same issue, but the workaround is easy).

The other files indeed have full access rights. I'm still guessing it's a ReadyNAS issue though.