Hi , it has bounced on me several times and it does not start, I have tried reinstalling from 0 from USB with a new image and nothing, very strange, desperate, it worked fine until the last update, I have tried installing Windows and it works correctly, I have UEFI BIOS and secure boot disabled.
when it boots from the usb the gnu brub appears
slot A ok=1 try=3
slot B ok=1 try=3
Slot A rescue shell
Slot B rescue shell
Hi,
A little later …
I have removed the disk from the PC where it does not work and I have installed it in another x64 PC and HA works, I have put it back in the HA PC and it does not work, I have tried all the possible options in the BIOS,
it is possible that the last one Is the update not compatible with my board? the board is old : gigabyte e350N Win8 It worked before, it´s all strange
I wiil keep trying a litter more
Then it would show bootlog with an error pointing to something specific. I had similar on old i5 processor. Some feature the cpu doesn’t support. Moved to other hardware because of that
There is also options to get older image for it and stay on that. But for me that’s only a temporary solution
I had the same issue with a test instance of HA in VirtualBox. The solution for me was to change System → Chipset from PIX3 to ICH9. The need for a specific chipset is not mentioned in the Hypervisor specific configuration for VirtualBox. Since this thread has no solution yet, I hope this bit of information can help.
I had the same error as above.
My problem had to do with the “Use host I/O cache” option at the SATA controller.
I enabled this in Virtualbox (7.1.4), and then the HA instance wouldn’t boot anymore.
Tried the combination of using Host I/O cache and selecting the ICH9 chipset, but that didn’t work either.
Turned off “Use host I/O cache” and switched back to PIX3. Then HA booted correctly.
I had a similar issue (freezes at Booting ‘Slot A (OK=0 TRY+0) when installing and running Home Assistant on an ASUS NUC.
The solution for ASUS Computers is to go into BIOS, go to Security Settings and UNCHECK the “Intel VT for Directed I/O (VT-d) option.” After saving the setting and rebooting Home Assistant ran successfully!
Home Assistant either needs to add this to their install instructions or troubleshooting notes or fix this issue. This was a pain! Photo and solution credit goes to Github user Riemers.