My fulcrum server crashed, database got corrupted, needs to resync from scratch 😭. The last (and first) time I did it it took almost 3 weeks on my rpi4.

Bad timing since I wanted to stack more sats and send them to Whirlpool while the latest SCODE is still active. I'm not willing to transact without my own node. Guess I will miss this one...

The lesson learned here is: fulcrum database is a little bitch with the sensitivity of a 6 year old girl. I need to back it up at least once to make sure I never need to resync from scratch.

Reply to this note

Please Login to reply.

Discussion

Maybe also run a backup node.

Where can one learn the SCODE?

Samourai's telegram or twitter

Something about being grateful to the finch

Notes like this make me so glad I'm transitioning to a more robust desktop machine with a RAID setup for my node. No more excruciating IBDs. No more corrupted SD cards. No more wonky external drives. I only need quieter fans and an UPS, and I'll have a really solid setup for the next couple years. I hope you get a node up and running soon. Maybe this is a good time for you too to ditch the rpi?

Replacing the pi has been on my wishlist for a long time...

I keep postponing it out of stubbornness.

The goddess of thermodynamics just gave you a nudge then when your system crashed. Now's the time!

I feel this. About 2 weeks in and it still wasn’t done or progressing. Thought something is hung up, and restarted the node. Long story short, took 5 total weeks.

I gave up syncing on the rpi. Connected my work PC to the rpi bitcoind gRPC, synced fulcrum in 6 hours on the work pc and moved the database to the pi. Lesson learned.

I can finally use sparrow/samourai and my mempool instance, what a relief!

nostr:nevent1qqst0pqvwhs2nfz6fsk2zy3hm9fpwa326qdpljxc4pdflpn5qquyd0qp2emhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtmwwp6kyvfkwgc8gmpcvyenj6rgvdexzurpxqen2dfe0psksum2w94rgues0ym8gvnwx4nhqertxc68vvpkdf6xwettw9jxk734wpkqygxsm6lelvfda7qlg0tud9pfhduysy4vrexj65azqtdk4tr75j6xdspsgqqqqqqsvt496z