I’m on Start09 0.3.5.x and I’ve been trying to sideload Knots 29.3.1 from this release,
in place of my current Knots 29.3.0 installation. StartOS shows that I need to update from 29.3.0 to 29.3.1. Neither pressing the Update button nor doing the sideloading is working. I’ve downloaded the bitcoind.s9pk file more than once and verified the SHA256 checksum. File seems to be fine, but Start OS is erroring out with the message:
Bitcoin Knots - Install Failed
Install of bitcoind@29.3.1 Failed: Filesystem I/O Error: error reading a body from connection: end of file before message length reached
Any thoughts on why this is happening and/or what I can do at this point to get updated to StartOS 0.4.0? Apparently I can’t update the OS until my Services are updated completely and for now I’ve still got an update notification that I can’t get rid of.
When I run the sideloading of the s9pk file it starts fine, but also errors out around the 40% mark of the progress bar shown below:
29.3.0, is the latest version of Bitcoin Knots available in the registry for 0.3.5.1. Please restart your server. Start all your services, and make sure nothing got broken during your efforts here. Then follow the instructions carefully to upgrade to 0.4.0.
I restarted my server yesterday before posting and had done exactly what you suggested. My 5 services are all running. Knots shows version 29.3.0 but I still have an Update Notice as shown below as a Bitcoin Core update. It still prompts to update my Knots installation to a newer version. Is it safe to update to StartOS 0.4.0 with this update notification still active?
Yes, you’re good to proceed. You’re not actually behind — 29.3.0 is the latest Knots in the official 0.3.5.1 registry, and the guide only requires Bitcoin to be on the latest minor of your major version, so you already meet the requirement.
The notice sticks around because Knots and Core share the same bitcoind package ID, so a bitcoind update shows with the “Bitcoin Core” label.
The failed sideload (“end of file before message length reached”, stall at 40%) was just the transfer cutting off partway — not a bad file. Your checksum was fine. You don’t need 29.3.1, so I wouldn’t keep retrying.
So go ahead and follow the 0.4.0 guide. Just don’t skip the backup: stop all services and take a full 0.3.5.1 backup before flashing (it’s only a rollback net — 0.3.5.1 backups can’t restore onto 0.4.0).
