I start to loose hope. I d like to run my own node, bought me all the things i need, installed Umbrel but always, while downloading the Blockchain umbrel crashes. I changed already all the Hardware, incl. Raspberry PI 4. I also tryed different versions of Umbrel, but never worked. Also very first i tryed Raspiblitz and also didnt worked. Until now i couldn’t manage to get the Log files, cause it always showed me errors, trying to get them by the terminal and in umbrel. Today i could manage to get them in Umbrel so i will share them. I have a third Log File, but can just add two files cause i am new (Umbrel System Log).
Hopefully you can help me. I have feelings its kind of a network problem but i am a noob in all this so would be thanksful if someone can help me.
Hi @luca1989 from your bitcoin core logs it looks like you have a corrupted peers.dat file, which is causing Bitcoin Core to be stuck in a restart loop. The fix is at the end of my post, but first here’s some details.
bitcoin_bitcoind_1 | 2024-06-17T15:17:48Z Error: Invalid or corrupt peers.dat (AutoFile::read: fread failed: iostream error). If you believe this is a bug, please report it to https://github.com/bitcoin/bitcoin/issues. As a workaround, you can move the file ("/data/.bitcoin/peers.dat") out of the way (rename, move, or delete) to have a new one created on the next start.
bitcoin_bitcoind_1 | Error: Invalid or corrupt peers.dat (AutoFile::read: fread failed: iostream error). If you believe this is a bug, please report it to https://github.com/bitcoin/bitcoin/issues. As a workaround, you can move the file ("/data/.bitcoin/peers.dat") out of the way (rename, move, or delete) to have a new one created on the next start.
bitcoin_bitcoind_1 | 2024-06-17T15:17:49Z Shutdown: In progress...
bitcoin_bitcoind_1 | 2024-06-17T15:17:49Z scheduler thread exit
bitcoin_bitcoind_1 | 2024-06-17T15:17:49Z Shutdown: done
This is actually pretty rare with Bitcoin Core nowadays because recent changes were implemented by Core to minimize the occurrence of peers.dat corruption. It sounds like you’ve had quite a hard time syncing Bitcoin across various umbrel versions and other software, so there may be some hardware component that is failing for you. You mentioned you swapped out the Raspberry Pi. Can you please let me know:
Are you using the official Raspberry Pi power supply or something else? 3rd party power supplies are a known issue and can result in fluctuating power which could result in corrupted data.
Have you tried swapping out your hard-drive and microSD card as well?
To fix the current issue you can just delete the peers.dat file and Bitcoin Core will rebuild it.
To do this can you please:
From your umbrelOS homescreen right-click on the Bitcoin Node app and select “Stop”.
From your umbrelOS homescreen go to Settings > Advanced Settings > Terminal > umbrelOS
Copy and paste this command exactly to delete the peers.dat file:
You will be prompted to type in your main password that you use to access your umbrel. The password won’t show up as you type in for security reasons. Just type it in and press Enter.
Go back to your homescreen, right-click on the Bitcoin Node app and select “Start”. Give the app a few minutes to come back online.
Thanks a lot @nmfretz for answering.
I am busy right now and will do the things you wrote in the afternoon.
Thanks a lot for your time!
To your questions;
First i didnt use the official power supply but i swiched to this one.
So yes, now i do, but same issues.
I changed the micro SD’s (Sandisk) several times. The SSD (Intenso Portabele SSD Premium 2TB) i replaced just once with a empty 750 gb ssd i had lying around. I format them always before starting to exfat, but is i figured out this is probabely not necessary cause Umbrel will format his own linux format before starting.
As i told i will try these things later. Thanks already for your help.
First i didnt use the official power supply but i swiched to this one.
So yes, now i do, but same issues.
Do you recall if your current umbrel is a fresh install using ONLY the official power supply? Or did you have this issue, then switch to the official power supply on the same umbrelOS install?
The problem is, after the Umbrel Crash, it crashes all. I can not access by the Browser anymore. Thats why its hard to get even the Log Files. I logged in in my Terminal to access Umbrel. There i can access it kind of. I copy paste this comand but it tells me it can not remove it cause it is a read-only file system.
Is it possible that is has something to do with IPv4 / IPv6?
And to your question; I bought the new raspi first. So i did use the old powersuply with the new raspy. But i dont think this is the problem. Because I also tryed today a brand new raspi 5 with official new powersupply for Raspi 5. Same Problem. Crashed after about 5-6 minutes.
I downloaded the log files every 2 minutes after downloading Bitcoin App (Actually it happens with any app. I does not have to be the Bitcoin one. I tried with others, too. Same.
The last version of the log before it crashes i share here with you (after about 5-6min. it crashes);
Thanks for the additional details and logs @luca1989, they are super helpful.
Is it possible that is has something to do with IPv4 / IPv6?
I don’t think so. Instead, the issue with Bitcoin Core having a corrupt peers.dat file, your file-system being “read only”, and the issue with your umbrel device in general are likely related to one or more of these underlying issues:
Your SSD has likely experienced filesystem corruption. And it seems quite likely that this corruption was caused by power supply issues from using a non-official power supply, but it is always possible that the SSD itself is failing for other reasons (e.g., quality of the SSD).
Your SSD is being remounted as read-only by the Raspberry Pi due to power supply issues. If you have the official power supply now though then this should no longer happen, so it seems more likely that previous power supply issues caused corruption which would explain this comment:
And to your question; I bought the new raspi first. So i did use the old powersuply with the new raspy. But i dont think this is the problem. Because I also tryed today a brand new raspi 5 with official new powersupply for Raspi 5. Same Problem. Crashed after about 5-6 minutes.
Can you please try wiping an unused SSD (e.g., your 750GB if available), shutting down your Pi, replacing the SSD with the wiped one, and starting up your Pi. Do things work or are you still getting issues?
Thanks you so much.