Results 1 to 4 of 4

Thread: How2:dual boot (windows 10, leap), after adding an nvme ssd for installation of 2nd version of suse

  1. #1

    Default How2:dual boot (windows 10, leap), after adding an nvme ssd for installation of 2nd version of suse

    bios options are limited: Dell xps 8920.
    allows choice of "RAID" or "AHCI"
    secure boot is enablled.

    With "RAID", windows 10 boots and sees (currently empty) Samsung nvme ssd. It is
    unformatted and I don't intend to use it for windows. Windows runs fine.
    If I boot into leap 42.3, which resides on a sata disk, that works fine, too.

    I wish to install a 2nd version of linux on the nvme ssd.
    But lsscsi and lspci don't see the nvme ssd.

    Advice on various web support blogs says: change bios from "RAID" to "AHCI" to get
    linux to recognize nvme ssd. But that will prevent booting windows.

    Worse, when I try changing the setting in the bios to "AHCI" I get a warning from the Dell bios: windows may
    be unbootable and require reinstallation. HP documentation says the same.

    1. Is that true? Why doesn't resetting the bios to "RAID" after installing linux on the nvme ssd, restore the windows boot process?
    If it does, then I simply have to remember to reset the bios each time I wish to switch between linux and windows.

    2. If setting "AHCI" and then booting, irreparably messes up windows, then is there a work-around which enables me to employ the nvme ssd as a linux
    boot disk with the Sata controller in RAID mode?

    I have read advice to set "AHCI", disable secureboot, boot into windows and let it fix the mess. Hmmm. I haven't enjoyed much success
    letting windows fix messes.

    I had believed that, when in RAID mode, the Sata controller enables both RAID and AHCI communications. Where am I going wrong?

    jim

  2. #2
    Join Date
    Sep 2012
    Posts
    5,141

    Default Re: How2:dual boot (windows 10, leap), after adding an nvme ssd for installation of 2nd version of

    Quote Originally Posted by 0jbennett View Post
    Worse, when I try changing the setting in the bios to "AHCI" I get a warning from the Dell bios: windows may
    be unbootable and require reinstallation. HP documentation says the same.

    1. Is that true?
    This will require different driver for Windows boot device so without extra steps it is true.

    Why doesn't resetting the bios to "RAID" after installing linux on the nvme ssd, restore the windows boot process?
    As long as Windows itself is not on NVMe it probably will, but then Linux will lose its boot device.
    If it does, then I simply have to remember to reset the bios each time I wish to switch between linux and windows.
    Well, it is hard to predict how access to "foreign" device will be impacted. If you can ensure that Linux will never attempt to modify content of Windows device and vice versa it will probably work. Of course it is equally hard to predict what happens if you by accident try to boot Windows in AHCI mode.

    If setting "AHCI" and then booting, irreparably messes up windows, then is there a work-around which enables me to employ the nvme ssd as a linux
    boot disk with the Sata controller in RAID mode?
    You could try to switch Windows to AHCI. Of course it presumes that you do not actually use RAID for boot device. Also you may lose some of features during this (see e.g. https://mjg59.dreamwidth.org/44694.html). Or you can build custom kernel with patches to enable access to NVMe behind Intel RAID. Of course, as these patches are rather old by Linux kernel standard it means you will be responsible for maintaining them and fixing any possible breakage.

    I have read advice to set "AHCI", disable secureboot, boot into windows and let it fix the mess. Hmmm. I haven't enjoyed much success
    letting windows fix messes.
    It is hard to comment without proper context. In general, it is more involved than just "let Windows fix mess you created". It may be possible that newer Windows 10 editions make it easier and that is what author had. But that's off topic on this list, you really need to ask on dedicated Windows forums.

  3. #3

    Default Re: How2:dual boot (windows 10, leap), after adding an nvme ssd for installation of 2nd version of

    "It is hard to comment without proper context. In general, it is more involved than just "let Windows fix mess you created". It may be possible that newer Windows 10 editions make it easier and that is what author had. But that's off topic on this list, you really need to ask on dedicated Windows forums."

    Will do. Thanks. jim

  4. #4

    Default Re: How2:dual boot (windows 10, leap), after adding an nvme ssd for installation of 2nd version of

    Follow-up:

    I did what is outlined in previous post. It enables linux to format, mount, etc., the nvme ssd.

    But windows 10 screws itself up. Once put into "safe mode" it is not possible again to login if a "pin"
    (as distinct from a pw) is assigned. I bought the computer with windows 10 installed and a pin added.

    There seems to be no workaround.

    So, I'll lurk on windows community forums until someone comes up with a solution. *Lots* of people
    get into "safe mode" and can't get out. Seems it isn't so "safe."

    End topic here. Thanks again, jim

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •