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

SANBOOT Hang

Scheduled Pinned Locked Moved
FOG Problems
5
16
5.1k
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
    JeffT
    last edited by May 29, 2014, 7:02 PM

    I upgraded our Fog server from .32 to 1.0.1 a few days ago. For the most part everything went smoothly. The biggest issue is that our HP All-in-one units go through the PXE menu with no job scheduled, default to the local hard disk, and then hangs at “SANBOOT 0x80”. As far as I know all of our other machine models work fine. I also tried changing the server setting from sanboot to exit, but it doesn’t stay that way.

    Any thoughts?

    Thanks

    [ATTACH=full]859[/ATTACH]

    [url=“/_imported_xf_attachments/0/859_sanboot0x80.jpg?:”]sanboot0x80.jpg[/url]

    1 Reply Last reply Reply Quote 0
    • W
      Wolfbane8653 Developer
      last edited by May 29, 2014, 7:06 PM

      Change your Fog Settings–> Fog Boot Settings --> Fog_Boot_Exit_Type from SANBOOT to [B]EXIT[/B]

      Then try again.

      1 Reply Last reply Reply Quote 0
      • J
        JeffT
        last edited by May 29, 2014, 7:22 PM

        I tried that, but the setting wouldn’t stay. When I go back to settings it is set to SANBOOT.

        Thanks for the fast reply.

        1 Reply Last reply Reply Quote 0
        • J
          Junkhacker Developer
          last edited by May 29, 2014, 7:31 PM

          i just tried changing the setting on my server. the setting does not appear to change on the settings page, but it does change in the database, where it counts. please set it to exit and see if it works for you.

          signature:
          Junkhacker
          We are here to help you. If you are unresponsive to our questions, don't expect us to be responsive to yours.

          1 Reply Last reply Reply Quote 0
          • J
            JeffT
            last edited by May 29, 2014, 7:32 PM

            I will do that shortly and get back to you. Thanks!

            1 Reply Last reply Reply Quote 0
            • J
              JeffT
              last edited by May 29, 2014, 8:33 PM

              Just tried it again, with no luck. I’m not certain how to check the setting in the database.

              1 Reply Last reply Reply Quote 0
              • J
                Junkhacker Developer
                last edited by May 29, 2014, 8:56 PM

                did the exact same error show up on the boot screen?

                signature:
                Junkhacker
                We are here to help you. If you are unresponsive to our questions, don't expect us to be responsive to yours.

                1 Reply Last reply Reply Quote 0
                • J
                  JeffT
                  last edited by May 30, 2014, 3:32 PM

                  Yes, it was the same error.

                  1 Reply Last reply Reply Quote 0
                  • J
                    Junkhacker Developer
                    last edited by May 30, 2014, 3:49 PM

                    ok, i think Tom has fixed this now. please update to the latest SVN version

                    signature:
                    Junkhacker
                    We are here to help you. If you are unresponsive to our questions, don't expect us to be responsive to yours.

                    1 Reply Last reply Reply Quote 0
                    • J
                      JeffT
                      last edited by May 30, 2014, 4:57 PM

                      I updated to the latest SVN, now showing 1.1.0. Now I can change it to exit and it stays, but the client still displays the same error on boot.

                      1 Reply Last reply Reply Quote 0
                      • T
                        Tom Elliott
                        last edited by May 30, 2014, 5:14 PM

                        It will NOT show you san boot exiting errors if it’s not even attempting to use sanboot.

                        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
                          JeffT
                          last edited by May 30, 2014, 5:20 PM

                          Let me rephrase. It’s not an error, it just hangs there. The same message is on the screen as in the picture that I posted. It’s odd that it’s only this model of computer as far as I have seen, but we have many of these types of computers unfortunately.

                          1 Reply Last reply Reply Quote 0
                          • B
                            Baite
                            last edited by May 30, 2014, 5:35 PM

                            Have you tried using undionly.INTEL as your undionly.kpxe file?

                            1 Reply Last reply Reply Quote 0
                            • J
                              JeffT
                              last edited by May 30, 2014, 6:24 PM

                              No, but it’s worth trying.

                              1 Reply Last reply Reply Quote 0
                              • J
                                JeffT
                                last edited by May 30, 2014, 8:03 PM

                                Changing it to undionly.kpxe.INTEL worked! Tested it with booting to the OS and to the FOG server.

                                Thanks for the help!

                                1 Reply Last reply Reply Quote 0
                                • B
                                  Baite
                                  last edited by Jun 2, 2014, 11:41 AM

                                  [quote=“JeffT, post: 28742, member: 24415”]Changing it to undionly.kpxe.INTEL worked! Tested it with booting to the OS and to the FOG server.

                                  Thanks for the help![/quote]
                                  Glad I could help.

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

                                  200

                                  Online

                                  12.0k

                                  Users

                                  17.3k

                                  Topics

                                  155.2k

                                  Posts
                                  Copyright © 2012-2024 FOG Project