It's normal. Raspberry Pi is notoriously slow and the record for me was 5 days with a fairly fast SSD and a RPi 4, can take up to weeks depending on which RPi you have. The CPU, the RAM and USB (again depending on your Pi) are bottlenecks.
That's what I did with my subsequent synchronization after it got corrupted a few times. Either that or just copy the entire dir of a copy that you've already fully synchronized (if you have).

Probably not. The only way to check is by looking at the resource usage, htop should show you how much ram is getting utilized and the CPU as well. I've never really had a bottleneck while using Tor, or at least it isn't that obvious to me at all.


As in my own RPi got corrupted due to an unclean shutdown. It has nothing to do with me synchronizing using my computer.

Yes. I rebuilt the block data by plugging the SSD in my computer and treating it as an external storage. It would be faster to simply copy another uncorrupted block dir onto the SSD though.

I set up a RPi node with a hard disk (not SSD) and TOR, and it took about a week to do the initial block download.

I have a UPS because power outages are common where I live.

Is there any way I can verify the blocks with my GPU instead? Both RPi's and my PC's CPUs are very slow and it'll take ages to finish. At the moment it's 18.62%. Also, in Umbrel I don't have many connections with other (possibly) Tor nodes which means that I may also have a slow downloading, too. Right now, I'm connected with one Bitcoin node and it sometimes, becomes, zero.

Hmm, that means around 14% per day. So I'm in a much worse situation. I have to do something (maybe using another Bitcoin node OS?) otherwise, it may take more than two months.

Does reindexing mean re-verifying each block?

Essentially, yes... The short answer is that it starts at the beginning and verifies the block data stored on disk. If an invalid block/file is encountered, it will start syncing (downloading blocks from peers) from that point to ensure the validity of all the blocks.


I'm not sure if the .onion servers are included in peer discovery or if you have to explicitly set them. The Electrum docs regarding Tor seems to indicate that you have to either set up as connecting to 1 server (ie. .onion only) or you run the risk of actually connecting to clearnet peers for blockheader download:



However, when I look through the list of "known" servers... I so see a couple of .onion servers listed:


So, it's possible that .onion nodes are included in peer discovery.


Note: Setting Electrum to use my Umbrel node (from a remote location)... it is connecting to my .onion address, but the other connected nodes are all clearnet.

Have you tried connecting to the Pi using ssh/terminal and checking what the Bitcoin Core logs say?

If you make sure you're inhome/umbrel/umbrel and then use:
That'll show you the last 100 lines of the debug.log file and then continue to output new lines (ctrl+c to stop). That should hopefully give you some idea of what it is actually doing.


Alternatively you should be able to check the network usage of the device to see if it is actually downloading blocks.

Mine is smaller:
https://bt.irlbtc.com/view/5364113

Is that a RPi in there? I am on mobile and I can't tell if it's that or something else.
I do like Umbrel, but as I have pointed out the 'app store' thing allowing it to do much more then BTC makes me worry about the security of it.
We know what the security risks are for a lot of the crypto apps, but what if you installed Pi-Hole and someone found and exploited something with that....

-Dave

I don't use Umbrel but looking at their code^[1], the number on the dashboard shows the total connection of your node received(inbound+outbound). So you have to either check on some explorer(BTC RPC explorer) or directly SSH'ing into the server. Anyway, isn't Umbrel default network are using Tor?

You can try SSH into the server.

Use Powershell if you are on Windows or if you are running on macOS/Linux you can directly type below command on the terminal.


Then enter your password.

After you've connected to the node, then proceed to see the network info by typing this on the terminal:

And then, the output should show you how many connections you got.
e.g.