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

m.2 PCIe SSD not recognised in FOG

Scheduled Pinned Locked Moved Solved
FOG Problems
9
54
41.8k
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.
  • T
    Toby777
    last edited by Dec 9, 2015, 7:51 AM

    Hi guys,

    Have an interesting one here.

    Has anyone tried or been able to image to/from an m.2 PCIe SSD?

    I’ve got a new DELL XPS 13 9350 which is an upgrade from the previous model that uses a regular SSD. I’ve been able to image the DELL XPS 13 9343 without any problems (with the setting in BIOS set to Legacy).

    Anyways, I’ve not been able to get FOG to capture an image from the PCIe SSD.

    What I’ve done to the XPS is…

    Set BIOS to Legacy
    Updated to the latest BIOS from the DELL Support site.
    Installed Windows 10 from scratch wiping all existing partitions and allowing the installer to create its own partitions (2 were created).

    When it comes to PXE booting off the DELL USB NIC (Realtek RTL8153)… if I try using undionly.kkpxe, it gets stuck at loading bzImage at 0%.
    If I try to use any of the .efi pxe images, it goes through the motions until it tried to detect for a HDD but fails and says…

    Looking for Hard Disk....
    
    An error has been detected!
    
    Cannot find HDD on system
    
    Computer will reboot in 1 minute.
    

    So just seeing if anyone has had any experience with PCIe SSDs?

    Cheers
    David

    C T 2 Replies Last reply Dec 9, 2015, 9:50 AM Reply Quote 0
    • Q
      Quazz Moderator
      last edited by Dec 9, 2015, 9:27 AM

      Is it an AHCI or NVMe SSD?

      1 Reply Last reply Reply Quote 0
      • C
        ch3i Moderator @Toby777
        last edited by Dec 9, 2015, 9:50 AM

        @Toby777 Hi, Fog version ?

        1 Reply Last reply Reply Quote 0
        • S
          Sebastian Roth Moderator
          last edited by Dec 9, 2015, 10:25 AM

          @Toby777 Please follow this: https://forums.fogproject.org/topic/6315/hp-z640-nvme-pci-e-drive

          If you could provide the same information this would help us improve FOG. Can you please run a debug session and post the full output of lsblk -pno KNAME,MAJ:MIN -x KNAME? We need the exact output (especially dev names AND the IDs. Just take a picture and post it 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

          1 Reply Last reply Reply Quote 1
          • T
            Toby777
            last edited by Toby777 Dec 9, 2015, 8:02 AM Dec 9, 2015, 1:46 PM

            Thanks for the response. I’m running FOG 5602.

            Not quite sure whether it is AHCI or NVMe. From searching on google it may possibly be NVMe as it is the top range model.

            I will try your suggestions tomorrow and post the output here.

            1 Reply Last reply Reply Quote 0
            • T
              Toby777
              last edited by Dec 9, 2015, 11:09 PM

              @Sebastian-Roth said:

              lsblk -pno KNAME,MAJ:MIN -x KNAME

              I tried excuting the above command but I got…

              [root@fog bin]# lsblk -pno KNAME,MAJ:MIN -x KNAME
              lsblk: invalid option -- 'p'
              
              Usage:
               lsblk [options] [<device> ...]
              
              Options:
               -a, --all            print all devices
               -b, --bytes          print SIZE in bytes rather than in human readable format
               -d, --nodeps         don't print slaves or holders
               -D, --discard        print discard capabilities
               -e, --exclude <list> exclude devices by major number (default: RAM disks)
               -I, --include <list> show only devices with specified major numbers
               -f, --fs             output info about filesystems
               -h, --help           usage information (this)
               -i, --ascii          use ascii characters only
               -m, --perms          output info about permissions
               -l, --list           use list format ouput
               -n, --noheadings     don't print headings
               -o, --output <list>  output columns
               -P, --pairs          use key="value" output format
               -r, --raw            use raw output format
               -s, --inverse        inverse dependencies
               -t, --topology       output info about topology
               -V, --version        output version information and exit
              

              Running CentOS 6.7

              1 Reply Last reply Reply Quote 0
              • S
                Sebastian Roth Moderator
                last edited by Dec 10, 2015, 6:12 AM

                @Toby777 As mentioned below this has to be on the DELL XPS client running a debug session (Host -> Basic Tasks -> Debug).

                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

                1 Reply Last reply Reply Quote 0
                • T
                  Toby777
                  last edited by Dec 10, 2015, 9:57 PM

                  My apologies…

                  Here’s the output…

                  0_1449784624431_FullSizeRender.jpg

                  1 Reply Last reply Reply Quote 1
                  • J
                    JJ Fullmer Testers
                    last edited by Dec 10, 2015, 11:04 PM

                    This is like my problem, except I’m trying to download not upload.
                    What happens if you set the “Host Primary Disk” for that client in the fog web gui to “/dev/nvme0n1” ?
                    That should get it past the cannot find HDD on system, but for me it wasn’t entering partclone for a download, who knows maybe it would work for upload.

                    Thanks,
                    -JJ

                    Have you tried the FogApi powershell module? It's pretty cool IMHO
                    https://github.com/darksidemilk/FogApi
                    https://fogapi.readthedocs.io/en/latest/
                    https://www.powershellgallery.com/packages/FogApi
                    https://forums.fogproject.org/topic/12026/powershell-api-module

                    T 1 Reply Last reply Dec 10, 2015, 11:25 PM Reply Quote 2
                    • T
                      Toby777 @JJ Fullmer
                      last edited by Dec 10, 2015, 11:25 PM

                      @Arrowhead-IT Thanks for the suggestion! I modified the Host Primary Disk value as you suggested and I then got the error saying “No resizable partitions found”.

                      So I then went to the Image properties and changed the Image Type from Single Disk - Resizable to Multiple Partition Image - Single Disk (Resizable), but it just hung after…

                      * Using Hard Disk: /dev/nvme0n1
                      

                      I then changed it to Raw Image and it is now currently uploading.

                      J 1 Reply Last reply Dec 10, 2015, 11:45 PM Reply Quote 1
                      • J
                        JJ Fullmer Testers @Toby777
                        last edited by Dec 10, 2015, 11:45 PM

                        @Toby777 Awesome! That’s good to know. Hopefully they’ll be able to fix it so that nvme works without using raw but the fact that it works at all is awesome! How fast is it uploading? RAW is typically much slower but those pci based drives are supposed to be crazy fast, just curious how fast.

                        Have you tried the FogApi powershell module? It's pretty cool IMHO
                        https://github.com/darksidemilk/FogApi
                        https://fogapi.readthedocs.io/en/latest/
                        https://www.powershellgallery.com/packages/FogApi
                        https://forums.fogproject.org/topic/12026/powershell-api-module

                        T 1 Reply Last reply Dec 10, 2015, 11:48 PM Reply Quote 2
                        • T
                          Toby777 @JJ Fullmer
                          last edited by Dec 10, 2015, 11:48 PM

                          @Arrowhead-IT The notebook and FOG server are on a Gigabit connections and at the moment, the upload rate is displaying 5.14GB/min

                          What’s the implications of using RAW when restoring to drives larger than what its currently being imaged? Will it just be a matter of manually expanding the partition to take up the remainder of the space?

                          J 1 Reply Last reply Dec 10, 2015, 11:56 PM Reply Quote 1
                          • J
                            JJ Fullmer Testers @Toby777
                            last edited by Dec 10, 2015, 11:56 PM

                            @Toby777 I think it might still work on larger drives and you can manually expand the partition. That’s pretty good for RAW from what I’ve seen. Trouble with RAW is that it does every sector of the drive no matter how much space is taken up. Before multiple and extended linux partitions became supported I only used it for very specialized images for computers that were always the same size hard drive.

                            Have you tried the FogApi powershell module? It's pretty cool IMHO
                            https://github.com/darksidemilk/FogApi
                            https://fogapi.readthedocs.io/en/latest/
                            https://www.powershellgallery.com/packages/FogApi
                            https://forums.fogproject.org/topic/12026/powershell-api-module

                            T 1 Reply Last reply Dec 11, 2015, 12:19 AM Reply Quote 1
                            • T
                              Toby777 @JJ Fullmer
                              last edited by Toby777 Dec 10, 2015, 6:21 PM Dec 11, 2015, 12:19 AM

                              @Arrowhead-IT ok cool… well the image on the server came to 20GB. That’s from a 256GB SSD and the Image Compression setting set to 6. Still not too bad actually considering a captured Windows 10 image from the previous model XPS 13 with a 256GB SATA disk using Single Disk - Resizable is about 17GB.

                              Now I guess the big test is to restore the Image on to the same machine and see if it boots. 🙂

                              1 Reply Last reply Reply Quote 1
                              • G
                                george1421 Moderator
                                last edited by Dec 11, 2015, 12:48 AM

                                While this is probably injecting noise into this thread. We will typically create our reference image on a VM with 1 vCPU and 40GB hard drive. With fog we will use a single disk non resizeable (only because 1.2.0 didn’t work to good with resizeable disks in our environment.) but anyway, in the setupcomplete.cmd file we would run a script to expand the logical disk to the size of the physical disk. It worked well. In this setup we capture the image without the drivers for the final target computer so the image comes in at about 5GB on disk for a thin Win 7 image and about 15GB for a fat win7 image with office and other apps. Then just after the images are laid down on the target computer we use the fog post install scripts to inject the right driver pack from the fog server to the target computer. This saves us about 15GB in space on the target computer that we don’t have to upload (once) and download for each OSD. Also as new hardware is released we just need to update the drivers on the fog server, there is no reason to recapture the image.

                                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!

                                W 1 Reply Last reply Dec 13, 2015, 2:11 AM Reply Quote 1
                                • S
                                  Sebastian Roth Moderator
                                  last edited by Sebastian Roth Dec 12, 2015, 4:09 PM Dec 12, 2015, 10:07 PM

                                  Here we go. I found some time to look into this more closely!
                                  Download init.xz/init_32.xz files to test https://drive.google.com/folderview?id=0B-bOeHjoUmyMazJLZDhGaEl5VTQ&usp=sharing and put into place in /var/www/fog/service/ipxe/ or /var/www/html/fog/service/ipxe/ (probably a good idea to rename the original files instead of just overwriting them!)

                                  Please test and report back if capturing/deploy is working (Image type: Multiple Partition - Single Disk, Host Primary Disk: /dev/nvme0n1).

                                  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

                                  T 1 Reply Last reply Dec 14, 2015, 12:40 AM Reply Quote 1
                                  • W
                                    Wayne Workman @george1421
                                    last edited by Wayne Workman Dec 12, 2015, 8:12 PM Dec 13, 2015, 2:11 AM

                                    @george1421 said:

                                    Also as new hardware is released we just need to update the drivers on the fog server, there is no reason to recapture the image.

                                    That’s pretty slick. But it requires a lot of knowledge - and I’ll admit you seem to have a lot more skills than I do, likely from your experience.

                                    For me - a 6TB drive is awful cheap, and I can update an existing image before lunch. 🙂 We have 22 images, one or two for each model. Keeping an image per model is simple to me, and deployment is more simple for both myself and co-workers. We can afford the drive-space and we have the time to make images.

                                    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!
                                    Daily Clean Installation Results:
                                    https://fogtesting.fogproject.us/
                                    FOG Reporting:
                                    https://fog-external-reporting-results.fogproject.us/

                                    G 1 Reply Last reply Dec 13, 2015, 3:28 PM Reply Quote 0
                                    • G
                                      george1421 Moderator @Wayne Workman
                                      last edited by Dec 13, 2015, 3:28 PM

                                      @Wayne-Workman said:

                                      For me - a 6TB drive is awful cheap, and I can update an existing image before lunch. 🙂 We have 22 images, one or two for each model. Keeping an image per model is simple to me, and deployment is more simple for both myself and co-workers. We can afford the drive-space and we have the time to make images.

                                      See the key/trick to this is that there is only one or two images for all systems. I don’t have to keep track of what the target computer is, because there is only one image. In our case we release a new golden image every quarter with all of the latest windows and application updates. If you have 22 images that would be almost impossible to do. In my situation I can tell you that a Dell 790 or 9020 have the same image on it as a e7404 or e7550 (sans the model specific driver). If there is an issue impacting a 790 I’m almost assured that it will impact all models, so I fix it one, I fix it for all (in theory).

                                      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
                                      • T
                                        Toby777 @Sebastian Roth
                                        last edited by Dec 14, 2015, 12:40 AM

                                        @Sebastian-Roth Thanks for that! I will download and test and let you know how it goes.

                                        1 Reply Last reply Reply Quote 0
                                        • T
                                          Toby777
                                          last edited by Dec 14, 2015, 2:01 AM

                                          I’ve set the image to Single Disk - Resizable and removed the custom entries in the Host’s Primary Disk field.

                                          It all looks good when recognizing the disk… however it appears to be stuck at the following…
                                          0_1450058060435_FullSizeRender (003).jpg

                                          I’ve tried repairing the MBR just in case but still seems to be stuck at this point when attempting to capture an image.

                                          1 Reply Last reply Reply Quote 0
                                          • 1
                                          • 2
                                          • 3
                                          • 1 / 3
                                          1 / 3
                                          • First post
                                            16/54
                                            Last post

                                          144

                                          Online

                                          12.0k

                                          Users

                                          17.3k

                                          Topics

                                          155.2k

                                          Posts
                                          Copyright © 2012-2024 FOG Project