• Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
  • Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login

Problematic Device - HP EliteDesk 705 G3 Mini - tg3_stop_block timed out

Scheduled Pinned Locked Moved Unsolved
Hardware Compatibility
2
6
2.2k
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • J
    joaoguedes
    last edited by joaoguedes May 25, 2017, 6:10 AM May 25, 2017, 12:09 PM

    Server
    • FOG Versions: 1.2.0 e 1.4.0 both
    • OS: Ubuntu 14.04 e 16.04 both

    I try version 1.2.0 on Ubuntu 14.04 and version 1.4.0 on Ubuntu 16.04.

    Client
    • Service Version:
    • OS:
    Description

    Model: HP EliteDesk 705 G3 Mini

    Dear friend,

    I had been facing troubles to connect this machine to the Fog Server. At the begining, the process occurs normally, however, the connection of the machine to the server is interrupted with this message: tg3_stop_block timed out.

    I’ve been researching and as far as I understand, Fog is experiencing compatibility issues with tg3 NIC network cards.

    Is there a thread for solving this specific problem for the next version? Or is there a manual solution to make the server compatible with this hardware? The problem occurs if I install de server on Debian or other Linux OSs?

    1 Reply Last reply Reply Quote 0
    • T
      Tom Elliott
      last edited by May 25, 2017, 12:18 PM

      I don’t know what you mean. Kernel problems, such as described here: https://forums.fogproject.org/topic/9976/hp-elitedesk-705-g2-mini/12

      Aren’t handled by FOG developers. In a perfect world, everything would just work, but this is far from a perfect world unfortunately.

      Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

      Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

      Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

      1 Reply Last reply Reply Quote 0
      • J
        joaoguedes
        last edited by May 25, 2017, 12:26 PM

        Apparently yes,

        I just wanted to point out that the same problem is occurring with this other model. I’m not with the machine now, but i can post more information later.

        What do you mean “Are not handled by FOG developers.”? Is not this a problem with their software? Or are they just not solving it right now?

        T 1 Reply Last reply May 25, 2017, 12:29 PM Reply Quote 0
        • T
          Tom Elliott @joaoguedes
          last edited by May 25, 2017, 12:29 PM

          @joaoguedes The kernel is not written by fog developers. The kernel is written by the linux kernel developers.

          Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

          Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

          Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

          1 Reply Last reply Reply Quote 0
          • J
            joaoguedes
            last edited by Jun 2, 2017, 6:48 PM

            i figured out a way to clone the machines, but I don’t know exactly what the problem is, not even the solution. When I used a new network cable connected to a 1000Mbps port, the cloning process goes perfectly, however when I use a 100Mbps port on the same switch, the error always occurs. I had to use my single gigabit port to clone all machines, 1-by-1.

            1 Reply Last reply Reply Quote 0
            • J
              joaoguedes
              last edited by Jun 2, 2017, 6:52 PM

              I reduced the server’s port speed from 1000Mbps to 100Mbps, forcing it to work at 100Mbps, but the gigabit port is the only one that keeps running.

              1 Reply Last reply Reply Quote 0
              • 1 / 1
              • First post
                Last post

              171

              Online

              12.0k

              Users

              17.3k

              Topics

              155.2k

              Posts
              Copyright © 2012-2024 FOG Project