Intel NUC NUC6i5SYH
FOG v1.3.1-RC-7
NUC BIOS v57
Single M.2 256MB Intel NVMe drive
8GB RAM
LEGACY Win7 x64 SP1 = WORKS (Host BIOS Exit Type: SANBOOT)
UEFI Win10 x64 = WORKS (Host EFI Exit Type: rEFInd)
Single disk, multiple partition, not resizable.
Date Tested: 3 Feb 2017
A
Best posts made by AllFoggedOut
-
RE: Hardware Currently Working with FOG v1.x.xposted in Hardware Compatibility
-
RE: FOG menu boot loop after image deploymentposted in FOG Problems
So, for reasons I don’t quite fully understand, the problem appears to be resolved (it wasn’t working yesterday after I installed v57 BIOS…)
I was looking at BIOS options, hoping to find something along the lines of “Always show Boot Menu”, thinking this might be a hack to work around the problem. Following a reboot I discovered the NUC now boots from iPXE Boot Menu w/o issue.
I’m still a little confused as to how this is now working, after testing it yesterday and finding it wasn’t playing ball. Not sure if the act of disabling the SATA channel has somehow adjusted configuration somewhere (I re-enabled SATA to confirm if that was the cause, but it made no difference - everything still works fine).
I’ve just completed a Legacy Win7x64 SP1 image deployment + reboot - no issues at all.
Weird…but in a good way.