Quote from: rarkenin on July 15, 2014, 06:54:03 PM

Might be me, but "ERROR: ReadBlockFromDisk : OpenBlockFile failed" looks like an error. Could you try renaming that offending file to some unrelated name?

If that fails, you may consider trying to re-sync after deleting or renaming the C:\bitcoin\data\blocks folder.

Yes would be the error I can see how the title would be confusing. Outside of the debug.log there was no error message when the application crashed. I restarted bitcoind and it validated blocks without issue. The start of the log after restart is the following (no indication of the read error).

Code:

2014-07-15 16:48:01 Bitcoin version v0.9.2.0-g505681f-beta (Fri, 13 Jun 2014 12:26:02 +0200)
2014-07-15 16:48:01 Using OpenSSL version OpenSSL 1.0.1h 5 Jun 2014
2014-07-15 16:48:01 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010)
2014-07-15 16:48:01 Default data directory
2014-07-15 16:48:01 Using data directory c:\bitcoin\data
2014-07-15 16:48:01 Using at most 250 connections (2048 file descriptors available)
2014-07-15 16:48:01 Using 8 threads for script verification
2014-07-15 16:48:01 Using wallet wallet.dat
2014-07-15 16:48:01 init message: Verifying wallet...
2014-07-15 16:48:01 CDBEnv::Open : LogDir=c:\bitcoin\data\database ErrorFile=c:\bitcoin\data\db.log
2014-07-15 16:48:02 Bound to [::]:8333
2014-07-15 16:48:02 Bound to 0.0.0.0:8333
2014-07-15 16:48:02 AddLocal(66.232.104.157:8333,5)
2014-07-15 16:48:02 init message: Loading block index...
2014-07-15 16:48:02 Opening LevelDB in c:\bitcoin\data\blocks\index
2014-07-15 16:48:02 Opened LevelDB successfully
2014-07-15 16:48:02 Opening LevelDB in c:\bitcoin\data\chainstate
2014-07-15 16:48:02 Opened LevelDB successfully
2014-07-15 16:48:11 LoadBlockIndexDB(): last block file = 157
2014-07-15 16:48:11 LoadBlockIndexDB(): last block file info: CBlockFileInfo(blocks=132, size=35903286, heights=310658...310789, time=2014-07-14...2014-07-15)
2014-07-15 16:48:11 LoadBlockIndexDB(): transaction index enabled
2014-07-15 16:48:11 LoadBlockIndexDB(): hashBestChain=000000000000000033cd828bf6b8662f424f165def4ccd6d3bf0aa86c89a4680 height=310789 date=2014-07-15 04:05:56 progress=0.998249
2014-07-15 16:48:11 init message: Verifying blocks...
2014-07-15 16:48:11 Verifying last 288 blocks at level 3
2014-07-15 16:48:41 No coin database inconsistencies in last 289 blocks (116571 transactions)
2014-07-15 16:48:42 block index 40463ms
2014-07-15 16:48:42 init message: Loading wallet...
2014-07-15 16:48:42 nFileVersion = 90200
2014-07-15 16:48:42 Keys: 0 plaintext, 1920 encrypted, 414 w/ metadata, 1920 total
2014-07-15 16:48:42 wallet 234ms
2014-07-15 16:48:42 init message: Rescanning...
2014-07-15 16:48:42 Rescanning last 37 blocks (from block 310752)...

Bitcoind has been very reliable. It was just unusual to get a fatal read error which caused the application to crash and then restarting it showed no issue. It would indicate the error (whatever caused it) was recoverable.