New Install Stuck at 77.41% Error Timed out retrying soon

DIY Community Support
41

Well I might be getting to the end of this server’s ability. Please take a look at recent log entries. Is there anything you can suggest?

Error updating blockchain info: error: timeout on transient error: Could not connect to the server 127.0.0.1:8332 (error code 0 - “timeout reached”)
2025-07-28T19:01:19-04:00
2025-07-28T19:01:19-04:00 Make sure the bitcoind server is running and that you are connecting to the correct RPC port.
2025-07-28T19:01:19-04:00 Use “bitcoin-cli -help” for more info.
2025-07-28T19:01:19-04:00
2025-07-28T19:09:25-04:00 2025-07-28T23:09:25Z UpdateTip: new best=000000000000000000003f299c620732440333a28f6dcaca5d17ce35303383fc height=882842 version=0x2001e000 log2_work=95.432711 tx=1152572990 date=‘2025-02-08T07:40:23Z’ progress=0.920830 cache=493.2MiB(3587617txo)
2025-07-28T19:24:38-04:00 Error updating blockchain info: error: timeout on transient error: Could not connect to the server 127.0.0.1:8332 (error code 0 - “timeout reached”)
2025-07-28T19:24:38-04:00
2025-07-28T19:24:38-04:00 Make sure the bitcoind server is running and that you are connecting to the correct RPC port.
2025-07-28T19:24:38-04:00 Use “bitcoin-cli -help” for more info.
2025-07-28T19:24:38-04:00
2025-07-28T19:28:05-04:00 2025-07-28T23:28:05Z UpdateTip: new best=000000000000000000004112df970ef89dec60c2f0229512189889c4a8c5bd01 height=882843 version=0x2000a000 log2_work=95.432723 tx=1152574604 date=‘2025-02-08T07:47:39Z’ progress=0.920827 cache=494.0MiB(3595630txo)
2025-07-28T19:39:38-04:00 Error updating network info: error: timeout on transient error: Could not connect to the server 127.0.0.1:8332 (error code 0 - “timeout reached”)
2025-07-28T19:39:39-04:00
2025-07-28T19:39:39-04:00 Make sure the bitcoind server is running and that you are connecting to the correct RPC port.
2025-07-28T19:39:39-04:00 Use “bitcoin-cli -help” for more info.
2025-07-28T19:39:39-04:00
2025-07-28T19:48:48-04:00 2025-07-28T23:48:48Z UpdateTip: new best=00000000000000000000a8fddbaf4070c24ba7398794fa22aebb2b3bbeffdf09 height=882844 version=0x24f3c000 log2_work=95.432736 tx=1152575619 date=‘2025-02-08T07:53:27Z’ progress=0.920823 cache=495.2MiB(3606376txo)
2025-07-28T19:54:44-04:00 Error updating blockchain info: error: timeout on transient error: Could not connect to the server 127.0.0.1:8332 (error code 0 - “timeout reached”)
2025-07-28T19:54:44-04:00
2025-07-28T19:54:44-04:00 Make sure the bitcoind server is running and that you are connecting to the correct RPC port.
2025-07-28T19:54:44-04:00 Use “bitcoin-cli -help” for more info.
2025-07-28T19:54:44-04:00
2025-07-28T20:08:06-04:00 2025-07-29T00:08:06Z UpdateTip: new best=00000000000000000001780be2391b3d5573f4a061a6722d2721038dcbf7ce86 height=882845 version=0x23564000 log2_work=95.432748 tx=1152575867 date=‘2025-02-08T07:54:55Z’ progress=0.920817 cache=496.8MiB(3620653txo)
2025-07-28T20:09:44-04:00 Error updating network info: error: timeout on transient error: Could not connect to the server 127.0.0.1:8332 (error code 0 - “timeout reached”)
2025-07-28T20:10:18-04:00
2025-07-28T20:10:18-04:00 Make sure the bitcoind server is running and that you are connecting to the correct RPC port.
2025-07-28T20:10:18-04:00 Use “bitcoin-cli -help” for more info.
2025-07-28T20:10:18-04:00
2025-07-28T20:14:55-04:00 2025-07-29T00:14:55Z Unable to open file /root/.bitcoin/blocks/rev04764.dat
2025-07-28T20:14:55-04:00 2025-07-29T00:14:55Z [error] UndoWriteToDisk: OpenUndoFile failed
2025-07-28T20:14:55-04:00 2025-07-29T00:14:55Z [error] A fatal internal error occurred, see debug.log for details: Failed to write undo data.
2025-07-28T20:14:55-04:00 Error: A fatal internal error occurred, see debug.log for details: Failed to write undo data.
2025-07-28T20:14:55-04:00 2025-07-29T00:14:55Z [error] ConnectTip: ConnectBlock 00000000000000000001bf4a73c26426a78c9e546fd816ea778914eb816726df failed, Failed to write undo data.
2025-07-28T20:14:55-04:00 2025-07-29T00:14:55Z [error] ProcessNewBlock: ActivateBestChain failed (Failed to write undo data.)
2025-07-28T20:14:56-04:00 2025-07-29T00:14:56Z tor: Thread interrupt
2025-07-28T20:14:56-04:00 2025-07-29T00:14:56Z Shutdown: In progress…
2025-07-28T20:14:56-04:00 2025-07-29T00:14:56Z addcon thread exit
2025-07-28T20:14:56-04:00 2025-07-29T00:14:56Z torcontrol thread exit
2025-07-28T20:14:56-04:00 2025-07-29T00:14:56Z opencon thread exit
2025-07-28T20:14:56-04:00 2025-07-29T00:14:56Z net thread exit
2025-07-28T20:14:56-04:00 2025-07-29T00:14:56Z msghand thread exit
2025-07-28T20:14:56-04:00 2025-07-29T00:14:56Z
2025-07-28T20:14:56-04:00
2025-07-28T20:14:56-04:00 ************************
2025-07-28T20:14:56-04:00 EXCEPTION: NSt10filesystem7__cxx1116filesystem_errorE
2025-07-28T20:14:56-04:00 filesystem error: cannot remove: Read-only file system [/root/.bitcoin/peers.91e6]
2025-07-28T20:14:56-04:00 bitcoin in scheduler
2025-07-28T20:14:56-04:00
2025-07-28T20:14:56-04:00
2025-07-28T20:14:56-04:00
2025-07-28T20:14:56-04:00 ************************
2025-07-28T20:14:56-04:00 EXCEPTION: NSt10filesystem7__cxx1116filesystem_errorE
2025-07-28T20:14:56-04:00 filesystem error: cannot remove: Read-only file system [/root/.bitcoin/peers.91e6]
2025-07-28T20:14:56-04:00 bitcoin in scheduler
2025-07-28T20:14:56-04:00
2025-07-28T20:14:57-04:00 Error updating network info: error: timeout on transient error: Could not connect to the server 127.0.0.1:8332
2025-07-28T20:14:57-04:00
2025-07-28T20:14:57-04:00 Make sure the bitcoind server is running and that you are connecting to the correct RPC port.
2025-07-28T20:14:57-04:00 Use “bitcoin-cli -help” for more info.
2025-07-28T20:14:57-04:00
2025-07-28T20:14:57-04:00 ERROR IN SIDECAR: Read-only file system (os error 30)
2025-07-28T20:14:57-04:00 terminate called after throwing an instance of ‘std::filesystem::__cxx11::filesystem_error’
2025-07-28T20:14:57-04:00 terminate called after throwing an instance of ‘std::filesystem::__cxx11::filesystem_error’
2025-07-28T20:14:57-04:00 what(): filesystem error: cannot remove: Read-only file system [/root/.bitcoin/peers.91e6]
2025-07-28T20:14:57-04:00 what(): filesystem error: cannot remove: Read-only file system [/root/.bitcoin/peers.c660]
2025-07-28T20:14:57-04:00 PROCESS TERMINATED BY SIGABRT

There is also an error opening database on the status screen under RPC and Synced.

Well it seems to be getting worse. I tried to restart. And it never restarted. Its stuck in status unknown state and a yellow connecting bar at the bottom, from the Start OS screen. I think I probably need to power off the server. But I am not sure if I need to shut down any processes first? Is there anyone out there that can please help me with this next phase? This seems to be getting worse and worse. And maybe I just wasted more money on a memory stick? I really don’t know.

42

Ah, man, that’s bad luck. “filesystem error: Read-only file system & ERROR IN SIDECAR: Read-only file system (os error 30)” indicates that your data volume was remounted read‑only. This happens either after disk errors are encountered or when running out of space. Since your SSD is 2TB, space is probably not the problem. Do you know what brand/model of SSD you are using? Hopefully you haven’t fallen victim to one of those SSD scams (although in my experience, those usually fail between 32GB - 128GB, not closer to 800GB which you are probably around about).

The Latitude 7050 is a laptop, right? (I couldn’t find that exact model, but I assume it is one of the 7000 series laptops?) If it isn’t a laptop (or if the screen is broken), you might try hooking up a monitor. In either case, see what error is being reported during startup on the device itself (rather than connecting from another computer on the network). Most likely there is a disk error, but let’s see what it says.

43

Its an Optiplex 7050 micro PC. But i guess it has laptop components in it. I will try to hook up a monitor and keyboard to it. What do you mean by an SSD Scam? The disk seemed to be working correctly before? I will check on the SSD also. Thanks for your help. I am pulling my hair out with this.

44

There are scams (typically from China) where the sellers reprogram the controller to make a disk report that it has more space than it really does, allowing them to mark up the price (usually at a competitive value compared to other drives with the actual reported capacity). These are devious, because you will not notice the problem until you try to use more space than the disk actually has. Like I said, though, these are almost always 32GB, 64GB, or 128GB in size. Since you are definitely beyond that, I doubt that is the issue here. Just throwing it out there as something we should keep in mind as a possibility while troubleshooting.

45

Gotcha. I think its a working SSD. Its a brand I never heard of Patriot. Well some positive news. Plugged in the monitor and keyboard and nothing. The only thing I could do was a hard power down on it. Hoping that it would power back up. While it was down. I went inside the case to verify the memory and the SSD. Memory is a Kingston 8G memory stick. And there is room for one more. I have ordered the second one. The SSD is a Patriot P210 2TB. 2.5 SSD 6GB/s SATA III. Model P210S2TB25.

Then I powered it up. Monitor and KB worked. And quite a few errors flew by. But it booted automatically into Start OS. Asked me for my password. And then logged in. I was able to see the Start OS console on the external monitor, and from my computer. And then eventually it started Syncing. Picking up at 91.91%. So it appears to be working.

What do you think? Let it run as long as it will go?

46

Yes, I’d let it run and see if the problem comes back. If you go to System > Monitor > Disk what does it show for Percentage Used? (just to rule out the disk filling up with runaway logs or something)

47

It looks pretty good actually. CPU shows 12.9%. Memory used 12.7%. Disk used 40.4%. And it does appear to recognize a Disk capacity of 2TB. And it also shows 818.98 GB disk used so far. So I think we are back on the horse. Hope it keeps crawling along.

48

I see a lot of reviews on that particular SSD model about it failing fairly quickly and slowing down after prolonged use. There are also a lot of good reviews, though, so take that with a grain of salt (a lot of it just comes down to luck of the draw).

Personally, I would stick with it and just get in a routine of making periodic backups once everything is up and running. If the SSD eventually does end up failing in the future, I’d recommend getting a more common name brand like Western Digital or Sandisk to replace it. They will be $20 or so more expensive than the off-brands, but the price difference is worth the better quality IMO.

49

Indeed. Lets hope it holds up. And I will do backups.

1 Like
50

Good news. I finally finished the download IBD. And my new memory order should be here any day now. I will wait until it arrives before doing Electrum Server. And setting up Sparrow wallet. Then I want to set it up to access my node remotely. And to allow my other wallets to connect to it. And finally do a backup and test all of it. Before the end of the month. Because then I will be traveling extensively. Any other things I should set up?

51

Awesome! Don’t forget to set the database cache back to 450. Now that the IBD is done, I think you’ll be fine setting up electrs, and using it however you intended. Yes, more ram will be good, but I think you’re fine with 8GB for now.

52

Gotcha. When shutting down the server. I just need to stop the BTC process, and then select shutdown from the power menu option? And nothing else correct? It appears to work. It didn’t at first. But after opening it up again and re-seating the memory really good. It booted fine and recognized everything. Thanks guys. If there are any other shutdown functions I need to do when powering down please let me know? I don’t want to mess up something.

53

You can just click shutdown. The shutdown sequence will cleanly shutdown services for you. When you turn the server on, services what were running will be started again.

54

I am both glad and sad I have found this thread because I think I have been scammed!
I have had a Raspberry Pi with an NVMe 1TB fall over during BTC Core installation showing read only filesystem errors in the Logs. I had put this down to flaky SD cards and write problems on the Raspberry Pi. However I have now built a Start9 instance on a virtual machine in Proxmox. I am getting the same filesystem error (read only) as I had using the Raspberry Pi.
Looking at the hardware on Proxmox I am guessing my NVMe SSD is a fake 1TB unit with a skinny 128GB available!

SSD
SSD2895×982 93.2 KB

I suspect this is a 128GB unit showing a 1TB filesystem that is full at only 12% of the BTC database. Note to self: Don’t buy any more asian SSD’s on the internet!!!

Does this look like the probable cause to you guys?

Thanks

Garry