Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Intel NUC won't boot off NVME M.2 drive #422

Closed
bruhautomation opened this issue Jul 1, 2019 · 29 comments · Fixed by #626
Closed

Intel NUC won't boot off NVME M.2 drive #422

bruhautomation opened this issue Jul 1, 2019 · 29 comments · Fixed by #626

Comments

@bruhautomation
Copy link

@bruhautomation bruhautomation commented Jul 1, 2019

Hello! Thanks for the awesome work on HassOS.

I'm trying to run HassOS off of a NUC. Everything works great when I use a standard SSD. I burned the image directly to the drive using balenaEtcher via a USB-to-SATA adapter. Pop the drive into the NUC and it's rolling.

However, when I repeat this exact process with a NVME M.2 drive, HassOS refuses to boot. I've tried copying the partitions from the working drive to the NVME drive, but that didn't resolve the issue.

I have the secure boot settings turned off in the BIOS and confirmed the NUC can see the NVME M.2 drive. I've scrubed the drive and confirmed that all the partions are being written identically to the working standard SSD.

No matter what I try, HassOS on the NVME M.2 drive tries to boot, but ultimately leaves me stuck at HassOS boot menu.

Do you have a guess why the switch the NVME M.2 drive prevents HassOS from booting/running?

I'm wondering if the partition labels are affecting something.

The working SSD uses /dev/sda1 /dev/sda2, etc. The not-working NVME drive uses /dev/nvme0n1p1 /dev/nvmeon1p2 etc.

Is HassOS looking for the standard partition labels on boot?

Thanks much!

@botne
Copy link

@botne botne commented Aug 21, 2019

Hi!

I have the same issue.
Did you find a workaround for this?

Br,
Frank

@bruhautomation
Copy link
Author

@bruhautomation bruhautomation commented Aug 26, 2019

Sorry for the slow response. I have not resolved this issue yet. I'm running it off of an SSD which works as expected.

@botne
Copy link

@botne botne commented Aug 26, 2019

ok, @bruhautomation. Will change the m.2 nvme for a m.2 sas instead. I guess that will fly :)

@pvizeli
Copy link
Member

@pvizeli pvizeli commented Aug 28, 2019

I think it's a barebox issue. I hope uboot come also soon with an working UEFI support

@rovrell
Copy link

@rovrell rovrell commented Sep 27, 2019

Ahh, that's the problem :/ tried for 2 days now.

@xbmcnut
Copy link

@xbmcnut xbmcnut commented Nov 14, 2019

Hey Ben. Happening for me too. Sorry, I duplicated the issue here https://github.com/home-assistant/hassio/issues/1365

@SBerg1980
Copy link

@SBerg1980 SBerg1980 commented Nov 27, 2019

I have the same problem, i want to switch from my pi to my NUC with a nvme disk but when i run de gunzip and then boot the NUC its stuck on boot.

@air720boarder
Copy link

@air720boarder air720boarder commented Dec 22, 2019

This is currently a blocker for me as well

@Mathijs0
Copy link

@Mathijs0 Mathijs0 commented Dec 23, 2019

This is why I now use Debian with hass.io and not hassos

@air720boarder
Copy link

@air720boarder air720boarder commented Dec 24, 2019

Any fixes in the pipeline for this?

@Mathijs0
Copy link

@Mathijs0 Mathijs0 commented Dec 24, 2019

Or a warning on the install page?

@niXta1
Copy link

@niXta1 niXta1 commented Dec 26, 2019

Also got stuck here...

@AdamNaj
Copy link

@AdamNaj AdamNaj commented Feb 5, 2020

Same problem for me... Was so excited when the NUC arrived, didn't last long...

@niXta1
Copy link

@niXta1 niXta1 commented Feb 6, 2020

Same problem for me... Was so excited when the NUC arrived, didn't last long...

Install a sata ssd or go with another OS... Only options for now...

@manavees
Copy link

@manavees manavees commented Feb 7, 2020

Any news about how to run hass in nvme ssd on a NUC? I am thinking of getting a NUC for my home assistant and would like to go with nvme

@xbmcnut
Copy link

@xbmcnut xbmcnut commented Feb 7, 2020

You'll have to run something like Promox as I ended up doing. Check out Drzzs videos in that process.

@manavees
Copy link

@manavees manavees commented Feb 7, 2020

You'll have to run something like Promox as I ended up doing. Check out Drzzs videos in that process.

What about using a 2,5'' SSD? Will it work without any issues?

@xbmcnut
Copy link

@xbmcnut xbmcnut commented Feb 7, 2020

Should do no issue although some reported that 3.8 was causing issues on my YouTube channel. Maybe 3.9 resolved this?

@manavees
Copy link

@manavees manavees commented Feb 7, 2020

So basically also a simple m.2 sata could work. Like the Samsung (https://s3.ap-northeast-2.amazonaws.com/global.semi.static/Samsung_SSD_860_EVO_M2_Data_Sheet_Rev1.pdf)

@niXta1
Copy link

@niXta1 niXta1 commented Feb 7, 2020

So basically also a simple m.2 sata could work. Like the Samsung (https://s3.ap-northeast-2.amazonaws.com/global.semi.static/Samsung_SSD_860_EVO_M2_Data_Sheet_Rev1.pdf)

No, that has a m2 interface, it needs to have a SATA connector (2.5").

@Mathijs0
Copy link

@Mathijs0 Mathijs0 commented Mar 31, 2020

Is there any progress in this issue?

@Blankf
Copy link

@Blankf Blankf commented Apr 8, 2020

Same question here, is there any progress on this issue? Or is someone looking at it?

@tradiuz
Copy link

@tradiuz tradiuz commented Apr 8, 2020

When you burn the NVMe with etcher, what do you see under /dev in the HassOS boot menu. I was able to get my AtomicPi to boot manually by mounting /dev/usbdisk1.hassos-kernel0 to /mnt/system because the system0 script assumes the drive is named disk*.hassos-kernel0 I suspect the NVMe drives show up similarly different from a "disk".

A stupid fix might just be changing the disk* to just * or some regex of all possible drive types (mmcblk, nvmeon, disk, usbdisk, etc).

@Blankf
Copy link

@Blankf Blankf commented Apr 9, 2020

How were you able to mount it from the shell?

i see a bunch of
disks0/1/2/3/4/5/6/7 and
disk1/2/3/4/5/6/7
disk0.hassos-boot
disk0.hassos-bootstate
disk0.hassos-data
disk0.hassos-kernel0
disk0.hassos-kernel1
disk0.hassos-overlay
disk0.hassos-system0 en 1

not seeing anything that looks like nvme.

@Mathijs0
Copy link

@Mathijs0 Mathijs0 commented Apr 21, 2020

Nice and thank you! I am gone try it out soon.

@Mathijs0
Copy link

@Mathijs0 Mathijs0 commented Apr 25, 2020

O this issue is closed but not jet released, when wil this fix be implemented? Now that I formatted my drive :-(

Copy link
Member

@frenck frenck commented Apr 25, 2020 — with Octobox

Yes, issues close when development is finished and does not tell anything about availability.

We don't have a schedule for this. Things are ready when they are ready.

@Mathijs0
Copy link

@Mathijs0 Mathijs0 commented Apr 25, 2020

okey thanks for your work!!

@Joc007
Copy link

@Joc007 Joc007 commented May 2, 2020

Success, it works now.
If you need details, see this: https://community.home-assistant.io/t/my-steps-to-success-for-hass-io-on-intel-nuc/43915/323

Thanks for this great work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.