• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. Tauric
    3. Topics
    T
    • Profile
    • Following 0
    • Followers 0
    • Topics 5
    • Posts 15
    • Best 0
    • Controversial 0
    • Groups 0

    Topics created by Tauric

    • T

      Unsolved Can't capture after updating

      FOG Problems
      • • • Tauric
      6
      0
      Votes
      6
      Posts
      524
      Views

      Tom ElliottT

      @Tauric I don’t think any amount of rollback is necessary, but you’re more than welcome to. Pretty sure there weren’t any schema updates or major component changes between 1.5.10 and 1.5.10.34

      that said, this looks more like a problem with the kernel, not a problem with FOG and its ability to capture/deploy images.

      You could download the kernels from the FOG GUI Kernel Updates

    • T

      Can't deploy/register/debug with parallels

      Hardware Compatibility
      • • • Tauric
      6
      0
      Votes
      6
      Posts
      782
      Views

      george1421G

      @Tauric said in Can't deploy/register/debug with parallels:

      Also for the initrd=init.xz

      That is precisely why you should not trust my memory. For a little clarity this is what boot.php file creates for the auto reg function.

      kernel bzImage loglevel=7 initrd=init.xz root=/dev/ram0 rw ramdisk_size=275000 web=http://192.168.50.23/fog/ consoleblank=0 rootfstype=ext4 storage=192.168.50.23:/images/ storageip=192.168.50.23 nvme_core.default_ps_max_latency_us=0 loglevel=7 mode=autoreg imgfetch init.xz

      So the command at the IPXE> prompt would be
      initrd init.xz or imgfetch init.xz There is no equals = sign in the command.

      And just to tag along with what Tom said, when I first read your post I was confused if your target computers are ARM or Intel? You menitoned Intel iMac, and then a little later ARM. But I took the ARM reference as it should work because its not ARM based.

      OK by setting the logging to 7 and you don’t see a bunch of text on the screen then the kernel (bzImage) is not starting up. So at the IPXE prompt I would try kernel bzImage to see if it is really transferring it. The boot command at the IPXE> should try to run the kernel.

    • T

      Unsolved Deploying to paralells, cant ping fog server

      Mac Problems
      • • • Tauric
      1
      0
      Votes
      1
      Posts
      194
      Views

      No one has replied

    • T

      Solved "Image size: ON CLIENT" shows the total size of the captured disk

      Bug Reports
      • • • Tauric
      3
      0
      Votes
      3
      Posts
      584
      Views

      S

      @Tauric From the pictures we see that FOG recognized the filesystem as NTFS and should be able to resize it. It’s still strange the size was larger. Good you got this fixed by reinstalling the master to capture from. No idea what could have been wrong with the other one.

    • T

      Solved TFTP Timeout

      FOG Problems
      • • • Tauric
      10
      0
      Votes
      10
      Posts
      1.6k
      Views

      george1421G

      @Tauric said in TFTP Timeout:

      (and took less than 10 minutes lol)

      Well I was taking into account for slow speeds between keyboard and chair…
      Glad you have it worked out. DNSMASQ should work flawlessly in your environment.

    • 1 / 1