Topic: "Error opening block database. Do you want to rebuild the block database now?" - page 3. (Read 48060 times)
August 10, 2013, 08:02:00 AM
You don't need to run Bitcoin-Qt. You can use Electrum or Multibit.
August 10, 2013, 05:04:44 AM
im already re indexing i had someone send me a coin a few days ago. whats the chances it was lost?
zero, if the transaction was recorded in the blockchain.
thanks so much thats a relief... now to learn about how to downgrade and do a work around. or keep BTC on a android or something. windows/android seems to be what everyone uses when hacked.. cant win it all.
August 10, 2013, 03:51:21 AM
im already re indexing i had someone send me a coin a few days ago. whats the chances it was lost?
zero, if the transaction was recorded in the blockchain.
August 10, 2013, 12:11:11 AM
i got the ""Error opening block database. Do you want to rebuild the block database now?"
im running osx. should i abort or rebuild?
im running osx. should i abort or rebuild?
Try aborting then restarting your computer.
worked the last time this happened to me.
im already re indexing i had someone send me a coin a few days ago. whats the chances it was lost?
August 09, 2013, 11:42:22 PM
i got the ""Error opening block database. Do you want to rebuild the block database now?"
im running osx. should i abort or rebuild?
im running osx. should i abort or rebuild?
Try aborting then restarting your computer.
worked the last time this happened to me.
August 09, 2013, 09:01:08 PM
i got the ""Error opening block database. Do you want to rebuild the block database now?"
im running osx. should i abort or rebuild?
im running osx. should i abort or rebuild?
July 01, 2013, 01:04:50 AM
now i get the same "reindexing" or rebuild problem out of the blue on my Bitcoin Qt Mac version 0.8.3.
in the last post, this same error occurred in Ubuntu with Bitcoind 0.8.2.
this is really a problem that needs to be fixed.
in the last post, this same error occurred in Ubuntu with Bitcoind 0.8.2.
this is really a problem that needs to be fixed.
June 30, 2013, 08:28:35 AM
just got back from vacation and find my server shutdown. 0.8.2
upon reboot, i get this same error:
is there an easier way to rebuild db w/o deleting and redownloading?
upon reboot, i get this same error:
Code:
: Error opening block database.
Do you want to rebuild the block database now?
is there an easier way to rebuild db w/o deleting and redownloading?
June 14, 2013, 07:27:56 PM
Ok, github account created, and my version of this issue reported:
https://github.com/bitcoin/bitcoin/issues/2770
https://github.com/bitcoin/bitcoin/issues/2770
June 14, 2013, 10:39:00 AM
So 7.1, 8.0, 8.1 all don't work now after uninstalling/wiping everything.
Then I logged into the admin account and installed it... that did run!
so, back to regular account, ran it... and it worked!
Then I stopped it, re-started it, and... it does the same thing and can't initialise the database :/
Can't work out what's going on at all.
Then I logged into the admin account and installed it... that did run!
so, back to regular account, ran it... and it worked!
Then I stopped it, re-started it, and... it does the same thing and can't initialise the database :/
Can't work out what's going on at all.
I had this same problem. Then I realized when I copied the files some were as root owner. I did a
Code:
chmod -R [username] *
June 11, 2013, 05:40:25 PM
Ok, I've now had three database corruption crashes with 0.8.2 Mac client. This is the only interesting line in debug.log is:
From what I've seen on github, LevelDB corruption issues were supposed to be resolved in the 0.8.2 release and now 0.8.2 is listed with no known issues.
Can someone with a github account please submit an issue report for this?
From what I've seen, we've had no real stable Mac client release since 0.7.2 so it would be nice to get whatever bug is causing this LevelDB corruption finally squashed.
Code:
Verifying last 288 blocks at level 3
LevelDB read failure: Corruption: block checksum mismatch
From what I've seen on github, LevelDB corruption issues were supposed to be resolved in the 0.8.2 release and now 0.8.2 is listed with no known issues.
Can someone with a github account please submit an issue report for this?
From what I've seen, we've had no real stable Mac client release since 0.7.2 so it would be nice to get whatever bug is causing this LevelDB corruption finally squashed.
June 11, 2013, 01:04:20 PM
A friend of mine with a new Macbook Air SSD having the same issue about 1 out of 5 launches it says the block chain is corrupt with Bitcoin 0.8.2
Are the other people having this issue also using a SSD?
Are the other people having this issue also using a SSD?
Unfortunately, yes.
I had so many corruption problems with 0.8.1 that I decided to downgrade to 0.7.2 until the known issues were resolved.
Now that 0.8.2 is released I decided to give it a try and unfortunately it's now crashed with database corruptions twice.
0.8.2 is definitely running better than the previous 0.8 Mac releases I tried, but there are definitely still problems. I was going to wait and see a bit before I start publicly complaining, but yes, since you asked I'm having problems as well.
June 11, 2013, 12:38:40 PM
A friend of mine with a new Macbook Air SSD having the same issue about 1 out of 5 launches it says the block chain is corrupt with Bitcoin 0.8.2
Are the other people having this issue also using a SSD?
Are the other people having this issue also using a SSD?
No SSD on my failure.
June 10, 2013, 10:29:54 AM
I also see this on 8.2 today after a couple weeks of using an 8.2 (rc and then release) without a problem.
May 31, 2013, 01:05:28 AM
I got this error today after using 8.2 for about 12 hrs. Couple of clean shutdowns and launches no problem, then tonight the error popped up out of the blue. Re-downloading the block chain now..
May 17, 2013, 07:01:16 AM
So I started changing permissions of the roaming folder. change the ownership to the user account, and set full control for everyone.... same result. thing is that the file and folders were created OK anyway when deleted.
Next I change the data directory to another HDD... finally it worked.
Restarted... still working.
So for some reason it will no longer work where it's supposed to. Not too much of a loss though, means I save space on the SDD moving it to the big HDD.
Next I change the data directory to another HDD... finally it worked.
Restarted... still working.
So for some reason it will no longer work where it's supposed to. Not too much of a loss though, means I save space on the SDD moving it to the big HDD.
May 16, 2013, 03:54:40 PM
So 7.1, 8.0, 8.1 all don't work now after uninstalling/wiping everything.
Then I logged into the admin account and installed it... that did run!
so, back to regular account, ran it... and it worked!
Then I stopped it, re-started it, and... it does the same thing and can't initialise the database :/
Can't work out what's going on at all.
Then I logged into the admin account and installed it... that did run!
so, back to regular account, ran it... and it worked!
Then I stopped it, re-started it, and... it does the same thing and can't initialise the database :/
Can't work out what's going on at all.
May 16, 2013, 01:28:52 PM
Also tried coping the entire blockchain etc from another machine with 8.1 on it... same thing.
Is levelDB libraries missing or something?
Is levelDB libraries missing or something?
May 16, 2013, 11:50:04 AM
I'm getting this error too.
updating from 7.1 to 8.1.
Tried 8.2rc1... same
went back to 7.1... loads
Tried wiping bitcoin (uninstalling, deleting all directories), re installing 8.1... same.
db.log is empty.
debug.log just shows:
updating from 7.1 to 8.1.
Tried 8.2rc1... same
went back to 7.1... loads
Tried wiping bitcoin (uninstalling, deleting all directories), re installing 8.1... same.
db.log is empty.
debug.log just shows:
Code:
Bitcoin version v0.8.1-beta (2013-03-17 15:35:36 -0400)
Using OpenSSL version OpenSSL 1.0.1c 10 May 2012
Startup time: 2013-05-16 15:44:00
Default data directory C:\Users\Casa\AppData\Roaming\Bitcoin
Used data directory C:\Users\Casa\AppData\Roaming\Bitcoin
Using 4 threads for script verification
init message: Verifying wallet integrity...
dbenv.open LogDir=C:\Users\Casa\AppData\Roaming\Bitcoin\database ErrorFile=C:\Users\Casa\AppData\Roaming\Bitcoin\db.log
Bound to [::]:8333
Bound to 0.0.0.0:8333
init message: Loading block index...
Opening LevelDB in C:\Users\Casa\AppData\Roaming\Bitcoin\blocks\index
init message: Loading block index...
Wiping LevelDB in C:\Users\Casa\AppData\Roaming\Bitcoin\blocks\index
Opening LevelDB in C:\Users\Casa\AppData\Roaming\Bitcoin\blocks\index
May 15, 2013, 08:30:29 PM
I have the same issue probably by bad shutdown, is there a way to fix this without redownloading the whole blockchain.
Thank you
P.S.
===
Ubuntu 12.04 x64
bitcoind 8.0.1
Code:
init message: Verifying block database integrity...
Verifying last 288 blocks at level 3
ERROR: bool CBlock::ReadFromDisk(const CDiskBlockPos&)() : deserialize or I/O error
ERROR: VerifyDB() : *** block.ReadFromDisk failed at 236342, hash=00000000000000643e739da0ba2ee988369423f186df6e8b22cc7a1c6a$
: Corrupted block database detected.
Do you want to rebuild the block database now?
Flush(false)
DBFlush(false) ended 0ms
StopNode()
Flushed 0 addresses to peers.dat 1ms
Committing 0 changed transactions to coin database...
Flush(true)
DBFlush(true) ended 0ms
Bitcoin exited
Thank you
P.S.
===
Ubuntu 12.04 x64
bitcoind 8.0.1
Jump to: