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
Comments
Hi! I have the same issue. Br, |
Sorry for the slow response. I have not resolved this issue yet. I'm running it off of an SSD which works as expected. |
ok, @bruhautomation. Will change the m.2 nvme for a m.2 sas instead. I guess that will fly :) |
I think it's a barebox issue. I hope uboot come also soon with an working UEFI support |
Ahh, that's the problem :/ tried for 2 days now. |
Hey Ben. Happening for me too. Sorry, I duplicated the issue here https://github.com/home-assistant/hassio/issues/1365 |
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. |
This is currently a blocker for me as well |
This is why I now use Debian with hass.io and not hassos |
Any fixes in the pipeline for this? |
Or a warning on the install page? |
Also got stuck here... |
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... |
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 |
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? |
Should do no issue although some reported that 3.8 was causing issues on my YouTube channel. Maybe 3.9 resolved this? |
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"). |
Is there any progress in this issue? |
Same question here, is there any progress on this issue? Or is someone looking at it? |
When you burn the NVMe with etcher, what do you see under A stupid fix might just be changing the |
How were you able to mount it from the shell? i see a bunch of not seeing anything that looks like nvme. |
Nice and thank you! I am gone try it out soon. |
O this issue is closed but not jet released, when wil this fix be implemented? Now that I formatted my drive :-( |
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. |
okey thanks for your work!! |
Success, it works now. Thanks for this great work. |
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!
The text was updated successfully, but these errors were encountered: