• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. Jarl2.0
    3. Topics
    J
    • Profile
    • Following 0
    • Followers 0
    • Topics 5
    • Posts 23
    • Groups 0

    Topics

    • J

      Error 'Could not open inode 'XXXXXX" through the library'

      Watching Ignoring Scheduled Pinned Locked Moved Solved FOG Problems
      35
      0 Votes
      35 Posts
      13k Views
      T

      Hi,

      Same problem as Scoude here with Fog 1.5.9 on Debian 10.
      I “defraged” (it’s a ssd), desactivated Fastboot, hibernate off, chkdsk…
      Nothing fixed the problem.

      Any idea ?

      Thanks

    • J

      FOG imaging blankspace

      Watching Ignoring Scheduled Pinned Locked Moved Solved FOG Problems
      5
      0 Votes
      5 Posts
      1k Views
      S

      @Jarl2-0 Thanks for letting us know. Marking this solved.

    • J

      Errors while PXE booting

      Watching Ignoring Scheduled Pinned Locked Moved FOG Problems
      2
      0 Votes
      2 Posts
      725 Views
      george1421G

      These errors are not related to any updates that happened to FOG, ubuntu. These are hardware errors with the target computer. The ACPI errors are a bit of a warning and can be ignored, if they bug you too much you can disable acpi on this target computer by placing acpi=off in the host’s kernel parameters.

      The USB ones are a bit more confusing. It appears you have a malfunctioning USB device connected to this target system? Is the firmware up to date on this target computer?

    • J

      Unable to reach Fog Management website

      Watching Ignoring Scheduled Pinned Locked Moved General Problems
      14
      0 Votes
      14 Posts
      4k Views
      J

      @sebastian-roth That worked I have no idea how those rules got loaded onto the firewall however…

    • J

      Image Size

      Watching Ignoring Scheduled Pinned Locked Moved General
      12
      0 Votes
      12 Posts
      2k Views
      george1421G

      @Jarl2.0 If you are using zStd capture speed will be much slower than deploy speed. That is the nature of the compression tool. With gzip you don’t get as good of compression ratio or deploy speeds, but capture and deploy are similar in speed. For Zstd 11-13 is probably a pretty good range to stay in.

    • 1 / 1