• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. rurap
    3. Topics
    R
    • Profile
    • Following 0
    • Followers 0
    • Topics 4
    • Posts 27
    • Best 2
    • Controversial 0
    • Groups 0

    Topics created by rurap

    • R

      Unsolved Slow restoration of Windows 11 with FOG on Proxmox

      FOG Problems
      • • • rurap
      17
      0
      Votes
      17
      Posts
      985
      Views

      R

      Hello again, I conducted additional tests. In debug mode on the client, I ran network tests between the client and the fog server using the iperf server. The results do not indicate any network issues:

      iperf -c 192.168.25.11 ------------------------------------------------------------ Client connecting to 192.168.25.11, TCP port 5001 TCP window size: 16.0 KByte (default) ------------------------------------------------------------ [ 1] local 192.168.25.49 port 35204 connected with 192.168.25.11 port 5001 (icwnd/mss/irtt= 14/1448/924) [ ID] Interval Transfer Bandwidth [ 1] 0.00-10.02 sec 1.09 GBytes 938 Mbits/sec

      I also conducted disk write tests, and they also do not indicate any issues with the disk:

      bash dd if=/dev/zero of=/tmp/testfile bs=1M count=1000 status=progress 1000+0 records in 1000+0 records out 1048576000 bytes (1.0 GB, 1000 MiB) copied, 0.17635 s, 5.9 GB/s

      I also created an uncompressed image, and it also restored slowly, with transfer speeds below 1GB/s, rather around 500-600 MB/s, which results in even lower speeds.

      I changed the PXE environment boot file, set it to realtek.efi, and then changed it to snp.efi.The snp.efi visibly improved the FOS loading process, but the image restoration is still slow. Can the FOS system use a different driver during restoration than it does when operating in debug mode?

    • R

      Solved FOG on Proxmox use UEFI booting.

      FOG Problems
      • • • rurap
      3
      0
      Votes
      3
      Posts
      194
      Views

      R

      I had a problem when capturing an image when the computer was in legacy mode, when it was in UEFI mode everything worked. Then I reinstalled FOG on PROXMOX and I didn’t check Legacy mode anymore, but now I just tested imaging in legacy mode and everything works. That’s why I thought it was somehow dependent on whether fog was installed in UEFI/Legacy mode. Topic to close then.

    • R

      Unsolved Fog client: iPXe error code 420c6001, Broken Pipe

      FOG Problems
      • • • rurap
      1
      0
      Votes
      1
      Posts
      94
      Views

      No one has replied

    • R

      Solved Can not deploy using multicast - read image_hdr block_size error

      FOG Problems
      • • • rurap
      25
      0
      Votes
      25
      Posts
      2.4k
      Views

      R

      @george1421

      thank you george, the current switch is unmanaged, it’s a simple switch. There is not much in the specification of the switch, so I bet that switch is the problem.
      All PCs are the same and support WOL and on the old switch they all turn on, but I will check it, maybe one of the students has changed something in the BIOS

    • 1 / 1