I flashed an 2.5 SSD with BalenaEtcher, installed in the NUC, and receive a “Image Authorization Fail. system can not boot to this device due to security violation.” Get the same error with the USB stick.
UPDATE: Opening the BIOS tool and selecting the SSD to boot from seems to have circumvented whatever security issue there was. Up and running.
Please help - my NUC freezes when I boot from USB and my googling has failed me.
I bought a NUC5i3RYK, installed brand new RAM and SSD (not NVMe), updated the bios, flashed hassio to a USB drive using Etcher, but the NUC freezes when I boot with the USB plugged in. I get some very brief output and then a blank screen with just an underscore at the the top and the functions legend at the bottom (press F2 for setup, etc.), except it’s frozen.
This was briefly printed before freezing:
Bootchooser: No valid targets found.
and
Nothing bootable found.
Maybe something went wrong with Etcher, even though it said success?
No wonder. You need to flash the image to the SSD directly. The easiest way is to remove the SSD from the NUC, connect it to a PC (10$USB to SATA adapter) and flash with etcher. Done.
In case you want to go the USB way, you have to flash a Linux live version to the USB drive, and from there flash the SSD. The HASSIO image is not bootable from USB
Yikes, okay. Thanks for the reply. I had thought steps 4-6 at the very top were pretty clear that I needed to flash and boot from the USB, but I guess the edit for NVMe also applies to non NVMe drives.
If I go the Linux Live route, is the end result still the same (only Hass OS installed on the SSD) or will I end up with HA running inside Linux as a container/VM? Trying to keep if relatively simple so I’d actually prefer to dedicate the NUC to HA for now.
the image downloaded from that github always says corrupt tried to install with various method etcher etc and all complain corrupt downloaded on 3 different devices HA need to sort their crap out with nucs so hard to make them work getting very fed up now.
Just wanted to give update in this thread. I got my new NUC8i5BEK with NVME running using the latest official release (4.12) and not the dev 4.5. So now it seems the official one works. My steps have been listed above but if anyone wants a fresh step-by-step that worked, then here goes:
Hope this helps someone as noob as me in regards to linux 
This looks good - will try it.
The weird thing is that originally I set my NUC up using the exact same method as at the beginning of this post, then had to re-use the NUC for another purpose before loading HA again. Unfortunately no amount of trying including using the original img file from 2 years ago would now work.
This method actually sounds promising.
In 11. you write that you wait 30 mins for download and updates. Are there any output written to the screen during the 30 mins wait?
I’m asking because my NUC stops booting (no output to screen) after a few seconds. Excatly the same problem as Blair_Pollard had in this thread.
Ya, I gotta ask the same thing…I’m doing this in a virtual machine, and on a pi.
On the VM with no addon devices, it gets to port 4, says its starting version 3.2.9, and then sits there forever.
With the pi it gets the last “usb” device (which is the built in BT I think) the it sits there and every few minutes spams IPv6 link is not ready, power save enabled.
With the pi, it might be a bad powersupply, or a bad SD card…but I have no clue what it is for the VM (I’ve also tried as a SATA, don’t really want to try as a scsii or ide unless someone says to)
Mine is on a NUC - no VM, and stops at the same place, the Bluetooth drivers. No amount of waiting will make it go any further,
OK, I figured it out…atleast for me…I had an internal DNS server that wasn’t running, the Hassio apparently doesnt lookup secondary DNSs that aren’t listed in its own files.
example:
hassio is on automatic
custom internal DNS 192.168.5.95 -> this is set on home router
standard DNS 8.8.8.8 -> this is set on cablemodem which router is plugged into
hassio will use the one set on the router but wont use the cablemodem one when the custom one fails (windows and ubuntu will both do this)
Which NUC do you have? And are you booting from a eMMC?
Edit: one more thing, I have noticed the NIC LEDs are both off. Is that the same for you?
Sorry, didn’t look. I have now successfully installed using Supervised install on Debian OS, which went without a hitch.
No worries. I found out that my problem is similar to HassOS Image not working on NUC 2TB SSD
Still no solution though.
Actually I didnt really pay that much attention. I just figured I would leave it for 20mins since the official installation instructions said so. I was out doing other things in the mean time and when I got back everythin was up and running!
I have just installed a m2 SSD in my NUC, and now it works. eMMC is apparently not supported.
So you switched from NVMe?
I tried resetting everything up and actually ended up with the same problem you guys have been reporting all along.
I tried all different things and finally I got hassio to start-up again. I really don’t know what the deal-breaker was.
Final setup:
I have no idea why or what solved it. I am just happy I got it running again…
And it just worked
- in bios disable WLAN
This is the only bit I didn’t try - and may be relevant as it was wireless / bluetooth drivers where it was stopping.
At the moment I am still with my HA on a Pi4 with SD card, but now I ordered:
- Intel NUC10i3FNK
- WD SN550 250GB M.2 PCIe NVME SSD
- 1 x HyperX Impact DDR4 HX426S15IB2/16 2666MHz CL15 SODIMM 16GB
I hope that after the NUC-image-file has been transferred to the SSD, I can easily import my backup from the Pi and that everything will work.
I have an adapter USB to M.2-NVME-PCIe (if I can only flash the SSD this way?)
Are there any pitfalls that could occur? If anyone says that there could be problems with the components, let them shout out loud now. 
Okay, here are the steps that were necessary, briefly summarized again:
Install memory in the NUC (hard disk not yet needed, but without memory the NUC did not start). HDMI cable connected to monitor and keyboard plugged in.
downloaded the current BIOS (“F7-BIOS”) and entered the BIOS-Update by pressing the F7 key during startup Select the file from USB-Stick
Set in BIOS: secure boot OFF (otherwise the NUC will not boot from the official image from the hard disk).
Under Power tap > Secondary Power Setting > After Power Fails: activate “power on” (otherwise the NUC will not restart automatically after power failure).
Disk image flashed to the M.2-SSD with Balea Etcher (under MacOS) I used a USB adapter and the Mac recognized the SSD as a drive.
Install the SSD in the NUC, removed HDMI and Keyboard, start the thing.
Home Assistant boots up, and was accessible via the browser. The brand new function (0.116) to import previously created backups directly in the setup screen did not work (“Bad Gateway 502” or so). So create a user, install Samba and copy the backup to the /backup folder of the HA installation. Then I could import it.
Everything was back again! Only the database and the logfile I deleted so that they would be recreated (there were problems with saving the log entries).