Linux will not boot from LUN in UCS

[conor0007]

Greetings from the Big Data world!

I am installing SUSE linux version 11sp3 (for SAP applications) on a B series blade. We are booting from a LUN on our SAN storage device (PURE). After successfully installing SUSE linux on our LUN, when the blade reboots, the LUN is still visible....

... but it will not boot. Also, there are entries for "SLES" which should not be there because there are no local disks. Our entire UCS system has been upgraded to 2.2(3f). We are using B440 M2 blades.

We are also getting this error.

Are there any known errors with UCS not booting from a LUN after installation? Could something be wrong with our BIOS? Any recommendations would help. 

[Walter Dey]

Can you please provide more Information, e.g.

- I assume it's FC ?

- any SAN Switches, or direct attachment of the storage Array ?

- can you provide screenshot of the boot policy

- what is the lun id of the boot lun ?

[otn-cco]

Edited for anyone finding this question.

*Fixed*    This was a UEFI issue. My service Profile had "Local CD/DVD" instead of just "CD/DVD". CentOS was loading the UEFI version and installing that on my M2 Blade which does not support UEFI. 

-----------------------------------------------------------------------------------------------------------------------------------------------------------

I am having this issue as well with CentOS 6.8 AND CentOS 7.2.  Both installations install successfully to the SAN disk.

I have B200M2 blades connected to a EMC VNX5300 via FC.

San Switches are FI connected to a Nexus 5010, connected to the VNX.

Boot Policy is: Boot from SAN Primary with the SAN WWN mapped to the Primary target.

Lun ID = 0.

*Note*

I can install ESXi onto this Lun and Boot from SAN.

Linux installs but boot hangs when it is time to boot of LUN...there is no output.

During the BIOS boot, I can loginto the FI and do a successful LUNLIST...

adapter 2/8/1 (fls):4# lunlist 7

vnic : 7 lifid: 4

  - FLOGI State : flogi est (fc_id 0x9f001f)

  - PLOGI Sessions

     - WWNN 50:06:01:64:3d:e0:XX:XX WWPN 50:06:01:64:3d:e0:XX:XX fc_id 0x9f00ef

       - LUN's configured (SCSI Type, Version, Vendor, Serial No.)

           LUN ID : 0x0000000000000000 (0x0, 0x4, DGC     , CKM0012470XXXX)

       - REPORT LUNs Query Response

           LUN ID : 0x0000000000000000

  - Nameserver Query Response

     - WWPN : 50:06:01:64:3d:e0:XX:XX

My only ideas are that it is a UEFI/Legacy Bios issue or a multipathing issue however I only have one path to the SAN open.