Boot from SAN device failed

[hariskar]

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!

[Wayne Workman]

Try to turn off secure boot.

[hariskar]

Boot mode selection: UEFI and Legacy
Storage Boot option control: Legacy first
Secure boot mode: Standard

[Wayne Workman]

@hariskar said:

Could it be some BIOS setting? I did not change the defaults. Any idea which BIOS settings could affect Boot 2 option to start after cancelled Boot 1 option?
Thank you

Is UEFI enabled? Is Secure Boot enabled?

[hariskar]

Thank you for very fast and great support! (I made a small donation )
I hope that my BIOS problem will be resolved too.

[ch3i]

@hariskar said:

Should I use the trunk from now on, or should I return to stable sometime?

Yep for sure

@hariskar said:

Any idea if some BIOS setting could interfire with Windows in 2 Boot option not booting?

Any idea sorry…

[hariskar]

Windows do not start even if they are boot option 2 after the DVD player with PXE deactivated. So, it is not relevant to fog. So my fog problem seems to be resolved. Should I use the trunk from now on, or should I return to stable sometime?

Any idea if some BIOS setting could interfere with Windows in 2 Boot option not booting?

[hariskar]

Could it be some BIOS setting? I did not change the defaults. Any idea which BIOS settings could affect Boot 2 option to start after cancelled Boot 1 option?
Thank you

[hariskar]

I run them. Nr 4 says that this PC seems compatible with fog. Do you want to post something of this test? If yes please tell me where can I find it.

[Wayne Workman]

It uses a Realtek® GbE LAN chip (10/100/1000 Mbit)

Can you try to run all of the compatibility checks from the FOG boot menu?

[hariskar]

Yes, this is it…

[Wayne Workman]

Is this it?

http://www.amazon.co.uk/Gigabyte-Z97P-D3-LGA1150-Motherboard-USB3-0/dp/B00K9R1OCW

[hariskar]

It is a desktop PC made from different parts.
The motherboard is: Gigabyte Z97P-D3 with firmware F7. What else would be useful?
Do you think it is incompatible?

[Wayne Workman]

@hariskar said:

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

That information doesn’t really help us.
@ch3i was asking for the model, not the specifications. This is the numbers on the front of the PC, or the back of the PC.

We have lists of working and non-working hardware that we normally check when we find out the model. Those lists are here:
https://wiki.fogproject.org/wiki/index.php/WorkingDevices
https://wiki.fogproject.org/wiki/index.php/ProblematicDevices

[hariskar]

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)

[ch3i]

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

[hariskar]

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…

[ch3i]

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

[hariskar]

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

[ch3i]

@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