Looks like this minor version update recently dropped an hour ago from the time i’m currently writing this post, cant update to it however. Keep getting this error: Update was not successful because of Filesystem I/O Error: No current.rootfs, not safe to prune
Anybody else seeing the same thing, or just me?
This is an attempted upgrade from 0.4.0 to 0.4.0.1
me too, same error, updating from 0.4.0
Hm, well the update just dropped an hour ago, still pretty fresh so maybe its a larger bug that needs ironing out, glad to hear i’m not the only one though! Hoping more people comment if they also experience the same thing
I have another start9 server, this 2nd one seems to be downloading the update ok…,. will see what happens
UPDATE: the 2nd server updated to 0.4.0.1 just fine. Rebooted and retried update on 1st server, failed again, same error
UPDATE2:
the server that failed the upgrade shows:
/home/start9# find /media | grep rootfs
/media/startos/current/usr/lib/startos/container-runtime/rootfs.squashfs
/media/startos/current/usr/lib/x86_64-linux-gnu/lxc/rootfs
/media/startos/current/usr/lib/x86_64-linux-gnu/lxc/rootfs/README
/media/startos/root/images/2bdb06bddbca2c78.rootfs
/media/startos/images/2bdb06bddbca2c78.rootfs
the server that upgraded OK:
/home/start9# find /media | grep rootfs
/media/startos/current/usr/lib/startos/container-runtime/rootfs.squashfs
/media/startos/current/usr/lib/x86_64-linux-gnu/lxc/rootfs
/media/startos/current/usr/lib/x86_64-linux-gnu/lxc/rootfs/README
/media/startos/images/f8b6854352ef683a01e35318480dd674.rootfs
/media/startos/images/22b735cbc71a40391cd67250b7caf75e.rootfs
/media/startos/images/3ce9a51f1d5c08920e8544fe94229e64.rootfs
/media/startos/images/2bdb06bddbca2c78af15f0f7b9db02f5.rootfs
/media/startos/images/c30f0292fd5a08325be32daed1d51605.rootfs
/media/startos/config/current.rootfs
/media/startos/root/config/current.rootfs
/media/startos/root/images/f8b6854352ef683a01e35318480dd674.rootfs
/media/startos/root/images/22b735cbc71a40391cd67250b7caf75e.rootfs
/media/startos/root/images/3ce9a51f1d5c08920e8544fe94229e64.rootfs
/media/startos/root/images/2bdb06bddbca2c78af15f0f7b9db02f5.rootfs
/media/startos/root/images/c30f0292fd5a08325be32daed1d51605.rootfs
Not sure if related or relevant
Same error. Fresh update from 0.3.5-1 to 0.4.0 last night. Was getting RPC error when attempting to login to StartOS via TOR. Hoping this would fix
I also get the filesystem error - in addition my server connection keeps going up and down. Nothing physical changed, just the OS acting up now.
I have the same issue on one of my 2 DIY servers.
One took the update (Minisforum UN1265) …no problem.
The other one (Minisforum UM890) gives the same error.
The Minisforum UM890 was on StartOS 0.3.5.~1 until the rollout of StartOS 0.4.0
Then it took the “Over the Air” 0.4.0 update just fine.
The only issue was Electrs. But an update came the next day… then there was peace in the valley.
Then this morning it just did not like the 0.4.0.1 update.
My server connection has also been going down randomly as well, and I need to keep restarting it manually and reconnecting the LAN cable. I didn’t want to mention that because I thought it was just me, but that may warrant another post
Same here. Got the same message.
Hi all,
This is an issue that appears to have affected all those who originally did an OTA update from 0.3.5.1 to 0.4.0.
The solution is going to be a manual reflash of the new version. We have a guide for that here: Update to StartOS 0.4.0 - StartOS
Everyone who upgraded manually during the better part of this year since v040 was released should be unaffected. Appologies to OTA stragglers 
Please see update above.
Another Update:
Those who want to avoid using an USB thumb drive and are comfortable with SSH can instead do:
sudo ln -rsf "$(sudo ls -t1 /media/startos/images/*.rootfs | head -n1)" /media/startos/config/current.rootfs
The OTA update will then work.
Sorry for the trouble. A lot of moving pieces here.
Awesome. @StuPleb is Da Man!
The SSH worked flawlessly and then I was able to upgrade OTA with 0.4.1. I was then able to use TOR address (https address version) to login to the StartOS. This is ideal for me when away from my home.
I was not able to use the TOR address (http address) to login- it timed out. I will try again later and hunt in the logs.
Thanks for your prompt response on this. I cannot imagine the technical fun you all are having with an upgrade this extensive. Best wishes.
sudo ln -rsf “$(sudo ls -t1 /media/startos/images/*.rootfs | head -n1)” /media/startos/config/current.rootfs
Worked for me also thanks @StuPleb
Is there a step by step guide on how to do this? I currently don’t have a flash drive and firsy time seeing there is this method to update from 0.4.0 to 0.4.1. Thanks.
Can you see the my messages above?
Yes, I opened my command prompt and ssh’d into my start9 then copied your code but nothing happens.
Did you try to do the OTA update again, after you entered the command?? It’s very unlikely that when you did that, that nothing happened.
Slight misunderstanding on my part. Thought after putting in the code in ssh it was going to update on the backend. Now that I logged back to my desktop and did OTA, it worked perfect. Thank you.