cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
393
Views
0
Helpful
3
Replies

No boot after enabling package 4.1(3f)B

Gravefall
Level 1
Level 1

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

3 Replies 3

Steven Tardy
Cisco Employee
Cisco Employee

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?

Wes Austin
Cisco Employee
Cisco Employee

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?

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.

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: