I did sadly not create a new snapshot or downloaded the latest configuration, yet I clicked on Update in the Lobby.
I noticed that the downloads were very slow, but finally the system did get down (with it's sound).
But I did not come up again.
I attached monitor and keyboard and saw this (actual photo attached):
I tried to find something in the boot menu, but it just boots to fast for me to even read it.
Any idea what I could do now?
- From which version you start the update process ?
- Which hardware is used ?
- There is only USB keyboard and vga or hdmi connected to the device and the ethernet lan port ?
- ......
- you try single mode boot?
- power cycle with keyboard and monitor attached
- abort the boot process and escape to the boot loader prompt
- disable the loading of the microcode update
This should get you going with a search engine, possibly AI, or search function of this forum - I don't have the time to research the details of each step just right now, sorry.
HTH,
Patrick
Quote from: Patrick M. Hausen on May 03, 2026, 10:52:18 PM- power cycle with keyboard and monitor attached
- abort the boot process and escape to the boot loader prompt
- disable the loading of the microcode update
This should get you going with a search engine, possibly AI, or search function of this forum - I don't have the time to research the details of each step just right now, sorry.
HTH,
Patrick
OK, thanks already!
I managed to select another snapshot and could boot it, create a new copy from it and then retry the update - the same happened again!
So indeed, something is wrong for my PROTECTLY firewall.
I will seek out disabling the microcode update but at least am running from an older snapshot again!
Boot the older version, uninstall the os-microcode plugin, redo the update.
Quote from: Patrick M. Hausen on May 03, 2026, 11:19:00 PMBoot the older version, uninstall the os-microcode plugin, redo the update.
That did it, great many thanks!
I also compared /conf/backup from the older snapshot and the original (now bad) snapshot, and as it seems there was no new config - I did not loose any changes, luckily!