|
maxmint
|
 |
April 01, 2013, 05:17:45 PM |
|
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/newWill do. |
|
|
|
|
|
|
|
|
|
|
"There should not be any signed int. If you've found a signed int
somewhere, please tell me (within the next 25 years please) and I'll
change it to unsigned int." -- Satoshi
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
|
|
maxmint
|
|
April 01, 2013, 05:19:20 PM |
|
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?
|
|
|
|
|
mobile4ever
|
 |
April 01, 2013, 05:40:16 PM |
|
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.
|
|
|
|
|
|
mobile4ever
|
 |
April 01, 2013, 07:02:55 PM |
|
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 |
|
|
|
|
|
maxmint
|
|
April 01, 2013, 08:03:39 PM |
|
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;allYeah 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. |
|
|
|
JustJake
Member
 Offline
Activity: 60
Merit: 10
Numisalis - Physical Tradable Bitcoin
|
|
April 01, 2013, 09:24:34 PM |
|
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.
|
|
|
|
|
|
redwraith
|
|
April 02, 2013, 02:15:38 PM |
|
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. 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. |
|
|
|
|
|
mobile4ever
|
|
April 02, 2013, 06:13:36 PM |
|
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.htmlThere 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. |
|
|
|
|
|
mobile4ever
|
|
April 02, 2013, 08:41:14 PM |
|
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.
|
|
|
|
|
|
maxmint
|
|
April 02, 2013, 08:59:34 PM |
|
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. |
|
|
|
|
|
|
maxmint
|
|
April 11, 2013, 11:44:20 AM |
|
... 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.
|
|
|
|
|
salfter
|
|
April 17, 2013, 02:49:10 PM |
|
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. |
|
|
|
|
maxmint
|
|
April 22, 2013, 06:17:18 AM |
|
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. |
|
|
|
seleme
Legendary
Offline
Activity: 2772
Merit: 1028
Duelbits.com
|
|
April 29, 2013, 02:28:56 AM |
|
I got it now too
|
|
|
|
|
salfter
|
|
May 03, 2013, 02:36:08 PM |
|
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. |
|
|
|
|
dansmith
|
|
May 10, 2013, 12:26:48 PM |
|
Happened to me today on 0.8.1 after a clean shutdown: Error opening block database.
Do you want to rebuild the block database now? Relevant part of debug.log: LevelDB read failure: IO error: /home/default/.bitcoin/chainstate/031746.sst: No such file or directory Brand new HDD here. |
|
|
|
|
keystroke (OP)
|
|
May 14, 2013, 05:34:54 AM |
|
Happened to me today on 0.8.1 after a clean shutdown: Error opening block database.
Do you want to rebuild the block database now? Relevant part of debug.log: 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. |
"The difference between a castle and a prison is only a question of who holds the keys."
|
|
|
|
2GOOD
|
|
May 16, 2013, 01:30:29 AM |
|
I have the same issue probably by bad shutdown, is there a way to fix this without redownloading the whole blockchain. 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 |
|
|
|
P_Shep
Legendary
Offline
Activity: 1795
Merit: 1198
This is not OK.
|
|
May 16, 2013, 04:50:04 PM |
|
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: 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
|
|
|
|
|
|
