Navigation

    FOG Project

    • Register
    • Login
    • Search
    • Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    1. Home
    2. Tags
    3. fog
    Log in to post

    • W

      Cannot exit IPXE menu and boot from hard drive?
      FOG Problems • fog linux ipxe fog 1.5.9 • • wmw509

      29
      0
      Votes
      29
      Posts
      113
      Views

      JJ Fullmer

      @wmw509 Disabling CSM makes sense. I’ve seen a lot of bioses that if CSM is enabled it only lets you use the legacy/bios pxe boot. I’ve had that disabled on all my hardware for so long I forgot it was a thing.

    • B

      SOLVED restoring gpt partition tables failed
      FOG Problems • fog error gpt imaging • • brakcounty

      3
      0
      Votes
      3
      Posts
      63
      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.

    • K

      SOLVED Captured Image is about the size of the Hard Drive
      Windows Problems • fog fog 1.3.3 • • KevFlwrs

      11
      0
      Votes
      11
      Posts
      310
      Views

      rogalskij

      I realize this post is a bit old, but I wanted to thank everyone for their suggestions and give our experience to back up what has been said in this topic already. We experienced an image that should have been about 120gb, but was showing in FOG as the full 500GB hard drive. After referencing this thread, it fixed the issue. The steps we took are below in order:

      Verified that the PC didn’t have a second drive or second large partition it was capturing
      Verified that bitlocker encryption was OFF using the command prompt command “manage-bde -off C:”
      Ran Disk Cleanup (to get rid of old unused files)
      Ran Tools > Check to scan for hard drive errors (may require reboot to fix)
      Ran Tools > Tools > Optimize and defagment
      Capture Image again

      Once we did those steps, the newly captured image only takes up the actual amount used on the hard drive.

    • F

      UNSOLVED FOG + Pfsense dhcp and vlan's: wrong subnetmask assigned
      FOG Problems • fog vlan pfsense subnetmask • • frederiekvictor

      2
      0
      Votes
      2
      Posts
      161
      Views

      F

      dhcp general settings on LAN:

      dhcp settings on other VLAN:

    • J

      FOG Management Console not accessible from other computers.
      FOG Problems • fog imaging centos 7 • • jjsplitter

      7
      0
      Votes
      7
      Posts
      734
      Views

      george1421

      @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.

    • S

      UNSOLVED macOS update broke iPXE
      Mac Problems • fog dhcp mac • • sysadminatelier

      23
      0
      Votes
      23
      Posts
      5990
      Views

      S

      Just cross-linking this here: https://forums.fogproject.org/topic/10615/ipxe-booting-possibly-broken-on-os-x-sierra-update

    • T

      SOLVED 1.3.5-RC-10 Capone problem: no os id passed (determineOS)
      FOG Problems • fog • • tommie

      9
      0
      Votes
      9
      Posts
      1112
      Views

      T

      @Tom-Elliott this fixed the issue!

      Thank you very much!

    • C

      SOLVED Debian + svn = error
      FOG Problems • fog • • craigcoulson

      9
      0
      Votes
      9
      Posts
      2178
      Views

      Jaymes Driver

      @craigcoulson said in Debian + svn = error:

      nevermind all - i rebuilt the server with only minimal packages and re-ran the svn install of Fog and it worked fine - go figure.

      Glad to hear you got it working

    • H

      SOLVED fog creates thousands of new empty images - after one deletion
      FOG Problems • fog database image mysql deletion • • Handtuch

      16
      0
      Votes
      16
      Posts
      2084
      Views

      H

      @Tom-Elliott And you can’t calculate all the hours you’ve saved for other admins.

    • F

      Wake On Lan With FOG on Debian
      FOG Problems • fog debian 8 wol wakeonlan • • fdrouard

      3
      0
      Votes
      3
      Posts
      1682
      Views

      Tom Elliott

      @fdrouard wol/wol.php path no longer exists.

    • arnaudrigole

      SOLVED Impossible to boot on PXE......
      FOG Problems • pxe fog dhcp debian 8 66 & 67 • • arnaudrigole

      41
      0
      Votes
      41
      Posts
      16549
      Views

      Wayne Workman

      @Sebastian-Roth said in Impossible to boot on PXE......:

      Wireshark filter bootp && tftp is great for this

      This has been in the wiki for some time, here:
      https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_TFTP

    • E

      SOLVED installing fog in full automatic mode
      Linux Problems • fog ansible answer automatic wizard • • erkax

      3
      0
      Votes
      3
      Posts
      1383
      Views

      E

      Ok thanks so i will write a expect script to install fog automaticly

    • ?

      SOLVED Binary symbols printed on login page
      FOG Problems • fog login 1.2.0 symbol • • A Former User

      4
      0
      Votes
      4
      Posts
      1326
      Views

      Tom Elliott

      I have solved this thread because as @Junkhacker stated, this is fixed in the dev builds as I am not using gzip compression on the page at all any more. If you are worried about the display, please update to Dev.

    • O

      SOLVED Inconsistent Image failure after Update 1.2.0
      FOG Problems • fog image issues updated inconsistent update 1.2.0 • • Omanimous

      6
      0
      Votes
      6
      Posts
      1621
      Views

      Wayne Workman

      @Omanimous said:

      Changed Option 67 in DHCP to undionly.kkpxe and it seems to be working fine.

      lol glad you got it working. I’m sure it will be fine.

      In the future, when you have network booting issues, the boot file should always be your first thing to inspect and think about

    • 1 / 1