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

Kernel Panic issue

Scheduled Pinned Locked Moved Solved
FOG Problems
4
7
2.6k
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.
  • T
    the_duke
    last edited by Dec 1, 2015, 7:47 PM

    I know that I’ve seen a couple topics through google search about kernel panic, but nothing that really addressed or helped my scenario. I have imaged a lab of 33 computers all the same and same image. I have one that is giving me issues. It gets part of the way done and comes up with a bunch of code and t hen an end trace code. Under that I get kernel panic - not syncing: Fatal exception in interrupt Kernel offset: disabled. I have tried several times to image. One time it did finish, but then had a corrupt boot record. I then tried to do a fast wipe to try and fix that and then reimaged and now back to the kernel panic errors. Any ideas?

    1 Reply Last reply Reply Quote 0
    • T
      Tom Elliott
      last edited by Dec 1, 2015, 7:56 PM

      Only two idea come into my head. The HDD is bad, or the ram/motherboard is bad. Seeing as the panic happens during imaging, I’m leaning more towards HDD.

      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 1
      • W
        Wayne Workman
        last edited by Dec 1, 2015, 8:13 PM

        I could see an intermittently bad power supply causing this too, or even an intermittently bad motherboard.

        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!
        Daily Clean Installation Results:
        https://fogtesting.fogproject.us/
        FOG Reporting:
        https://fog-external-reporting-results.fogproject.us/

        1 Reply Last reply Reply Quote 0
        • G
          george1421 Moderator
          last edited by george1421 Dec 1, 2015, 2:16 PM Dec 1, 2015, 8:15 PM

          I would also suspect the hard drive. Using other image deployment tools, I’ve seen them get part of the way through the image deployment and then bomb out (like ghost). It is usually related to a bad hard drive. We would just swap a hard drive in the system from inventory and reimage. If the imaging process went through then we would tag and discard the old drive. Based on my experience 4-5 years on a consumer hard drive is typically where we start to see system errors.

          If that system is a normal business system and is 4-5 years old, that would also increase the chances the hard drive has some bad sectors.

          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
          • T
            the_duke
            last edited by Dec 1, 2015, 8:20 PM

            I went and did a system diagnostic in my bios after you said this and it was my memory. I removed it from the slot that it was in and placed it into another slot on the MB and everything seems good to go now. Thanks for the tip.

            1 Reply Last reply Reply Quote 1
            • G
              george1421 Moderator
              last edited by Dec 1, 2015, 8:29 PM

              Just trying to tidy up, can we marked this as solved?

              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
              • T
                Tom Elliott
                last edited by Dec 2, 2015, 2:26 PM

                I went ahead and solved this. First, the issue wasn’t something FOG was, or wasn’t, doing. Second, the issue (as I understood it) was the host memory.

                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
                • 1 / 1
                1 / 1
                • First post
                  3/7
                  Last post

                300

                Online

                12.0k

                Users

                17.3k

                Topics

                155.2k

                Posts
                Copyright © 2012-2024 FOG Project