Sun Storage 7000 Unified Storage System: When replacing faulted Readzilla SSD and System disks in the head unit the replacement is not recognized

Asset ID:	1-72-1457578.1
Update Date:	2012-06-28
Keywords:

Solution Type Problem Resolution Sure

Solution 1457578.1 : Sun Storage 7000 Unified Storage System: When replacing faulted Readzilla SSD and System disks in the head unit the replacement is not recognized

Applies to:

Sun ZFS Storage 7420 - Version Not Applicable to Not Applicable [Release N/A]
Sun ZFS Storage 7320 - Version Not Applicable to Not Applicable [Release N/A]
Sun ZFS Storage 7120 - Version Not Applicable to Not Applicable [Release N/A]
Sun Storage 7410 Unified Storage System - Version Not Applicable to Not Applicable [Release N/A]
Sun Storage 7310 Unified Storage System - Version Not Applicable to Not Applicable [Release N/A]
7000 Appliance OS (Fishworks)

Symptoms

When replacing a read cache SSD or a system disk in the head unit of a 7000 series ZFS Storage Appliance the new disk may not be recognised and it might appear as if the new SSD is broken too

Changes

Replacing a faulted system disk or "readzilla" read cache SSD can trigger the problem.

Cause

This is caused by a known problem with the SATA driver used by the SSDs and HDDs in the head unit.

The problem leads to the nv_sata port associated with the drive becoming locked up.

See <Bug 7023548> Replacement Failed for Faulted Readzilla

Check for the locked nv_sata port with mdb -k:

> *nv_statep::walk softstate | ::print nv_ctl_t nvc_port[0] nvc_port[1] | ::print nv_port_t nvp_state

nvp_state = 0

nvp_state = 0

nvp_state = 0

nvp_state = 0

nvp_state = 0

nvp_state = 0

nvp_state = 0

nvp_state = 0

nvp_state = 0x4c       <---- PORT LOCKED IN RESET

nvp_state = 0

nvp_state = 0

nvp_state = 0

Solution

The problem is fixed in appliance software release 2011.1.3.0 or later, which is available for download since May 14. 2012.

The workaround to release the nv_sata port prior to upgrading to the 2011.1.3.0 code will be to reboot the system. This reboot can be scheduled for a quiet period to minimize impact on production.

A reboot is the only way to workaround the problem for System Disks, however if the problem is with a Read Cache SSD then another possibility is to add the replacement SSD to a different empty slot if one is available.

The readzilla can then be added to the appropriate pools configuration using

s7000-a:> configuration storage add

See <Document 133120.1> for further details.

To get the faulted Read Cache SSD device removed from the pool please contact Oracle Support who can carry this out via a shared shell session.

To remove the faulted readzilla:

Example:

# zpool status pool-0

<skip>

        cache
          c0t0d0                                       FAULTED    0     0     0
          c9t0d0                                       ONLINE       0     0     0

# zpool remove pool-0 c0t0d0

# zpool status pool-0

<skip>

cache
c9t0d0 ONLINE 0 0 0

References

<NOTE:133120.1> - OSP-FCOMP: SellingPoint Functional Companions - Setup
@ <BUG:7023548> - NEED SOURCE CODE FOR OIM UI CUSTOMIZATION

Attachments

This solution has no attachment