Hi. I have a two NUC5i5RYH boxes, each with a small M.2 drive (250 GB) and a larger 2.5-inch SATA SSD drive (500GB).
My objective is to install the OS on the smaller M.2 drive, and use the larger 2.5-inch drive for data. And I got this to work in Win8.1 and Win10. *But* Windows Setup and the Windows Disk Management tool interprets the 2.5-inch drive as Drive 0, the *first* physical drive, and the M.2 drive as Drive 1, the *second* physical drive in the unit.
A quick check with Debian via a live USB stick indicates that same - the 2.5-inch is the first drive, designated SDA, and the M.2 is the second drive, designated SDB.
From the above symptoms, I'm interpreting that the NUC firmware is presenting to the OS the 2.5-inch as the first drive, and the M.2 as the second drive.
Is there a way to reverse this, i.e. have the M.2 drive as the first drive?
My thoughts were that as faster NVMe M.2 drives become more generally available, it will make sense to place the OS on the faster M.2 drive, and data on the slower 2.5-inch SATA drive. And to have the M.2 as the first drive. This is obviously a nice-to-have vs an essential issue. But I guess I`m a bit OCD, and this was a surprise when I put together the units. I can`t see anything in the BIOS that controls this.
Here`s the Hardware Details:
- M.2 drive (Samsung 850 EVO 250 GB)
- 2.5-inch SATA SSD drive (Samsung 850 EVO 500GB)
- BIOS: v0249
- UEFI is enabled.
Any ideas appreciated!
Colin