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

Open
bruhautomation opened this issue Jul 1, 2019 · 12 comments
Open

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

bruhautomation opened this issue Jul 1, 2019 · 12 comments

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

This comment has been minimized.

Copy link

@botne botne commented Aug 21, 2019

Hi!

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

Br,
Frank

@bruhautomation

This comment has been minimized.

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

This comment has been minimized.

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

This comment has been minimized.

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

This comment has been minimized.

Copy link

@rovrell rovrell commented Sep 27, 2019

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

@xbmcnut

This comment has been minimized.

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

This comment has been minimized.

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

This comment has been minimized.

Copy link

@air720boarder air720boarder commented Dec 22, 2019

This is currently a blocker for me as well

@Mathijs0

This comment has been minimized.

Copy link

@Mathijs0 Mathijs0 commented Dec 23, 2019

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

@air720boarder

This comment has been minimized.

Copy link

@air720boarder air720boarder commented Dec 24, 2019

Any fixes in the pipeline for this?

@Mathijs0

This comment has been minimized.

Copy link

@Mathijs0 Mathijs0 commented Dec 24, 2019

Or a warning on the install page?

@niXta1

This comment has been minimized.

Copy link

@niXta1 niXta1 commented Dec 26, 2019

Also got stuck here...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
9 participants
You can’t perform that action at this time.