UNSOLVED

JarrodSmith

updated

6 years ago

J

JarrodSmith

1 Rookie

•

41 Posts

0

710

September 13th, 2020 10:00

XPS 8900, SATA and NVMe incompatibilities

I have recently added an NVMe SSD to the M.2 slot (yes I'm aware it's only PCIe X1).  As my system drive (Samsung SATA SSD - EVO 850) was nearly full, I decided to make the (larger) NVMe drive my system drive and relegate the SATA drive to other duties.  Furthermore, I decided it was time to "un-cruft" my Win10 installation and do a fresh install, from the metal.  So I did that.

Long story short, I seems the current Win10 installer simply will not install to any partition, at all, if you have both SATA and NVMe devices enabled in the UEFI BIOS on this computer.  I wasted almost an entire day before finding some obscure post about this, buried in the comments on somebody's blog.  But lo and behold, as soon as I disabled all the SATA drives in the BIOS (I am running the latest as of this writing - 2.8.0), the Win10 installer happily put a fresh OS on my NVMe drive.  Yay, we all lived happily ever after, right?  Not yet...

After everything was installed and configured I went back into the UEFI and re-enabled my SATA ports.  Now, it takes something like 10-15 minutes to boot.  My best guess at this point is that Win 10 insists on doing a full scan on the SATA drives, because at the VERY end of this delayed boot, a message pops up for two seconds about scanning/fixing one of the volumes.  Furthermore, when I tried to get Macrium Reflect to add an item to the Windows boot menu, for recovery from backups, THAT fails unless I go back into BIOS settings and turn off all the SATA ports.  And if I want to actually access the boot menu, you guessed it - back tot he BIOS to disable the SATA ports.

This is incredibly frustrating - I'd very much like to use all the storage capabilities on my machine but I can't find any info about this issue and have basically run out of resources to look at and things to try, so here I am asking.  Hope one of you knows about this and perhaps a workaround.  I am considering retrograding the BIOS down to 2.6.1 to see if that fixes it but at this point everything is just a guess and I've burned an incredible amount of time on this already - nearly two weekends' worth.

  • JarrodSmith

    1 Rookie

    •

    41 Posts

    495

    0

    Posted September 13th, 2020 11:00

    Incredibly, after three days of fighting this, I may have solved it 15 minutes after posting.

    I had the theory that maybe one of the SATA ports listed in the BIOS was actually referring to the SATA capability of the M.2 slot (I still don't know if this is true or not) and was somehow interfering at boot time.  So decided I would only turn on the SATA ports that had something connected.  So I opened the case, read the mobo connectors and decided I'd turn on SATA 0, 1, 2 (my BDROM, SSD, and HDD, respectively).

    While I was in there, I noticed that I had "Enable Legacy Option ROMS" enabled.  I already knew I did't need that - not sure when or why that got flipped on - so I turned it off.  For good measure I enabled Secure Boot since in my reading I learned this seems to work now in recent UEFI FW.

    I rebooted and everything works as expected now.

    To summarize - if you are mixing NVMe and SATA devices, all configured as GPT devices with UEFI booting:

    1. Turn off Enable Legacy Option ROMS
    2. Turn on Secure Boot
    3. Only enable the SATA ports you have physically connected devices to.

    Some combination of that appears to be the magic I've been looking for.