Why my node is running backwards – The price of a cheap SSD 🐌🏎️
I’m learning the hard way: if you cut corners while building a Bitcoin node, you better have nerves of steel. My node has been running for five days now – and earlier, something happened I didn't think was possible: The progress percentage actually dropped.
At 4:10 PM, I was at 68.62%. A few hours later, at 9:31 PM, it was suddenly down to 68.57%. My node is running in reverse!
The Problem: A race car with a wooden transmission
I bought a Raspberry Pi 5 with 8GB RAM. A real powerhouse, basically a race car. But what’s the point of having 500 HP if you have a wooden transmission that can’t put the power to the pavement?
My "wooden transmission" is the cheap external USB SSD I bought. I thought: "2 Terabytes are 2 Terabytes, the cheap one will do." I was wrong.
Why the cheap SSD fails (and runs backwards):
A Bitcoin node doesn’t just store data. It validates every single block and has to handle millions of tiny read and write operations simultaneously (Random I/O).
• Overload: Cheap SSDs can't write as fast as the Pi processes the data. Under this constant heavy load, they overheat and the internal cache fills up.
• Loss of Sync: If the SSD makes errors or responds too slowly, the software (Bitcoin Core) loses its connection to the stream.
• The Result: The node realizes the data on the disk no longer matches the blockchain. It discards the faulty blocks and rolls back a bit to try again "cleanly." That’s the moment your progress shrinks.
AI advice to all newcomers:
When buying, don’t just look at the Pi and the Terabyte count. The SSD is the heart of your node!
1. Avoid bargain-bin SSDs: Look for models with high write endurance (TBW) from reputable brands.
2. NVMe over SATA: If possible, use an NVMe adapter (HAT) for the Pi 5. It’s the high-speed highway for your data.
3. Cooling: SSDs get incredibly hot during synchronization. A heat-dissipating case is a must.
My Conclusion:
I’m going to stick it out with my "snail SSD," even if I have to watch my progress shrink right now. But if you’re starting fresh: invest the extra 20–30 € in a high-quality NVMe with a good cache. Your time is worth more than the savings!
To the pros:
Which SSD/adapter combination do you recommend for the Pi 5 to actually get the power onto the road? ⚡️
#EINUNDZWANZIGWrite #Bitcoin #Umbrel #RaspberryPi5 #Hardware #PlebLearning #BitcoinNode
EchoFrame
npub1x3…mlns0
2026-02-12 21:58:14 UTC
Author Public Key
npub1x3d7vr4gyhfy2najf5uxuk6k7n4rayfd36jaqn6apj26wn68q08slmlns0Seen on
wss://nos.lolPublished at
2026-02-12 21:58:14 UTCEvent JSON
{
"id": "c377aab2281853db6f91da30e207f8babdd339c80d5c5943d89fdbeb2444b1fc",
"pubkey": "345be60ea825d2454fb24d386e5b56f4ea3e912d8ea5d04f5d0c95a74f4703cf",
"created_at": 1770933494,
"kind": 1,
"tags": [
[
"t",
"EINUNDZWANZIGWrite"
],
[
"t",
"Bitcoin"
],
[
"t",
"Umbrel"
],
[
"t",
"RaspberryPi5"
],
[
"t",
"Hardware"
],
[
"t",
"PlebLearning"
],
[
"t",
"BitcoinNode"
]
],
"content": "Why my node is running backwards – The price of a cheap SSD 🐌🏎️\n\nI’m learning the hard way: if you cut corners while building a Bitcoin node, you better have nerves of steel. My node has been running for five days now – and earlier, something happened I didn't think was possible: The progress percentage actually dropped.\n\nAt 4:10 PM, I was at 68.62%. A few hours later, at 9:31 PM, it was suddenly down to 68.57%. My node is running in reverse!\n\nThe Problem: A race car with a wooden transmission\n\nI bought a Raspberry Pi 5 with 8GB RAM. A real powerhouse, basically a race car. But what’s the point of having 500 HP if you have a wooden transmission that can’t put the power to the pavement?\nMy \"wooden transmission\" is the cheap external USB SSD I bought. I thought: \"2 Terabytes are 2 Terabytes, the cheap one will do.\" I was wrong.\n\nWhy the cheap SSD fails (and runs backwards):\n\nA Bitcoin node doesn’t just store data. It validates every single block and has to handle millions of tiny read and write operations simultaneously (Random I/O).\n\n• Overload: Cheap SSDs can't write as fast as the Pi processes the data. Under this constant heavy load, they overheat and the internal cache fills up.\n\n• Loss of Sync: If the SSD makes errors or responds too slowly, the software (Bitcoin Core) loses its connection to the stream.\n\n• The Result: The node realizes the data on the disk no longer matches the blockchain. It discards the faulty blocks and rolls back a bit to try again \"cleanly.\" That’s the moment your progress shrinks.\n\nAI advice to all newcomers:\n\nWhen buying, don’t just look at the Pi and the Terabyte count. The SSD is the heart of your node!\n\n1. Avoid bargain-bin SSDs: Look for models with high write endurance (TBW) from reputable brands.\n\n2. NVMe over SATA: If possible, use an NVMe adapter (HAT) for the Pi 5. It’s the high-speed highway for your data.\n\n3. Cooling: SSDs get incredibly hot during synchronization. A heat-dissipating case is a must.\n\nMy Conclusion:\n\nI’m going to stick it out with my \"snail SSD,\" even if I have to watch my progress shrink right now. But if you’re starting fresh: invest the extra 20–30 € in a high-quality NVMe with a good cache. Your time is worth more than the savings!\n\nTo the pros:\n\nWhich SSD/adapter combination do you recommend for the Pi 5 to actually get the power onto the road? ⚡️\n\n#EINUNDZWANZIGWrite #Bitcoin #Umbrel #RaspberryPi5 #Hardware #PlebLearning #BitcoinNode",
"sig": "e1799987dda3fafb44632213b4b704d772343d0078a4e5225bb1b0174552742233f60b5a7c1ac5bf635773f12aed213aeb05cd8e41363d8732288ad9ff6267cf"
}