Question regards Asus Code IX Board and NVME

[Formaleins]

Wonder if anyone out there can help with this one?

I have an Asus Maximus Code IX Motherboard which comes with two onboard M.2 NVME Drive slots. However, when I read the manual for the MB, it has a section where it refers to the NVME drive slots and the SATA onboard slots.

Basically, what the manual seems to infer is that if you take up one NVME slot on the board, then it will disable one of the SATA ports. If you take up 2 NVME slots then it disables 2 of the SATA slots.

Seems a bit pointless in having them if this is true. Now, going into the BIOS on the motherboard there is a separate option that allows you to configure the NVME slots as either SATA or NVME/PCIE. (Obviously I want to use the PCIE option for the higher bandwidth)

Can someone out there tell me if I enable the NVME drives and set them up using the PCIE option rather than SATA option, will that prevent the Motherboard disabling the 2 SATA slots onboard?

 

Cheers!

[Formaleins]

No, I am not replying to my own topic, just adding another additional query.

In advance of getting the NVME's I decided that I would try out cloning the OS drive so I can move it onto the new NVME when it arrives. 

Using Macrium Reflect, I cloned the original operating software onto my spare hard drive, with the intention of then restoring it to the new NVME.

The idea was to make sure everything would work so that it would be easy once the new drive arrived.

Next, I created a recovery boot drive again with Macrium, that allows a boot from a USB stick. Then once booted I could restore the OS to the new drive.

So, the recovery drive worked fine and booted up allowing me to access the Image and to simulate the operation, I then transferred it to the Samsung T5 drive.

All was going OK until I tried to boot from the Samsung T5, I got passed the BIOS screen and got the first of the windows logo screen with the swirling arrow. After about 10 seconds, I get a BSOD saying INNACESSABLE_BOOT_DEVICE.

 

I tried rebooting and this time it did the same but then went into automatic repair, then BSOD again. Any ideas as what might be going wrong?

[thedemon]

The symptoms sound like an AHCI setting mismatch between the HDD cloned from and the new (SSD?) being cloned to.

 

Isn't a Samsung T5 a portable USB drive? If it is, I don't think that can work anyway.

[Formaleins]

On ‎5‎/‎16‎/‎2018 at 1:11 AM, thedemon said:

The symptoms sound like an AHCI setting mismatch between the HDD cloned from and the new (SSD?) being cloned to.

 

Isn't a Samsung T5 a portable USB drive? If it is, I don't think that can work anyway.

Yes, the Samsung is an external SSD and you are probably right the more I look into it, it probably cannot be used the way I wanted it to.

The ACHI makes sense too, I guess I will have to wait until I get the NVME and give it a try.

 

Thanks for the help.