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

    Deploy fails - detected stalls on CPUs/tasks

    Scheduled Pinned Locked Moved Solved
    FOG Problems
    2
    5
    1.3k
    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.
    • mosesM
      moses
      last edited by moses

      Server
      • FOG Version: 1.3.5
      • OS: Centos 7 x64
      Client
      • Service Version: N/A
      • OS: Windows 7
      Description

      I did a quick registration on a HP Z400 workstation, and that worked fine, but when I attempted to deploy an image I got the following:

      Screenshot1

      So I then stopped the task, deleted the host, and did a full registration instead. The registration worked okay, and the deploy task got a little further this time, but then it halted here:

      Screenshot2

      Any idea what’s going on? I’m using undionly.kpxe, if that’s relevant.

      1 Reply Last reply Reply Quote 0
      • mosesM
        moses @george1421
        last edited by moses

        @george1421 Well, acpi=off in the kernel options did the trick. Must be one of those finicky models. Thanks!

        george1421G 1 Reply Last reply Reply Quote 0
        • george1421G
          george1421 Moderator
          last edited by

          So this appears to be a legacy (bios) system?

          If you register this device (manual or auto) once that is done, add this option to the kernel parameters for this host acpi=off

          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!

          mosesM 2 Replies Last reply Reply Quote 1
          • mosesM
            moses @george1421
            last edited by

            @george1421 It’s BIOS, yes, but I’ve never had to add that argument for any other computer using BIOS. Regardless, I’ll give it a whirl and report back the results.

            1 Reply Last reply Reply Quote 0
            • mosesM
              moses @george1421
              last edited by moses

              @george1421 Well, acpi=off in the kernel options did the trick. Must be one of those finicky models. Thanks!

              george1421G 1 Reply Last reply Reply Quote 0
              • george1421G
                george1421 Moderator @moses
                last edited by

                @moses well its more of a band-aid than a solution. I’m glad you got passed this issue. From what I’ve found this is a in kernel issue with some hardware that dates back to 2009. You might want to see if there is a firmware update for this hardware, or, you just might want to take this kernel parameter as a WIN and move on.

                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!

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

                308

                Online

                12.0k

                Users

                17.3k

                Topics

                155.2k

                Posts
                Copyright © 2012-2024 FOG Project