• Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
  • Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login

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

Scheduled Pinned Locked Moved
Hardware Compatibility
3
7
3.7k
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • G
    geardog
    last edited by Dec 1, 2017, 9:24 PM

    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”
    0_1512162599791_585599cb-7c9e-4390-9913-1daa8794cbb1-image.png

    I added …
    Host Kernel Arguments: mdraid=true & Host Primary Disk: /dev/md126
    which gave me “failed to read back partition (runPartprobe)”
    0_1512162227133_97bf105c-3a5b-4105-9aa5-b3e037edc20f-image.png

    System
    0_1512160546552_0b2a3ac8-a1f4-4693-8563-e163f34793c0-image.png

    1 Reply Last reply Reply Quote 0
    • G
      george1421 Moderator
      last edited by Sebastian Roth Dec 2, 2017, 4:41 AM Dec 1, 2017, 9:40 PM

      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.

      Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

      1 Reply Last reply Reply Quote 0
      • G
        geardog
        last edited by Dec 1, 2017, 9:52 PM

        @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?

        G 1 Reply Last reply Dec 1, 2017, 10:12 PM Reply Quote 0
        • G
          george1421 Moderator @geardog
          last edited by Dec 1, 2017, 10:12 PM

          @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
            lsblk
            blkid
          7. Post the results here. The lsblk will post what the FOS engine is seeing for block devices on the system.

          Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

          G 1 Reply Last reply Sep 12, 2018, 8:48 PM Reply Quote 1
          • G
            geardog @george1421
            last edited by geardog Sep 12, 2018, 2:50 PM Sep 12, 2018, 8:48 PM

            @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…
            0_1536785231194_e0b4e504-71b8-4777-9f40-18b451245345-image.png

            Any hope of getting this NVMe to show up?

            also … on pxe boot this comes up … significant?
            0_1536785366652_3a799a7c-c5e2-47bf-9a6f-c48caa158569-image.png

            1 Reply Last reply Reply Quote 0
            • S
              Sebastian Roth Moderator
              last edited by Sep 12, 2018, 9:36 PM

              @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.

              Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

              Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

              G 1 Reply Last reply Sep 13, 2018, 5:30 PM Reply Quote 0
              • G
                geardog @Sebastian Roth
                last edited by geardog Sep 13, 2018, 11:31 AM Sep 13, 2018, 5:30 PM

                @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

                1 Reply Last reply Reply Quote 1
                • 1 / 1
                • First post
                  Last post

                183

                Online

                12.0k

                Users

                17.3k

                Topics

                155.2k

                Posts
                Copyright © 2012-2024 FOG Project