[Solved] Unable to install Server 2012 on UCS B220 M3

[JLogan3o13]

 have been asked to install Windows Server 2012 R2 on a B200 M3 blade. My storage team presented one drive of 150GB (single path) as LUN ID 1. I boot up through the KVM using the mounted Server disk, and get to the point where it cannot find any drives. I then switch over to the UCS driver ISO (v. 3.2.3b which matches what we're on) and load the fnik2k12.inf from Storage>>Cisco>>VIC>>WsK12R2>>x64. Once I do so I can see the drive, it comes up as Drive 2 Partition 1. However, I have a warning at the bottom that Windows can't be installed on drive 2 partition 1. The warning message states:

Windows cannot be installed to this disk. This computer's hardware may not support booting to this disk. Ensure that the disk's controller is enabled in the computer's BIOS menu.

I have checked that the BIOS policy is the same as what is being used by two physical servers that were built by a previous admin back in September. I am unfortunately new to UCS and taking over the entire environment with little previous experience. I am hoping that I am missing something stupid simple, and would appreciate any suggestions.

[Wes Austin]

Once you mount the driver ISO and Windows can see the disk, have you re-mapped the Windows ISO  installer to continue?

[JLogan3o13]

Yes, I did. I then hit refresh, but I get the same error message.

[Wes Austin]

Does it give you the option to format the disk at the bottom? Please provide screen capture(s)

[JLogan3o13]

Yes, I can Delete the partition, format it, then select new, etc. Even after deleting it, creating a new partition and formatting, I get the same error.

[Kirk J]

Just to confirm, when your server goes through POST, and the vic Option Rom loads, it displays the boot LUN under each vHBA (usually two)?

Also, please confirm that the Storage target WWPN specified in boot policy belongs to the storage controller that actually owns the boot LUN, as 'trespassing' method of accessing a boot LUN will frequently not boot.

The SAN boot policy also references Lun ID #1?

Kirk...

[JLogan3o13]

It turns out this was due in part to my own ignorance and in part to some of the previous administration's mess I am trying to clean up.

• I knew with Windows I could only have the single path until I get the OS installed and MPIO enabled, but I thought just having storage team point to the one path was enough. I still have multiple vHBAs assigned, so the server still saw multiple paths.
• For the boot path in the boot policy, I made an assumption that it would be the same as the servers that were built back in September instead of checking with the storage team. I found out my assumption was wrong.

All in all a comedy of errors. Thanks, all, for the suggestions