Quote from: bob123 on February 22, 2018, 09:45:47 AM

Quote from: Teeruk on February 22, 2018, 08:44:01 AM

Code:

2018-02-22 01:24:37 IO error: Win32WritableFile.Sync::FlushFileBuffers F:\work\Bitcoin core\blocks\index\001215.ldb: The request failed due to a fatal device hardware error.
..
2018-02-22 01:24:41 IO error: Win32WritableFile.Sync::FlushFileBuffers F:\work\Bitcoin core\blocks\index\000001.dbtmp: The request failed due to a fatal device hardware error.
..
2018-02-22 01:24:42 CDBEnv::EnvShutdown: Error -30974 shutting down database environment: DB_RUNRECOVERY: Fatal error, run database recovery
...
2018-02-22 01:24:48 IO error: Win32WritableFile.Sync::FlushFileBuffers F:\work\Bitcoin core\blocks\index\000001.dbtmp: The request failed due to a fatal device hardware error.
...
2018-02-22 01:24:49 IO error: Win32WritableFile.Sync::FlushFileBuffers F:\work\Bitcoin core\blocks\index\000001.dbtmp: The request failed due to a fatal device hardware error.

It seems like your hard drive is somehow broken and this led to your data getting corrupted.
Did you already check whether your HD is working as intended?
You could try to read out the S.M.A.R.T values of your HD and see if everything works as it should. [1]

My guess would be that your HD got corrupted during v0.14.2 and core wasn't able to read those files after updating to 0.15.1

[1] Tools to read out S.M.A.R.T. values: https://en.wikipedia.org/wiki/Comparison_of_S.M.A.R.T._tools

I doubt smth wrong with the drive... As far as I running plenty of virtual machines on the same drive.
It's a T1 with built-in encryption. Maybe something wrong with that...

But anyway, what should I do to fix it now?
I dont want to download 16x gb again lol

Teeruk

Posts

Merits