05-27-2022 10:39 AM
When we pushed the firmware package 4.1(3f) from the 3.2(d) version on the existing blades (Cisco UCS B420 M4), the Windows 2016 OS wouldn't get past the driver load phase and would hang on the windows flag loading screen. In the meantime on the video UCS Blades running Hyper-V on windows 2016.
We are keeping the firmware down leveled from the fabric interconnects to keep it on production.
We upgraded the drivers as follows as recommended on the compatibility matrix:
enic 4.2.0.5 -> 4.3.7.4
fnic 3.2.0.14 -> 3.3.0.11
05-27-2022 10:44 AM
Does it boot into safe mode?
What is the boot device? (local disk/SAN/iSCSI/etc)
Was the server in Legacy BIOS or UEFI mode?
05-27-2022 10:48 AM
Did you notice the problem after the firmware upgrade or after changing the drivers?
If you roll back to 3.2 does Windows load normally?
If you go to the latest 4.1.3h B-series firmware bundle does Windows load normally?
05-27-2022 11:44 AM
Did you notice the problem after the firmware upgrade or after changing the drivers?
After the firmware upgrade
If you roll back to 3.2 does Windows load normally?
Yes, I can roll back and it works normally
If you go to the latest 4.1.3h B-series firmware bundle does Windows load normally?
No, it hangs on the windows loading screen provided before.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide