Cache - PD(s) OK, Not usable after controller replacement

  • 132 Views
  • Last Post 18 March 2024
  • Topic Is Solved
Dean Trasente posted this 15 March 2024

I have a D5800 that a controller failed in and I replaced the controller with a new FRU purchased from PromiseWorks. After replacing the failed controller, the cache SSD's show as "PD(s) OK, Not usable". I have pulled the SSD's and they work just fine in other systems with no issues.

All 4 of these SSD's are MICRON S650DC-400FIPS. They can be reformatted fine in other systems and show no errors in functional use in other systems. However even after formatting they refuse to be re-recognized by the D5800 and show the status of "OK, Not usable".

Seem to recall having this or a similar issue with the original SSD's used when this was setup last year. At that time I replced the SSD's with these fresh MICRON drives and all was fine until the recent controller swap.

Is there some trick to reintroducing SSD's for the cache drives that have been used before, I would think reformatting should remove any stale configuration information from thyese and have them behave as new? Is there something else that needs to be done to reset things and allow these to be used?

One other anomoly (not sure if it has any bearing on the issue) but under the Physical Drive Information screen, I noticed that these drives are showing a media type of HDD. They show as SSD in applications when installed in other systems (Linux / Windows).

Any advice or thoughts on how to fix?

 

Order By: Standard | Latest | Votes
Dean Trasente posted this 15 March 2024

Additional information ... If I try to configure cache in the command line interface, it tells me only SSD can be used:

administrator@cli> cache -a add -t read -p 27

Error (0x4027): Invalid physical drive type

only SSD type drive can be used

 

 

Also other attempts to utilize CLI commands show these types of errors:

administrator@cli> phydrv -a clear -p 27

Error (0x49841602): Invalid physical drive id in data buffer

 

 

administrator@cli> phydrv -a offline -p 27

Error (0x49841602): Invalid physical drive id in data buffer

 

 

So it appears that the fact that the D5800 thinks these are HDD's may be an issue. How do I get the D5800 to recognize these as SSD and or clear the invalid data buffer?

 

R P posted this 16 March 2024

Hi Dean,

The usual reason for "OK, not usable" is that both controllers can't see the drive. This is true for cache drives as well. The SSDs you mention (SED?) are SATA, not SAS, so you'll need a SATA to SAS adapter for each SSD. And also the short SAS cables between the controllers and the SSD bays need to be correctly installed.

That aside, about the HD issue, can you run this command and post the output?

phydrv -v -p 27

 

Dean Trasente posted this 16 March 2024

Here is a image of the drive label. It appears to be a 12GB SAS drive not SATA. It is also listed under the Promise compatability sheet under the SAS SSD section, and shows on the Physical Drive Information page as SAS so not thinking I need an adapter on this drive.

This cache configuration worked with these 4 drives for the last year so they are known to be compatible. 

The cabling has the cable from each drive bay connection going into the left most SFF port on each controller.

Here are the results from verbose drive command:

 

administrator@cli> phydrv -v -p 27
-------------------------------------------------------------------------------
PdId: 27                                EnclId: 1
SlotId: 27                              DriveType: SAS
OperationalStatus: OK, Not usable       Alias: 
PhysicalCapacity: 400.09 GB             ConfigurableCapacity: 399 GB
UsedCapacity: N/A                       BlockSize: 512 Bytes
CfgStatus: N/A                          Location: Encl1 Slot27
ModelNo: MICRON  S650DC-400FIPS         ModelBrief: S650DC-400FIPS
VisibleTo: Controller 2                 SerialNo: ZB0108W50000822150Z3
FwVer: MB17                             ProtocolMajorVer: Not reported
TrimType: Not Support                   MediaType: HDD
Type: SAS HDD                           Temperature: 0C/32F
ReferenceTemperature: 0C/32F            PowerSavingLevel: Disabled
MediumErrorThreshold: 64                Glatency: 0

Dean Trasente posted this 16 March 2024

Thanks for providing the information about the "The usual reason for "OK, not usable" is that both controllers can't see the drive. This is true for cache drives as well. "

Looking at the verbose drive information, I noted that all of the drives were only being seen from controller number 2. In swapping the cables around, the seen controller followed one of the cables. So it appears that one of the cables is bad.

I replaced the suspect cable and all is happy and good now :-) ....

Many thanks for your assistance in helping me chase this down.

Best regards,

Dean 

R P posted this 18 March 2024

Hi Dean,

Looking at the verbose drive information, I noted that all of the drives were only being seen from controller number 2.

And that was the purpose of phydrv -v and what I would have pointed out when I responded.

In swapping the cables around, the seen controller followed one of the cables. So it appears that one of the cables is bad.

Good debug.

Oddly googling the PN gave several SATA SSDs and I had not yet seen the disk label above. But SAS SSDs they are, so we were down to the only possibile root cause being with the SAS cabling.

Search
Categories
Close