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

Chainloading failure: Toshiba Tecra C40-C UEFI & Samsung SSD MZNLF128HCHP-000

Scheduled Pinned Locked Moved
FOG Problems
5
88
37.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.
  • M
    mabarton
    last edited by mabarton Jul 2, 2016, 4:20 PM Jul 2, 2016, 12:15 AM

    I am attempting to image 100 new Toshiba Tecra C40-C computers running Windows 10.

    They have UEFI based systems and SSDs. The SSD is an M.2 Samsung MZNLF128HCHP-00.

    I am able to iPXE and get to the Fog menu and register the computers. However, they will not boot back to the SSD but says “chainloading failure.”

    Also, I am able to schedule a task and begin uploading an image but that fails at the end, too.

    I began using Fog in September and have successfully imaged many machines in legacy mode or BIOS with no trouble but this is a real problem.

    I need to figure this out because we need all of these computers by August 1st.

    Thank you for your help,
    Melissa

    M 3 Replies Last reply Jul 2, 2016, 1:45 AM Reply Quote 0
    • G
      george1421 Moderator
      last edited by george1421 Jul 1, 2016, 6:19 PM Jul 2, 2016, 12:18 AM

      I guess the first question is what version of fog are you using? (hint: look about the cloud on the FOG management page).

      Are these traditional ssd (sata) drives or M.2 drives?

      Will the images machines boot if you take PXE out of the boot order?

      [edit] Slightly off topic, since you now have a mix of uefi and bios (legacy) systems if your dhcp server is linux or Windows 2012 you can make the dhcp server issue the right boot file depending on the target 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!

      M 3 Replies Last reply Jul 2, 2016, 12:22 AM Reply Quote 0
      • M
        mabarton
        last edited by mabarton Jul 1, 2016, 6:22 PM Jul 2, 2016, 12:19 AM

        This post is deleted!
        1 Reply Last reply Reply Quote 0
        • G
          george1421 Moderator
          last edited by george1421 Jul 1, 2016, 6:24 PM Jul 2, 2016, 12:21 AM

          A quick look up of the MZNLF128HCHP-00 drive, its a M.2 device. You will need to be on the trunk build post (git) r6500 (I think).

          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
          • M
            mabarton @george1421
            last edited by Jul 2, 2016, 12:22 AM

            @george1421 1.2.0 upgraded to trunk on Ubuntu 14.04

            G 1 Reply Last reply Jul 2, 2016, 12:22 AM Reply Quote 0
            • G
              george1421 Moderator @mabarton
              last edited by george1421 Jul 1, 2016, 6:27 PM Jul 2, 2016, 12:22 AM

              @mabarton said in Chainloading failure: Toshiba Tecra C40-C UEFI & Samsung SSD MZNLF128HCHP-000:

              @george1421 1.2.0 upgraded to trunk on Ubuntu 14.04

              OK, what release? (numbers by cloud on web gui page)

              In regards to the chain load failure, you may need to update the host record for these specific computers. You will need to change the uefi exit mode field. You will have to test each of the uefi exit modes until you find the one that works for you.

              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!

              M 1 Reply Last reply Jul 2, 2016, 12:31 AM Reply Quote 0
              • M
                mabarton @george1421
                last edited by Jul 2, 2016, 12:28 AM

                @george1421

                They are M.2

                The machine boots fine when not in PXE

                1 Reply Last reply Reply Quote 0
                • M
                  mabarton @george1421
                  last edited by Jul 2, 2016, 12:31 AM

                  @george1421 I have tested each mode some give me the chainloading issue and some give me no valid OS.

                  Running Version 8291
                  bzImage Version 4.6.2
                  bzImage32 4.6.2

                  G 1 Reply Last reply Jul 2, 2016, 12:32 AM Reply Quote 0
                  • G
                    george1421 Moderator @mabarton
                    last edited by Jul 2, 2016, 12:32 AM

                    @mabarton Just for clarity these are uefi systems, so you adjusted the uefi exit mode in the host record? The bios exit modes won’t apply here.

                    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!

                    M 1 Reply Last reply Jul 2, 2016, 2:14 AM Reply Quote 0
                    • M
                      mabarton @mabarton
                      last edited by mabarton Jul 1, 2016, 8:15 PM Jul 2, 2016, 1:45 AM

                      This post is deleted!
                      1 Reply Last reply Reply Quote 0
                      • M
                        mabarton
                        last edited by mabarton Jul 1, 2016, 8:16 PM Jul 2, 2016, 1:49 AM

                        The PXE, Fog Menu (FOS?), and Chainloading failure.

                        0_1467423993262_IMG_3461.PNG0_1467424044630_IMG_3463.PNG
                        0_1467424063736_FullSizeRender.jpg

                        1 Reply Last reply Reply Quote 0
                        • G
                          george1421 Moderator
                          last edited by george1421 Jul 1, 2016, 8:12 PM Jul 2, 2016, 2:07 AM

                          @Developers I had a lengthy chat session with the OP. To summarize the situation here is where it is.

                          The OP has a 100 (first in the environment) uefi system, with gpt disk structure on a M.2 ssd drive. The OP is trying to capture a Windows 10 reference image using a current release of the FOG trunk. The uefi target system boots into FOS and begins to copy the image off the ssd drive, but it fails near the end of the image capture (the OP has agreed to snap a picture of the actual error with a mobile phone and post the image to this thread). The reference image the OP is trying to capture is a Factory installed image that has been customized for the OPs environment. FWIW this image also contains a factory installed restore partition.

                          Another part of the puzzle here is that FOG menu will not exit properly and boot the system. If the OP changes the firmware so that the target boots directly to the hard drive the device boots OK. The OP has tested all FOG UEFI exit modes with no success. None yield a system that boots.

                          At this point the OP has already tried most things before I suggested them. When I exited the chat the OP was attempting to clone the disk with clonezilla to see if its a partclone issue or something else with fog.

                          At this point I’m out of ideas on how to verify the disk structure without damaging the content of the reference image. I’m suspecting there is a corrupted partition table or that factory restore partition is gumming up the capture (wouldn’t be the first time I saw that issue).

                          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
                          • M
                            mabarton @george1421
                            last edited by Jul 2, 2016, 2:08 AM

                            @george1421
                            I use DHCP from the fog setup. I have an isolated network.

                            G 1 Reply Last reply Jul 2, 2016, 2:09 AM Reply Quote 0
                            • G
                              george1421 Moderator @mabarton
                              last edited by george1421 Jul 1, 2016, 8:14 PM Jul 2, 2016, 2:09 AM

                              @mabarton Just for clarity, the picture you posted appears to be a pxe boot issue, where did that come from? We’d like to see a screen shot of the image capture error.

                              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
                              • M
                                mabarton @george1421
                                last edited by Jul 2, 2016, 2:14 AM

                                @george1421
                                The three pics are the order in which it fails.

                                1. PXE booting
                                  2)FOG menu
                                  3)Chainloading failure (when leaving the Fog menu after the 3 sec.)

                                The other picture with mostly a black screen is the Raw image failure at the end of the cloning process.

                                I will submit more pics of the different exits and what they do.

                                G 1 Reply Last reply Jul 2, 2016, 2:16 AM Reply Quote 0
                                • G
                                  george1421 Moderator @mabarton
                                  last edited by Jul 2, 2016, 2:16 AM

                                  @mabarton Lets not focus on the exit modes right now. I think they are all related. But lets focus on image capture. Because if you can’t capture the image, the exit mode issue is a moot point. A clear image of the capture error will give the devs something to reference.

                                  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!

                                  T M 3 Replies Last reply Jul 2, 2016, 2:18 AM Reply Quote 0
                                  • T
                                    Tom Elliott @george1421
                                    last edited by Jul 2, 2016, 2:18 AM

                                    @george1421 the pic shows ftp issues for image capture

                                    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! Get in contact with me (chat bubble in the top right corner) if you want to join in.

                                    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
                                      Tom Elliott @george1421
                                      last edited by Jul 2, 2016, 2:19 AM

                                      @george1421 uefi exit should be handled by rEFInd type but it needs a Config file for it as well.

                                      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! Get in contact with me (chat bubble in the top right corner) if you want to join in.

                                      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 Jul 2, 2016, 2:20 AM Reply Quote 0
                                      • M
                                        mabarton @george1421
                                        last edited by Jul 2, 2016, 2:19 AM

                                        0_1467425947375_IMG_3450.JPG
                                        This is when I attempted a Raw image. At the end this came up

                                        1 Reply Last reply Reply Quote 0
                                        • W
                                          Wayne Workman
                                          last edited by Jul 2, 2016, 2:20 AM

                                          Looking at the picture that has FTP related messages, the upload script can authenticate but cannot enter into the ftp root directory - which is /home/fog. This is exactly what the error says in fact.

                                          Troubleshooting should focus on this directory. Does it exist? What are the permissions?

                                          Please post the output of this command:
                                          ls -lahRt /home/fog

                                          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/

                                          1 Reply Last reply Reply Quote 0
                                          • 1
                                          • 2
                                          • 3
                                          • 4
                                          • 5
                                          • 1 / 5
                                          1 / 5
                                          • First post
                                            16/88
                                            Last post

                                          233

                                          Online

                                          12.0k

                                          Users

                                          17.3k

                                          Topics

                                          155.2k

                                          Posts
                                          Copyright © 2012-2024 FOG Project