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

    Blessing Fog server doesn't work on Macmini7,1

    Scheduled Pinned Locked Moved Unsolved
    Mac Problems
    7
    23
    9.9k
    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.
    • C
      cpast
      last edited by

      Server
      • FOG Version: 1.3
      • OS: RHEL 7
      Client
      • Service Version:
      • OS: OS X 10.11
      Description

      I’m trying to set up a Mac Mini (Macmini7,1) to automatically boot from my Fog server. I used csrutil to authorize the Fog server as a netboot source, and then used bless --netboot --server bsdp://192.168.1.10 to tell the Mac to boot from that server. When I reboot, it loads iPXE, which then says “Could not open net1: input/output error”. It then very briefly displays a hex dump of some sort before booting from the hard drive.

      When I hold Alt at boot to access startup options and select Fog from there, the same thing happens, except that it doesn’t boot from the hard drive. After the hex dump goes on for a bit, it successfully boots using net0 and pulls up the Fog menu.

      Any idea what’s going on? I have a video of the failed autoboot I can upload if it’d help.

      1 Reply Last reply Reply Quote 0
      • Tom ElliottT
        Tom Elliott
        last edited by Tom Elliott

        I’m not familiar with the way to get mac to work, but I’m pretty sure bsdp is specific to Mac DeployStudio (though I’ve been wrong before.)

        Pretty sure you should be using:

        bless --netboot --booter tftp://192.168.1.10/ipxe.efi

        https://wiki.fogproject.org/wiki/index.php?title=FOG_on_a_MAC#Using_bless

        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

        C 1 Reply Last reply Reply Quote 1
        • C
          cpast @Tom Elliott
          last edited by

          @Tom-Elliott I can try that tomorrow and post the results, but as far as BSDP goes it is getting to iPXE successfully (the failure happens once iPXE has loaded), and I can successfully boot using BSDP from the Mac boot menu.

          Attached are images of the failed boot sequence using BSDP. There’s some activity, then it hangs on the first screenshot for a sec, then it scrolls through the second and third screenshots (the third screenshot is what it shows immediately before failing and booting the internal hard drive).0_1479179594522_ipxe.PNG0_1479179725199_hexdump1.PNG
          0_1479179732511_hexdump2.PNG

          1 Reply Last reply Reply Quote 0
          • Q
            Quazz Moderator
            last edited by

            As far as I know (and tested), you should simply be able to boot into FOG from the boot select menu.

            1 Reply Last reply Reply Quote 0
            • S
              Sebastian Roth Moderator
              last edited by

              Linking another post here as it seems related (but unfortunately unsolved): https://forums.fogproject.org/topic/7818/could-not-open-net1

              Still I am wondering why it is saying “net1” as iPXE usually starts counting the NICs from zero.

              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
              • C
                cpast
                last edited by

                @Tom-Elliott Blessing ipxe.efi directly leads to it not even loading iPXE.

                @Quazz I was under the impression that FOG is supposed to be the default boot option for machines (so that they’ll complete any assigned tasks automatically on startup). Is that wrong? (although if that’s how it’s supposed to work, there’s another issue that should maybe be a separate question: the menu’s “boot from hard drive” option leads to a “chainload failed” message).

                @Sebastian-Roth The weird thing is that if I launch it from the boot menu, after net1 fails it then tries net0 (which works).

                Q 1 Reply Last reply Reply Quote 0
                • S
                  Sebastian Roth Moderator
                  last edited by

                  @cpast Possibly net0 is not ready on first boot? Do you have spanning tree protocol configured on your (managed) switch? Could you try setting “port fast” for that switch port?

                  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
                  • Q
                    Quazz Moderator @cpast
                    last edited by

                    @cpast Depends on how you configure the client. You’d need to tell the client to have PXE boot as primary boot.

                    Otherwise, you can simply go in the boot menu during boot and it should be one of the boot options.

                    Very few of the menu options work properly on Mac though, I find. I’ve been able to capture and deploy but that’s about the extend.

                    1 Reply Last reply Reply Quote 0
                    • C
                      cpast
                      last edited by

                      @Sebastian-Roth My test environment uses a normal desktop switch, so I don’t think I can do that. I did look at a tcpdump on the FOG server, and didn’t see any traffic from iPXE before it tries net1.

                      @Quazz My ultimate goal is centralized management of computers across a large campus, so I’d prefer something that let me reimage a lot of computers without running all around campus. If I want to do that, is it possible to do without setting netboot as the default?

                      1 Reply Last reply Reply Quote 0
                      • C
                        cpast
                        last edited by

                        On a hunch, I physically pulled the Wi-Fi card out of the Mac Mini. It no longer tries booting to net1, and ipxe.efi works (though it does pop up error messages initially). Unfortunately, pulling the Wi-Fi card from all computers isn’t necessarily a viable option. It seems, though, that it’s trying the Wi-Fi card before the Ethernet for some reason.

                        Tom ElliottT Wayne WorkmanW 2 Replies Last reply Reply Quote 0
                        • Tom ElliottT
                          Tom Elliott @cpast
                          last edited by

                          @cpast THis shouldn’t even be possible. Why? There are 0 wireless drivers built in with the ipxe binaries that I’m providing. At the least, we don’t have the wireless capabilities even enabled though either.

                          Maybe if you try snponly.efi?

                          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
                          • Wayne WorkmanW
                            Wayne Workman @cpast
                            last edited by

                            @cpast said in Blessing Fog server doesn't work on Macmini7,1:

                            pulling the Wi-Fi card from all computers isn’t necessarily a viable option.

                            https://support.apple.com/en-us/HT204417
                            It can likely be scripted to use ethernet first, also.

                            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
                            • C
                              cpast
                              last edited by

                              @Wayne-Workman It was booting to ipxe.efi fine; the issue was that once ipxe.efi loaded it didn’t work right.

                              @Tom-Elliott snponly.efi worked on a Mini with the wifi card still in. It showed the same error message (with DUView.c and AppleBootUI.c) that net1 showed in ipxe.efi, but it tried net0 first instead of net1 and successfully loaded the menu.

                              Once it reached the menu, “Boot from hard drive” failed with a “chainloading failed” message. Should I use this thread for that question or start a new one?

                              Tom ElliottT 1 Reply Last reply Reply Quote 0
                              • Tom ElliottT
                                Tom Elliott @cpast
                                last edited by

                                @cpast Change the registered host’s “exit” type. You can do this globally too.

                                Exit doesn’t know how to release properly and sanboot is the “default” but sanboot uses the “legacy” machinisms. YOu can try setting exit for efi exit type though.

                                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
                                • C
                                  cpast
                                  last edited by

                                  @Tom-Elliott Setting “EFI Exit Type” to “EXIT” (in the host settings, in global settings, and in group settings) didn’t work. Also, I noticed an issue with the snponly.efi solution: trying to deploy an image results in nothing happening after it says “bzImage loaded” and “init.xy” (it just stays on that screen).

                                  Tom ElliottT 1 Reply Last reply Reply Quote 0
                                  • Tom ElliottT
                                    Tom Elliott @cpast
                                    last edited by

                                    @cpast So using snponly.efi wasn’t expected to work, just was hoping to see if it would try the wifi address.

                                    If exit type isn’t working (and obviously sanboot isn’t) then I think the only option left for mac’s is to use the rEFInd exit type (though you may need to edit the config for yourself as I don’t know it’s inner workings yet.)

                                    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
                                    • C
                                      cpast
                                      last edited by

                                      @Tom-Elliott rEFInd works (I just had to set it using the web interface). However, if snp.efi and snponly.efi don’t work, I’m back where I started with it not working without the wifi card pulled.

                                      Tom ElliottT 1 Reply Last reply Reply Quote 0
                                      • Tom ElliottT
                                        Tom Elliott @cpast
                                        last edited by

                                        @cpast You tried both? What about specifying intel or realtek? I don’t know what type apple uses.

                                        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
                                        • C
                                          cpast
                                          last edited by

                                          @Tom-Elliott I tried both snp and snponly and neither supported a deploy operation. The Mac Mini uses Broadcom, so I tried building a tg3.efi iPXE, and that seems to be working. If other Macs don’t use a tg3.efi driver, is there a way to build multiple drivers into one EFI that’s not ipxe.efi?

                                          Tom ElliottT 1 Reply Last reply Reply Quote 0
                                          • Tom ElliottT
                                            Tom Elliott @cpast
                                            last edited by

                                            @cpast if you built tg3.efi, you can build intel, realtek, etc… just by choosing to do so when building.

                                            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

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

                                            166

                                            Online

                                            12.0k

                                            Users

                                            17.3k

                                            Topics

                                            155.2k

                                            Posts
                                            Copyright © 2012-2024 FOG Project