Hey y'all. Had my node running for some 19-20 months now. Following the Stadicus guide. on a raspberry pi 3. Bitcoin v0.19.0.1
the other day I just checked up on it and noticed it was in a failed state and didn't have the HDD mounted. The log seems to indicate it just stopped, the last entry is
2020-08-21T17:35:41Z socket recv error Connection reset by peer (104) I did the troubleshooting guide (no stranger to this) figuring there had been a power outage possibly. I ran fsck and it took a LONG while to find and clean up a lot of errors. The drive works fine, i can connect to it via my pc (using linux file systems paragon) transfer files.. etc. I ran fsck another time or two to be sure and no errors found. It's got 57% free space.
I got the raspberry pi to mount the HDD again, started up bitcoind and it started to sync slowly. I'd check with getblockchain info and figured it would take around 60+ hours to finish and left it overnight.
Today I come back to find it was no longer syncing. Now no matter what I do, starting bitcoind manually, or having it automatically boot getblockchain info gives me an error
error: Could not connect to the server 127.0.0.1:8332 Make sure the bitcoind server is running and that you are connecting to the correct RPC port. So bitcoind seems to shutdown instantly after starting it. AND checking the log, the last message from the 21st (above) is all that's there, no new information in the log.
I tried to re-install bitcoin v0.19.0.1 and got a suspect. When extracting the package into the tmp folder, it fails due to out of space errors. So this possibly means something is going on with the SD card? or something filled it up? Not sure what to check, or how really.
curiously the startup script for the raspibolt displays this for the SSD. Not sure how to interpret that. 36M free?
SSD 36M (240%) here i'm stuck, what can I try next? I believe I have backups of the important information. I'd like to avoid a total reformatting if at all possible.
No comments:
Post a Comment