SABnzbd Forums

Hello.

I've read all the other threads concerning this error and they usually end with it being fixed with a new build but the last one was ages ago and I'm still having this issue for months now.

I dont really mind since just pressing Pause to unpause sabnzbd "fixes" the error and it'll continue happily as if there never was an issue. Until it happens again. With large download queues usually every couple of hours.

I assumed it is my SSD dying since it had PB of data written to it and even though the tool says it's in ok health, it should have died hundreds and hundreds of TB ago apparently. Another reason I wasnt to bothered by that error.

What does bother me is not so much the error itself but that I seem to be unable to find a way to get sabnzbd to automatically resume operation once it happened. You know, instead of me having to up-pause it. That would be marvellous for when I'm away it sabnzbd sits there idle for hours when it really didnt have to,

Any switch or script to cover that scenario?

You'll have to be much more specific.. Disk errors are a collection of all things that can co wrong when writing files.
It could be permissions, network, broken folders, corrupt disk.. Anything. What is the exact error you get?
It isn't throwing them for fun..

no it's throwing them to piss me off :-)

I've sent you the log via email.

that's all I see outside the log:

ERROR an hour ago Disk error on creating file G:\__PROCESSING\_PENDING_NG\
ERROR 6 hours ago Disk error on creating file G:\__PROCESSING\_PENDING_NG\
ERROR 15 hours ago Disk error on creating file G:\__PROCESSING\_PENDING_NG\

I've removed the file names.

hypersucker wrote: ↑March 13th, 2022, 3:40 pm
ERROR an hour ago Disk error on creating file G:\__PROCESSING\_PENDING_NG\
ERROR 6 hours ago Disk error on creating file G:\__PROCESSING\_PENDING_NG\
ERROR 15 hours ago Disk error on creating file G:\__PROCESSING\_PENDING_NG\

What kind of driver is G:? Built-in, USB, NAS ... ?

internal 1TB SSD

I get no error on this disk from other apps or explorer but to be fair, sabnzbd does 90% of the load

OK. And why then the strange/high letter G:? Internal, but special config? Or a lot of drives? (I don't know too much about Windows)

What happen if you let SAB save to C:?

hey sander I think safihre found the error. gonna test the build he suggested later.

G high? I'm down to X. and yes, very, very many drives. but I'll reorg soon.

safihre, I think the patch from the minor release works, havent seem any disk errors anymore. I think this is solved. thank you!

works fabulously. no error in the last 30TB.

I have another issue and I'll gladly open a new thread for it but maybe this is only relevant to me or so rare no one really cares then I'll leave it be since I have a manual solution for it.

every now and then, a release wont complete because it is too broken. usually they get uploaded multiple times anyway so one of them is bound to be complete. but sometimes all of them are broken beyond repair. that is, the single downloads (nzbs) are broken beyond repair. e.g. when I collect all the single download folders within multipar, most of the times I end up with a working download. it is probably to hard for sabnzbd to automatically see which folders are actually the same files and combine (mix/match/throw out) those instead of just focusing repair efforts on each single folder? Hydra 2 already does a good job recognizing which nzbs should be grouped together, if sabnzbd would do something similar, it could try repair efforts within groups and not just with in a nzb folder. hope that made any sense at all lol.

separate thread please, with a relevant subject