topic Re: SAS disk status disabled/PCD. Disk not showing LED in ONTAP Hardware

SAS disk status disabled/PCD. Disk not showing LED

selvi — Tue, 26 Apr 2011 12:12:53 GMT

Hi,

There was a disk failure in FAS 2020 storage 0c.00.00. Disk does not showup LED even after replacing it. its showing disabled/PCD in SAS EXPANDER PHY STATE. copied the command output below. Removing and reinserting the disk on the slot 0c.00.00 does not showup in the syslog messages. How to enable the slot and get the disk detected. Or is this any BURT?

===========================================================================================

Expander phy state on 0c.0:
                                  Dngl     Pwr         Invald Disprt Loss   Phy    CRC    Phy
                          Dongle FW   Pwr Ccl Rsv Rls DWord Error Sync   Reset Error Change SATA
PHY/BAY STATE             Type    Rev. ON Cnt Cnt Cnt Count Count Count Prob   Cnt    Cnt    Affiliation
------- ----------------- ------- ---- --- --- --- --- ------ ------ ------ ------ ------ ------ ----------------
0/P0:0 3.0 Gb/s          ------- ---- --- --- --- --- 0      0      0      0      0      1      ----------------
1/P0:1 3.0 Gb/s          ------- ---- --- --- --- --- 0      0      0      0      0      1      ----------------
2/P0:2 3.0 Gb/s          ------- ---- --- --- --- --- 0      0      0      0      0      1      ----------------
3/P0:3 3.0 Gb/s          ------- ---- --- --- --- --- 0      0      0      0      0      1      ----------------
4/P1:0 Rate unknown
5/P1:1 Rate unknown
6/P1:2 Rate unknown
7/P1:3 Rate unknown
8/0    Disabled/PCD      SPS3G   6    YES 1   0   0
9/1    3.0 Gb/s          SPS3G   6    YES 0   0   0   0      0      0      0      0      3      f080c72910000000
10/2    3.0 Gb/s          SPS3G   6    YES 0   0   0   0      0      0      0      0      3      f080c72910000000
11/3    3.0 Gb/s          SPS3G   6    YES 0   0   0   0      0      0      0      0      3      f080c72910000000
12/4    3.0 Gb/s          SPS3G   6    YES 0   0   0   0      0      0      0      0      3      f080c72910000000
13/5    3.0 Gb/s          SPS3G   6    YES 0   0   0   0      0      0      0      0      3      f080c72910000000
14/6    3.0 Gb/s          SPS3G   6    YES 0   0   0   0      0      0      0      0      3      f080c72910000000
15/7    3.0 Gb/s          SPS3G   6    YES 0   0   0   0      0      0      0      0      3      f080c72910000000
16/8    3.0 Gb/s          SPS3G   6    YES 0   0   0   0      0      0      0      0      3      f080c72910000000
17/9    3.0 Gb/s          SPS3G   6    YES 0   0   0   0      0      0      0      0      3      f080c72910000000
18/10   3.0 Gb/s          SPS3G   6    YES 0   0   0   0      0      0      0      0      2      f080c72910000000
19/11   3.0 Gb/s          SPS3G   6    YES 0   0   0   0      0      0      0      0      2      f080c72910000000
20/V99 3.0 Gb/s          ------- ---- --- --- --- --- 0      0      0      0      0      0      ----------------

===========================================================================================

regards,

Selvi

Re: SAS disk status disabled/PCD. Disk not showing LED

LTDCLSERGAO — Tue, 23 Apr 2013 13:25:17 GMT

Hello,

I'm facing the same issue :

sasadmin expander_phy_state 1b.10

Expander phy state on 1b.10 (NETAPP :DS424IOM3

Pwr Invald Disprt Loss Phy CRC Phy

Pwr Ccl Rsv Rls DWord Error Sync Reset Error Change SATA

PHY/BAY STATE ON Cnt Cnt Cnt Count Count Count Prob Cnt Cnt Affiliation

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

0/P0:0 3.0 Gb/s --- --- --- --- 0 0 0 0 0 8 ----------------

1/P0:1 3.0 Gb/s --- --- --- --- 0 0 0 0 0 8 0000000000001005

2/P0:2 3.0 Gb/s --- --- --- --- 0 0 0 0 0 8 0000000000001005

3/P0:3 3.0 Gb/s --- --- --- --- 0 0 0 0 0 8 0000000000001005

4/P1:0 3.0 Gb/s --- --- --- --- 0 0 0 0 0 1 ----------------

5/P1:1 3.0 Gb/s --- --- --- --- 0 0 0 0 0 1 ----------------

6/P1:2 3.0 Gb/s --- --- --- --- 0 0 0 0 0 1 ----------------

7/P1:3 3.0 Gb/s --- --- --- --- 0 0 0 0 0 1 ----------------

8/0 3.0 Gb/s YES 0 0 0 0 0 0 0 0 2 ----------------

9/1 3.0 Gb/s YES 0 0 0 0 0 0 0 0 2 ----------------

10/2 3.0 Gb/s YES 0 0 0 0 0 0 0 0 2 ----------------

11/3 3.0 Gb/s YES 0 0 0 0 0 0 0 0 2 ----------------

12/4 3.0 Gb/s YES 0 0 0 0 0 0 0 0 2 ----------------

13/5 3.0 Gb/s YES 0 0 0 0 0 0 0 0 2 ----------------

14/6 3.0 Gb/s YES 0 0 0 0 0 0 0 0 2 ----------------

15/7 3.0 Gb/s YES 0 0 0 0 0 0 0 0 2 ----------------

16/8 3.0 Gb/s YES 0 0 0 0 0 0 0 0 2 ----------------

17/9 3.0 Gb/s YES 0 0 0 0 0 0 0 0 2 ----------------

18/10 Disabled/BRST_PCD YES 6 0 0

19/11 3.0 Gb/s YES 0 0 0 0 0 0 0 0 2 ----------------

20/12 3.0 Gb/s YES 0 0 0 0 0 0 0 0 2 ----------------

21/13 3.0 Gb/s YES 0 0 0 0 0 0 0 0 2 ----------------

==========

Any help ?

Said

Re: SAS disk status disabled/PCD. Disk not showing LED

CAPGEMINI_USERS — Thu, 19 Feb 2015 15:48:44 GMT

Hello,

I'm having the same issue here, does any of you manage to resolved it ?

Re: SAS disk status disabled/PCD. Disk not showing LED

ChartLogic_IT — Fri, 02 Jun 2017 19:39:54 GMT

DId you ever solve this error? I'm getting the same thing:

19/11 Disabled/BRST_PCD SPS3G 6 YES 0 0 0

The drive in that bay is a known good drive, but the device wont recognize it.

Yes, the device is end-of-life'd, but we're using it to tinker with.

Any help would be appreciated.

Re: SAS disk status disabled/PCD. Disk not showing LED

Anirban — Tue, 13 Jun 2017 06:37:07 GMT

Same issue has been faced by us in 7-mode and we were able to rectify it.

What we did is we reseat the controller.

Process:

First of all check if your rc file is ok(partner interfaces are defined) and your zoning is ok so that you get a non disruptive functionality.
Then test your takeover and giveback. If it is successful and you obtain a nondisruptive service(both NAS and SAN), go ahead and reseat the controller.

So first of all check CPU utilization an takeover one controller. Login from the SP of the takenover controller and check when the controller is waiting for giveback.
When the controller is waiting for giveback go ahead and very very carefully pull out the controller. Pull out 20% until you see all the lights are off. Wait for 2 minutes and put it back in. Let it boot automatically.(you can see the lights come back on and become green).

Once the controller is booted up it will again display waiting for giveback. Wait for 5 minutes and let the NVRAM sync and then do a giveback from the partner node.
Once the giveback is successful take 10-15 minutes and check if access to files ad shares and luns are ok.

Perform the same action for the other controller now.(takeover>pullout>put back in>auto boot>lights turn green>giveback)

Once this is done login to management console and issue

sasadmin shelf and sysconfig -r to check for the disk.

If still the disk is in failed state

manually unfail the disk.

This solved our issue and our disk was ok.
It was a spare disk which was not visible/failed status. after this entire activity it came online as a spare and non zeroed disk. So manually we triggered the zeroing.

However i would advise to take the help of tech support to resolve such issues. Similar reseting can be done via ACP(i am told) but unsure how to do such.