Problem with Sickbeard

[KingBel]

Hi,
I'm hoping someone can help. I can't seem to get Sickbeard to load anymore.

This is what I found in the error logs:

Traceback (most recent call last):
File "SickBeard.py", line 403, in <module>
File "SickBeard.py", line 323, in main
File "sickbeard\__init__.pyo", line 643, in initialize
File "sickbeard\db.pyo", line 191, in sanityCheckDatabase
File "sickbeard\databases\mainDB.pyo", line 35, in check
File "sickbeard\databases\mainDB.pyo", line 57, in fix_duplicate_episodes
File "sickbeard\db.pyo", line 152, in select
File "sickbeard\db.pyo", line 129, in action
sqlite3.OperationalError: disk I/O error

Anybody know how I can fix without having to reinstall and setup again?

 

[kidcolt]

sqlite3.OperationalError: disk I/O error

scandisk / fsck... depending on your platform

 

[Tinuva]

>>> sqlite3.OperationalError: disk I/O error

You have possibly hardware problems. Physical disk have issues, or the partition has corrupt data and you need to do a checkdisk to fix the errors.

It is possible that the hard drive is fine, and you have a faultly memory module, but that is a rare case. I would first try a checkdisk, if that doesn't fix it, it is possible you may need to replace that hard drive to prevent even further data loss.

 

[KingBel]

scandisk / fsck... depending on your platform

hmmm.. so possibly a bad sector? hope not. although that HD is quite old... :/

 

[KingBel]

Thanks guys. So the error would most likely be on the HD that Sickbeard is installed on? Not the source drive for the media?

I would probably end up scanning all drives for errors in any case.

 

[KingBel]

ran scandisk.. fixed the error.. but now the sickbeard.db is not accessible.. looks like i'm going to have to setup from scratch. Luckily (Sadly), I'm not doing anything else this weekend..

 

[KingBel]

Sorry to necro, but I didn't want to start a new thread. Is anybody else experiencing problems on SABNzb? I have a huge queue of items waiting, but nothing is downloading. I'm have a usenetbucket account and never had issues before.

Could this be because of the SEACOM cable issues?