StartOS does not boot after upgrade to 0.4.0-beta.7

StartOS Support
1

Did the upgrade from 0.3.5.1 to 0.4.0 beta 7 today, followed all instructions according to Update to StartOS 0.4.0 - StartOS (except for setting SSH key)

I saw the migrations success / complete message (matrix animation) and downloaded the “StartOS-info.html” file and pressed restart. I noticed that I could not reach the server so I connected it to a display to see where its getting stuck.

I see the StartOS boot screen and after a while its getting stuck while showing this message:

“Not activating Mandatory Access Control as /sbin/tomoyo-init does not exist”

Here is my server setup:

  • HP Elitedesk 800 G2 Mini PC
  • Core i5-6500
  • 32GB RAM
  • startos-0.4.0-beta.7-50df139_x86_64-nonfree.iso
2

Quick update..

I kept the server running overnight and this morning I tried to open the web interface and to my surprise the login screen showed up.. I saw a similar post here mentioning the same.

Will continue the rest of the steps and return with an update afterwards.

3

Yes, patience is the way to go when updating from StartOS 0351 to StartOS 040.

Depending on how much data you have, it could take many hours to finish. Just let it do it´s thing and all will be fine.

4

Agree but the instructions clearly mention patience during the migration, not patience during the first reboot after the migration.

5

Patience all the way, is never a bad philosophy of life. Letting things settle down and just flow.

6

Re: UI not loading after migration to 0.4.0 beta.7

For anyone stuck at this point — migration complete, server alive (ping works), but UI not loading after restart — the missing step was trusting the Root CA certificate.

The StartOS-info.html file downloaded during setup contains a “Download certificate” button. Download the certificate, install it to your System keychain (not Local Items), and set it to Always Trust. Once trusted, StartOS served a “Root CA Trusted — Go to Login” screen immediately.

The server was up the whole time. It was waiting for the certificate trust before serving the UI. Hope this saves someone a few hours.

2 Likes
7

This is the exact issue my HP Envy was having after the latest update to 4.0 beta 9 but I am a Linux/terminal n00b so my situation was a little different.

I will add what I did here to avoid duplicate threads, but please remove if inappropriate.

I flashed a USB with the most recent version and booted from that. When the install wizard asked if I wanted a fresh install or if I wanted to preserve data, I clicked ‘Preserve’. So far, no issues BUT:

  1. I had done a full backup just prior to this (the attempted version update)so I was feeling pretty care-free.

  2. I also just use my node for verifying my Bitcoin transactions, so this may not work with more/more complicated services installed.