I'm unclear why this M.2 drive is not listed from the BIOS as a bootable device. Windows 10 allows me to install to it, but when it comes down to actually booting from it the drive is missing from the offering from any BIOS driven menu. I don't remember seeing any "unsupported" keywords in this product when I bought it, but I fear that something isn't kosher in documentation land that I'm about to find out. The specs are: Toshiba Memory America THN-RC10Z2400G8(TS OCZ RC100 Series NVMe M.2 2242 Internal SSD 240GB I updated the firmware to 104 from 103 and even tried the trick of throwing in an empty SD card, but that didn't help either. The last time I remember seeing this sort of nightmare, dubbed due to the severity of confusion it has caused, I recall was when SATA was just becoming a thing and manufacturers couldn't agree on which operating mode to standardize on which made drive support a zoo.
1) Which port are you connecting it to? 2) Have you tried connecting it on a different port? 3) Have you tried connecting it on a different computer? 4) Have you tried connecting a different SSD to the same port?
According this discussion a NVMe M2 SSD is not (yet?) supported by Udoo X86 in its NGFF slot https://www.udoo.org/forum/threads/pcie-x2-nvme-ssd.10787/
Sad day, can't have fast things to boot from... well Win 10 is a glutton during major updates and I know from first hand experience that it failed on another device I own that only offers 32GB of EMMC onboard storage. This is due to OS + Software space consumed leaves less than what the Windows update demands which in my case was 8GB. I'll do what I can to offset this issue with setting software to install to the M.2 drive and see what can be done to re-home the Windows Update cache folder to reside on that drive as well.
@Snakebyte The drive works, just not as a bootable device on this particular board. Its like having a phone that supports voice recognition, but only when the screen is unlocked. @waltervl Is there rumor of extending support for NVMe on NGFF slots?
If you want to boot directly from NVMe, the firmware has to have the proper code to make it happen. AFAIK, no such function exists on UDOO x86's.
The closed source, proprietary firmware for Udoo's x86 SBC is increasingly disappointing. I find it unfortunate that the developers did not take the time to implement a open source firmware like Open Firmware, which is BSD licensed. I spent some time a while back porting it to Haiku with gcc and it can clearly run in an x86 environment without much effort. With such a firmware and some NVRAM, the Udoo community could contribute the necessary Forth code to allow OF to boot new devices (not to mention that OF can do serial debugging over telnet, which would have greatly aided my porting of a different OS to Udoo x86).
For those that made the unfortunate choice of trying to use Windows 10... https://www.zdnet.com/article/windo...-your-files-to-avoid-crashes-warns-microsoft/ Devices with 32 GB of RAM like these are likely doomed from the WinDoze lineage of OS.
