Old Dell laptop. 1TB internal SATA drive.
Full BTC node was working…
Added other services.
Got to be too much.
Won’t even boot past this screen now.
Now what?
If you have a recent backup you might try a reflash and then recover from existing backup and just install Bitcoin and not all the services
https://docs.start9.com/0.3.5.x/misc-guides/attach-drive#attach-drive
No backup. Had just gotten it working from scratch and didn’t imagine that the services would fill it up so much more.
Can’t I just delete something?
I’ll assume you didn’t get through much of the setup either since you’re just getting starting and were testing… so you don’t have SSH access either?
With SSH access you can SSH in and uninstall services via the command line or delete files. Without SSH access, your best bet is to start over.
There’s a reason we don’t sell 1TB servers in 2025.
I had a full node downloaded and blazing along.
But had to shut it off once I learned about the huge bandwidth and total data capacity that it requires each month, that my internet DSL plan doesn’t accommodate for, (especially after downloading the full node in the first place.)
REFERENCE = Monthly Bandwidth?
Near the end of last month, I had enough data remaining to fire it up again and at least have the node update. It got stuck at about 85% I think it was. Services wouldn’t update. I couldn’t figure out why. Shut it down at the last day of my DSL cycle.
Started it back up a day or two again (for this month), and now it won’t even boot past the screen I’m showing here.
So, I hope that explains where I’m at with this device.
In regards to your proposed “SSH” concept: I don’t know how to do that. Is that type of troubleshooting/recovery/deleting procedure in the DIY documentation?
thx
OK, so you can’t boot the OS fully because it goes to diagnostic mode. But in the background core parts of the OS are running. From your client device(s), instead of using the browser to access an interface that isn’t there, you’d connect to the server via command line and type the commands I’d give you to delete some services or data to at least get the device to be able to turn on.
Setting up SSH however is only something you can do before your server stops working properly, and is one of the later steps in the user manual…
https://docs.start9.com/0.3.5.x/user-manual/ssh
If you haven’t done that then solutions are limited. Reinstalling the OS and restoring from backups is one. Starting over is another, but that’s a bad option in your case. Maybe the best option is get a decent size drive and go through the transfer process…
Thanks for the options. I’ll maybe throw some time at them in the future… I already spent a lot of time on this for nothing, other than a bit of learning (good), and finding out what not to do every step of the way (not so good).
It would be good to have a feature built into the OS where if it gets to the point of this screen, that it would just instantly present a list of installed features and ask what the user wants to delete. No need to SSH, etc.
Better yet: not even let the drive fill completely up in the first place, but instead give warnings, and halt usage before 100%.
Meanwhile, hopefully the DIY documentation (Start9 | DIY x86) is updated to account for all these requirements (drive space for now AND future expansion of the blockchain, monthly bandwidth needs, not letting the drive fill up, need to have SSH set up ahead of time for recovery, etc) so that someone knows BEFORE they get all the way to the point I’m at, just to find out that it’s not going to work out as planned… again… again.
To our success.
Agreed on the feature request. We’re a small team with a lot of feature requests.
Yes of course programming takes time.
Updating the documentation only takes a few minutes though.
Sure, but StartOS works on small drives just fine and the minimum specs are just that – StartOS actually has nothing to do with blockchains or Bitcoin, or any future expansion. We also don’t have a warning of a need for a 4TB drive if building a huge Jellyfin media library.
But I accept your point regarding an OS feature being a good idea.