Cannot find disk on system, NVMe, RAID mode, Intel RST

  • I’ve installed FOG 1.4.4 on ubuntu 16.04, imaged almost two dozen boxes around the house, and loving it. The UEFI boxes are proving a bit of a pain.

    This is an NVMe drive with SATA mode set to RAID for Intel’s RST. Reading I’ve done on this box and NVMe drives says you must keep RAID mode to boot. I’ve seen a dozen posts similar to this dealing with raid, and my head is swimming quite honestly. This isn’t an array. It’s simply RAID mode. Is mdraid or mdadm appropriate?

    Basic vanilla capture gave
    “Cannot find disk”

    I added …
    Host Kernel Arguments: mdraid=true & Host Primary Disk: /dev/md126
    which gave me “failed to read back partition (runPartprobe)”


  • @Sebastian-Roth

    lspci -nn showed the drive to be in raid mode

    using a tutorial on bcdedit via cmd for safemode boot I was able to change the setting without reinstalling windows

    now the machine is imaged

    resolved and thankyou

    coming back to this with a fresh mind and some new info helped

  • Senior Developer

    @geardog Ok your NVMe disk is not seen by our FOS linux system. Can you run another debug task and run lspci -nn - post picture here.

  • @george1421
    Back at it. One of the other hats I wear got in the way.

    I’m on FOG 1.5.4 \ kernel 4.18.3

    As requested…

    Any hope of getting this NVMe to show up?

    also … on pxe boot this comes up … significant?

  • Moderator

    @geardog said in Cannot find disk on system, NVMe, RAID mode, Intel RST:

    I’m pretty sure all the screenies came from this Dell XPS 8920 box I’m sitting at. What would make you think otherwise?

    Sorry that just shows my ignorance of the Dell consumer bios screens. I use the Dell business computers in my office and the bios is totally different.

    OK what I want you to do this is this.

    1. Configure the firmware to what ever you consider as default.
    2. Manually register this computer if its not currently registered.
    3. Schedule a image capture or deploy I don’t care, but before you hit the submit button to schedule the task, click the checkbox for debug.
    4. PXE boot the target computer, this should automatically start the debug capture/deploy.
    5. After a few enter key presses on the target computer’s console it should drop you to a linux command prompt (on the target computer).
    6. Key in the following command
    7. Post the results here. The lsblk will post what the FOS engine is seeing for block devices on the system.

  • @geardog said in Cannot find disk on system, NVMe, RAID mode, Intel RST:

    Thanks for the quick response.

    I am running one NVMe “disk.” This is a SATA mode setting in the “BIOS.”

    I switched to AHCI once, and no boot options were accepted. No access to bios was allowed. It was a boot loop until a bios setting “3 failed boots and restore last good settings” broke the loop and gave bios access back. After that, I was really hoping there was another route.

    I’m pretty sure all the screenies came from this Dell XPS 8920 box I’m sitting at. What would make you think otherwise?

  • Moderator

    Lets make sure we understand something here.

    Do you, are you using intel’s “fake-raid” on this computer or do you have a single disk and raid-on is enabled in the bios.

    I can tell you with Dell computers in UEFI mode, and the disk adapter set to raid-on (factory default) with a single disk installed, linux will not boot in this configuration. You MUST change the disk mode to AHCI mode to get the device to boot in linux (FOS uses linux to move image files). Once the image file has been deployed you can switch raid-on back on.

    I understand that screen shot is not a Dell systems, but the same rules apply.

    Now if you ARE using Intel’s hardware assisted software raid, then you have started down the right path. Once we know what you have we can give you better debugging directions.

Log in to reply