Try using hard drives or ssds if you can for the blockchain storage (an ssd has a controller that checks and automatically marks bad sectors).
i think this will be the next thing i do.
Topic: is core shutting down properly? (Read 160 times)
Try using hard drives or ssds if you can for the blockchain storage (an ssd has a controller that checks and automatically marks bad sectors).
i think this will be the next thing i do.
As bitmaxz says it is most likely a historical corruption issue corruption issue.
MicroSD cards aren't designed to handle this sort of thing. It might be a defrag issue but I'd suggest just replacing the drive unless you can scan the good and bad sectors.
Flash memory works by charging nand gates in blocks. If a nand gate is charged or discharged too much (like here) the electron ends up stuck and gives a negative result that core can't handle. I broke a micro sd card by formatting it and transferring it between machines too often.
Fcsk can be used to scan the drive and mark the damaged sectors of the drive..
Try using hard drives or ssds if you can for the blockchain storage (an ssd has a controller that checks and automatically marks bad sectors).
MicroSD cards aren't designed to handle this sort of thing. It might be a defrag issue but I'd suggest just replacing the drive unless you can scan the good and bad sectors.
Flash memory works by charging nand gates in blocks. If a nand gate is charged or discharged too much (like here) the electron ends up stuck and gives a negative result that core can't handle. I broke a micro sd card by formatting it and transferring it between machines too often.
Fcsk can be used to scan the drive and mark the damaged sectors of the drive..
Try using hard drives or ssds if you can for the blockchain storage (an ssd has a controller that checks and automatically marks bad sectors).
How long is the last session on the log?
Does the wallet load up alright? It'll stop at some point as it has to unlock the data directory and I'm not sure if this is before or after this oint but I'm guessing it's after.
Is this being stored on flash to hard drives? Flash is more likely to undergo data failures especially if it is a micro sd card.
Does the wallet load up alright? It'll stop at some point as it has to unlock the data directory and I'm not sure if this is before or after this oint but I'm guessing it's after.
Is this being stored on flash to hard drives? Flash is more likely to undergo data failures especially if it is a micro sd card.
last session was about 28 hours
i've disabled the wallet on this one. just contributing bandwidth. i have my wallet on another node i am running.
it's a 512GB micro sdcard. i've reformatted that card and reinstalled everything hoping that would solve my crashing problem, but doesn't seem like it wants to work. it's a shame because it runs flawlessly otherwise.
It seems you have a corrupted block.
Let me ask if what OS you currently using on your raspberry Pi?
-rescan should fix the issue I don't know how to perform it in debian but according to this -rescan can fix this issue.
Let me ask if what OS you currently using on your raspberry Pi?
-rescan should fix the issue I don't know how to perform it in debian but according to this -rescan can fix this issue.
How long is the last session on the log?
Does the wallet load up alright? It'll stop at some point as it has to unlock the data directory and I'm not sure if this is before or after this oint but I'm guessing it's after.
Is this being stored on flash to hard drives? Flash is more likely to undergo data failures especially if it is a micro sd card.
Does the wallet load up alright? It'll stop at some point as it has to unlock the data directory and I'm not sure if this is before or after this oint but I'm guessing it's after.
Is this being stored on flash to hard drives? Flash is more likely to undergo data failures especially if it is a micro sd card.
i've been having issues with core crashing on my raspberry pi for a while. still working through it. today it crashed and i see this error as the last entry on the debug.log
i dont see any shutdown messages or anything after this entry. does the software just bug out so much that it can't go through a proper shutdown sequence?
Code:
2019-06-07T08:40:49Z ERROR: ReadBlockFromDisk(CBlock&, CBlockIndex*): GetHash() doesn't match index for CBlockIndex(pprev=0x5a623e80, nHeight=346374, merkle=a9b8f4b722b19b3ea7dafb7a5298f7d92731311485e3311ccd92d4dc2e150930, hashBlock=00000000000000000a9c0518a2749c9b897b7cce009e2d30cc9e31507df6637b) at CDiskBlockPos(nFile=239, nPos=6068974)
i dont see any shutdown messages or anything after this entry. does the software just bug out so much that it can't go through a proper shutdown sequence?
Jump to: