SABnzbd Forums

zoggy, did you read Safihre's issue & analysis on https://github.com/sabnzbd/sabnzbd/issues/3212 ?

Yeah same for me if I reload them. It's a 1TB NVMe SSD mounted locally so I can maximise my download speeds. The issue only happens about 1/2 times a week, all other nzbs work fine.

sander wrote: ↑December 1st, 2025, 1:49 pm zoggy, did you read Safihre's issue & analysis on https://github.com/sabnzbd/sabnzbd/issues/3212 ?

I saw the initial post which got me here because my knee jerk reaction was to question if direct unpack was a factor as not using that simplifies the process greatly. imho people that use direct unpack and have decent internet should go to config > switches > Download all par2 files -- enable that. that way things can verify/repair quickier, less runs to do if direct unpack tries to have to abort to fallback because something was incomplete.

In this case it wouldn't help. It's a race condition and a bug all at once.

safihre wrote: ↑December 1st, 2025, 4:49 pm In this case it wouldn't help. It's a race condition and a bug all at once.

yeah i didnt say it would just was responding to sander, i saw your comment that basically direct unpacker aborts and deletes and goes fubar..
but was a bit shocked we didnt log why and just said no files extract -- i would think if we abort direct unpacker we should fail back to non direct unpack ?

Thanks for all your support, added a small donation.

Just wanted to see if this will be fixed, or has been fixed in a beta release? I am on 4.5.5 and seeing this happen intermittently

I’m on 4.6.0 beta 2 and haven’t had it happen since updating to beta 1