Setting up Umbrel to run in an external SSD attached to an old laptop is proving to be an absolute pain in the ass. The #Bitcoin node synchronization was taking so long that I have decided to download the blockchain on another PC and then copy it to the SSD. Otherwise it'd take me a life to have the node up and running.

#noderunners #thelongwait

Reply to this note

Please Login to reply.

Discussion

Yes.. Initial sync is a pain in the back on umbrel.

It uses tor connections by default and max about 10 connections.

You can disable that bit at detriment of privacy.

Also, increasing the ram dedicated to the btc node can speed up sync (settings in the btc node app). Standard is 450mb.. I increased it to 3gb (total 8gb ram) while syncing.

I didn't know about the Tor connections, I'm guessing that's the problem. I'm now past the 75% mark on the other PC, so I might as well just let it finish.

Thanks for the tip though, I was wondering why it was so dreadfully slow.

I just went through this building my first bitcoin node on Umbrel. ended up switching from a 7200rpm spinner over to an SSD, made a world of difference! I had't thought of turning off the TOR, sounds like something I should think about. Does having TOR on make much of a difference nostr:npub1xn9fxlmwj92svvllfkpcrvugkrx2ytfp9luw0w2n7r693jckay2sahvhwl ?

If you run into trouble migrating data nostr:npub16up8472yajrceaxq72yz4an7lggw0s6esgg7rm74k8fh3khsesjs6vnevp let me know. I just did it a couple of times after doing the initial block sync, worked like a charm. they don't have docs for it on Umbrel, but it wasn't too bad if you're good on the command line.