![]() ![]() Please wait while DiskPart scans your configuration.ĭiskPart has finished scanning your configuration. X:\windows\system32>wmic /namespace:\\root\microsoft\windows\storage path msft_disk get Model,BusTypeĬopyright (C) 1999-2013 Microsoft Corporation. Volume 1 SYSTEM FAT32 Partition 260 MB Healthy Hidden Volume 0 N Windows NTFS Partition 232 GB Healthy Volume # Ltr Label Fs Type Size Status Info NUC10i3FNK with Crucial MX500 M.2 SATA SSDĭisk ID: In each scenario the USB key is removed prior to running the diskpart or wmic commands. I have collected information relating to how the devices are detected on v3.1, using a NUC10i3FNK with M.2 SATA and M.2 NVMe. If the device in the M.2 socket is an NVMe, the M.2 Device is Disk 1 and the USB key is Disk 0. NVMe calls for better performance vectors than AHCI (Advanced Host Controller Interface), including scalable bandwidth, increased IOPS, and low latency. Using the same driver set, and WinPE v3.1, booting via USB with a board where the M.2 socket has a SATA SSD, the M.2 device is Disk 0 and the USB key is Disk 1. NVMe (or NVM Express®) is a host controller interface standard designed to address the needs of enterprise and client applications that utilize PCI Express-based solid-state storage. Using a fixed driver set, WinPE v3.0, booting via USB with a board where the only disk installed is in an M.2 socket, either SATA SSD or NVME, WinPE will give the M.2 device Disk 0 and the USB key Disk 1. The issue has been seen on 5 different boards so far, two different chipset manufacturers and 3 different board manufacturers. After much testing it appears that current WinPE detects an NVMe in an m.2 socket as a different type of disk (as expected) but then gives priority to other interfaces when it comes to disk numbering. While unknown as to what version this issue started with, the problem is replicated in WinPE v3.1 but is not replicated in v3.0. up until windows preview build 14986, the pcie driver 'Mobile 6th Generation Intel(R) Processor Family I/O PCI Express Root Port 5 - 9D14' (v10.1.1.27) correctly detects the 'Standard NVM Express Controller' storage controller and the Toshiba THNSN5512GPU7 NVMe disk attached to it. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |