Hi guys,
I am following this instruction, booted my NUC using Parted Magic, but after I run:
gunzip -c /media/sdc1/hassos_intel-nuc-3.8.img.gz | dd of=/dev/sda bs=4M conv=fsync
It says:
gzip: /media/sdc1/hassos_intel-nuc-3.8.img.gz: not in gzip format
Any ideas?
Update:
Redownloaded the file again and looks better now. Previously even via gui it din’t want to open the archive, so maybe it was corrupted or not fully downloaded
Hi, It might be too late for some, but I have really been struggling with this and finally succeeded. Just posting this in case somebody else faces the same problem, with a bit of luck they can find it all (or at least most of it) here. Note that it is not a detailed guide as I tried so many things, but it should give the overall gist of it.
I am new to both Hassio/OS and Linux so had to go through a lot of posts. This one somehow led me on the right track so I am posting here. I, like others did not want to run it on a linux/docker (yes, I know, many arguments for doing that, but I did not want to deal with that).
First problem was that most posts are about loading the hassio image to SD, which I do not have, some then resort to burning it directly to the SSD/HDD which I also could not do. So wanted to do it from USB. As others have encountered next problem was to get it to boot from USB, played around with bios settings, a lot. The main thing is to change USB from legacy to UEIF. I believe not everybody has to do that, but I had.
Once I got it to boot, the third problem was that the Hass installation got stuck, as other have, on the menu with autoboot, system 0, system 1, shell options. Neither of which worked.
Saw somewhere the description of a Linux Live distribution, where you run Linux from your USB. Tried that. Worked fine. Then some were talking about having the hass image on a nas server, a second USB and god knows what. Sounded very complicated. I put the gz file on the same USB as the Linux live. Then followed xbmcnut’s description (see post above): gunzip -c /home/ubuntu/Downloads/hassos_intel-nuc-2.12.img.gz | sudo dd of=/dev/sda
Problem four: As I was new to Linux I had no idea how/where to enter the above command. Turns out it is in a terminal window which you can open by pressing Ctrl + Alt + T. Probably obvious to Linux people, but not to me.
xmbcnut’s post might actually be what gave me the clue as he writes, offhandedly sort of, that BerryClaim “had downloaded the GZ using a live Ubuntu install instead”. And I had seen somewhere else that a live linux was running it from USB.
At some point during the above I had to put the USB back to legacy, not sure when that was, so play around with it.
So a big thanks to xmbcnut and the many others whose posts allowed me to piece this together.
Hi @eriktoft,
Can you expand on this, please?
I’ve been trying to install Proxmox on my NUC8i5 from a USB stick with the Proxmox iso image, prepared using Etcher, and getting an error when it starts to boot:
“Image Authorization Fail, System cannot boot to this device due to Security Violation.”
When you mention ‘putting the USB back to legacy’, how did you do that? Is it something you did to the USB stick, or something in the bios during the boot process?
This might just be the bit I’m missing!
TIA.
Yes, it was changing the USB settings in bios, I could not boot from bios without changing it back. But it was a different error message, I think, I got, so perhaps you need to change some security settings also in bios. Trial and error, a lot, did it for me:-)
Thanks for the information, that helps. I’ll give it another try soon.
This method just doesn’t seem to work HA starts to boot but gets stuck on Bluetooth firmware revision line and just does nothing.
Silly question time!
i have tried the dd method and etcher on both the internal emmc and an ssd all 4 installs end up at the hassOS boot menu, holding the enter key for a while causes a message to kinda display and from what i can make out the install is looking for a /boot/efi partition… Can anyone offer any suggestions on this?
This I have exactly the same… cant get it working
I was able to install it on my nuc as following:
I did startup gparted shortly and noticed the bootable flag was not set (I had deleted entire disk content and re-created partition table) so I enabled bootable flag
Also I did nothing to resize it, I can see the total size of the disk being used (120GB) mostly being used by /dev/sda8 with 100GB free space left
Hope it helps for someone
I want to give you an overview what I experienced.
I bought a NUC7CJYH2 with 8 GB Ram and 256 SSD!
With etcher I wrote the image to the SSD.
I started the nuc with an Ethernet cable connected.
It couldn‘t boot because the image wasn‘t save. So I started the bios and and changed the boot option.
Then NUC Booted, but stucked with connecting to the network. That’s why I deactived the WiFi in the BIOS.
The NUC Booted properly and I could see it on my dhcp server, but I couldn‘t connect to it.
I restarted the Nuc and updated the bios.
After a restart I had the same problem, but after 30-40 minutes the webpage loaded.
I installed the smb plugin and placed my last backup in the backup folder.
After a restart, I had to wait 30-40 minutes again and could load the backup.
Finally, my NUC booted in 45 seconds and everything is working like a charm!
It replaced my rpi2 and is running as a Live System for 4 days now (deconz and zwave included)
Success with your method and particularly with the approach of imaging the SSD externally first. The tip on identifying the ethernet identifier also helped so thank you.
I have traditionally run my HA instance on a smart plug that can be reset through some other system if needed, as a last ditch solution. If anyone is aware of another option that the NUC permits, that would be interesting.
I have been having this exact same issue for far too long… did you have any luck solving the problem?
I used balena etcher in an Ubuntu Live distro to image to a Samsung 970 NVMe m.2. This is an Intel NUC.
I’ve found it’s easier to use Rufus to make a bootable Ubuntu USB and then install to the drive. Try following THIS
Thanks, but the issue @Blair_Pollard and me have are specific when installing HASSIO as an OS directly to a NUC. I have been running it fine for over a year on a R-Pi but whenever I revisit my NUC I get stuck at the same place. I realize I could install Ubuntu or another distro and go that route, but I have enjoyed the simplicity of HASSIO on my R-Pi for a while and would love to maintain that.
Hass.io was never an OS, and also no longer exists. I think you are confusing it with the old HassOS that is now called Home Assistant OS.
The docs haven’t all been updated since the name change.
It’s super easy to install Ubuntu and then Home Assistant Supervised (Hass.io). Maintenance is very easy.
Yeah, not sure on the nomenclature. At any rate, installing it on a NUC causes the above error being faced.
I did find the following as it relates to another distro but seems to be the exact issue (https://forums.balena.io/t/bluetooth-firmware-failed-intel-nuc7i5-intel-wireless-ac-8265-bt-4-2/1837). Seems the firmware looks to be out of date on the hass img.
The more I read into the above, it seems like I need to inject a library into the Hassio disk image: https://github.com/pop-os/linux-firmware/blob/master/intel/ibt-19-0-4.sfi
Anyone have an idea how this can be done?
Well, for anyone that has been stuck getting your NUC to boot with HassOS, here is MY solution… and it’s super easy: DO NOT USE A NVMe M.2 DRIVE.
After a ton of reading and experimentation I found that swapping out my Samsung 970 EVO Plus with a M.2 SSD, worked perfectly. Also, in my case this is for a NUC8i3 and NUC10i3. If this is in fact true across the board for all NUC models, this should really be documented/fixed.
Hope this helps someone… I’ve seen several of you stuck at the same place as me.
Bingo!
NVME disk now working on Intel NUC
This is what I did:
To enable WiFi:
nmcli dev wifi connect “SSID” password “password”
Make sure to include “”. This helped me a lot: networking - Unable to connect to any wifi with NetworkManager due to error: Secrets were required, but not provided - Unix & Linux Stack Exchange
