Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Error opening block database" after regular startup. Works again once after each fresh install. #9454

Closed
Compunologist opened this issue Jan 1, 2017 · 5 comments

Comments

@Compunologist
Copy link

Happy New Year everybody!

Describe the issue

I have installed Bitcoin Core (64-bit) and changed the data directory to one on my NAS. I ran Bitcoin Core and after 2 days of synchronizing the Bitcoin Core window shows "Up to date". The program exits without any problems.

After each following regular startup however Bitcoin Core (64-bit) reports "Error opening block database. Do your want to rebuild the block database now?" and I have to abort the operation.

When I install Bitcoin Core again and choose to "Run Bitcoin Core (64-bit)" everything works again, including the already synchronized blocks.

Can you reliably reproduce the issue?

If so, please list the steps to reproduce below:

  1. Start Bitcoin Core
  2. Message: "Error opening block database. Do your want to rebuild the block database now?"

error opening block database do your want to rebuild the block database now - 2017-01-01 19_33_06-bitcoin

  1. Run the Bitcoin Core installer again: "bitcoin-0.13.1-win64-setup.exe"
  2. Choose "Run Bitcoin Core (64-bit)", everything works again

2017-01-01 20_54_08-bitcoin core - wallet

What version of bitcoin-core are you using?

Bitcoin Core version v0.13.1 (64-bit)

Machine specs:

  • OS: Windows 10 Pro
  • CPU: Intel Core i7
  • RAM: 8.00 GB
  • Disk size: 256GB & 4TB
  • Disk Type (HD/SDD): SSD & HD

Any extra information that might be useful in the debugging process.

This is how the debug.log looks like when the error occurs:
Bitcoin debug_not working on regular startup.txt

This is how the debug.log looks like after a reinstall with Bitcoin Core correctly running:
Bitcoin debug_working again after fresh install.txt

@maflcko maflcko added the Windows label Jan 1, 2017
@maflcko
Copy link
Member

maflcko commented Jan 1, 2017

Relevant highlights from debug.log:

2017-01-01 18:33:00 GUI: "registerShutdownBlockReason: Successfully registered: Bitcoin Core didn't yet exit safely..."
[...]
2017-01-01 18:33:01 Opening LevelDB in \\diskstation\incoming\Bitcoin\blocks\index
2017-01-01 18:33:01 IO error: C:\Program Files\Bitcoin\\diskstation\incoming\Bitcoin\blocks\index\LOCK: Could not lock file.

@robmcl4
Copy link
Contributor

robmcl4 commented Jan 1, 2017

I suspect the problem exists in src/leveldb/util/env_win.cc in ModifyPath(), which assumes paths beginning with a backslash are relative paths.

@maflcko maflcko modified the milestone: 0.13.2 Jan 1, 2017
@unsystemizer
Copy link
Contributor

NAS? Has Bitcoin on Windows ever supported SMB? I don't think it did.
Furthermore, #3641 (comment)

@jonasschnelli
Copy link
Contributor

AFAIK LevelDB doesn't support SMB/AFP and other network based file-systems.

@jonasschnelli
Copy link
Contributor

Duplicate of #9157. Closing

@bitcoin bitcoin locked as resolved and limited conversation to collaborators Sep 8, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants