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

    Cannot deploy (download) image in 1.2.0

    Scheduled Pinned Locked Moved Unsolved
    FOG Problems
    3
    20
    4.9k
    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.
    • Wayne WorkmanW
      Wayne Workman @netman86
      last edited by

      @netman86 Would you consider upgrading to FOG Trunk? Your issue might be resolved by this alone.

      1 Reply Last reply Reply Quote 0
      • N
        netman86
        last edited by

        I can’t say I’ve got a compelling reason not to, assuming it’s a fairly pain free process and the TRUNK version is considered fairly stable.

        This FOG machine was built just for this job (I’ve always wanted to try it out) so I don’t have too much to lose if it goes awry.

        1 Reply Last reply Reply Quote 0
        • N
          netman86
          last edited by

          Since I see the d1p5 has data in the image, I’m going to upgrade to trunk and try to re-deploy to another laptop- assuming it lets me deploy an image made with 1.2.0

          1 Reply Last reply Reply Quote 0
          • N
            netman86
            last edited by

            So after spending a few hours fixing everything after attempting to upgrade to trunk, I’m running trunk.

            I tried to deploy the same image to another laptop and had the same issue I had in 1.2.0.

            I then tried to create a NEW image from the source, and that appeared to go fine- but it overwrote my old source instead of creating a new one as I had specified (Odd issues with changing options in host management not sticking)

            For whatever reason, the image didn’t work. It went through and did a partition copy, and wrote new files to /images/source2, but under image management that source shows up as 0.00B when it’s about 50G on disk.

            I went and changed it to source3 again and created an upload job, which failed- I had to manually create a Source3 directory in /images/ for it to start the process, which tells me that maybe something is screwy with permissions for /images- but everything appears to be 777 so I can’t fathom what it could be.

            Creating a new source3 image now just to see what happens…

            1 Reply Last reply Reply Quote 0
            • N
              netman86
              last edited by

              New image appears to have created correctly, and shows up in image from the web UI with a size- but the restore back to another box had the same results.

              1 Reply Last reply Reply Quote 0
              • N
                netman86
                last edited by

                update:

                after the failed deployment, the size listed under image management changed to 0.00iB. Odd.

                Wayne WorkmanW 2 Replies Last reply Reply Quote 0
                • Wayne WorkmanW
                  Wayne Workman @netman86
                  last edited by

                  This post is deleted!
                  1 Reply Last reply Reply Quote 0
                  • Wayne WorkmanW
                    Wayne Workman @netman86
                    last edited by Wayne Workman

                    @netman86 said:

                    update:

                    after the failed deployment, the size listed under image management changed to 0.00iB. Odd.

                    That’s a minor bug that is non-impacting. I have a few images that list as 0 in size on client, but they work just fine.

                    Why do you have 5 partitions?

                    1 Reply Last reply Reply Quote 0
                    • N
                      netman86
                      last edited by

                      1. the windows 100mb boot partition
                      2. C drive
                      3. D drive (required for this purpose)
                      4. extended for 5
                      5. backup partition with image of C for on the road re-imaging (also required…)

                      I might be able to get away with keeping the image on partition 3 as a file, but TPTB want it on its own partition.

                      1 Reply Last reply Reply Quote 0
                      • N
                        netman86
                        last edited by

                        I just spoke to the guy wanting these and the requirement has changed- I also need a small (100mb) partition for the lab, so that’ll be six partitions in all.
                        I’m testing a RAW image clone right now, I can’t think of a reason it wouldn’t work if FOG manages to initiate the copy on the destination…

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

                        139

                        Online

                        12.1k

                        Users

                        17.3k

                        Topics

                        155.3k

                        Posts
                        Copyright © 2012-2024 FOG Project