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

    Deployment issues on some Dell 740s and 520s

    Scheduled Pinned Locked Moved
    FOG Problems
    4
    14
    4.2k
    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.
    • neodawgN
      neodawg
      last edited by

      As a temp patch by I am going to upload the image to a .32 server and move it to my production server as a partimage image. This should work. Will post back if doesnt.

      EDIT
      Didnt work, really thought this should have. Going to have to run 2 fog servers while i push the images back out to the problem computers.

      would be really nice if i could upload using PartImage on fog 1+.

      1 Reply Last reply Reply Quote 0
      • neodawgN
        neodawg
        last edited by

        For those wonder what error i get trying to use PartImage. Here is a screen shot.[IMG]http://ruppnet.net/fog740partimg.jpg[/IMG]

        1 Reply Last reply Reply Quote 0
        • Tom ElliottT
          Tom Elliott
          last edited by

          This sounds like an issue with the image and the partition layouts.

          Your partition layout on the “new” system’s hard drives is different than what is expected.

          When you created the “resize” image, how did you resize the original disk?

          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
          • neodawgN
            neodawg
            last edited by

            [quote=“Tom Elliott, post: 36144, member: 7271”]This sounds like an issue with the image and the partition layouts.

            Your partition layout on the “new” system’s hard drives is different than what is expected.

            When you created the “resize” image, how did you resize the original disk?[/quote]

            Not 100% sure I follow, but here is what i did.

            Deploy image to working 740 from production server. ( single part/single disk image)
            switch over to my new .32 server
            register the host
            upload as single disk/single part
            copy image to production server
            switch back to production server
            schedule image deploy from new file (i did chmod on the permissions for the file so it matches the rest in the /images directory)
            didnt work, tried debug and thats where the image came from.

            Do you have any thoughts on the original post?
            in my testing it seems that no matter the kernel or bios version it can always see the network and the hard drive, it appears to be directly an issue with partclone.

            Should pull the hard drive from a not working machine and try to image that drive in a working machine?

            Thanks,

            1 Reply Last reply Reply Quote 0
            • JunkhackerJ
              Junkhacker Developer
              last edited by

              did you set the format to partimage on the image profile?

              signature:
              Junkhacker
              We are here to help you. If you are unresponsive to our questions, don't expect us to be responsive to yours.

              1 Reply Last reply Reply Quote 0
              • neodawgN
                neodawg
                last edited by

                [quote=“Junkhacker, post: 36178, member: 21583”]did you set the format to partimage on the image profile?[/quote]

                Yes I did, forgot to mention that in the post before. I did this on the production server I pushed from

                1 Reply Last reply Reply Quote 0
                • neodawgN
                  neodawg
                  last edited by

                  Is it possible that the issue is that the computer the image came from has a larger hard drive then the destination computer? I thought the single partition option was supposed to support this, pending that your image isnt larger than the disk. This is in thought to the original problem.

                  1 Reply Last reply Reply Quote 0
                  • neodawgN
                    neodawg
                    last edited by

                    Well, I tried to resize the partition before uploading to a small size and then try deploying it, still didnt work.

                    1 Reply Last reply Reply Quote 0
                    • Tom ElliottT
                      Tom Elliott
                      last edited by

                      If the smallest size the image can be (windows 7 defaults base install sysprepped and all is 8.9GB) is larger than the disk you’re trying to put the image on, it will not work.

                      If you resize the partition before FOG get’s to resize it, the partition is marked that it’s already shrunk and fog Cannot do anything with it. So let’s say you make a partition size of 40GB as the shrunken state, and you try putting the image on an exactly the same size, in 1.2.0 I made the partition size to 99% of the full size of the partition, so you’d end up with around a 39GB partition which is smaller than 40GB and the image would not deploy. I have since found and corrected this issue in SVN. That said, with the release of 1.0.0 we went with partclone as your primary upload method. We are still supporting partimage for legacy compatibility reasons. If you’d be willing you can send me your gmail address in a pm and I’ll see if I can help fix the image for you.

                      Hopefully this helps you out too. If you’re willing, try out SVN and see if your image starts working. There’s always a chance it won’t work and you’re left in a state no different than you currently are. However, there’s also the chance that this may help you out. You’ll also get to see some of the work we’ve been putting forward for 1.3.0 or whatever it’s labeled when we release.

                      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
                      • neodawgN
                        neodawg
                        last edited by

                        [quote=“Tom Elliott, post: 36348, member: 7271”]If the smallest size the image can be (windows 7 defaults base install sysprepped and all is 8.9GB) is larger than the disk you’re trying to put the image on, it will not work.

                        If you resize the partition before FOG get’s to resize it, the partition is marked that it’s already shrunk and fog Cannot do anything with it. So let’s say you make a partition size of 40GB as the shrunken state, and you try putting the image on an exactly the same size, in 1.2.0 I made the partition size to 99% of the full size of the partition, so you’d end up with around a 39GB partition which is smaller than 40GB and the image would not deploy. I have since found and corrected this issue in SVN. That said, with the release of 1.0.0 we went with partclone as your primary upload method. We are still supporting partimage for legacy compatibility reasons. If you’d be willing you can send me your gmail address in a pm and I’ll see if I can help fix the image for you.

                        Hopefully this helps you out too. If you’re willing, try out SVN and see if your image starts working. There’s always a chance it won’t work and you’re left in a state no different than you currently are. However, there’s also the chance that this may help you out. You’ll also get to see some of the work we’ve been putting forward for 1.3.0 or whatever it’s labeled when we release.[/quote]

                        PM Sent

                        1 Reply Last reply Reply Quote 0
                        • neodawgN
                          neodawg
                          last edited by

                          For anyone that is following this thread, this issue has been resolved and should be included in the 1.3.0 release.

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

                          153

                          Online

                          12.0k

                          Users

                          17.3k

                          Topics

                          155.2k

                          Posts
                          Copyright © 2012-2024 FOG Project