Unsupported drive on Smart Array P212

[MartinN]

Hey Everyone,

I recently installed two new drives (Mfg. Part: 628059-B21) into one of our HP Proliant DL165 servers with a Smart Array P212 controller. This server is running VMware ESXi 5.1 with hputils installed so we can manage our smart array controller without needing to rebooting the server. After I installed the drives I log into the server and run a show config command. Here is the command and output: 

~ # esxcli hpacucli cmd -q "controller slot=1 show config"

Smart Array P212 in Slot 1 (sn: **Confidential info erased**)

array A (SAS, Unused Space: 0 MB)

logicaldrive 1 (1.8 TB, RAID 1, OK)

physicaldrive 1I:1:1 (port 1I:box 1:bay 1, SAS, 2 TB, OK)
physicaldrive 1I:1:2 (port 1I:box 1:bay 2, SAS, 2 TB, OK)

unassigned

physicaldrive 1I:1:3 (port 1I:box 1:bay 3, SATA, 0 MB, Unsupported)
physicaldrive 1I:1:4 (port 1I:box 1:bay 4, SATA, 0 MB, Unsupported)

SEP (Vendor ID PMCSIERA, Model SRC 8x6G) 250 (WWID: 5001438014701DFF)

As you can see, the output shows that the two new drives are Unsupported, if I try to make a raid array using these drives I get an error that says "Unassigned drives for creation not available". 

I tried to find some compatability lists for the drives, array controller, and server but I was unable to find anything useful. If anyone has any ideas as to what my problem might be, they would be much appreciated. I would preferably like to solve this issue without needing to reboot.

[Robert_Jewell]

You shouldnt need to reboot, I agree.

I know you cannot mix SAS and SATA drives within the same array, but you should be able to create a new array with just these two drives.

What does the following show for the two drives:

>ctrl slot=1 pd 1I:1:3 show detail

-Bob

[MartinN]

Hey Bob,

Here is the output for that command.

~ # esxcli hpacucli cmd -q "ctrl slot=1 pd 1I:1:3 show detail"

Smart Array P212 in Slot 1

unassigned

physicaldrive 1I:1:3
Port: 1I
Box: 1
Bay: 3
Status: Unsupported
Drive Type: Unassigned Drive
Interface Type: SATA
Size: 0 MB
Rotational Speed: 7200
Firmware Revision: HPG3
Serial Number: **Confidential info erased**
Model: ATA MB3000EBKAB
SATA NCQ Capable: True
SATA NCQ Enabled: True
Current Temperature (C): 37
Maximum Temperature (C): 45
PHY Count: 1
PHY Transfer Rate: 3.0Gbps

[Robert_Jewell]

This part doesnt look good:

 > Size: 0 MB

Do you have another system you can install the disk just to check its status from another system?

-Bob

[MartinN]

Hey Bob,

Just to clerify, you want me to pop this disk into a different ProLiant server and run this same show config command? I already have 4 of these disks in two different servers that are all giving me the same output. 

[Robert_Jewell]

OK, didnt catch that, so it seems unlikely that all drives would be bad.  The P212 supports these 3TB disks per QuickSpecs so not sure whats wrong.

Perhaps, check the P212 firmware and see if it can be updated???

-Bob

[MartinN]

Hey Bob, 

Judging based on this output, it looks like I'm running firmware version 3.66.

~ # esxcli hpacucli cmd -q "controller slot=1 show detail"

Smart Array P212 in Slot 1
Bus Interface: PCI
Slot: 1
Serial Number: **Confidential info erased**
Cache Serial Number: **Confidential info erased**
RAID 6 (ADG) Status: Disabled
Controller Status: OK
Hardware Revision: C
Firmware Version: 3.66
...

And Judging based on this webpage (https://support.hpe.com/connect/s/product?language=en_US&kmpmoid=3885791&tab=driversAndSoftware) it looks like 3.66 is the newest version  avilable.

Also, I'm guessing that in order to do a firmware upgrade I would need to poweroff/reboot the server, right?

[Moderator edit: Updated the broken link.]

[Robert_Jewell · Accepted solution]

Actually, it looks like version 5.06 is the latest....

and in reviewing the release notes:

Enhancements/New Features:

  Added support for the following features:

• HDDs that exceed 2.2 TB in size

So, looks like you need to simply update firmware.  Yes a reboot is required.

-Bob

[MartinN]

Ah, yes, It looks like I was looking at the wrong collum.

Thanks for your answer, I'm not too pleased that I will need to reboot this server, but I guess that's the way life works. 

[Mark Matthews]

Hi sorry to crash your thread but how did you get the hpacucli to work via the command line?
Did you install ESX using an HP 'enhanced' CD or have you installed something over the top of the normal ESX installation?

Looking for info on doing this myself...

Thanks

Mark...