4.2a gold crash durring indexing

Page 1 of 1 (6 items)
This post has 5 Replies | 0 Followers

Posts 1150
Anthony H | Forum Activity | Posted: Tue, Mar 1 2011 7:04 PM

 

0172.Logos4IndexerCrash.txt

 

Posts 19176
Rosie Perera | Forum Activity | Replied: Tue, Mar 1 2011 7:15 PM

The crash error in the first file is "Some kind of disk I/O error occurred" -- that usually indicates some sort of hard disk failure. I would recommend doing some hardware diagnostics. Are you running Windows? I'd try running CHKDSK to find if there are bad sectors and flag them so Logos doesn't try to write to them in the future (see http://www.pcstats.com/articleview.cfm?articleid=1583&page=5).

The Logos4Indexer crash file has a later timestamp than the earlier one, so the error message there is not as interesting because a disk I/O error can cause all kinds of other problems later down the road.

EDIT: Anthony, while I was composing my reply, you removed the key file. Please put it back if you still have it. It had important info in it that was more relevant than the one you left posted here.

Posts 9468
Forum MVP
Mark Smith | Forum Activity | Replied: Tue, Mar 1 2011 8:11 PM

Anthony, could you upload the indexer log file and the Logos4 log file as well?

Pastor, North Park Baptist Church

Bridgeport, CT USA

Posts 1150
Anthony H | Forum Activity | Replied: Wed, Mar 2 2011 6:16 AM

Disregard the first post altogether.

I do in fact have some bad sectors on the hard drive. The issue doesn't appear to Logos specific. I was able to work around the crashes by using "Rebuld Index" in the command field right after the indexer crashed the third time. I meant to get back on here and report/correct my post but "blue screened". Looks like I will be shopping for a new hard drive.

Posts 19176
Rosie Perera | Forum Activity | Replied: Wed, Mar 2 2011 6:23 AM

Anthony H:
I do in fact have some bad sectors on the hard drive. The issue doesn't appear to Logos specific. I was able to work around the crashes by using "Rebuld Index" in the command field right after the indexer crashed the third time. I meant to get back on here and report/correct my post but "blue screened". Looks like I will be shopping for a new hard drive.

Backup, backup, backup any vital files, now while you still can. A few bad sectors don't mean a HD is completely about to fail; they can be marked for avoidance (using CHKDSK), but if it's crashing a lot and continues to do so even after you mark the bad sectors, then a failure is imminent and you need to get as much of the data off the drive as you can before it dies altogether. And I'd start doing such a backup as soon as the first bad sectors start rearing their ugly head, because total HD failures can come up rather suddenly. All the best with it!

Posts 1150
Anthony H | Forum Activity | Replied: Wed, Mar 9 2011 11:07 AM

Just an fyi,

 A bit of a hassle initially but I had a good disk image so a blessing was then end result.

I have replaced my hard-drive with a 7200rpm. Wow! positive improvement on Logos 4 performance.Thank you Jesus!

 

P.S. There is wisdom in regular back-ups! Create an disk image. You may never need it, but when you do, you'll be thankful you have it!

Page 1 of 1 (6 items) | RSS