got myself a new Asus NUC with 256Gb SSD, try installing Home assistant but keeps failing with the error on screen Slot A(OK=1 Try=2)
Done this install several times on the old PC works OK.
Can install windows or linux on the machine and boot OK, But keeps failing after install Home assistant
The install goes exactly the same as on my old pc (Which I am replacing) using Ubuntu thumb drive.
I know I can use proxmox and it works but I would like not to go this route as I am not familiar or comfortable with the virtual machine system.
Why can Home assistant not boot bare metal. tried all different BIOS setting but to no avail
saw several post taking about the display driver but this is not an available option change.
Hi
sorry for my late reply. been out of contact for past few days
I tried the Suggestion of using N-2 version but on installing it will not boot as it finds no bootable device as the first partition is empty, maybe I doing it wrong but tried several times.
Also I tried several other variants with no luck all show the same error or not boot at all (as they are incorrect version for the hardware)
I dont understand why it wont boot as I tried 6 different versions of Linux and 3 different versions of windows. all load and boot correctly.
I thought HAOS was a linux variant…
How are you trying to install? Have you tried to put the drive in another Ubuntu system, use the restore method mentioned in the x86 Installation guide? Looks like the drive is not recognized by the HAOS.
I tried install directly into the SSD
I then took this out and put into the old PC and it works fine so I know the install works
I then did the opposit installing on the old PC and put the drive into the NUC and it fails
I also created a drive formatted on a working windows PC using a drive creator tool which also works on the old pc but not the NUC
I tried about every setting change of the NUC bios but no change
I am at a loss what next to try
Have you disabled the secure boot? There is similar issue that is mentioned here.
Alternatively you may install Ubuntu that is working fine as you have mentioned earlier. Try to install Docker and get the home assistant setup.
If you have sufficient memory in your NUC, you may go with Virtualization method. Virtual Box is free and can be installed on top of Ubuntu.
I can get home-adsistant working on proxmox
However I am not so familiar with proxmox or virtualization so would prefer bare metal system, I have enough skill to get basic proxmox but this is also enough skill to get myself in trouble…
But it seems this is the only way to go.
I will keep my old PC working until I find solution to this problem
I also worry I could have similar issue under proxmox,(I see several of this error on proxmox) I don’t want this coming back to bite me when I am depending on this system to run my home
There is a fix to this issue involving ASUS NUC computers. I had this issue on my ASUS NUC 14 PRO+. If you have an Asus computer and it freezes when setting up Home Assistant with an error on screen such as Slot A (OK=1 Try=1), then do the following:
Boot into BIOS (Press F2 at boot).
Go to the “Security” Section.
Click on the link within that section and look for an option “Intel VT for Directed I/O (VT-d)” option. UNCHECK “Intel VT for Directed I/O (VT-d)”!
Save your changes.
Reboot and it should now work. Home Assistant either needs to add this to their install instructions or troubleshooting notes or fix this issue. This was a pain to find the solution! Credit goes to user Riemers on GITHUB who posted the below photo of the menu screen and commented on the solution.
Hi Bob
Thank you, Thank you, Thank you, Thank you,
I thought I had tried all options in the BIOS obviously I missed that one.
Thought I was going to have to install windows on this so that I don’t have to give away.
Installed and working great, now I can start adding the extra features without worrying about lack of memory, my old pc currently using has very small old and slow hard disk. and can add the Google Coral M2 Accelerator I was gifted by a friend who bought by mistake…
I’m kinda scratching my head on how VT-d, a virtualization technique for I/O memory mapping which is not used by linux until it has been enabled in the kernel (which is not likely in HAOS), would cause this. But yeah googling around some it seems to be a problem in other non-HAOS situations as well, but no one seems to know why.
Anyway, here is the github thread mentioned above for anyone interested:
Hi
I found another issue with the NUC
Had to disable the sound card was throwing up an error and sometimes would freeze HAOS
[ 62.520073] snd_hda_intel n0000:00:1f.3 no codec found!
after disable the sound card ran for 6 hours and no problem showed again.
