Just to get it right: Your mini-PC still doesn’t boot? Or it does boot but is not reachable through the LAN?
If the device is still not booting from the SSD:
How did you flashed the OS to the SSD, what software did you use for the procedure and which OS-image did you exactly try to flash?
It boots but it is unreachable via LAN.
I used Balena Etcher getting the OS from link reported in the official page: https://github.com/home-assistant/operating-system/releases/download/6.5/haos_generic-x86-64-6.5.img.xz
My best guess is that I’m not correctly configuring my bios but I don’t really know what else I should do.
Connect a monitor and keyboard to your Q920 and do the initial onboarding through direct connection. You should be able to configure LAN settings directly through the HA web interface.
If I connect it with a monitor I only get a black screen, same as if I connect a monitor to my Raspberry.
Small update.
It seems like if I set the bios in UEFI mode I have only IP4 and IP6 as boot options, however, the device it shows on my local network.
If I set the bios in UEFI and Legacy mode, putting the SSD as boot point, I get only a constant black screen and the device doesn’t appear anymore on my local network.
I really don’t know about how to get out to this impasse…
Unfortunately I have never worked with a Fujitsu Esprimo Q920-PC thus I don’t know about the available BIOS parameters.
As the next step to narrow down on why the Q920 is unavailable on your LAN I would set
Since you don’t plan to boot the Q920 over Ethernet it should be safe to disable all settings referring to LAN-booting from the BIOS-settings.
Let me know how it goes.
Would this mini PC be able to install windows or linux at all?
If yes. I would do that, and then use the windows/linux as the host OS of an VM setup, and then run HAOS as an VM.
I mean, you absolutely could, but you don’t have to dedicate the entire box for HAOS.
The Fujitsu box is (way) overspec’d just for HAOS.
Well unless you have other considerations.
So, after some dig I discovered that other users had my same trouble with the same device, therefore the only solution I see is to utilize a VM.
I installed Proxmox and, consequently HAOS. Now I’ve a question, If I restore a backup from my instance installed and running on my raspberry, this will create some conflicts if I run them simultaneously (Raspberry and Fujitsu)?
Did you install HA via Proxmox successfully? I cannot even do that, I get PCIe errors and cannot boot UEFI disk with HA even when it’s a Proxmox VM…
Make sure virtualization support is turned on in the BIOS of the server.
Disable Secure Boot in UEFI Bios. Usually under Device Manager.
For some reason, I needed to disable secure boot in the Proxmox BIOS when launching HA install. When on Proxmox7, I also got errors with ‘waiting until kernel time synchronized’ and ‘wait until come online’. These were likely caused by Proxmox 7 using Crono instead of timesync-d of Proxmox 6, so I needed to install 6.4 instead of 7.1, This did the job and now HA is running smoothly.
@PatBat any news about this stupid issue?
Or any other suggestion from you, guys, in order to run native HassOS on this mini-PC?
I am forced to run hassio as you, @PatBat, using Proxmox. By the way, what is your feedback about this alternative? Is it still working smoothly?
Hi, I “solved” it by returning the device, I had some issues with DuckDNS + HA on Proxmox, so I decided to quit.
For anyone reading this, same problem appears on FUJITSU ESPRIMO Q556. I cannot set the hard drive to UEFI boot mode, only network adapter appears to work in UEFI boot mode.
Hello,
I also tried to install HA OS on Fujitsu Esprimo Q920 without luck, there are some problems with UEFI at this devices: Service Facts UEFI-BIOS bug Affected and unaffected products
In order to use Q920, I found a workaround, I used an USB 3.0 adaptor for SSD/HDD 2.5. It works perfect!
After you plug the USB, you need to enter in Boot menu and select USB as first boot device.
Hey Guys, I managed to do it (Install on Esprimo Q960)
In short:
After you flashed Home Assistant with balenaEtcher (Used a Live Ubuntu for this) you need to create the EFI Boot Sector, according to the Home Assistant Documentation here: Generic x86-64 - Home Assistant
In case you want to read a more detailed instruction, feel free to check out my blog here: Home Assistant auf Intel NUC installieren (Generic x86-64) 🚀
How do you get into BIOS? - I’m also having a Q920, but when I boot I cant see how to get into BIOS and select e.g. boot device.
BTW: According to manual it’s F2, but does not work for me
I managed to get into BIOS, attached a USB keyboard and NOT the wireless that I was using. I think my refurb system had a really old BIOS, so I have send it return.
Getting into BIOS is with F2 - but don’t use a wireless keyboard
A bit off topic - can Q920 automatically boot after power loss?
Hello everyone. Im also a “happy“ Fujitsu Esprimo Q920 owner 
I managed to start the Service with the command sudo efibootmgr -c -l /EFI/BOOT/BOOTx64.EFI -L HomeAssistant . But now I have the problem of to many HAOS sectors… I dont really know if that is actually a problem. Does anybody know, if and how I could delete the no needed HAOS sectors?
Thank you very much.
Alex
P.S. Thank you for the awesome community!
