Cisco UCS - Rackmount Server: RAID Config

[zykobot]

Hi.

I've configured a C-series server that's managed within Cisco UCS with RAID 10 using 10 disks (I know excessive but they came as part of some special).

For some reason the disk located in Slot 2 doesn't seem to be participating in the RAID so we've now moved it to Slot 12.. same thing,

I'm thinking perhaps the disk had stopped working/participating before the RAID policy was applied thus the configuration is only using 9 disks.

Are there commands I can use to see what the health of the RAID is and whether there is a disk missing?

I've checked the following guide but there doesn't seem to be any deep look into the RAID.

http://www.cisco.com/en/US/docs/unified_computing/ucs/sw/cli/config/guide/2.0/b_UCSM_CLI_Configuration_Guide_2_0.html

Detail below...

PRIUCS01-A /server/raid-controller # show detail

RAID Controller:

    ID: 2

    Type: Sas

    PCI Addr: 20:00.0

    Vendor: LSI Corp.

    Model: LSI 6G MegaRAID 9261-8i

    Serial: SV23211032

    HW Rev: B4

    Raid Support: : RAID0, RAID1, RAID5, RAID6, RAID00, RAID10, RAID50, RAID60, PRL 11, PRL 11 with spanning, SRL 3 supported, PRL11-RLQ0 DDF layout with no span, PRL11-RLQ0 DDF layout with span

NPPRIUCS01-A /server/raid-controller # show lun

Local LUN:

    ID: 0

    Block Size: 512

    Blocks: 2918430277

    Size (MB): 1425014

    Operability: N/A

    Presence: Equipped

PRIUCS01-A /server/raid-controller # show local-disk

Local Disk:

    ID: 3

    Block Size: 512

    Blocks: 583983104

    Size (MB): 285148

    Operability: Operable

    Presence: Equipped

    ID: 4

    Block Size: 512

    Blocks: 583983104

    Size (MB): 285148

    Operability: Operable

    Presence: Equipped

    ID: 5

    Block Size: 512

    Blocks: 583983104

    Size (MB): 285148

    Operability: Operable

    Presence: Equipped

    ID: 6

    Block Size: 512

    Blocks: 583983104

    Size (MB): 285148

    Operability: Operable

    Presence: Equipped

    ID: 7

    Block Size: 512

    Blocks: 583983104

    Size (MB): 285148

    Operability: Operable

    Presence: Equipped

    ID: 8

    Block Size: 512

    Blocks: 583983104

    Size (MB): 285148

    Operability: Operable

    Presence: Equipped

    ID: 9

    Block Size: 512

    Blocks: 583983104

    Size (MB): 285148

    Operability: Operable

    Presence: Equipped

    ID: 10

    Block Size: 512

    Blocks: 583983104

    Size (MB): 285148

    Operability: Operable

    Presence: Equipped

    ID: 11

    Block Size: 512

    Blocks: 583983104

    Size (MB): 285148

    Operability: Operable

    Presence: Equipped

    ID: 12

    Block Size: Unknown

    Blocks: Unknown

    Size (MB): Unknown

    Operability: Operable

    Presence: Equipped

PRIUCS01-A /server/raid-controller #

[gehanson]

After UCSM inventories drives as part of its discovery process and after it associates the service profile to the server,

it has limited visibility in the state of the disks and the virtual drives. The reason is that it uses host-based utilities to retrieve this information.

There are a few different ways to get more information about the drive in question:

1. Use an LSI utility such as MegaRaid CLI or Megaraid Storage Manager (MSM). The availability of this

depends on what O/S you're using. This is the only option if you don't want to reboot.

2. Reboot your server and go into LSI's WebBIOS utility.

3. From UCSM, re-acknowledge the server. This will cause the O/S to reboot and UCSM will re-discover the

drives and virtual drive. Please note that for this third option, you have to be careful. Make sure the local

disk policy is set to "protect configuration" or you have selected "any configuration". Otherwise, there is a chance

that your data may be lost, as UCSM may redo the LSI RAID configuration.

Let me know if you have any questions.

Geoff Hanson

UCSM Development

Data Center Business Group

Cisco Systems