Topic: Disappointingly unable to install (Read 542 times)
Sorry to see your having problems and hope they can get sorted. Also sorry for your loss in the earlier years but it's good you getting back on the old bitcoin horse!
Having just noticed that 0.8.6 has been released, I downloaded it, deleted the ~/.bitcoin directory and launched bitcoin-qt. It started allright, created all the files in ~/.bitcoin, started loading from bootstrap.dat and again I got a database is corrupted message!
So, 0.8.6 does not fix the problem either.
So, 0.8.6 does not fix the problem either.
Try post this thread to Technical Support section...
https://bitcointalk.org/index.php?board=4.0
Having just noticed that 0.8.6 has been released, I downloaded it, deleted the ~/.bitcoin directory and launched bitcoin-qt. It started allright, created all the files in ~/.bitcoin, started loading from bootstrap.dat and again I got a database is corrupted message!
So, 0.8.6 does not fix the problem either.
So, 0.8.6 does not fix the problem either.
There are no problems with memory or hard disk. All tests I ran come back negative, including a just completed test to humour you.
As for trying windows... Really!? I take that this is a joke, right?
The error is either with the data since it occurs with bootstrap.dat or with the network, at the same place, or, with the software which does not handle a specific dataset correctly. If the former, then there need be a big question mark about the trustworthiness of Bitcoin, if the latter, it depends on the nature of the error.
As for trying windows... Really!? I take that this is a joke, right?
The error is either with the data since it occurs with bootstrap.dat or with the network, at the same place, or, with the software which does not handle a specific dataset correctly. If the former, then there need be a big question mark about the trustworthiness of Bitcoin, if the latter, it depends on the nature of the error.
maybe try to use windows?
I would check HDD one more time, corruption maybe of that, maybe RAM errors too.
I would check HDD one more time, corruption maybe of that, maybe RAM errors too.
I have done this, I honestly don't know how many times, more than ten times for sure.
I have tried from zero as many times, at least!
This is the first error that I see after numerous restart following failure, in the debug log, when I run it with the checklevel set to 2, hoping to bypass the negative value.:
received block 000000000000003214522c135f00a3028cdb21fbeb3a2ef6fe17b2640aac6918
InvalidChainFound: invalid block=000000000000003214522c135f00a3028cdb21fbeb3a2ef6fe17b2640aac6918 height=252370 log2_work=71.23717 date=2013-08-15 23:59:53
InvalidChainFound: current best=0000000000000420a2051f48db53b0373207e3765599d858980e67216d6e637f height=200869 log2_work=68.772481 date=2012-09-28 05:50:47
InvalidChainFound: Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade.
ProcessBlock: ACCEPTED
And from then on it is full of errors including these types:
InvalidChainFound: invalid block=0000000000000026ccdf147a2d20ec55b266eb0f80fa19a17cd4e92605c4760b height=252878 log2_work=71.293524 date=2013-08-18 18:21:16
InvalidChainFound: current best=0000000000000420a2051f48db53b0373207e3765599d858980e67216d6e637f height=200869 log2_work=68.772481 date=2012-09-28 05:50:47
InvalidChainFound: Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade.
and more!
I have tried from zero as many times, at least!
This is the first error that I see after numerous restart following failure, in the debug log, when I run it with the checklevel set to 2, hoping to bypass the negative value.:
received block 000000000000003214522c135f00a3028cdb21fbeb3a2ef6fe17b2640aac6918
InvalidChainFound: invalid block=000000000000003214522c135f00a3028cdb21fbeb3a2ef6fe17b2640aac6918 height=252370 log2_work=71.23717 date=2013-08-15 23:59:53
InvalidChainFound: current best=0000000000000420a2051f48db53b0373207e3765599d858980e67216d6e637f height=200869 log2_work=68.772481 date=2012-09-28 05:50:47
InvalidChainFound: Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade.
ProcessBlock: ACCEPTED
And from then on it is full of errors including these types:
InvalidChainFound: invalid block=0000000000000026ccdf147a2d20ec55b266eb0f80fa19a17cd4e92605c4760b height=252878 log2_work=71.293524 date=2013-08-18 18:21:16
InvalidChainFound: current best=0000000000000420a2051f48db53b0373207e3765599d858980e67216d6e637f height=200869 log2_work=68.772481 date=2012-09-28 05:50:47
InvalidChainFound: Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade.
and more!
Try delete the blockchain, Bitcoin-qt will redownload it again after next start. Your blockchain database could be corrupted somewhere
After a few years have passed and I am over my previous losses of bitcoins due to Bitcoin software failure, I again have been trying to install Bitcoin for the last couple of days. Every time it fails with a database corruption whilst loading. This corruption happens around the loading of the 28th or 29th of September 2012. I did find some posts on the net that mentioned an issue with a negative value where there should not be around that date.
Hard information: I am running on a 16Gb machine with six cores and 700Gb free hard disk space and running under a 64 bits Debian derivative. There is nothing wrong with the disk used either. The problem occurs whether I use the bootstrap.dat file or whether I update from the net. I am running bitcoin-qt 0.8.5. I tried re downloading this as well, thinking it may have been corrupted although I did check the SHA256 sig.
Now, to me, a problem with the chain, puts everything about Bitcoin in question. There is no way I would trust any money, except play money, until an explanation of this problem is forthcoming. I would also have to advise others to treat Bitcoin with the same circumspection.
Am I wrong? If so, how is a corrupted chain not a very serious risk?
And no, I have absolutely no interest in a offside wallet. I mean that is another piece of software and entity that I need to trust. I just do not.
I am an experienced software developer and have no issue installing software; software that works that is!
I can add any information that may be useful, just ask.
Hard information: I am running on a 16Gb machine with six cores and 700Gb free hard disk space and running under a 64 bits Debian derivative. There is nothing wrong with the disk used either. The problem occurs whether I use the bootstrap.dat file or whether I update from the net. I am running bitcoin-qt 0.8.5. I tried re downloading this as well, thinking it may have been corrupted although I did check the SHA256 sig.
Now, to me, a problem with the chain, puts everything about Bitcoin in question. There is no way I would trust any money, except play money, until an explanation of this problem is forthcoming. I would also have to advise others to treat Bitcoin with the same circumspection.
Am I wrong? If so, how is a corrupted chain not a very serious risk?
And no, I have absolutely no interest in a offside wallet. I mean that is another piece of software and entity that I need to trust. I just do not.
I am an experienced software developer and have no issue installing software; software that works that is!
I can add any information that may be useful, just ask.
Jump to: