We noticed the following problem with NUC-6Gen devices (NUC6CAY):
At startup, the device stays in the POST phase with the message "BIOS has detected unsuccessful POST attempt (s) ..."
This happens when:
a. a network cable is connected, but on the same network no DHCP server is available.
b. the BIOS option "UEFI PXE & iSCSI" is active.
In this configuration, the device takes also a long time to display the BIOS menu (with the F2 key).
Our previous tests have shown:
o Without a network cable, the device starts.
o The device starts with cable and DHCP server.
o After disabling "UEFI PXE & iSCSI" in the BIOS, the device starts normally, but not always.
o As soon as the device has received DHCP information, the problem has disappeared, although "PXE" is still active and the device is put back into a network without DHCP server.
o A BIOS update doesn't solve the problem.
The difficulty is that there is no DHCP server available where we install the NUCs, and if the problem is solved, the problem cannot be reproduced.
Thank you in advance for your help.
Yea, this issue has been reported before and reproduced by technical support. A sighting has been opened. Watch for a BIOS update that addresses this issue.
Are you actually using PXE boot? If not, disable this feature completely in the BIOS:
This should avoid the issue you are having,
As Scott has noted, this issue has been reported and I've opened a bug sighting against it.
There's currently no fix, however there's a couple ways to mitigate it until we do have a fix.
We are looking into a permanent fix and as soon as I know more, I will post here.
I just had the same issue after upgrading to the latest BIOS (0065) from a really old version.
This is strange because the release notes state that this problem is fixed.
Seems like this isn't the case!
Disabling PXE fixed it for me but it's just luck that I don't rely on that!
Please have a look into it again.
Hi @DAsdf4 ,
Thank you for letting us know about this. Yes, it was supposed to be fixed, but obviously it isn't.
What's interesting is that when I tested BIOS 0065, it worked for me. Then I saw this post and now it keeps failing for me too! So weird!
I have let the team know and they are looking into this.
I'll respond here when I know more.