Author

Topic: "Error opening block database. Do you want to rebuild the block database now?" (Read 48060 times)

sr. member
Activity: 420
Merit: 250
I accidentally deleted my bitcoin and wallet years ago after freeing up space on my hard drive. I have not used this computer much since then. The 2010 MacBook Pro works fine. I thought I had backed it up when I ran parrelels with windows xp on this machine. However, I deleted parrelels and windows xp from the machine and the backup. I haven’t done anything else on this machine until I can find out if any trace still exists. Is there anyway to find out if they are on the hard drive still? Any feedback is appreciated. Thank you.

You have a (very) slim chance that your wallet is still available somewhere on the disk. First of all, stop using your computer.  The more you use your computer, the larger the possibility that your wallet is overwritten. If possible move your HD to another computer. Then install one of the existing programs for recovery of deleted files on this new computer (on his old disc, not on the moved disc with deleted wallet). There are some solutions on the market but cannot talk about them since i never used any of them. If you're lucky, your wallet might still be intact since the deletion just removes the reference to the file but not the file itself. But if even a single bit is changed on that file, you will not be able to recover it. Good luck.

you should email yourself your private keys and pass phrase.or whatever other information. even if your computer gets destroyed you can still recover your email from a different device

This is very bad advice for one simple reason - anyone who has the access to your mail also has the access to your funds. You have to backup passphrase and private keys, but mailing them is the last possible way you should do it.
member
Activity: 238
Merit: 10
you should email yourself your private keys and pass phrase.or whatever other information. even if your computer gets destroyed you can still recover your email from a different device
newbie
Activity: 2
Merit: 0
I accidentally deleted my bitcoin and wallet years ago after freeing up space on my hard drive. I have not used this computer much since then. The 2010 MacBook Pro works fine. I thought I had backed it up when I ran parrelels with windows xp on this machine. However, I deleted parrelels and windows xp from the machine and the backup. I haven’t done anything else on this machine until I can find out if any trace still exists. Is there anyway to find out if they are on the hard drive still? Any feedback is appreciated. Thank you.
hero member
Activity: 544
Merit: 507
Delete all Bitcoin related registry keys (use search within regedit.exe located at Windows directory) and afterwards run BitcoinQt wallet then adjust it to your likings via Settings menu.

Also if wallet.dat you are using was created with very old version of BitcoinQt use -upgradewallet option when starting your new wallet, just once is fine so remove option afterwards.

Im running the node with walletless >> disablewallet=1
hero member
Activity: 651
Merit: 518
Delete all Bitcoin related registry keys (use search within regedit.exe located at Windows directory) and afterwards run BitcoinQt wallet then adjust it to your likings via Settings menu.

Also if wallet.dat you are using was created with very old version of BitcoinQt use -upgradewallet option when starting your new wallet, just once is fine so remove option afterwards.
hero member
Activity: 544
Merit: 507
...

Think it is worth running?

No, seems ok.


Edit: Also perhaps a checkdsk /r is in order?

Give it a go, I assumed you already tried that.

Ok thanks, will run that tonight. So it is likely to be an HD issue I guess rather than client issue as nobody has reported it?

Could I mount (linux) a flash disk (64GB) and place datadir there?
That would be more efficient than using a regular hdd right?
hero member
Activity: 651
Merit: 518
Delete all Bitcoin related registry keys (use search within regedit.exe located at Windows directory) and afterwards run BitcoinQt wallet then adjust it to your likings via Settings menu.
sr. member
Activity: 395
Merit: 408
Bitcoin OG artworks collection
I have a similar issue today and few days ago
legendary
Activity: 2576
Merit: 2267
1RichyTrEwPYjZSeAYxeiFBNnKC9UjC5k
Reindexing was taking forever. It's now about 12 hours later and I was still only caught up to Feb.

I guess the lesson is to backup your blocks and chainstate directories (which fortunately, I did or rather had a copy for a different instance of bitcoind). That represents work which is hard and slow to recover.
legendary
Activity: 2576
Merit: 2267
1RichyTrEwPYjZSeAYxeiFBNnKC9UjC5k
Just had this happen to me. Latest version of bitcoin on Linux. Halted the bitcoind with "bitcoin-cli stop" so it should have been clean. Currently trying the reindex.


Grrr. It started downloading the blockchain all over again :/
(Edit: It wasn't downloading the blockchain, just regenerating the rev*.dat files)


If it makes any difference, the blocks and chainstate directories are symlinked from elsewhere. Is there something in that that could be causing it? I mention it because the person is having trouble with the SD card. Could we get more info on what triggers this error?

Never mind. Disk space issue...
hero member
Activity: 563
Merit: 500
This index screwed my blockchain up, closed bitcoin client with an error. I had to download the bootstrap and totally redo my blockchain.
hero member
Activity: 563
Merit: 500
Same error on 0.10.1.

-reindex at the end of the target of a shortcut of bitcoin.exe  is fixing it atm.
https://en.bitcoin.it/wiki/Running_Bitcoin#Command-line_arguments
legendary
Activity: 1358
Merit: 1001
https://gliph.me/hUF

If you worked with computers for many years, surely you have a backup.

The file you are looking for is called wallet.dat; the default location is here: https://en.bitcoin.it/wiki/Data_directory

newbie
Activity: 9
Merit: 0
Hello guys, I will try to lift this thread and tell a story about a strange behavior on my PC two days ago.
I have had bitcoin core on my PC for just a few days.
I believe it all started with with FSX Flightsimulator did not start up. I made a repair on it, and was reading tips on the net how to get it up and running again.
I was not able to solve it that night, and closed down the computer.
The next morning i connected to the net, Mozilla Firefox would not start. Or, I got the message it was already up and running, but it did not respond. Following advices on Mozillas home page
did not help, it was not to be seen in task manager, or not possible to close it anywhere. So I uninstalled it and reinstalled the program. Then it worked fine.
What I discovered at the same time, was that several icons on my desktop had disappeared.

And today when I wanted to open bitcoin-core, the icon was gone, even on the start menu. 
I had to go to the files, and start it from the exe file. When starting, I got the messages you guys had here. Made a try a couple of times, and downloaded a new one, but same result.

Looking in the file folder, I find only these files:
daemon
doc
bitcoin-qt.exe
copying.txt
readme.txt
uninstall.exe

Should it not be more files?

Now, this morning I am trembling of nervousity, have I lost my bitcoins??

The HDD is only one year old, I have 300 Gb of free space.
Yesterday I did a maintenance with AVG PC Tune up and Bitdefender. That was after the icons disappeared on the desktop.

Can also mention that AVG PC Tune up, also have a strange behavior today. It give a error message and ask if I want to send a report.
Then it crashes.

I guess it will not help to make a system recovery?

Been working with computers for many years, but this is a new experience.
If I have lost the bitcoins, as I today understand, probably is stored on the pc, I am in chock.
Tried to read through this thread, but can not keep my mind clear. Besides it seems like my problem here is of an another dimension.
I use Bitdefender total security, but still, there could be a hidden intruding from outside....


full member
Activity: 196
Merit: 100
try checkdisk on the drive

i have that problem with my USB/SD cards from time to time...

Warning: keep in mind, that it might break the whole blockchain, and might make you redownload everything!
full member
Activity: 301
Merit: 106
full member
Activity: 196
Merit: 100
Hi,

I have a similar issue, that appeared suddenly, and I am unable to fix/debug it on my own. Maybe you can help.

My environment is a Win8.1 Laptop with an SSD, and I am running Bitcoin and Litecoin QT clients.
Since space on SSD is "spare", I moved the datadirectory to a permanently inserted SDXC card (exFat) months ago.

To avoid accidental database corruption (ejecting SD-card; windows hibernation, etc), I keep a backup of the data directory, that I make ~ once a month and that I can use to start off again, if something goes wrong.


Recently both BTC and LTC QT got an update to 0.8.6/0.8.6.1 and worked like a charm, until now.

After syncing and (I think proper) shutdown, I wanted to start the software yesterday morning and it ended with the "Error opening block database. Do you want to rebuild the block database now?" error.

neither clicking ok to reindex, nor aborting gets me back at my db.

I tried several recovery (e.g. going back to my backup), they all failed.
I now focused on the litecon-qt since blockchain size and folder copying/indexing does not take days, but it seems BTC and LTC behave the same.



Even deleting the whole directory (keeping/discarding wallet.dat) before starting, results in the same error when using the datadir on the SD card (which worked fine before).



Now I went back to my main SSD and removed the "datadir" back to default, and redownloaded the blockchain.
moving it to other drives (even network mounted drives) works, but the moment I move it to the SD card, the client ends with the error message.

I have 50GB of free space on the SD card and ran disk-check tools. Also I verified that the card is working by running write/read tests. the card seems ok.

what can cause this issue?

I am posting the Litecon debug info (please bear with me), since i am running tests for filesize/copy-speed limitations witht litecoin right now, as I think it is the same error:


Code:
2013-12-20 20:06:12 Litecoin version v0.8.6.1-beta (2013-12-05 22:52:50 -1000)
2013-12-20 20:06:12 Using OpenSSL version OpenSSL 1.0.1c 10 May 2012
2013-12-20 20:06:12 Default data directory C:\Users\MyUsername\AppData\Roaming\Litecoin
2013-12-20 20:06:12 Using data directory E:\crypto-blockchain\Litecoin
2013-12-20 20:06:12 Using at most 125 connections (2048 file descriptors available)
2013-12-20 20:06:12 Using 4 threads for script verification
2013-12-20 20:06:12 init message: Verifiziere Brieftasche...
2013-12-20 20:06:13 dbenv.open LogDir=E:\crypto-blockchain\Litecoin\database ErrorFile=E:\crypto-blockchain\Litecoin\db.log
2013-12-20 20:06:13 Bound to [::]:9333
2013-12-20 20:06:13 Bound to 0.0.0.0:9333
2013-12-20 20:06:13 scrypt: using scrypt-sse2 as detected.
2013-12-20 20:06:13 init message: Lade Blockindex...
2013-12-20 20:06:13 Opening LevelDB in E:\crypto-blockchain\Litecoin\blocks\index
2013-12-20 20:06:29 init message: Lade Blockindex...
2013-12-20 20:06:29 Wiping LevelDB in E:\crypto-blockchain\Litecoin\blocks\index
2013-12-20 20:06:29 Opening LevelDB in E:\crypto-blockchain\Litecoin\blocks\index
2013-12-20 20:06:31 Shutdown : In progress...
2013-12-20 20:06:31 StopNode()
2013-12-20 20:06:31 Flushed 0 addresses to peers.dat  138ms
2013-12-20 20:06:31 Shutdown : done



Can anybody help? Any Ideas?

Why doesnt even the empty directoy work?








soy
legendary
Activity: 1428
Merit: 1013
Found a dated hidden ./.lock file in the ./.bitcoin directory.  Was getting a Corrupted Database error.  Deleted the hidden file, rebooted, restarted Bitcoin-QT, had started a reindexing and the client is building from where the reindexing had stopped.  Seems okay.
newbie
Activity: 16
Merit: 0
I'm having the same issue with v0.8.5-beta, specs at bottom of the post for reference.

This happens any time I close and then reopen Bitcoin-Qt. I was having an issue with another application last night, so I manually closed it and all other applications (including Qt) and rebooted. Sure enough, when I reopened Qt, it prompted me to re-index (which takes several overnight sessions with my processor pinned near 100%). My entire system is backed up, so this time I closed Qt and restored the .../Application Support/Bitcoin/ directory, and then re-opened Qt and received a different error that I stupidly closed because I was so pissed. Instead I RErestored back to the unindexed version that existed and just let the reindex start. Again.

Is there some issue that prevents the data directory from being restored from backup?

Code:
Model Name: MacBook Pro
Model Identifier: MacBookPro5,1
Processor Name: Intel Core 2 Duo
Processor Speed: 2.53 GHz
Number of Processors: 1
Total Number of Cores: 2
L2 Cache: 6 MB
Memory: 8 GB
Bus Speed: 1.07 GHz
Boot ROM Version: MBP51.007E.B06
SMC Version (system): 1.33f8

Code:
  Capacity: 480.1 GB (480,103,981,056 bytes)
  Model: OCZ-AGILITY3                           
  Revision: 2.220000
  Serial Number: OCZ-#######
  Native Command Queuing: Yes
  Queue Depth: 32
  Removable Media: No
  Detachable Drive: No
  BSD Name: disk0
  Medium Type: Solid State
  TRIM Support: No
  Partition Map Type: GPT (GUID Partition Table)
  S.M.A.R.T. status: Verified
  Volumes:
disk0s1:
  Capacity: 209.7 MB (209,715,200 bytes)
  BSD Name: disk0s1
  Content: EFI
Macintosh HD:
  Capacity: 479.24 GB (479,243,194,368 bytes)
  Available: 11.49 GB (11,487,240,192 bytes)
  Writable: Yes
  File System: Journaled HFS+
  BSD Name: disk0s2
  Mount Point: /
  Content: Apple_HFS
  Volume UUID: ###########
Recovery HD:
  Capacity: 650 MB (650,002,432 bytes)
  BSD Name: disk0s3
  Content: Apple_Boot
  Volume UUID: ############
sr. member
Activity: 408
Merit: 261
This happened to me today (again). Latest OSX, bitcoin-qt 0.8.5. FileVault 2 enabled, but it doesn't sound like that matters.

Any update/progress?


You can follow along here:

https://github.com/bitcoin/bitcoin/issues/2770

It's being worked on, but hasn't been completely squashed yet.

this problem has gotten so bad with OSX that i've gone back to the Windows version.

I suggest running Mac client v0.7.2 (with the May 15 workaround) if you want to maintain a flawless OSX experience until things are sorted out.
newbie
Activity: 10
Merit: 0
This happened to me today (again). Latest OSX, bitcoin-qt 0.8.5. FileVault 2 enabled, but it doesn't sound like that matters.

Any update/progress?
legendary
Activity: 1764
Merit: 1002
this problem has gotten so bad with OSX that i've gone back to the Windows version.
hero member
Activity: 715
Merit: 500
I have just encountered this error since I downloaded Bitcoin-Qt version 0.8.5 for OSX running on Mountain Lion, having replaced version 0.8.4 which I downloaded just a few days ago, and am seeing this when I attempt to run it: "Error opening block database. Do you want to rebuild the block database now?". I did not see this error when I ran 0.8.4.

Should I click "Ok" and allow the rebuild of the block database to proceed? Or would it be wise to stick to 0.8.4 for the time being?

Same problem here.
hero member
Activity: 798
Merit: 1000
Account was hacked and now reclaimed.
I bit the bullet and decided to delete all the files and re-download the blockchain. Replaced wallet.dat with a backup and I'm good to go on 0.8.5.

But now I'm reluctant to shut down Bitcoin-Qt in case I encounter the error again. Huh

so you dont know for sure if it worked. only one way to find out.

mine just finished re indexing. im looking for a new wallet if anyone has any recommendations. i would consider a cloud wallet or whatever they are called.
 
legendary
Activity: 1025
Merit: 1000
I bit the bullet and decided to delete all the files and re-download the blockchain. Replaced wallet.dat with a backup and I'm good to go on 0.8.5.

But now I'm reluctant to shut down Bitcoin-Qt in case I encounter the error again. Huh
newbie
Activity: 39
Merit: 0
Not just MAC, it's happening on Linux also.

I am now on my 3rd reindex, and to make matters worse, have forgotten some of my wallet encryption passphrase. But that is a different post.

What is giving me cause for concern now is the fact there is a post on here which says 0.8.5 solves the problem, but now I am seeing
users of 0.8.5 with the same problem.

WTF is going on?
hero member
Activity: 798
Merit: 1000
Account was hacked and now reclaimed.
What you're describing doesn't make sense except coincidentally. 0.8.4 and 0.8.5 are nearly identical, save for turning off the check that was getting tripped up by the negative version transactions.

I wonder— is everyone having frequent problems on OSX running filevault?

and this is a fresh install version of mac os 10.8.4 that is only 2 mo old.

I could use a osx fresh install
legendary
Activity: 1764
Merit: 1002
What you're describing doesn't make sense except coincidentally. 0.8.4 and 0.8.5 are nearly identical, save for turning off the check that was getting tripped up by the negative version transactions.

I wonder— is everyone having frequent problems on OSX running filevault?

no.  i have Filevault turned off specifically to try and avoid this problem but yet it occurred again in 0.8.5 Sad

and this is a fresh install version of mac os 10.8.4 that is only 2 mo old.
legendary
Activity: 1025
Merit: 1000
What you're describing doesn't make sense except coincidentally. 0.8.4 and 0.8.5 are nearly identical, save for turning off the check that was getting tripped up by the negative version transactions.

I wonder— is everyone having frequent problems on OSX running filevault?

No, not filevault. However when I first set up the client on version 0.6.3 I moved the contents of the Bitcoin directory into an encrypted disc image and hard linked the contents back into the original location. This meant that every time I needed to run Bitcoin-Qt I had to open the disc image first.

Of course now that I have encountered this error and looked into the file structure again I realise that it has changed. Doh. Oh well, this has still worked faultlessly until now.

Since posting about the error I have restored all the files to the Bitcoin directory from a backup and also restored the 0.8.4 application. I ran it with the checklevel=2 commandline option. It is now stuck at the "Verifying blocks..." stage and has been for more than 30 hours. It seems to be creating and removing files ending in .sst in the "chainstate" directory (for example 068675.sst) continuously. This seems like a very long time, and a little concerning tbh. I'm starting to wonder if it might be better to simply delete the Bitcoin directory, re-download the blockchain, then copy the wallet.dat file back when it's finished  Huh
hero member
Activity: 798
Merit: 1000
Account was hacked and now reclaimed.
osx 10.6 says im running "bitcoin version v0.8.3- beta" with this same problem..  Angry I guess I'll wait to download the blocks one last time and find a new wallet? It does not seem like much else could be done with in reason.
staff
Activity: 4284
Merit: 8808
What you're describing doesn't make sense except coincidentally. 0.8.4 and 0.8.5 are nearly identical, save for turning off the check that was getting tripped up by the negative version transactions.

I wonder— is everyone having frequent problems on OSX running filevault?
sr. member
Activity: 408
Merit: 261

I had the error with 0.8.4.  I updated to 0.8.5.  It worked.  Upon restart, same error with 0.8.5.  Also using OSX 10.8.5.



Same here.

https://github.com/bitcoin/bitcoin/issues/2770#issuecomment-24437169
newbie
Activity: 30
Merit: 0
I have just encountered this error since I downloaded Bitcoin-Qt version 0.8.5 for OSX running on Mountain Lion, having replaced version 0.8.4 which I downloaded just a few days ago, and am seeing this when I attempt to run it: "Error opening block database. Do you want to rebuild the block database now?". I did not see this error when I ran 0.8.4.

Should I click "Ok" and allow the rebuild of the block database to proceed? Or would it be wise to stick to 0.8.4 for the time being?

Same as Keewee:

I had the error with 0.8.4.  I updated to 0.8.5.  It worked.  Upon restart, same error with 0.8.5.  Also using OSX 10.8.5.

legendary
Activity: 1025
Merit: 1000
I have just encountered this error since I downloaded Bitcoin-Qt version 0.8.5 for OSX running on Mountain Lion, having replaced version 0.8.4 which I downloaded just a few days ago, and am seeing this when I attempt to run it: "Error opening block database. Do you want to rebuild the block database now?". I did not see this error when I ran 0.8.4.

Should I click "Ok" and allow the rebuild of the block database to proceed? Or would it be wise to stick to 0.8.4 for the time being?
staff
Activity: 4284
Merit: 8808
No, it was not.  This thread was created for what was genuine database corruption, though 0.8.4 fixed several causes of that on OSX.

The last couple of posts here (the September ones) are almost certainly the issue linked above, however... which is fixed via the workaround there or in 0.8.5 that just came out.
hero member
Activity: 900
Merit: 1014
advocate of a cryptographic attack on the globe
sr. member
Activity: 448
Merit: 250

I have been fighting this same issue on 2 different servers for the last 12 hours or so. Not sure if it was introduced in the update to 0.8.4.

I've run with the -reindex flag, deleted the chainstore directory and let the system rebuild it and also removed the entire home directory and let it re-sync the entire blockchain. Every single time, it works fine until the process is restarted, and then it complains about a corrupted database:

Code:
2013-09-09 13:56:14 Bitcoin version v0.8.4.0-g839c7d1-beta ()
2013-09-09 13:56:14 Using OpenSSL version OpenSSL 1.0.1 14 Mar 2012
2013-09-09 13:56:14 Default data directory /var/lib/bitcoin/.bitcoin
2013-09-09 13:56:14 Using data directory /var/lib/bitcoin/.bitcoin
2013-09-09 13:56:14 Using at most 125 connections (1024 file descriptors available)
2013-09-09 13:56:14 Using 4 threads for script verification
2013-09-09 13:56:14 init message: Verifying wallet...
2013-09-09 13:56:14 dbenv.open LogDir=/var/lib/bitcoin/.bitcoin/database ErrorFile=/var/lib/bitcoin/.bitcoin/db.log
2013-09-09 13:56:14 Bound to [::]:8333
2013-09-09 13:56:14 Bound to 0.0.0.0:8333
2013-09-09 13:56:14 init message: Loading block index...
2013-09-09 13:56:14 Opening LevelDB in /var/lib/bitcoin/.bitcoin/blocks/index
2013-09-09 13:56:14 Opened LevelDB successfully
2013-09-09 13:56:14 Opening LevelDB in /var/lib/bitcoin/.bitcoin/chainstate
2013-09-09 13:56:14 Opened LevelDB successfully
2013-09-09 13:56:17 LoadBlockIndexDB(): last block file = 80
2013-09-09 13:56:17 LoadBlockIndexDB(): last block file info: CBlockFileInfo(blocks=200, size=24210772, heights=256747...256945, time=2013-09-08...2013-09-09)
2013-09-09 13:56:17 LoadBlockIndexDB(): transaction index enabled
2013-09-09 13:56:17 LoadBlockIndexDB(): hashBestChain=0000000000000021bc464889a73c170549c2b4fc877a1de31f3e11ef8f94a13c  height=256945 date=2013-09-09 13:55:20
2013-09-09 13:56:17 init message: Verifying blocks...
2013-09-09 13:56:17 Verifying last 288 blocks at level 3
2013-09-09 13:56:20 ERROR: DisconnectBlock() : added transaction mismatch? database corrupted
2013-09-09 13:56:22 ERROR: VerifyDB() : *** coin database inconsistencies found (last 128 blocks, 16270 good transactions before that)

2013-09-09 13:56:22 : Corrupted block database detected.
Do you want to rebuild the block database now?
2013-09-09 13:56:22 Flush(false)
2013-09-09 13:56:22 DBFlush(false) ended               1ms
2013-09-09 13:56:22 StopNode()
2013-09-09 13:56:22 Flushed 0 addresses to peers.dat  4ms
2013-09-09 13:56:22 Committing 32881 changed transactions to coin database...
2013-09-09 13:56:22 Flush(true)
2013-09-09 13:56:22 DBFlush(true) ended               1ms
2013-09-09 13:56:26
hero member
Activity: 725
Merit: 503
Ok, this is ridiculous!

1) Can't stop bitcoind with ./bitcoind stop; it replies "error: bla bla bla" (can't remember)..
2) Shuts down via jsonrpc and bitcoind process just sits there with 0% cpu though port is closed
3) Kills -9 process then this thread!?

So WTF now, delete database? I don't wan't to redownload whole blockchain after each "failed" restart of bitcoind?!?

Why is bitcoind asking a question you can't reply to?

EDIT: Currently reindexing, it's connectable, we'll see how that goes... funny thing bitcoind reports negative balance while indexing...
hero member
Activity: 798
Merit: 1000
Account was hacked and now reclaimed.
You don't need to run Bitcoin-Qt. You can use Electrum or Multibit.

could i have my BTC transfer without finishing my blockchain in QT? I have a coin that was sent to me i have not received yet. could using Multibit or electrum intercept it? or should i wait?

also what one would people recommend? Electrum or Multibit?
member
Activity: 98
Merit: 10
I do not sell Bitcoins. I sell SHA256(SHA256()).
You don't need to run Bitcoin-Qt. You can use Electrum or Multibit.
hero member
Activity: 798
Merit: 1000
Account was hacked and now reclaimed.
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. 
full member
Activity: 140
Merit: 100
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.
hero member
Activity: 798
Merit: 1000
Account was hacked and now reclaimed.
i got the ""Error opening block database. Do you want to rebuild the block database now?"

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?
full member
Activity: 140
Merit: 100
i got the ""Error opening block database. Do you want to rebuild the block database now?"

im running osx. should i abort or rebuild?

Try aborting then restarting your computer.
worked the last time this happened to me.
hero member
Activity: 798
Merit: 1000
Account was hacked and now reclaimed.
i got the ""Error opening block database. Do you want to rebuild the block database now?"

im running osx. should i abort or rebuild?
legendary
Activity: 1764
Merit: 1002
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.
legendary
Activity: 1764
Merit: 1002
just got back from vacation and find my server shutdown.  0.8.2

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?
sr. member
Activity: 408
Merit: 261
Ok, github account created, and my version of this issue reported:

https://github.com/bitcoin/bitcoin/issues/2770
sr. member
Activity: 351
Merit: 250
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.

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] *
and the problem was solved.
sr. member
Activity: 408
Merit: 261
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:

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.
sr. member
Activity: 408
Merit: 261
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?

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.
newbie
Activity: 47
Merit: 0
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?

No SSD on my failure.
newbie
Activity: 47
Merit: 0
I also see this on 8.2 today after a couple weeks of using an 8.2 (rc and then release) without a problem. 
sr. member
Activity: 255
Merit: 250
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..
legendary
Activity: 1795
Merit: 1208
This is not OK.
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.
legendary
Activity: 1795
Merit: 1208
This is not OK.
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.
legendary
Activity: 1795
Merit: 1208
This is not OK.
Also tried coping the entire blockchain etc from another machine with 8.1 on it... same thing.

Is levelDB libraries missing or something?
legendary
Activity: 1795
Merit: 1208
This is not OK.
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:
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
hero member
Activity: 547
Merit: 531
First bits: 12good
I have the same issue probably by bad shutdown, is there a way to fix this without redownloading the whole blockchain.

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
hero member
Activity: 900
Merit: 1014
advocate of a cryptographic attack on the globe
Happened to me today on 0.8.1 after a clean shutdown:

Quote
Error opening block database.
Do you want to rebuild the block database now?
Relevant part of debug.log:
Quote
LevelDB read failure: IO error: /home/default/.bitcoin/chainstate/031746.sst: No such file or directory

Brand new HDD here.

How about 0.8.2rc1? So far I haven't experienced the issue with it.
full member
Activity: 202
Merit: 100
Happened to me today on 0.8.1 after a clean shutdown:

Quote
Error opening block database.
Do you want to rebuild the block database now?
Relevant part of debug.log:
Quote
LevelDB read failure: IO error: /home/default/.bitcoin/chainstate/031746.sst: No such file or directory

Brand new HDD here.
hero member
Activity: 651
Merit: 501
My PGP Key: 92C7689C
AFAICT, the only thing likely to get it running again is to redownload the blockchain.  I moved .litecoin to a safe location, created a new .litecoin directory, copied over my litecoin.conf and wallet.dat, and am now letting litecoin-qt pull in the blockchain again.  It's set to only talk to the litecoind on my mining rig, so the transfer's only running across the LAN and should be done in less than a half-hour.  It's halfway done as I write this; if it ends up working properly, I'll do the same thing with bitcoin-qt.

As a bit of follow-up, this method worked.  It took a little longer to pull the Litecoin blockchain through (and it took a few hours to rebuild the Bitcoin blockchain), but it beats having to download them from outside the LAN.
legendary
Activity: 2772
Merit: 1028
Duelbits.com
hero member
Activity: 700
Merit: 500
Wow, this is really getting annoying. Had the same error again, tried rebuilding the database which made bitcoin-qt completely crash.
Downloaded new block chain and now getting "wallet.dat corrupt, salvage failed".

Any hints on what could be causing this? Bitcoin-qt is almost unusable for me, since I have to redownload the block chain every week.
Also reported this here at github.
hero member
Activity: 651
Merit: 501
My PGP Key: 92C7689C
Just opened 0.8.1 after having successfully opened it a few times and received:
"Error opening block database. Do you want to rebuild the block database now?"

I started getting this error today on a machine on which I had upgraded LibreOffice to 4.0.  litecoind and litecoin-qt were throwing database-related exceptions as well.  The LibreOffice upgrade pulled in a newer version of Boost, which meant everything else that uses Boost (including *coind and *coin-qt) needed to be rebuilt as well.  No problem, right?  Gentoo is good at this sort of thing.

It looks like there's some interaction between Boost and the database used such that the on-disk format changed in a way that *coind/*coin-qt don't like.  AFAICT, the only thing likely to get it running again is to redownload the blockchain.  I moved .litecoin to a safe location, created a new .litecoin directory, copied over my litecoin.conf and wallet.dat, and am now letting litecoin-qt pull in the blockchain again.  It's set to only talk to the litecoind on my mining rig, so the transfer's only running across the LAN and should be done in less than a half-hour.  It's halfway done as I write this; if it ends up working properly, I'll do the same thing with bitcoin-qt.
hero member
Activity: 700
Merit: 500
... and I get the same error again. I had it about 3 weeks ago, decided to re-download the whole blockchain and not get the same error again.
I don't have any idea on what could be causing this.
sr. member
Activity: 408
Merit: 261
I and others have reported similar issue on Mac:

https://github.com/bitcoin/bitcoin/issues/2435

After 5 crashes and reindexes I've downgraded to v0.7.2
hero member
Activity: 700
Merit: 500
Will this work?

Download the blockchain and then upload it to one of those download sites. It wont be totally current, but it may be faster than having to wait for the bitcoin wallet to redownload it. The uploader may even make some money off of it.

I now keep a local backup copy of the block chain, so in case of getting errors again I can copy over my backup.
hero member
Activity: 546
Merit: 500
Will this work?

Download the blockchain and then upload it to one of those download sites. It wont be totally current, but it may be faster than having to wait for the bitcoin wallet to redownload it. The uploader may even make some money off of it.
hero member
Activity: 546
Merit: 500

Oh boy, this is one those "geeky" things that the masses won't understand.  How did you implement this solution, in layman's terms?  This is happening to me as well.


The masses should learn to backup their wallet and the bitcoin folder itself. 7zip is free software (but please make a donation if you can, its good software )


http://www.7-zip.org/download.html

There may be software available to do it automatically. If not, just for the sake of bitcoin, it should be made. I dont believe in the online wallet thing.
full member
Activity: 188
Merit: 102
Same problem, immediately upon upgrading from bitcoin-0.8.0rc1-win32 to 0.8.1, on Win7-64.

Chose Cancel. The .sst file referenced did not exist, but no problem creating the .sst file with Cygwin "touch". Deleted the .sst file I had created, restarted Bitcoin-Qt, ran fine the second time, no further mention of .sst files in the debug.log. 2-month old SATA laptop drive with no problems.

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-03-20 12:52:37
Default data directory C:\Users\username\AppData\Roaming\Bitcoin
Used data directory C:\Users\username\AppData\Local\LargeDB\Bitcoin
Using 4 threads for script verification
init message: Verifying wallet integrity...
dbenv.open LogDir=C:\Users\username\AppData\Local\LargeDB\Bitcoin\database ErrorFile=C:\Users\username\AppData\Local\LargeDB\Bitcoin\db.log
Bound to [::]:8333
Bound to 0.0.0.0:8333
init message: Loading block index...
Opening LevelDB in C:\Users\username\AppData\Local\LargeDB\Bitcoin\blocks\index
Opened LevelDB successfully
Opening LevelDB in C:\Users\username\AppData\Local\LargeDB\Bitcoin\chainstate
Opened LevelDB successfully
LoadBlockIndex(): last block file = 14
LoadBlockIndex(): last block file: CBlockFileInfo(blocks=789, size=119258104, heights=225479..226267, time=2013-03-12..2013-03-17)
LoadBlockIndex(): transaction index disabled
LoadBlockIndex(): hashBestChain=00000000000002e60135b76ddd31d727f4ca44c28f142e85ff38c199b1a098e8  height=226267 date=2013-03-17 02:17:42
init message: Verifying block database integrity...
Verifying last 288 blocks at level 3
LevelDB read failure: IO error: C:\Users\username\AppData\Local\LargeDB\Bitcoin\chainstate\013292.sst: Could not create random access file.

Oh boy, this is one those "geeky" things that the masses won't understand.  How did you implement this solution, in layman's terms?  This is happening to me as well.
member
Activity: 60
Merit: 10
Numisalis - Physical Tradable Bitcoin
I have gone from scratch several times and have even grabbed the torrent of the blockchain to see if it would load more smoothly pulling transactions from the .dat file instead of downloading from peers.  I get a checksum error every single time and it is never in the same place so I know that it isn't like there is some embedded corruption.  I do appreciate that the blockchain loads significantly faster than in 0.7 days but I would prefer it loading correctly as well.
hero member
Activity: 700
Merit: 500
Just got the same error again, decided to rebuild. Bitcoin-qt crashed, I re-ran the app now get this error:
"System error: Database corrupted" and the programm crashes again.

Not sure what to do know. Should I delete everything (expect my wallet) and re-download the block chain?

It does not matter if you delete your wallet. Just save the "wallet.dat" file, because that is where your transactions are.


https://bitcointalk.org/index.php?topic=112429.0;all

Yeah thanks, I know that. My question was rather if I have to re-download the whole block chain now or if there's a way to repair it somehow.
Anyhow, this is really strange and right now weakens my trust in the official client. I really hope that the problem is on my side (SSD defect?) and not within the current client, that would be really bad.
hero member
Activity: 546
Merit: 500
Just got the same error again, decided to rebuild. Bitcoin-qt crashed, I re-ran the app now get this error:
"System error: Database corrupted" and the programm crashes again.

Not sure what to do know. Should I delete everything (expect my wallet) and re-download the block chain?

It does not matter if you delete your wallet. Just save the "wallet.dat" file, because that is where your transactions are.


https://bitcointalk.org/index.php?topic=112429.0;all
hero member
Activity: 546
Merit: 500
I will learn someday to back up the wallet. I got the same thing as you guys.... but I dont have time to do anything but redownload the blockchain again.                           
hero member
Activity: 700
Merit: 500
Just got the same error again, decided to rebuild. Bitcoin-qt crashed, I re-ran the app now get this error:
"System error: Database corrupted" and the programm crashes again.

Not sure what to do know. Should I delete everything (expect my wallet) and re-download the block chain?
hero member
Activity: 700
Merit: 500
It's been a few hours now  and I tried to open my bitcoin-qt client again. It's working now without any errors.
I'm on a brand new iMac, the blockchain is on a SSD and I just checked the disk integrity, everything is good.

So strange, I just don't know what was causing this.

Please post the issue on Github so developers can have a look at it.

https://github.com/bitcoin/bitcoin/issues/new
Will do.
legendary
Activity: 924
Merit: 1004
Firstbits: 1pirata
It's been a few hours now  and I tried to open my bitcoin-qt client again. It's working now without any errors.
I'm on a brand new iMac, the blockchain is on a SSD and I just checked the disk integrity, everything is good.

So strange, I just don't know what was causing this.

Please post the issue on Github so developers can have a look at it.

https://github.com/bitcoin/bitcoin/issues/new
hero member
Activity: 700
Merit: 500
It's been a few hours now  and I tried to open my bitcoin-qt client again. It's working now without any errors.
I'm on a brand new iMac, the blockchain is on a SSD and I just checked the disk integrity, everything is good.

So strange, I just don't know what was causing this.
hero member
Activity: 700
Merit: 500
I'm on a Mac, running bitcoin-qt v0.8.1-beta. I get the same error:
"Error opening block database. Do you want to rebuild the block database now?"

This is from my log file:

Quote
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-03-31 08:58:46
Default data directory /Users/max/Library/Application Support/Bitcoin
Used data directory /Users/max/Library/Application Support/Bitcoin
Using 8 threads for script verification
init message: Verifying wallet integrity...
dbenv.open LogDir=/Users/max/Library/Application Support/Bitcoin/database ErrorFile=/Users/max/Library/Application Support/Bitcoin/db.log
Bound to [::]:8333
Bound to 0.0.0.0:8333
init message: Loading block index...
Opening LevelDB in /Users/max/Library/Application Support/Bitcoin/blocks/index
Opened LevelDB successfully
Opening LevelDB in /Users/max/Library/Application Support/Bitcoin/chainstate
Opened LevelDB successfully
LoadBlockIndex(): last block file = 50
LoadBlockIndex(): last block file: CBlockFileInfo(blocks=699, size=126642116, heights=228135..228833, time=2013-03-26..2013-03-30)
LoadBlockIndex(): transaction index disabled
LoadBlockIndex(): hashBestChain=000000000000026e424ea170da0ba79e671e081b2c0ee5e389def9d8b4724a75  height=228833 date=2013-03-30 23:08:49
init message: Verifying block database integrity...
Verifying last 288 blocks at level 3
LevelDB read failure: Corruption: block checksum mismatch

The essential part seems to be this: "LevelDB read failure: Corruption: block checksum mismatch"

Anyone knows what's going on?
hero member
Activity: 900
Merit: 1014
advocate of a cryptographic attack on the globe
I ran a long SMART test which took 2+ hours. I says the drive is in perfect health. So no explanation really for the error as far as I can tell.

I think the issue wasn't on your part, instead with the recent Bitcoin 0.8.1 reference client. Developers have tweaked DB parameters in order to comply with older 0.7 client limitations and it seems like LevelDB started complaining. It only affects 0.8.0 to 0.8.1 upgrade. Solution is given by @inglian a few posts up.

Hope it helps.

Thanks, that makes sense! It works well now Smiley Something like this should be included in the release notes though. (Weird however because the issue didn't happen the first time I opened the client after the upgrade.)
legendary
Activity: 924
Merit: 1004
Firstbits: 1pirata
I ran a long SMART test which took 2+ hours. I says the drive is in perfect health. So no explanation really for the error as far as I can tell.

I think the issue wasn't on your part, instead with the recent Bitcoin 0.8.1 reference client. Developers have tweaked DB parameters in order to comply with older 0.7 client limitations and it seems like LevelDB started complaining. It only affects 0.8.0 to 0.8.1 upgrade. Solution is given by @inglian a few posts up.

Hope it helps.
hero member
Activity: 900
Merit: 1014
advocate of a cryptographic attack on the globe
I ran a long SMART test which took 2+ hours. I says the drive is in perfect health. So no explanation really for the error as far as I can tell.
hero member
Activity: 900
Merit: 1014
advocate of a cryptographic attack on the globe
Ran chkdsk /r overnight. It didn't detect any bad blocks, bad file records, or unindexed files. It did discover free space marked as allocated in the volume bitmap and it did clean up unused index entries/security descriptors.
newbie
Activity: 23
Merit: 0
Same problem, immediately upon upgrading from bitcoin-0.8.0rc1-win32 to 0.8.1, on Win7-64.

Chose Cancel. The .sst file referenced did not exist, but no problem creating the .sst file with Cygwin "touch". Deleted the .sst file I had created, restarted Bitcoin-Qt, ran fine the second time, no further mention of .sst files in the debug.log. 2-month old SATA laptop drive with no problems.

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-03-20 12:52:37
Default data directory C:\Users\username\AppData\Roaming\Bitcoin
Used data directory C:\Users\username\AppData\Local\LargeDB\Bitcoin
Using 4 threads for script verification
init message: Verifying wallet integrity...
dbenv.open LogDir=C:\Users\username\AppData\Local\LargeDB\Bitcoin\database ErrorFile=C:\Users\username\AppData\Local\LargeDB\Bitcoin\db.log
Bound to [::]:8333
Bound to 0.0.0.0:8333
init message: Loading block index...
Opening LevelDB in C:\Users\username\AppData\Local\LargeDB\Bitcoin\blocks\index
Opened LevelDB successfully
Opening LevelDB in C:\Users\username\AppData\Local\LargeDB\Bitcoin\chainstate
Opened LevelDB successfully
LoadBlockIndex(): last block file = 14
LoadBlockIndex(): last block file: CBlockFileInfo(blocks=789, size=119258104, heights=225479..226267, time=2013-03-12..2013-03-17)
LoadBlockIndex(): transaction index disabled
LoadBlockIndex(): hashBestChain=00000000000002e60135b76ddd31d727f4ca44c28f142e85ff38c199b1a098e8  height=226267 date=2013-03-17 02:17:42
init message: Verifying block database integrity...
Verifying last 288 blocks at level 3
LevelDB read failure: IO error: C:\Users\username\AppData\Local\LargeDB\Bitcoin\chainstate\013292.sst: Could not create random access file.
legendary
Activity: 924
Merit: 1004
Firstbits: 1pirata
...

Think it is worth running?

No, seems ok.


Edit: Also perhaps a checkdsk /r is in order?

Give it a go, I assumed you already tried that.

Ok thanks, will run that tonight. So it is likely to be an HD issue I guess rather than client issue as nobody has reported it?

Yes sir, working fine here on an SSD drive at breathtaking speeds  Smiley

hero member
Activity: 900
Merit: 1014
advocate of a cryptographic attack on the globe
...

Think it is worth running?

No, seems ok.


Edit: Also perhaps a checkdsk /r is in order?

Give it a go, I assumed you already tried that.

Ok thanks, will run that tonight. So it is likely to be an HD issue I guess rather than client issue as nobody has reported it?
legendary
Activity: 924
Merit: 1004
Firstbits: 1pirata
...

Think it is worth running?

No, seems ok.


Edit: Also perhaps a checkdsk /r is in order?

Give it a go, I assumed you already tried that.
hero member
Activity: 900
Merit: 1014
advocate of a cryptographic attack on the globe
How old is your HDD? You could be dealing with a faulty disk drive.

Code:
LevelDB read failure: IO error: C:\Users\User\AppData\Roaming\Bitcoin\chainstate\041412.sst: Could not create random access file.

It is about two years now. I can run some SMART tests.

Please do and report back.

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

I just ran a short offline which Completed without error.

None of the raw values for the monitored attributes looks odd.

I last ran the 2 hour long test 2,404 hours ago.

Think it is worth running?

Edit: Also perhaps a checkdsk /r is in order?
legendary
Activity: 924
Merit: 1004
Firstbits: 1pirata
How old is your HDD? You could be dealing with a faulty disk drive.

Code:
LevelDB read failure: IO error: C:\Users\User\AppData\Roaming\Bitcoin\chainstate\041412.sst: Could not create random access file.

It is about two years now. I can run some SMART tests.

Please do and report back.
hero member
Activity: 900
Merit: 1014
advocate of a cryptographic attack on the globe
have you tried moving the data directory to some other drive, and starting bitcoin with datadir=d:\new directory\ ?

No, I reindexed it and it is working fine now.
hero member
Activity: 900
Merit: 1014
advocate of a cryptographic attack on the globe
How old is your HDD? You could be dealing with a faulty disk drive.

Code:
LevelDB read failure: IO error: C:\Users\User\AppData\Roaming\Bitcoin\chainstate\041412.sst: Could not create random access file.

It is about two years now. I can run some SMART tests.
legendary
Activity: 924
Merit: 1004
Firstbits: 1pirata
How old is your HDD? You could be dealing with a faulty disk drive.

Code:
LevelDB read failure: IO error: C:\Users\User\AppData\Roaming\Bitcoin\chainstate\041412.sst: Could not create random access file.
legendary
Activity: 2058
Merit: 1452
have you tried moving the data directory to some other drive, and starting bitcoin with datadir=d:\new directory\ ?
hero member
Activity: 900
Merit: 1014
advocate of a cryptographic attack on the globe
LevelDB read failure: IO error: C:\Users\User\AppData\Roaming\Bitcoin\chainstate\041412.sst: Could not create random access file.

Is it possible your disk is full?

Good question but I have a few 100 gigs free.
legendary
Activity: 2506
Merit: 1010
LevelDB read failure: IO error: C:\Users\User\AppData\Roaming\Bitcoin\chainstate\041412.sst: Could not create random access file.

Is it possible your disk is full?
hero member
Activity: 900
Merit: 1014
advocate of a cryptographic attack on the globe
Just opened 0.8.1 after having successfully opened it a few times and received:
"Error opening block database. Do you want to rebuild the block database now?"

I clicked OK. Here is the debug.log. What might have happened? It shut down cleanly last time.

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-03-20 01:05:38
Default data directory C:\Users\User\AppData\Roaming\Bitcoin
Used data directory C:\Users\User\AppData\Roaming\Bitcoin
Using 4 threads for script verification
init message: Verifying wallet integrity...
dbenv.open LogDir=C:\Users\User\AppData\Roaming\Bitcoin\database ErrorFile=C:\Users\User\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\User\AppData\Roaming\Bitcoin\blocks\index
Opened LevelDB successfully
Opening LevelDB in C:\Users\User\AppData\Roaming\Bitcoin\chainstate
Opened LevelDB successfully
LoadBlockIndex(): last block file = 9
LoadBlockIndex(): last block file: CBlockFileInfo(blocks=726, size=73739518, heights=226085..226810, time=2013-03-16..2013-03-19)
LoadBlockIndex(): transaction index disabled
LoadBlockIndex(): hashBestChain=00000000000002f51920c4ef0b7f89c08df10c7c8594a750d30532bfd9a7575b  height=226810 date=2013-03-19 22:32:29
init message: Verifying block database integrity...
Verifying last 288 blocks at level 3
LevelDB read failure: IO error: C:\Users\User\AppData\Roaming\Bitcoin\chainstate\041412.sst: Could not create random access file.
init message: Loading block index...
Wiping LevelDB in C:\Users\User\AppData\Roaming\Bitcoin\blocks\index
Opening LevelDB in C:\Users\User\AppData\Roaming\Bitcoin\blocks\index
Opened LevelDB successfully
Wiping LevelDB in C:\Users\User\AppData\Roaming\Bitcoin\chainstate
Opening LevelDB in C:\Users\User\AppData\Roaming\Bitcoin\chainstate
Opened LevelDB successfully
Initializing databases...
Jump to: