Bitcoin Forum
May 10, 2024, 08:15:45 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Crashing while syncing please advise.  (Read 978 times)
unknownerrors (OP)
Newbie
*
Offline Offline

Activity: 4
Merit: 0


View Profile
October 29, 2015, 06:21:44 PM
 #1

Hello. I have for a number of days now been trying to sync Bitcoin core x64 (latest version) but continue to fail. Every time i get to 1 year and 50 some odd weeks away it crashes leaving this in the log

Code:
UpdateTip: new best=000000000000000013777bcd7eb9ae81522926ce1deff250ab023792e3aabbeb  height=310234  log2_work=79.659989  tx=42332895  date=2014-07-11 10:03:53 progress=0.314831  cache=60.9MiB(14116tx)
2015-10-29 11:25:58 LevelDB read failure: Corruption: block checksum mismatch
2015-10-29 11:25:58 Corruption: block checksum mismatch
2015-10-29 11:45:44 ping timeout: 1200.011580s
2015-10-29 11:45:44 ping timeout: 1200.022580s
2015-10-29 11:45:44 ping timeout: 1200.021580s
2015-10-29 11:45:44 ping timeout: 1200.020580s
2015-10-29 11:45:44 ping timeout: 1200.017582s
2015-10-29 11:45:44 ping timeout: 1200.016583s
2015-10-29 11:45:53 socket sending timeout: 1201s
2015-10-29 11:45:54 socket sending timeout: 1201s
2015-10-29 15:16:06 Error reading from database: Database corrupted
2015-10-29 15:16:30 GUI: "registerShutdownBlockReason: Successfully registered: Bitcoin Core didn't yet exit safely..."
2015-10-29 15:16:30

Every time i retry I start with a clean data directory and another disk drive as well (USB3, SATA HDD/SDD doesn't matter same error) the only thing i do before i start syncing is copy my backed up wallet.dat to the data directory. Is it possible that my wallet.dat file is screwed up in some way? can it be repaired?

DXdiag report can be downloaded to view system specs
http://www.mediafire.com/view/qbu53c8gqgz8a5d/DxDiag.txt

Thanks in advanced
~UE
1715372145
Hero Member
*
Offline Offline

Posts: 1715372145

View Profile Personal Message (Offline)

Ignore
1715372145
Reply with quote  #2

1715372145
Report to moderator
I HATE TABLES I HATE TABLES I HA(╯°□°)╯︵ ┻━┻ TABLES I HATE TABLES I HATE TABLES
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1715372145
Hero Member
*
Offline Offline

Posts: 1715372145

View Profile Personal Message (Offline)

Ignore
1715372145
Reply with quote  #2

1715372145
Report to moderator
1715372145
Hero Member
*
Offline Offline

Posts: 1715372145

View Profile Personal Message (Offline)

Ignore
1715372145
Reply with quote  #2

1715372145
Report to moderator
1715372145
Hero Member
*
Offline Offline

Posts: 1715372145

View Profile Personal Message (Offline)

Ignore
1715372145
Reply with quote  #2

1715372145
Report to moderator
achow101
Moderator
Legendary
*
Offline Offline

Activity: 3388
Merit: 6635


Just writing some code


View Profile WWW
October 29, 2015, 07:41:42 PM
 #2

The wallet.dat makes absolutely no difference and has no affect on the syncing or the block indexing.

The only thing I can think of right now is that maybe you have hardware problems. Are you absolutely sure that your hard drives have enough space since it always stops around the same spot?

unknownerrors (OP)
Newbie
*
Offline Offline

Activity: 4
Merit: 0


View Profile
October 29, 2015, 09:34:28 PM
 #3

space is certainly not the issue. I have roughly 20TB of storage no single drive less than 2TB, beside the SSD which is 250GB with more than 100gb free.
rosmo01
Member
**
Offline Offline

Activity: 66
Merit: 10


View Profile
November 15, 2015, 08:20:49 PM
 #4

I have the same issue, and it started now in November. Even if I restore all of Bitcoin data-tree (renamed old  to make a clean restore) to September or October 2015 (long before this corruption began), the problem is the same. I'm considering downgrading to pre 11.1.
rosmo01
Member
**
Offline Offline

Activity: 66
Merit: 10


View Profile
November 23, 2015, 11:00:32 AM
 #5

I had to give up and downgrade to 11.0. That made all the difference. Syncing completed without a hitch and client is now stable.
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!