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

    Fog registration with NUC

    Scheduled Pinned Locked Moved
    FOG Problems
    7
    36
    12.2k
    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
      Jjared
      last edited by

      Having trouble using Fog with the new Intel Nuc D54250WYK.

      It will PXE boot to the fog menu, and then no matter which option I choose it stalls about mid way through. I’ve tried registering it, even manually entering it and then trying to image. No luck as it always fails. It’s even stopping in different parts of the process.

      Anyone see this before?

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

        Try the undionly.kkpxe in the /tftpboot directory.

        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
        • M
          Mike Adams
          last edited by

          As a newbie to FOG\Ubuntu - Can you point me to some reference on the steps I should use to accomplish this?

          1 Reply Last reply Reply Quote 0
          • B
            Baite
            last edited by

            Just go to /tftpboot [#cd /tftpboot]
            Then rename undionly.kpxe to undionly.kpxe.ORIGINAL (for backup purposes only) [#mv undionly.kpxe undionly.kpxe.ORIGINAL]
            Then copy undionly.kkpxe to undionly.kpxe [#cp undionly.kkpxe undionly.kpxe]

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

              I typically use symbolic links.

              [code]cd /tftpboot
              mv undionly.kpxe undionly.kpxe.ORIGINAL
              ln -s undionly.kkpxe undionly.kpxe[/code]

              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
              • M
                Mike Adams
                last edited by

                This is what I get
                mv: cannot stat ‘undionly.kpxe’: No Such File or directory

                I must be missing a step someplace.

                1 Reply Last reply Reply Quote 0
                • B
                  Baite
                  last edited by

                  Well… can you access /tftpboot? [#cd /tftpboot]
                  What do you see when you type [#ls -alh]? Can you see severall files, including undionly.kpxe and undionly.kkpxe?
                  Copy commands from what Elliot typed, one by one, and paste them in Linux shell…

                  1 Reply Last reply Reply Quote 0
                  • M
                    Mike Adams
                    last edited by

                    I see files, but not undionly.kpxe - here is what I see:
                    root@FOG:~# cd /tftpboot
                    root@FOG:/tftpboot# ls -alh
                    total 220K
                    drwxr-xr-x 5 fog root 4.0K Apr 1 14:44 .
                    drwxr-xr-x 26 root root 4.0K Apr 2 08:46 …
                    -rw-r–r-- 1 fog root 828 Apr 2 08:46 boot.txt
                    drwxr-xr-x 5 fog root 4.0K Apr 1 14:44 fog
                    -rw-r–r-- 1 fog root 25K Apr 2 08:46 memdisk
                    -rw-r–r-- 1 fog root 17K Apr 2 08:46 pxelinux.0
                    drwxr-xr-x 2 fog root 4.0K Jun 26 14:43 pxelinux.cfg
                    drwxr-xr-x 2 fog root 4.0K Apr 1 14:44 tftpboot
                    -rw-r–r-- 1 fog root 145K Apr 2 08:46 vesamenu.c32
                    root@FOG:/tftpboot#

                    1 Reply Last reply Reply Quote 0
                    • M
                      Mike Adams
                      last edited by

                      I found this, so let me try its steps and see if I can complete to make the files.
                      [url]http://www.fogproject.org/wiki/index.php/Building_undionly.kpxe[/url]

                      1 Reply Last reply Reply Quote 0
                      • JunkhackerJ
                        Junkhacker Developer
                        last edited by

                        what version of fog are you running?

                        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
                        • Tom ElliottT
                          Tom Elliott
                          last edited by

                          What version of fog are you running?

                          I should’ve asked this first but…

                          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
                          • M
                            Mike Adams
                            last edited by

                            Running FOG 0.32

                            1 Reply Last reply Reply Quote 0
                            • JunkhackerJ
                              Junkhacker Developer
                              last edited by

                              fog 0.32 doesn’t use undionly.kpxe
                              you need pxelinux.0

                              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
                              • Tom ElliottT
                                Tom Elliott
                                last edited by

                                There’s your problem man.

                                FOG 0.32 is not the same as 1.x.x, which I’d highly recommend upgrading to.

                                Anyway, what problems are you having. You seem to have taken over this thread and I believe Jjared had 1.x.x.

                                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
                                • M
                                  Mike Adams
                                  last edited by

                                  Jared and I work together, same FOG machine. I have read some posts on upgrading from 0.x to 1.x will cause loss of data, is this still a risk with 1.1.2?

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

                                    Loss of data?

                                    What do you mean?

                                    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
                                    • M
                                      Mike Adams
                                      last edited by

                                      [FONT=sans-serif][COLOR=#000000][B]NOTE: 1.0.0 is a, nearly, complete rewrite from previous versions of FOG. There may be issues when upgrading from past revisions of FOG so please backup you installation before upgrading![/B][/COLOR][/FONT]
                                      [FONT=sans-serif][COLOR=#000000]Migration for 0.32 to version 1.x.x will cause you to loose the operation system information that was associated with your hosts. This information has been moved to the image item now, so you will need to update all your images to set the appropriate operating system! Please see the Migration Instructions section below for more information.[/COLOR][/FONT]
                                      [FONT=sans-serif][COLOR=#000000]All commands are assumed to be run as root. If you don’t have access to root, prepend the installation with sudo (ex.[/COLOR][/FONT]
                                      [FONT=sans-serif][COLOR=#000000] [/COLOR][/FONT]
                                      [FONT=sans-serif][COLOR=#000000]from [url]http://fogproject.org/wiki/index.php?title=Upgrade_to_1.0.0[/url][/COLOR][/FONT]

                                      1 Reply Last reply Reply Quote 0
                                      • JunkhackerJ
                                        Junkhacker Developer
                                        last edited by

                                        what that’s talking about is not a “risk.” It’s a change in operating procedure. Before, OS was associated with hosts. but the actual operating system resides in the image. so, that’s where that info has been put now.
                                        you should, of course, be prepared for a catastrophic failure, as you should be at all times, and especially when performing a major upgrade. We recommend that you do a fresh install instead of an upgrade, and migrate your data over to the new server. that is because you’re much less likely to have issues that way. upgrading is, however, supported.

                                        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
                                        • M
                                          Mike Adams
                                          last edited by

                                          Update: I have built a new UBUNTU desktop 14.04lts and have installed FOG 1.1.2 and I am to this point from the instructions on Building UNDIONLY.KPXE file (see link above) and I do not understand the “[B][FONT=sans-serif][COLOR=#000000]Remove the {}'s and only apply the file you wish to build if you want only a specific file.” from this part.[/COLOR][/FONT][/B]

                                          [FONT=sans-serif][COLOR=#000000]Build the undionly/ipxe files.[/COLOR][/FONT]
                                          [FONT=sans-serif][COLOR=#000000][B]I USE THE FOLLOWING COMMAND TO BUILD ALL FILES AT ONCE.[/B] [B]Remove the {}'s and only apply the file you wish to build if you want only a specific file.[/B][/COLOR][/FONT]
                                          [COLOR=#000000][FONT=monospace]make bin/{undionly,ipxe}.{,k,kk}pxe EMBED=ipxescript[/FONT][/COLOR]
                                          [SIZE=5][B][FONT=sans-serif][SIZE=19px][COLOR=#000000]Copy and/or Use your files[/COLOR][/SIZE][/FONT][/B][/SIZE]

                                          [FONT=sans-serif][COLOR=#000000][B]I USE THE FOLLOWING COMMAND TO COPY ALL FILES AT ONCE. Remove the {}'s and only copy the file you wish to use if you want only a specific file.[/B][/COLOR][/FONT]
                                          [COLOR=#000000][FONT=monospace]cp bin/{undionly,ipxe}.{,k,kk}pxe /tftpboot/ [/FONT][/COLOR]
                                          [COLOR=#000000][FONT=monospace]I ran the full command - make bin/{undionly,ipxe}.{,k,kk}pxe EMBED=ipxescript then realized it said to REMOVE the brackets should it be re-run but as[/FONT][/COLOR]
                                          [FONT=monospace]make bin/undionly,ipxe.,k,kk pxe EMBED=ipxescript[/FONT]
                                          [COLOR=#000000][FONT=monospace][/FONT][/COLOR]
                                          [COLOR=#000000][FONT=monospace][/FONT][/COLOR]

                                          1 Reply Last reply Reply Quote 0
                                          • JunkhackerJ
                                            Junkhacker Developer
                                            last edited by

                                            why are you building unidonly.kpxe? one is included with fog, that has fog-specific embedded scripting

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

                                            204

                                            Online

                                            12.0k

                                            Users

                                            17.3k

                                            Topics

                                            155.2k

                                            Posts
                                            Copyright © 2012-2024 FOG Project