Thread: Classy Calibre
View Single Post
Old 05-24-2012, 05:46 PM   #14
theducks
Well trained by Cats
theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.
 
theducks's Avatar
 
Posts: 30,972
Karma: 60358908
Join Date: Aug 2009
Location: The Central Coast of California
Device: Kobo Libra2,Kobo Aura2v1, K4NT(Fixed: New Bat.), Galaxy Tab A
Quote:
Originally Posted by ilovejedd View Post
Sounds like a failing hard drive. Symptoms just happened to coincide with the Calibre update. The thing to do when something like the above happens is to pull the HDD from the system, slave it and create an image/backup while it's still possible to read from the drive. You certainly don't try to keep writing to it.

I have an Intel Atom 330-based PC (slower than later P4s) that handles a Calibre library with 3,000 titles just fine with Microsoft Security Essentials running in the background so I doubt Calibre is the culprit. It's possible that the Calibre update (and resulting metadata.db upgrade) brought the issue to the forefront but I reckon it would still have happened sooner or later.
The fact the op manage to kill his system backs up the idea of hardware failure. They kept making a cardiac case run uphill in a misguided attempt at recovering.

Bulging Caps, clogged fan grills/fins are other common faults that bring systems down under load. some kill them dead if not resolved in a short period.
theducks is offline   Reply With Quote