Page 1 of 1

Download in History stuck with - "» Repair: Starting Repair" Status.

Posted: July 29th, 2010, 4:02 pm
by DejaVu
And I've checked to see if par2.exe has started but it hasnt. This download is not exactly slowig progress, but it's annoying it's there.

Does anyone know how to purge a download that has no remove button?

If not, I'll simply reinstall.

I'm on the latest vesion 0.53

It's only a 9Mb download, but there is nothing in Complete or Incomplete at all...?

Re: Download in History stuck with - "» Repair: Starting Repair" Status.

Posted: July 30th, 2010, 6:57 am
by shypike
What's your Operating system?
Where did you get the NZB from?
Is the download within the retention time of your Usenet provider?
Do you get missing articles warnings?

Re: Download in History stuck with - "» Repair: Starting Repair" Status.

Posted: August 1st, 2010, 8:14 pm
by fallchild
I have the same issue on osx

Re: Download in History stuck with - "» Repair: Starting Repair" Status.

Posted: August 2nd, 2010, 1:45 pm
by feerlessleadr
this may be a stupid question, but have you tried restarting sab?

i have a problem sometimes where a download will get stuck between 'repair failed' and 'repairing'

All i have to do is restart sab and I am good to go.

Re: Download in History stuck with - "» Repair: Starting Repair" Status.

Posted: August 6th, 2010, 9:09 am
by MasterDocious
Once it restarts does sab automatically boot up and all ready to use or do you have to do anything special to it in order to be able to fully use it? Im aware of this post on the wiki (http://wiki.sabnzbd.org/faq#toc10) also so I'm not ignoring this. I am not the owner of the server and so I cannot go into the task manager and kill that task. Will restarting do the trick or am I gonna have some snags? Do I need to do any extra things once it's restarted that could only be done from the first person stance...right there in the physical room where the server is?

Re: Download in History stuck with - "» Repair: Starting Repair" Status.

Posted: August 13th, 2010, 7:36 am
by shypike
Removing the job's folder in the "temporary download folder" should take care of this.
The next restart you'll get some error messages, but the problem should be gone.