Booting From SAN device 0x80 issue
-
Server
- FOG Version:
- OS:
Client
- Service Version:
- OS:
Description
-
Sanboot, typically, doesn’t work for VM systems. This isn’t something I have direct control over unfortunately.
That said, as @Arsenal101 stated, please try using the Exit or Grub exit types instead.
If the VM is not registered in the fog server, you will need to adjust the “global” setting from:
FOG Configuration Page->iPXE Boot Menu->{Exit to Hard Drive Type,Exit to Hard Drive Type(EFI)}
-
@kyle.heath Sorry I hit the submit button on accident. Running this version of FOG
Tue Dec 13, 2016 16:54 pm
Running Version 1.3.0-RC-7
SVN Revision: 5946I’m creating a windows 10 golden image using Vsphere Web Client. Using ESXi 5.5. Guest operating system is Windows 8 because 5.5 does not have Windows 10. I’ll post photos of my config below. This happens after I do a full registration to Fog.
-
You may be able to change the iPXE boot menu exit mode to “exit” or I have had luck changing it to “grub” too
-
Erm, what happens?
-
@Arsenal101 If he changes it to EXIT or GRUB it doesn’t boot. He has also tried E1000, and VMXNET3 for NIC settings, neither will get him past the 0x80. I have seen this with machines needing to have their SATA operation set to AHCI, but never in a VM.
-
@Tom-Elliott I sent a reply to my original message. I accidentally hit the submit button early. After Full Registration it gives me a screen that only says Booting From SAN device 0x80. It won’t go past this screen into the windows 10 setup.
-
Sanboot, typically, doesn’t work for VM systems. This isn’t something I have direct control over unfortunately.
That said, as @Arsenal101 stated, please try using the Exit or Grub exit types instead.
If the VM is not registered in the fog server, you will need to adjust the “global” setting from:
FOG Configuration Page->iPXE Boot Menu->{Exit to Hard Drive Type,Exit to Hard Drive Type(EFI)}
-
@Tom-Elliott Thanks! This worked.