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.
I’m assuming from this that you imaged your existing HA install first and then just copied it back to the new NVMe? Is this easier than doing a backup and restore?
EDIT. Sorry, re-read. So your using Gnome to write the downloaded disk image to the NVMe. Got ya now. That’s easier than my method. Will give that a try.
Thanks for this. Huge help. A tip for those trying this.
Wipe the partition first if the disk was previously used as mine was, otherwise the restore does not work. I had Proxmox on mine prior and the restore keep coming up with an error until I booted back to Windows, wiped the drive and created a new partition.
It’s best to have downloaded and unzipped the image file prior to booting into Ubuntu and have this on another USB stick. That will provide the easiest method of locating the *.img file for the restore process.
I’ve noted that the dev version does not seem to have a ‘reload’ icon for the snapshot page. Not sure if this is 0.109.3 or the HassOS. Once you’ve copied your backup files to the backup folder, you’ll need to reboot the hardware for these to be discovered.
‘it’ is your disk on which you want to restore the image.
Since you are running this on a nuc I presume there is just one disk? I did this on my m2
So on a root terminal
run gnome-disks
restore image/disk (under the waffle icon)
choose your disk
overwrite contents (you will be erasing the current disk)
I started gparted and checked bootable flag on the disk as well
Just bought a NUC5i3, 8Gb/128Gb M.2 and using gnome-disks did not worked for me, it booted but was stuck before the end of the boot. I downloaded Balena Etcher and HassOS from Ubuntu live and then flashed HassOS image directly to SSD. Worked perfectly!
For performance improvement, I’m working on upgrading the a HA setup to NUC i5-6260U | 1.8GHz | 16GB RAM running Ubuntu 20.04 with Virt-Manager but am still unable to get working in a stable & consistent manner see post
The NUC is on my desk, SSD drive inside. No usb/sata adapter at hand, can’t use balena and will try gparted method. How/when can I set the fixed IP address for hassio?
Thank you all for this great information on installing what appears to be Home Assistant’s flagship device, especially now that generic linux is no longer supported.
I think it’s important to get this documentation improved as it’s certainly been a headache hunting down all the information from a long thread, especially as a noob.
A $20 NVME USB adapter seems like an expensive solution for a single use case not to mention the delicate NVME port which isn’t intended to handle repeated installment.
I found a way that’s easier than using “gnome-disks”/“Disks” (although I did get this to work once) to flash the NVME SSD w/ Etcher on a “Try Ubuntu” live boot from Ubuntu Desktop flashed USB.
Live Boot from Ubuntu USB
Download/Copy Etcher + Hassio img
Turn off safe mode in Etcher settings (for Etcher to recognize SSD)
Flash SSD w/ HASSIO NUC img
Reboot NUC
At this point, I’m having connectivity issues with http://hassio.local.8123 which worked on PI and VM. I attempted to edit the nmcli config based on T.H.U. recommendations for VM, notably connection to my router and rbpi’s old ip address(I’ve reused this ip address before so I’m doubting it’s a router issue). Something I did in nmcli bricked the device w/ blackscreen w/ white underscore requiring a re-flash after multiple attempts.
Could this be to do with some boot setting? - I can’t change my boot priority boot type from UEFI like in Intel’s OpenElec documentation as recommended somewhere in the community. UPDATE I attempted legacy boot but this failed to recognize my SSD.
