This results from a bug in StartOS v0.3.5.1 which won’t be fixed until StartOS v0.4.0 comes out, but it is still in alpha stage, so the thing to do is flash this 035 disk repair fix iso, available here:
Then take these steps:
- flash the iso to a usb thumb drive, and boot that thumb drive in your server.
- Visit http://start.local
- select “Re-install StartOS”
- Remove USB & Reboot to the new installation.
- Visit http://start.local again and select:
- Recover > Use existing drive
At first boot, it should do the disk repair, hopefully successfully so it might take up to hours to boot. But once it does the disk should be repaired (assuming it’s not beyond repair – if you get errors, it may be).
Once it has run it’s course, your server should be available again at its regular, unique name that follows the pattern adjective-noun.local. You’ll want to reset SSH access since you’re now on a dev build which won’t be reverted to the prod track until StartOS v0.4.0. The other option is to now flash back to prod 0351 again after the disk repair function runs. Or follow these steps to continue with the diskrepair fix dev build:
- Setup SSH access
SSH in to the server, using the following:
hostname: adjective-noun.local
username: start9
password: embassy
command line example to ssh in:
ssh start9@youruniqueadjective-noun.local
On the ssh shell, perform the following commands (one by one, waiting for each one to complete before you paste the next one):
sudo /usr/lib/startos/scripts/chroot-and-upgrade
#at the resulting shell, do:
sed -i "s/^\(PasswordAuthentication yes\)/#\1/g" /etc/ssh/sshd_config
exit
The server should then reboot, and everything should be back to normal.