chainstate files?

[calkob]

PC Crashed yesterday due to a graphics error, nothing to do with Bitcoin core.  went to run core again today but getting this error below.  I had a look in the Chainstate folder and all files are locked by Microsoft Access, any ideas on how to resolve this? 

also tried running with arg -reindex but still error.

Thanks



2024-02-28T10:21:38Z Opening LevelDB in E:\BitcoinNode\chainstate
2024-02-28T10:21:38Z Fatal LevelDB error: IO error: E:\BitcoinNode\chainstate/LOCK: The file or directory is corrupted and unreadable.\x0d

2024-02-28T10:21:38Z You can use -debug=leveldb to get more complete diagnostic messages
2024-02-28T10:21:38Z Fatal LevelDB error: IO error: E:\BitcoinNode\chainstate/LOCK: The file or directory is corrupted and unreadable.\x0d

2024-02-28T10:21:38Z : Error opening block database.
Please restart with -reindex or -reindex-chainstate to recover.
: Error opening block database.
Please restart with -reindex or -reindex-chainstate to recover.
2024-02-28T10:21:38Z Aborted block database rebuild. Exiting.
2024-02-28T10:21:38Z Shutdown: In progress...
2024-02-28T10:21:38Z scheduler thread exit
2024-02-28T10:21:38Z Shutdown: done

[1714650935]

1714650935

[1714650935]

1714650935

[1714650935]

1714650935

[1714650935]

1714650935

[1714650935]

1714650935

[ranochigo]

What error do you receive when you're running the reindex? Try renaming the chainstate to another name before trying the reindex again. Bitcoin Core should trigger a reindex if it doesn't detect the chainstate directory in the datadir.

[calkob]

What error do you receive when you're running the reindex? Try renaming the chainstate to another name before trying the reindex again. Bitcoin Core should trigger a reindex if it doesn't detect the chainstate directory in the datadir.

2024-02-28T11:07:52Z Initializing databases...
2024-02-28T11:07:52Z Wiping LevelDB in E:\BitcoinNode\chainstate
2024-02-28T11:07:52Z Opening LevelDB in E:\BitcoinNode\chainstate
2024-02-28T11:07:52Z Fatal LevelDB error: IO error: E:\BitcoinNode\chainstate/LOCK: The file or directory is corrupted and unreadable.\x0d

2024-02-28T11:07:52Z You can use -debug=leveldb to get more complete diagnostic messages
2024-02-28T11:07:52Z Fatal LevelDB error: IO error: E:\BitcoinNode\chainstate/LOCK: The file or directory is corrupted and unreadable.\x0d

2024-02-28T11:07:52Z Error: Error opening block database
2024-02-28T11:07:52Z Shutdown: In progress...
2024-02-28T11:07:52Z scheduler thread exit
2024-02-28T11:07:52Z Shutdown: done


***UPDATE**** Renaming the Chainstate folder seems to have worked, currently reindexing.  Thanks will let ya know if it has further issues.

[NotATether]

***UPDATE**** Renaming the Chainstate folder seems to have worked, currently reindexing.  Thanks will let ya know if it has further issues.

Yeah, as the diagnostic says, these kind of issues can almost always be fixed by running Core with -reindex (or -reindex-chainstate if only chainstate is corrupted).

[nc50lc]

Yeah, as the diagnostic says, these kind of issues can almost always be fixed by running Core with -reindex (or -reindex-chainstate if only chainstate is corrupted).

But, what actually fixed it is by renaming the chainstate folder which is somehow restricted by a certain Microsoft product, then --reindex after.
The log and the errors in the second reply are the ones he got after using --reindex without renaming it first.

[NotATether]

Yeah, as the diagnostic says, these kind of issues can almost always be fixed by running Core with -reindex (or -reindex-chainstate if only chainstate is corrupted).

But, what actually fixed it is by renaming the chainstate folder which is somehow restricted by a certain Microsoft product, then --reindex after.
The log and the errors in the second reply are the ones he got after using --reindex without renaming it first.

Why rename it? Old, corrupted chainstate folders still use a few GB.

Wouldn't it be better to delete the folder entirely?

[ranochigo]

Why rename it? Old, corrupted chainstate folders still use a few GB.

Wouldn't it be better to delete the folder entirely?

Of course, though I'm aware that chainstate would be rebuild regardless, I wanted to eliminate the possibility of the existence of the folder being an issue. Hence, the advice to rename instead of deleting it. In this case it is, so the chainstate can be deleted now.

[nc50lc]

-snip-

Why rename it? Old, corrupted chainstate folders still use a few GB.

Wouldn't it be better to delete the folder entirely?

That besides the point.
Of course OP can do that to get rid of the restricted files but it's what previously suggested and followed by the OP.

But the point is, this particular issue can't be solved by --reindex/--reindex-chainstate alone as it somehow can't wipe the chainstate directory by itself.

[calkob]

-snip-

Why rename it? Old, corrupted chainstate folders still use a few GB.

Wouldn't it be better to delete the folder entirely?

That besides the point.
Of course OP can do that to get rid of the restricted files but it's what previously suggested and followed by the OP.

But the point is, this particular issue can't be solved by --reindex/--reindex-chainstate alone as it somehow can't wipe the chainstate directory by itself.

This is correct, I renamed the old, locked "chainstate" folder to "chain" then ran bitcoind -reindex.  Bitcoin core created a new chainstate folder,  until that point, --reindex/--reindex-chainstate wouldnt work.