SABnzbd Forums

Hi all,
I have setup my DS 212+ so SABnzbd and Sickbeard are working properly.

Now my question is, since the DS isnt very powerfull, is there a way to configure SAB so it would... copy the downloaded files to another computer, that computer would then do the repair job, copy back to my DS, and SAB would take it from there...

Basically, I just want to be able to do the repairing on a much more powerfull computer than my DS. So it could also be to pause the repair from SAB, manually copy the files I want to check, on my computer, repair them, but then afterward, "let know" SAB that the files are fixed and ready for post-processing...

I don't know if that makes any sense, but anyway, I'm taking a chance to ask you guys!

Thanks

That's probably too complicated, unless you're good at
writing scripts and reproducing part of the functionality of SABnzbd in those scripts.

what about doing it manually?

Sure, then use "Download" instead of "+Delete".
But you'll lose most of the reasons to use SABnzbd

If possible, would it make sense? Imagine you have downloaded all rar and par2 files, total 5GB. You then copy this over your LAN, at a speed of ... let's say 100 Mbps = 10 MB/s. So that takes 500 seconds = more than 8 minutes. You repair on some other machine, and then you have to copy back 4.5GB ... which takes almost 8 minutes.

So, you loose 16 minutes, which must we won by a faster par2 and unrar process. Now the main questions: how long does the par2/unrar process take on the Synology DS?

sander wrote:If possible, would it make sense? Imagine you have downloaded all rar and par2 files, total 5GB. You then copy this over your LAN, at a speed of ... let's say 100 Mbps = 10 MB/s. So that takes 500 seconds = more than 8 minutes. You repair on some other machine, and then you have to copy back 4.5GB ... which takes almost 8 minutes.

So, you loose 16 minutes, which must we won by a faster par2 and unrar process. Now the main questions: how long does the par2/unrar process take on the Synology DS?

I see your point.

but the thing is, the Synology DS212+ has a single core 2.0 ghz processor.. http://www.marvell.com/embedded-process ... 2-3_pb.pdf
I get repairs in about 3-4 hours per download... and that's when after verifying has completed successfully, as most of the time, after 2-3 hours of verification, it fails, then I manually have to press retry so they start downloading the missing part, verify again, retry manually then repair (most of the time, I need 2-3 verify/retry before it actually does the repairing).

So maybe it's just that the NAS should be the one doing the downloads and repair stuff.. I should probably simply install all this on a computer, and then have Sickbeard copy the files TO the NAS. So all the hard processing would have been done on the computer.

So you see, doing it manually wouldn't be that bad if I kept that setup like that as I would actually be saving a LOT of time. But maybe I should just rethink my setup instead...!

Repairs take 3-4 hours on a 2 GHz processor? How big are those downloads? This must be much bigger than 5GB downloads, right?

But still: is it a problem that your NAS is working somewhere in the back?

sander wrote:Repairs take 3-4 hours on a 2 GHz processor? How big are those downloads? This must be much bigger than 5GB downloads, right?

But still: is it a problem that your NAS is working somewhere in the back?

It's a 2GHz arm processor, must slower than x86 running at the same speed... and no, the downloads are roughly around 3.5-4.5GB so yeah, it's really slow... and when verifying/repairing the NAS is mostly only doing this...

No it's not a big deal that it's running in the back, it's just that I wish I could have started building my library faster