• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. dmcadams
    3. Topics
    D
    • Profile
    • Following 0
    • Followers 0
    • Topics 3
    • Posts 14
    • Best 1
    • Controversial 0
    • Groups 0

    Topics created by dmcadams

    • D

      Multicast image is pushed, but it does not "finish/finalize"

      FOG Problems
      • • • dmcadams
      6
      0
      Votes
      6
      Posts
      588
      Views

      D

      @sebastian-roth
      I’ve only been able to test this in one environment and only with 2 PCs. It did work in that particular test. In a couple of weeks, we are going to have an opportunity to hit a good number of PC’s in another environment where it previously failed, so we’ll have more data then. So far so good though! Thank you much!

    • D

      Multicast session is not starting

      FOG Problems
      • • • dmcadams
      10
      0
      Votes
      10
      Posts
      1.3k
      Views

      S

      @dmcadams said in Multicast session is not starting:

      These client machines also have NVMe drives, so on the receiver side, instead of “/dev/sda1” should we use “/dev/nvme0”?

      Yes, for the first partition use /dev/nvme0n1p1

    • D

      Multiple I/O Errors during imaging

      FOG Problems
      • • • dmcadams
      10
      0
      Votes
      10
      Posts
      747
      Views

      S

      @dmcadams Sorry for the late reply but I’ve had too much on my table this week and couldn’t find the time to think through this again.

      Great you tested different kernels and found one working fine. Short answer is, name this kernel binary different to the default Kernel naming theme, e.g. bzImage-4.19.6 or whatever suites you and set this name as Host Kernel in each host’s settings having this issue. Make sure you update the general kernel to the latest via FOG settings again so all your other machines will use the new one.

      The longer answer is: With that new information I don’t think it’s a temperature issue really. Sounds like this kicks in with a certain Kernel version probably because it has some new driver or feature added that is causing this. Often some new features (e.g. NVMe optimization or so) are implemented differently by various vendors. While drives from vendor A might go with it just fine some other vendor uses a different code in its firmware causing a problem in the Linux kernel.

      If you are really keen we can go and test each kernel version one by one to find what’s causing it and possibly find a solution (special kernel parameter or a patch for the code). Though this will need work and time. I can give you many hints and instructions but it’s your call to work on it. Compiling kernel after kernel (very easy to do) and testing each while keeping close track of the results to find it. It really needs determination to stick with it. But you will learn a lot I am sure.

    • 1 / 1