Hello!
A few weeks ago, I spent a day exchanging M.2 drives between my main PC and an Intel Hades Canyon NUC that I have recently received.
However, after the M.2 drives have been installed and running in the NUC, they are no longer being detected and booted on my main PC once I moved them back over. The drives do work perfectly when placed back into the NUC, though.
When troubleshooting one of the drives as an experiment, I found that, from a windows 10 bootable USB, diskpart detected the drive and the problem was completely fixed once I formatted and reinstalled the OS on it.
I do not wish to format my other drives, since they hold my primary Windows 10 boot and other files that I do not want to lose/transfer. Could there be any alternative solutions to this issue? I have heard that some OEM boards do some odd firmware stuff to components that are installed onto it, and I am unsure on how to revert this without clearing all of my data. Also, when trying the defaulted NVME drive that came with the NUC, this exact no-booting issue still occurred, so this is where I have concluded that the NUC is doing something with the M.2 drives.
If this helps any, the specs on my main PC are:
X399 Taichi ATX Motherboard
Ryzen Threadripper 1900X
32GB Trident Z 3200MHz (8GB in quad channel)
A few weeks ago, I spent a day exchanging M.2 drives between my main PC and an Intel Hades Canyon NUC that I have recently received.
However, after the M.2 drives have been installed and running in the NUC, they are no longer being detected and booted on my main PC once I moved them back over. The drives do work perfectly when placed back into the NUC, though.
When troubleshooting one of the drives as an experiment, I found that, from a windows 10 bootable USB, diskpart detected the drive and the problem was completely fixed once I formatted and reinstalled the OS on it.
I do not wish to format my other drives, since they hold my primary Windows 10 boot and other files that I do not want to lose/transfer. Could there be any alternative solutions to this issue? I have heard that some OEM boards do some odd firmware stuff to components that are installed onto it, and I am unsure on how to revert this without clearing all of my data. Also, when trying the defaulted NVME drive that came with the NUC, this exact no-booting issue still occurred, so this is where I have concluded that the NUC is doing something with the M.2 drives.
If this helps any, the specs on my main PC are:
X399 Taichi ATX Motherboard
Ryzen Threadripper 1900X
32GB Trident Z 3200MHz (8GB in quad channel)