• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. Tags
    3. imaging
    Log in to post
    • All categories
    • JJ FullmerJ

      Image Deploy Job doesn't show up in image history and shows as 2020+ years duration in imaging report

      Watching Ignoring Scheduled Pinned Locked Moved FOG Problems imaging report image-history
      7
      0 Votes
      7 Posts
      1k Views
      JJ FullmerJ

      @sebastian-roth I have not, it seems to have just been that one time.

    • S

      Deploying an Image with a 150GB Disk to 128GB Disk Failing Using Single Disk - Resizable Option

      Watching Ignoring Scheduled Pinned Locked Moved FOG Problems resizing imaging deployment
      2
      0 Votes
      2 Posts
      502 Views
      JJ FullmerJ

      That error says that partition 4 is too small. So it seems to think that the image is bigger than the spin 5’s drive.
      Looking at your image settings I’d recommend recapturing using partclone zstd at compression level 19. Probably won’t fix this problem, but might speed up your imaging while saving space on the server.

      I believe the when fog captures the image it shrinks it down to only what is actually in use, so your scenario should work. Personally, as a fail safe, I use a 80 GB virtual disk size for my images which never had an issue deploying to 120 GB drives. Granted after a while we found that users with 120 GB drives ran out of space just from windows maintenance (updates, caches, etc.), well that and the users never deleting an email in outlook.

      So if it’s feasible, maybe try recapturing the image with the virtual drive being smaller than anything in your environment. (80-120 GB perhaps).

    • D

      restoring gpt partition tables failed

      Watching Ignoring Scheduled Pinned Locked Moved Solved FOG Problems fog imaging gpt error
      3
      0 Votes
      3 Posts
      1k Views
      S

      @brakcounty To get some more information, can you please schedule a debug deploy task (same as you would do a normal deploy task but just before you hit the last button in the web UI there is a check box for debug). Boot up the client as usual and let it boot up. Then you need to hit ENTER twice to get to the shell. Now type fog and ENTER again to start and step through all the process till you hit the error. It will throw you back to the shell. Now type:

      sgdisk -gl /images/Win10Standard_GPT_EFI/d1.mbr /dev/sda

      It surely will fail. Take a picture of the screen and post that here.

    • J

      FOG Management Console not accessible from other computers.

      Watching Ignoring Scheduled Pinned Locked Moved FOG Problems fog imaging centos 7
      7
      0 Votes
      7 Posts
      3k Views
      george1421G

      @jjsplitter Since you still had firewalld enabled, did you remember to set selinux to permissive? If not you will have a sad time when you try to capture an image.

    • JJ FullmerJ

      Image Prep Script

      Watching Ignoring Scheduled Pinned Locked Moved Tutorials sysprep devcon imaging scripts automation
      19
      2 Votes
      19 Posts
      10k Views
      J

      @JJ-Fullmer this is awesome thank you for sharing your knowledge and scripts.

    • H

      V0.32 Storage Node Selection Process?

      Watching Ignoring Scheduled Pinned Locked Moved Solved FOG Problems node v0.32 imaging image issues
      6
      0 Votes
      6 Posts
      2k Views
      Wayne WorkmanW

      The OP’s problem can be solved with the location plugin in FOG 1.2.0, and FOG 1.3.0. Documentation on the plugin are linked below. Marking this thread as solved.
      https://wiki.fogproject.org/wiki/index.php?title=Location_Plugin

    • Scott BS

      can't image! image fails, pigz: skipping: stdin in not compressed...

      Watching Ignoring Scheduled Pinned Locked Moved Solved FOG Problems partclone imaging
      9
      0 Votes
      9 Posts
      6k Views
      Scott BS

      @Wayne-Workman

      I think so, if any new info or issues related comes up I’ll post.

    • J

      Simultaneous Hard Drive Imaging?

      Watching Ignoring Scheduled Pinned Locked Moved Solved FOG Problems hard drives multiple simultaneous imaging
      9
      0 Votes
      9 Posts
      3k Views
      S

      An image defined as “All disks” will upload from all disks and deploy to all disks… So, yes. You need to (re-)upload.

    • 1 / 1