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

Boot from SAN device failed

Scheduled Pinned Locked Moved Solved
Hardware Compatibility
3
33
21.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.
  • H
    hariskar
    last edited by May 27, 2015, 7:47 AM

    I added a PC and try to make it boot with fog, but I get this message:
    Boot from SAN device 0X80 failed: Operation cancelled (http://ipxe.org/0b8080a0)

    I use latest fog 1.2.0 and have no problems with the other 2 PCs.
    What could I do?
    Thank you!

    C 2 Replies Last reply May 27, 2015, 8:15 AM Reply Quote 0
    • C
      ch3i Moderator @hariskar
      last edited by May 27, 2015, 8:15 AM

      @hariskar said:

      have no problems with the other 2 PCs.

      Hi,

      The others 2 PCs are the same model than the last added ?

      Regards,
      Ch3i.

      1 Reply Last reply Reply Quote 0
      • H
        hariskar
        last edited by May 27, 2015, 8:20 AM

        No the other are older PCs with Win XP. I just mentioned them for you to know that I have done this procedure again.

        Thank you Ch3i.

        C 1 Reply Last reply May 27, 2015, 8:21 AM Reply Quote 0
        • C
          ch3i Moderator @hariskar
          last edited by May 27, 2015, 8:21 AM

          @hariskar What is the model of the new PC ?

          1 Reply Last reply Reply Quote 0
          • H
            hariskar
            last edited by May 27, 2015, 8:32 AM

            Here are some details. I hope they help.

            Microsoft Windows 8.1
            6.3.9600 Δομή 9600

            Microsoft Corporation
            Manufactor Gigabyte Technology Co., Ltd.
            Model Z97P-D3
            System type x64-based PC
            CPU Intel® Core™ i5-4590 CPU @ 3.30GHz, 3301 Mhz, 4 cores, 4 λογικοί επεξεργαστές
            Έκδοση BIOS/Ημερομηνία American Megatrends Inc. F7, 22/4/2015
            Έκδοση SMBIOS 2.7
            Λειτουργία BIOS UEFI
            BaseBoard Gigabyte Technology Co., Ltd.
            RAM 8,00 GB

            C W 2 Replies Last reply May 27, 2015, 9:10 AM Reply Quote 0
            • C
              ch3i Moderator @hariskar
              last edited by May 27, 2015, 9:10 AM

              @hariskar Do you use undionly.kpxe for iPXE ? in your DHCP option 67.

              1 Reply Last reply Reply Quote 0
              • H
                hariskar
                last edited by May 27, 2015, 9:20 AM

                Yes, I use in Tomato DHCP / DNS Server (LAN) settings: dhcp-boot=undionly.kpxe,192.168.1.6

                C 1 Reply Last reply May 27, 2015, 9:26 AM Reply Quote 0
                • C
                  ch3i Moderator @hariskar
                  last edited by May 27, 2015, 9:26 AM

                  @hariskar said:

                  Yes, I use in Tomato DHCP / DNS Server (LAN) settings: dhcp-boot=undionly.kpxe,192.168.1.6

                  Could you try the kkpxe ?

                  1 Reply Last reply Reply Quote 0
                  • H
                    hariskar
                    last edited by May 27, 2015, 9:31 AM

                    With dhcp-boot=undionly.kkpxe,192.168.1.6 the result was the same.

                    C 1 Reply Last reply May 27, 2015, 9:39 AM Reply Quote 0
                    • C
                      ch3i Moderator @hariskar
                      last edited by May 27, 2015, 9:39 AM

                      @hariskar The error if after you get an IP ?

                      1 Reply Last reply Reply Quote 0
                      • H
                        hariskar
                        last edited by May 27, 2015, 9:43 AM

                        Sorry, I did not understand what to do, where should I look this?
                        After the error Boot from SAN device 0X80 failed: Operation cancelled (http://ipxe.org/0b8080a0) the PC stacks and the only think I can do is reboot and boot with Windows boot loader.

                        C 1 Reply Last reply May 27, 2015, 9:51 AM Reply Quote 0
                        • C
                          ch3i Moderator @hariskar
                          last edited by May 27, 2015, 9:51 AM

                          @hariskar In your server, in /tftpboot you have some ipxe files, can you return me the command :

                          ls -l /tftpboot
                          
                          1 Reply Last reply Reply Quote 0
                          • C
                            ch3i Moderator @hariskar
                            last edited by May 27, 2015, 9:57 AM

                            @hariskar I think the simple way to solve your problem is update your server to SVN version : https://wiki.fogproject.org/wiki/index.php/SVN

                            1 Reply Last reply Reply Quote 0
                            • H
                              hariskar
                              last edited by May 27, 2015, 9:57 AM

                              total 2564
                              -rw-r–r-- 1 fog root 840 Jul 23 2014 boot.txt
                              -rw-r–r-- 1 root root 293 Jul 23 2014 default.ipxe
                              -rw-r–r-- 1 fog root 389009 Jul 23 2014 ipxe.kkpxe
                              -rw-r–r-- 1 fog root 389057 Jul 23 2014 ipxe.kpxe
                              -rw-r–r-- 1 fog root 388044 Jul 23 2014 ipxe.krn
                              -rw-r–r-- 1 fog root 389073 Jul 23 2014 ipxe.pxe
                              -rw-r–r-- 1 fog root 25340 Jul 23 2014 memdisk
                              -rw-r–r-- 1 fog root 16794 Jul 23 2014 pxelinux.0.old
                              -rw-r–r-- 1 fog root 165088 Jul 23 2014 snponly.efi
                              -rw-r–r-- 1 fog root 101989 Jul 23 2014 undionly.kkpxe
                              -rw-r–r-- 1 fog root 102037 Jul 23 2014 undionly.kpxe
                              -rw-r–r-- 1 fog root 382650 Jul 23 2014 undionly.kpxe.INTEL
                              -rw-r–r-- 1 fog root 102053 Jul 23 2014 undionly.pxe
                              -rw-r–r-- 1 fog root 147728 Jul 23 2014 vesamenu.c32

                              C 1 Reply Last reply May 27, 2015, 9:58 AM Reply Quote 0
                              • C
                                ch3i Moderator @hariskar
                                last edited by ch3i May 27, 2015, 3:59 AM May 27, 2015, 9:58 AM

                                @hariskar said:

                                total 2564
                                -rw-r–r-- 1 fog root 840 Jul 23 2014 boot.txt
                                -rw-r–r-- 1 root root 293 Jul 23 2014 default.ipxe
                                -rw-r–r-- 1 fog root 389009 Jul 23 2014 ipxe.kkpxe
                                -rw-r–r-- 1 fog root 389057 Jul 23 2014 ipxe.kpxe
                                -rw-r–r-- 1 fog root 388044 Jul 23 2014 ipxe.krn
                                -rw-r–r-- 1 fog root 389073 Jul 23 2014 ipxe.pxe
                                -rw-r–r-- 1 fog root 25340 Jul 23 2014 memdisk
                                -rw-r–r-- 1 fog root 16794 Jul 23 2014 pxelinux.0.old
                                -rw-r–r-- 1 fog root 165088 Jul 23 2014 snponly.efi
                                -rw-r–r-- 1 fog root 101989 Jul 23 2014 undionly.kkpxe
                                -rw-r–r-- 1 fog root 102037 Jul 23 2014 undionly.kpxe
                                -rw-r–r-- 1 fog root 382650 Jul 23 2014 undionly.kpxe.INTEL
                                -rw-r–r-- 1 fog root 102053 Jul 23 2014 undionly.pxe
                                -rw-r–r-- 1 fog root 147728 Jul 23 2014 vesamenu.c32

                                You can try the undionly.kpxe.INTEL

                                1 Reply Last reply Reply Quote 0
                                • H
                                  hariskar
                                  last edited by May 27, 2015, 10:07 AM

                                  With dhcp-boot=undionly.kpxe.INTEL,192.168.1.6 the result is the same… 😞

                                  C 1 Reply Last reply May 27, 2015, 10:11 AM Reply Quote 0
                                  • C
                                    ch3i Moderator @hariskar
                                    last edited by May 27, 2015, 10:11 AM

                                    @hariskar Please try SVN if it’s possible for you (it’s “stable”)

                                    1 Reply Last reply Reply Quote 0
                                    • H
                                      hariskar
                                      last edited by May 27, 2015, 12:14 PM

                                      I made a clean installation of 3480 and with dhcp-boot=undionly.kpxe I registered the new PC and I can network-boot it. Now I have a new BIOS related problem I guess.
                                      With boot option:

                                      1. Windows
                                        2…

                                      it boots normaly to WIndows

                                      But with:

                                      1.Network Boot
                                      2. Windows

                                      it boots to PXE, but when I cancel it with Esc it does not goes to option 2 and boot Windows but it stacks and tells me to reboot and choose a correct boot disk etc…

                                      C 1 Reply Last reply May 27, 2015, 12:22 PM Reply Quote 0
                                      • C
                                        ch3i Moderator @hariskar
                                        last edited by May 27, 2015, 12:22 PM

                                        @hariskar You can change your exit to hard drive type like that : https://forums.fogproject.org/topic/5028/pxe-boot-in-previous-environemnt/4

                                        1 Reply Last reply Reply Quote 0
                                        • H
                                          hariskar
                                          last edited by May 27, 2015, 12:41 PM

                                          Thank you.
                                          I changed Exit to Hard Drive Type to 'Exit style" and after Exc it goes again to PXE boot.
                                          Then I changed it to “Grub style” and with Esc it stacks to reboot and choose a correct boot medium. I didn’t put anything in Advanced Configuration Options because I don’t know what.

                                          I did not have this problem with the other PCs, after Esc it continued to boot with Option 2 (Windows)

                                          1 Reply Last reply Reply Quote 0
                                          • 1
                                          • 2
                                          • 1 / 2
                                          1 / 2
                                          • First post
                                            16/33
                                            Last post

                                          192

                                          Online

                                          12.1k

                                          Users

                                          17.3k

                                          Topics

                                          155.2k

                                          Posts
                                          Copyright © 2012-2024 FOG Project