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

Dell latitdue imageing problem

Scheduled Pinned Locked Moved Solved
FOG Problems
7
20
4.0k
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.
  • K
    KellyM
    last edited by KellyM Dec 2, 2015, 11:47 AM Dec 2, 2015, 5:27 PM

    Sebastian,
    I am experiencing the exact same thing as JTech.
    To answer your question, here is a screenshot of my image that had the same issue.0_1449076803209_upload-07664469-33e9-4745-8477-e78b020c8e92
    When I first loaded the image, the “Size on Client” was accurate. After attempting to download my image onto a new hard drive as a test, it then changes to what you see, after failing to actually reimage the new hard drive.

    For Reference, we are running FOG 1.2.0, no SVN, I believe a UEFI image, (though our machines are set to boot using legacy BIOS, so I am not sure how FOG sees it) and our OS is Ubuntu 14.04 LTS hosting FOG.

    Any help you can provide would be tremendous!

    T G 2 Replies Last reply Dec 2, 2015, 5:44 PM Reply Quote 0
    • T
      Tom Elliott @KellyM
      last edited by Dec 2, 2015, 5:44 PM

      @KellyM @Jtech This is because of the way the “size on client” gets calculated.

      The size on client get’s updated (just in case something changed) every time there’s an image task. This way things will be as accurate as possible. In order to do this, relatively simply, I zero out the original value. Due to this, if there’s a problem actually deploying the image, it would leave it in a “zeroed” out state.

      This does not mean there is a problem with the image or fog though. This is just a calculation, so this (itself) is NOT a problem to be concerned about.

      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

      G 1 Reply Last reply Dec 2, 2015, 5:59 PM Reply Quote 0
      • J
        JTech @george1421
        last edited by Dec 2, 2015, 5:54 PM

        @george1421

        it reads 1.2.0

        1 Reply Last reply Reply Quote 0
        • J
          JTech
          last edited by Dec 2, 2015, 5:56 PM

          Kelly m post with the picture is doing exactly what my system is doing. hope fully this clear some stuff up there are no error code in this process.

          G 1 Reply Last reply Dec 4, 2015, 3:14 PM Reply Quote 0
          • G
            george1421 Moderator @Tom Elliott
            last edited by george1421 Dec 2, 2015, 12:06 PM Dec 2, 2015, 5:59 PM

            @Tom-Elliott It appears that the OP is using the 1.2.0 stable image on pretty new hardware (2014). It was my understanding that 1.2.0 stable had issues with uefi image deployment. It would capture the image no problem but it would not lay it down correctly on the disk. It was my understanding that it was fixed in the mid 4000 range of the Git trunk. Is that accurate? For me I would recommend the OP upgrade to the latest SVN trunk, with the understanding it is still beta and pre 1.3.0 release (i.e. there may be a few bugs in the system, but they will get stamped out pretty quick).

            [edit] corrected a grammar error in my post [/edit]

            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 1 Reply Last reply Dec 2, 2015, 6:03 PM Reply Quote 0
            • T
              Tom Elliott @george1421
              last edited by Dec 2, 2015, 6:03 PM

              @george1421 I would recommend the same for both people having the problem.

              Highly recommend the users switch to trunk, though I can’t say for sure UEFI imaging will just “work” but hopefully it will do much more in a better sense than what you are seeing with 1.2.0.

              https://wiki.fogproject.org/wiki/index.php/Upgrade_to_trunk

              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 2
              • G
                george1421 Moderator @KellyM
                last edited by george1421 Dec 2, 2015, 12:07 PM Dec 2, 2015, 6:04 PM

                @KellyM said:

                For Reference, we are running FOG 1.2.0, no SVN, I believe a UEFI image, (though our machines are set to boot using legacy BIOS, so I am not sure how FOG sees it) and our OS is Ubuntu 14.04 LTS hosting FOG.

                UEFI vs Bios is a state of being. You either are or are not. On the Dells you CAN have UEFI enabled with the legacy roms turned on. In this case uefi emulates bios. For me its not clear either if fog sees a uefi system or an emulated bios device. There is a way to tell if you capture the initial bootp request from the client as its asks for an IP address. It will state the arch in object 60 or 93 (I believe). It will be 00000 for bios, 00006 for uefi 32 and 00007 for uefi x64. There are a few others but that is what I can remember.

                If you are using the 1.2.0 stable then you may have the same issue as the OP, hang tight.

                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 1
                • K
                  KellyM
                  last edited by Dec 3, 2015, 3:40 PM

                  Hey guys!

                  Just wanted to update you to let you know that my image is working just fine. Just like Tom said, The image appears to still be good. I was attempting to use an old hard drive off our shelves and I’m just gonna chalk this issue up to a bad hard drive. I was just able to successfully upload the image to a new Dell SSD (which is ultimately the type of hard drive we are wanting to use anyway).

                  I didn’t have to switch to trunk or anything and I was still able to successfully download the new image.

                  I hope JTech’s issue is as simple to solve as mine was.

                  Thanks for your help guys!!

                  1 Reply Last reply Reply Quote 1
                  • G
                    george1421 Moderator @JTech
                    last edited by Dec 4, 2015, 3:14 PM

                    @JTech Any update on this?

                    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
                    • J
                      JTech
                      last edited by Dec 9, 2015, 5:13 PM

                      we are still working on this and have made progress but it is still happening

                      1 Reply Last reply Reply Quote 0
                      • A
                        Atech
                        last edited by Dec 14, 2015, 9:56 PM

                        @george1421

                        I work with @JTech

                        Upgrading to the newest SVN Trunk version worked.

                        To answer your previous questions we were using:

                        1. 1.2.0
                        2. It was not a SVN Trunk version, simply the latest stable version
                        3. The image capture was Capture with Legacy boot (secure boot off)
                        4. FOG was installed on Ubuntu 14.04.3 LTS

                        The Functional/upgraded setup is:

                        1. 1.2.0
                        2. SVN 5688
                        3. Image captured with Legacy boot (secure boot off)
                        4. Fog is installed on Ubuntu 14.04.3 LTS
                        T 1 Reply Last reply Dec 15, 2015, 2:02 AM Reply Quote 0
                        • G
                          george1421 Moderator
                          last edited by Dec 14, 2015, 10:10 PM

                          @Atech Thank you for the feedback. So the ultimate solution was to update to the latest trunk version.

                          If that is accurate and the issue is resolved, can I mark this issue resolved?

                          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
                            Tom Elliott @Atech
                            last edited by Dec 15, 2015, 2:02 AM

                            @Atech can you tell us what the cloud version shows? It sounds like you got the latest which is not known as 1.2.0.

                            1.2.0 on 5678 is still 1.2.0. The tag hasn’t changed just the revision has. I’m just trying get the information more directly so new users and searches can find the info in this thread

                            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

                            W 1 Reply Last reply Dec 15, 2015, 2:08 AM Reply Quote 0
                            • W
                              Wayne Workman @Tom Elliott
                              last edited by Dec 15, 2015, 2:08 AM

                              @Tom-Elliott I thought SVN 2094 was the 1.2.0 release? I’m very confused right now.

                              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/

                              T 1 Reply Last reply Dec 15, 2015, 2:10 AM Reply Quote 0
                              • T
                                Tom Elliott @Wayne Workman
                                last edited by Dec 15, 2015, 2:10 AM

                                @Wayne-Workman you’re absolutely correct. 2094 is the svn rev at which we made the tag of 1.2.0. But if you’re pulling the tag instead of trunk, the rev will display the current rev of the repository, not the rev of the tagged released

                                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
                                • 1 / 1
                                1 / 1
                                • First post
                                  15/20
                                  Last post

                                153

                                Online

                                12.0k

                                Users

                                17.3k

                                Topics

                                155.2k

                                Posts
                                Copyright © 2012-2024 FOG Project