Hi everyone,
I’m looking for instructions to update my original Embassy with below specs
Cortex-A72: 4 cores @ 1500.0000MHz
122.64804 Gb Disk
3919812 kB Memory
presumably to the latest OS version. I want to re-use the hardware, even if I have to swap the SD card to a bigger one. I haven’t looked at this in a long time, and I also don’t think I have any data to worry about if a fresh start is required.
Thanks
If you have no interest in the data, you might as well save yourself hours of work and just flash the microSD card.
To do that, you can follow the DIY guide here:
https://docs.start9.com/0.3.5.x/diy/diy-pi
Yeah it’s what I suspected. I saw that doc. But it’s sort of vague.
Will the new OS run on 3.7Gb RAM ?
The minimum requirements for StartOS state that with 4GB of RAM it should run, but 8 GB and above are recommended.
But make sure to keep these warnings in mind:
You will need to run everything off of a MicroSD Card (high endurance, 64GB minimum)
Ok, so I took out the sd card and flashed this image https://github.com/Start9Labs/start-os/releases/download/v0.3.5.1/startos-0.3.5.1-39de098_raspberrypi.img.gz on the card. I’m using Balena Etcher on a Debian laptop. The flashing probably worked because my OS saw two volumes, a 17GB and a 268 MB. I checked that the PI would start by connecting an HDMI to it. It ends with a start login: prompt. I don’t have the credentials to that and couldn’t find them.
Next I took it to my router and plugged the Cat5 it used to have and powered it.
I got no response from http:start.local or 192.168.0.100 which is the IP it used to grab.
Now what ?
Disconnect the monitor… you’re running a headless server OS… then proceed to a client device on your network.
Using a web browser, visit http://start.local/
Then follow the guide here:
https://docs.start9.com/0.3.5.x/user-manual/initial-setup/initial-setup-start-fresh
Assuming it’s booting, you’d have to go through these steps:
https://docs.start9.com/0.3.5.x/support/common-issues#during-initial-setup-i-am-unable-to-connect-to-start-local
But considering you just flashed this SD card, you’d also have to take into account any possibility of flashing it incorrectly in some way… from human error to fluke accidents to hardware issues (i.e. bad SD).
Ah. My router probably blocked mDNS. Accessing it through the IP worked, noting that it must be done through http and not https .
Thanks… I’m on the next step now. I expect it’ll go smoothly.
Everything went smoothly. My router supports mDNS only in the same VLAN, so it’s not recognizing start.local or classic-bite.local on the LAN from the laptop on WIFI.
But it’s good now. I was able to install modules form the marketplace.
Thanks a lot for the help.
