4.0a Indexing crashes on completion of index
This is 100% reproducible. Indexer crashes when index is about 1470MB (about usual size), and then it crashes. When I dismiss the crash dialog, the index files are all deleted.
L4 is able to run apparently without any problems.
I'm currently running indexing again with logging enabled.
Has anyone else encountered this specific set of circumstances?
Comments
-
I've had a number of indexer crashes. I've only been able to 'fix' them by reloading all my resources.
Pastor, North Park Baptist Church
Bridgeport, CT USA
0 -
Ah ... what does "reloading all my resources" mean? Deleting them and redownloading?
0 -
I purchased the DVD of the L4 resources and used that for the majority of them and then let the others download. I doubt you have the DVD or wouldn't be asking.
You would have to delete the resources and re-download.
My install crashed when it was almost finished. I sent in the log files in hopes of getting a work-around, but that never materialized, so I deleted, reloaded, and indexing successfully completed after that.
I really wish Logos could create a way to identify what is causing a specific indexing crash so one wouldn't have to do what I (and others) did. AFAIK these crashes have always been traced back to one or more defective resources.
Pastor, North Park Baptist Church
Bridgeport, CT USA
0 -
The indexer log should help. Often the cause can be a corrupt resource. This can sometimes be fixed by temporarily hiding the resource (so you don't need to re-download all the resources, just one).
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
Great, thanks - I'll give those a try.
Cheers
Richard0 -
Turns out that the indexer has finished indexing and is performing some other operations when the crash occurs - from the indexer log:
Does this suggest anything?
Thanks
Richard2009-12-23 17:38:13.9687 7 Info LibraryIndex Finished indexing resources (in 01:40:46.9743945); writing postings.
2009-12-23 17:38:27.7187 1 Info Program Setting notification icon tool tip to: Logos Bible Software is indexing (44 minutes remaining)
2009-12-23 17:39:57.7187 1 Info Program Setting notification icon tool tip to: Logos Bible Software is indexing (31 minutes remaining)
2009-12-23 17:40:14.6875 7 Error Program Unhandled exception: System.IO.IOException: Data error (cyclic redundancy check).
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.FileStream.ReadCore(Byte[] buffer, Int32 offset, Int32 count)
at System.IO.FileStream.Read(Byte[] array, Int32 offset, Int32 count)
at Libronix.Utility.StreamUtility.ReadExactly(Stream stream, Byte[] buffer, Int32 offset, Int32 count)
at Libronix.SearchEngine.StreamBlockManager.ReadBlock(Int32 nBlock, Byte[] abyBuffer)
at Libronix.SearchEngine.BlockRunStream.LoadCurrentBlock(Boolean bGrowRun)
at Libronix.SearchEngine.BlockRunStream.ReadByte()
at Libronix.Utility.BitReader.ReadNextByte()
at Libronix.Utility.BitReader.ReadUnary()
at Libronix.Utility.BitUtility.ReadGamma(BitReader reader)
at Libronix.Utility.BitUtility.ReadDelta(BitReader reader)
at Libronix.SearchEngine.SortedPostingReader.MoveNext()
at Libronix.SearchEngine.PostingsFileCreator.ExternalMergeSortFileBlocks(BlockRunManager mgrIn, BlockRunManager mgrOut, IWorkState state, Action`1 fnReportProgress)
at Libronix.SearchEngine.PostingsFileCreator.WritePostings(IWorkState state, IIndexerProgress progress)
at Libronix.SearchEngine.Indexer.WritePostings(IWorkState state)
at Libronix.DigitalLibrary.LibraryIndex.DoBuildIndex(ILibraryIndexWorkState state, Int32 nResourceCount, String strIndexName, Double fFractionOfIndexableResourcesBeingIndexed, Int32 nMaxAdditionalThreads)
at Libronix.DigitalLibrary.LibraryIndex.BuildIndex(LibraryIndexWorkState state, String strIndexName, Double fFractionOfIndexableResourcesBeingIndexed)
at Libronix.DigitalLibrary.LibraryIndex.IndexResources(IPausableWorkState threadOwnerWorkState, LibraryIndexWorkState state)
at Libronix.Utility.Threading.WorkStateThreadOwner`1.ThreadProc(Object objData)
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart(Object obj)
2009-12-23 17:40:27.7187 1 Info Program Setting notification icon tool tip to: Logos Bible Software is indexing (30 minutes remaining)0 -
That suggests corruption on your hard disk. Can you run scandisk and check for errors?
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
Here's the log files ... created before the Scandisk.
Scan disk found and repaired some minor NTFS index errors, but the files in question were JPGs.
8787.Logos Log Files.zip">http://community.logos.com/cfs-file.ashx/__key/CommunityServer.Discussions.Components.Files/76/8787.Logos-Log-Files.zip:550:0]
]Am currently attempting indexing again after the Scandisk run.
0 -
Richard,
I still think it's a disk error, though it's theoretically possible that Logos has an internal error with the same name as a Windows disk error. If you didn't do so before, run Scan disk looking for bad sectors across your whole drive. The problem could well be on an empty part of your drive that the indexer attempts to write to.
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
Hi ...
It looks like my HD is going belly up - CRC errors all over the place, so maybe it's a good thing we caught this so I can salvage as much as possible.
Thanks
Richard0 -
Yes, best to do that ASAP, I think. Once you've backed up your vital data, turn on SMART monitoring (if it's not on already), and run a SMART monitor from your disk manufacturer, or from here: http://www.ntfs.com/disk-monitor.htm
It's normal to get some bad sectors during the life of a disk, but once it goes a certain level, that's a fairly sure sign the disk is about to go. Monitoring software will help you determine whether that level's been reached.
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
Thanks again ... I've been using Crystal Disk monitor but will try the one you suggest.
A little Logos error has alerted me to a larger issue and save vital data before the Titanic sinks, as it were!
Thanks
Richard0
