Update to 12.3 prevents boot on Fujitsu Esprimo Q920 about operating-system HOT 27 OPEN

Maybe relevant - maybe not: On my Fujitsu q920 i5 I now also had the described problem and it seems to have something to do with the connected USB devices:

...

* no connected USB device: boot
  Regards

I can confirm this observation. Removing all usb devices made it boot for me. Which was very useful to revert the upgrade.

from operating-system.

@asciinaut Can you also check if you're using the latest BIOS (as it sometimes resolves some weird UEFI boot issues) and try booting a fresh 12.3 install e.g. from an USB thumb drive?

from operating-system.

@sairon booting from a fresh 12.3 USB thunb drive has the same issues on two identical esprimo.

However both have a BIOS update pending. Will update one to see if the issue persists.

from operating-system.

Sure. I downloaded the latest ubuntu version and flashed it on an usb stick with balena etcher. Put the stick into your esprimo and start it. Use F12 to open the boot menu and select the usb stick as boot device. After some time ubuntu will start.
Open the firefox browser and download the "old" GRUB files from here
Opened the terminal with a right click on the desktop and "open in terminal"
create a new folder with
sudo mkdir /mount01
Then mount the /EFI/BOOT folder to your created folder with
sudo mount /dev/sda1 /mount01
(maybe the /dev/sda1 ist different on your sytem but i think it will be the same as you also have an esprimo.)
Cooy the downloaded files with
sudo cp command
In my case it was something like
sudo cp /home/ubuntu/downloads/grub/xxx.efi /mount01
Repeat that for both files (you will not see a message that it was succesfull)

That way is also described here

Shutdown ubuntu and restart the esprimo. It will take some minutes till your ha is available again.

from operating-system.

Maybe relevant - maybe not:
On my Fujitsu q920 i5 I now also had the described problem and it seems to have something to do with the connected USB devices:

• USB keyboard: no boot
• Eaton UPS via USB: no boot
• Bluetooth USB stick: boot
• no connected USB device: boot
  Regards

from operating-system.

Having the same Grub Boot Freezing Error again with the current update...

from operating-system.

How is this still not fixed? How could 2 Updates in a row from the GUI Break the System completely in a way that it is not bootable any more in a row?! I don't get it. How could you guys break things with an Update, we tell you, and the next update breaks the exact same thing?! how?!

As far as I remember, the q920 already required some intervention during the initial installation, as the BIOS is probably a bit "special". Is this a mistake on the part of the HAOS developers? As of today and with today's knowledge, I would no longer go for the q920 and not blame the developers of HAOS.
And: if I already have a problem with a version, then I'll have a look at the release notes before the next update: "Fujitsu Esprimo Q920 fails to boot with GRUB bootloader distributed in this OS release, updating to 12.4.rc1 may cause a boot failure and manual intervention might be needed, see #3348 for details." What did you expect?

from operating-system.

How is this still not fixed? How could 2 Updates in a row from the GUI Break the System completely in a way that it is not bootable any more in a row?! I don't get it. How could you guys break things with an Update, we tell you, and the next update breaks the exact same thing?! how?!

As far as I remember, the q920 already required some intervention during the initial installation, as the BIOS is probably a bit "special". Is this a mistake on the part of the HAOS developers? As of today and with today's knowledge, I would no longer go for the q920 and not blame the developers of HAOS. And: if I already have a problem with a version, then I'll have a look at the release notes before the next update: "Fujitsu Esprimo Q920 fails to boot with GRUB bootloader distributed in this OS release, updating to 12.4.rc1 may cause a boot failure and manual intervention might be needed, see #3348 for details." What did you expect?

There where no intervention during the initial installation needed. Never. Ever.
And: What manual intervention might be needed exactly and when? With Every update from now on?! Because the manual intervention where this AFTER it broke:

Sure. I downloaded the latest ubuntu version and flashed it on an usb stick with balena etcher. Put the stick into your esprimo and start it. Use F12 to open the boot menu and select the usb stick as boot device. After some time ubuntu will start. Open the firefox browser and download the "old" GRUB files from here Opened the terminal with a right click on the desktop and "open in terminal" create a new folder with sudo mkdir /mount01 Then mount the /EFI/BOOT folder to your created folder with sudo mount /dev/sda1 /mount01 (maybe the /dev/sda1 ist different on your sytem but i think it will be the same as you also have an esprimo.) Cooy the downloaded files with sudo cp command In my case it was something like sudo cp /home/ubuntu/downloads/grub/xxx.efi /mount01 Repeat that for both files (you will not see a message that it was succesfull)

That way is also described here

Shutdown ubuntu and restart the esprimo. It will take some minutes till your ha is available again.

How is it Possible that even this is not clear by now?!

What did you expect?

i expect it not breaking when updating from GUI. How would that be?! as it were the case before for years...

Is this a mistake on the part of the HAOS developers?

yes it is. And it was with the last Update.

I hope that was clear enough now... In general you guys do great stuff, but this here is shit...

from operating-system.

Well, a lot of users of the q920 (me included) ran into trouble during installation / first boot of HAOS like describe here: #1760 (similar: https://community.simon42.com/t/haos-x86-bootet-nicht-von-fujitsu-esprimo-q920/534 and in principle the same problem I assume here: AlmaLinux/almalinux-deploy#31 )

I don't understand the details and the source of the problem but it is obvious that the BIOS of the q920 is somehow more problematic than the BIOSes of lots of other x86-64 computer models.

Yes, it would be nice to get a fix. But the q920 in my opinion is not the ideal hardware to run HAOS on it - it causes too much trouble.

And once again: If your q920 does not boot, try to pull out all USB devices. Maybe you're in luck and it boots again. Makes troubleshooting a lot easier.

from operating-system.

probably related to #3347 ?

from operating-system.

probably related to #3347 ?

Unlikely, as this is Home Assistant Yellow.

This is probably related to the GRUB revert in #3324.

What x86-64 machine are you running on?

Sometimes it boots into rescue mode automatically

What rescue mode exactly? Is ha os info working in that shell?

Probably your best way forward here is to replace the GRUB bootloader on the first partition of your boot disk (e.g. using a Ubuntu Live USB flash drive). You can find older version of the GRUB bootloader capable of booting HAOS in this comment #3305 (comment).

from operating-system.

Thank you very much for your answer.

What x86-64 machine are you running on?

Fujitsu Esprimo Q920 - Intel Core i5 4590T

What rescue mode exactly? Is ha os info working in that shell?

This does not work in the rescue shell but I can exit the rescue shell which makes the supervisor start. In that case it is HAOS 12.2 so I assume I starts from Slot B rescue. From that point on I have access to the system and can provide additional information.

➜  ~ ha os info
board: generic-x86-64
boot: B
boot_slots:
  A:
    state: inactive
    status: bad
    version: "12.3"
  B:
    state: booted
    status: good
    version: "12.2"
data_disk: MicroFrom-256GB-SATA3-SSD-07042223E0108
update_available: true
version: "12.2"
version_latest: "12.3"

Start into this rescue mode is successfull in about 1 out of 10 boot attempts. Otherwise I only see the mentioned error.

from operating-system.

Adding system information of 12.2 startet from Slot B rescue:

System Information

from operating-system.

Hm, weird, so the new GRUB is able to boot HAOS 12.2, but not 12.3? 🤔 I wonder if boot slot A (or the kernel partition thereof) is somehow corrupted. When in boot slot B, can you just try to install HAOS 12.3 again? It should try to install it to the boot slot A again:

ha os update --version 12.3

from operating-system.

➜  ~ ha os update --version 12.3
Processing... Done.

Command completed successfully.

After the reboot the problem persists.

I will transfer an image of the SSD to another identical esprimo and downgrade the production one to 12.2.

If I can reproduce the problem on the other esprimo, I will try older grub images as suggested in #3305 (comment) starting with the 32-bit EFI files and then 64-bit ones to check if this is the same behaviour.

from operating-system.

A BIOS update did not fix the problem. I'm waiting for the images to finish and then continue with the older GRUB images.

For reference the Q920 BIOS versions tested:

• R1.47.0
• R1.46.0

from operating-system.

Just wanted to report that i had exactly the same behaviour with my Q920. BIOS updates didnt work for me too. Only solution was to replace the GRUB Files via ubuntu. Unfortunately i have already replaced both an can not report if only changing one of them would help.

from operating-system.

Just wanted to report that i had exactly the same behaviour with my Q920. BIOS updates didnt work for me too. Only solution was to replace the GRUB Files via ubuntu. Unfortunately i have already replaced both an can not report if only changing one of them would help.

Can you please describe how to replace the GRUB Files via ubuntu? I have the same Problems with my Q920 since Updating to HAOS.

from operating-system.

....

Shutdown ubuntu and restart the esprimo. It will take some minutes till your ha is available again.

Thank You Very much. Got Control Back again.

from operating-system.

@agners I have tested the 12.1 grub files and can confirm that the 64-bit grub image fixed the problem. The 32-bit version have the same problem as before.

For that reason it think it is indeed related to #3305 (comment).

What irritates me, is that unlike described in the other issue, the grub loader from version 12.2 started without any problems. So it doesn't seem to be the exact same problem. @Botschafter, @kimzeuner can you confirm that the Grub from version 12.2 also booted smoothly on your Q920?

from operating-system.

Yes, i can confirm that. Im currently running 12.2 without any problems.

from operating-system.

I try it, but no works.

I don't know if I'm using the right /dev/sda...

How do I know which one is the right one?

from operating-system.

Im not an expert but as i have read in the other issue it should always be the first partition with 32M so /dev/sda1 should be the right one for you. I think in my system it looked similar to yours in the screenshot

from operating-system.

I have the same problem on a ThinkCentre m93 p, I already wrote here: #3376
If I install 12.3 and then go back to 12.2, and then install 12.3 again from HA UI, HA works. If I install then my backup and restart the ThinClient, it also works. But if I restart a second time, I cannot boot haos from slot A or B.
I also installed Proxmox 8.2 and HA as a VM, and I also could not restart proxmox twice.

Now I hope I have a solution for me, but not for haos itself: I found that proxmox can be rebooted multiple times if I use legacy bios mode. With uefi mode not. And now I also can restart Home assistant VM multiple times without problems. Will see what happens if a next os update is out and the boot slots are exchanged!

from operating-system.

I have the same problem, helped me to run in Terminal
"ha os update --version 12.1"
and
"ha core update --version 2024.6.0"

Fujitsu Esprimo Q920 works again, as before

from operating-system.

How is this still not fixed? How could 2 Updates in a row from the GUI Break the System completely in a way that it is not bootable any more in a row?! I don't get it. How could you guys break things with an Update, we tell you, and the next update breaks the exact same thing?! how?!

from operating-system.

I bought the Hardware Refurbished in 2021 from Amazon Marketplace and never had any issues or Manuel intervention needed. I never made any BIOS Updates or Settings or opend the case... I don't know what you are talking about, but i installed the HAOS on this Hardware without any issues ever and it ran for years and i did every update with Rebooting and Everything. And out of nothing the Hardware is to Blame, when Updating from GUI whcih where never a Problem?! Because an Update breaks Grub?!

What is wrong with you?!

from operating-system.