Failed Drive Alarm May Not Clear Automatically After Drive Replacement When Drive is Assigned to an Empty VDISK

Asset ID:	1-72-1496245.1
Update Date:	2015-02-14
Keywords:

Solution Type Problem Resolution Sure

Solution 1496245.1 : Failed Drive Alarm May Not Clear Automatically After Drive Replacement When Drive is Assigned to an Empty VDISK

Applies to:

Sun Storage 2530-M2 Array - Version Not Applicable to Not Applicable [Release N/A]
Sun Storage 2540 Array - Version Not Applicable to Not Applicable [Release N/A]
Sun Storage 2540-M2 Array - Version Not Applicable to Not Applicable [Release N/A]
Sun Storage Flexline 380 Array - Version Not Applicable to Not Applicable [Release N/A]
Sun Storage 6540 Array - Version Not Applicable to Not Applicable [Release N/A]
Information in this document applies to any platform.

Symptoms

After a failed disk drive is replaced, the new disk reports as Optimal, however, the alarm for the disk failure never clears.

Event Code : XX.66.1023
Description : Drive Tray.YY.Drive.ZZ failed.

This problem is only known to occur in 25x0 and 6xx0 arrays running 7.x versions of controller firmware.

Changes

The failed Disk Drive was replaced in the array.

Cause

The problem occurs when the disk is a member of a Virtual Disk (aka Volume Group) that has NO associated volumes. Since there is no data to reconstruct, the array does not clear the failed drive condition.

Solution

Verify the alarm.

# ./sscs list alarm
...
Alarm Id         : alarm352
Severity         : Critical
Type             : 6180.ProblemEvent
Topic            : Tray.85.Drive.01
Event Code       : 90.66.1023
Date             : 2012-10-04 07:31:56
Device           : 6180-1[SUN.16502-00.1T54402516]
Description      : Drive Tray.85.Drive.01 failed.
State            : Open
Acknowledged By : -
Auto Clear       : Y
Aggregated Count : 0
...
#
Verify the drive is part of a Virtual Disk by first listing the Virtual Disks in the array:

# ./sscs list -a 6180-1 vdisk
Virtual Disk: 1
#
Verify that the Virtual Disk has no volumes in it by listing the details of that Virtual Disk(s):

# ./sscs list -a 6180-1 vdisk 1
Virtual Disk: 1
Status:               Optimal
State:                Ready
Number of Disks:      5
RAID Level:           5
Hot Spare Coverage:   No
Total Capacity:       544.911 GB
Configured Capacity: 0.000 MB
Available Capacity:   544.911 GB
Array Name:           6180-1
Array Type:           6180
Disk Type:            Fibre Channel
Security:             Non-secure
Maximal Volume Size: 544.910 GB
Associated Disks:
    Disk:               t85d01
    Disk:               t85d02
    Disk:               t85d03
    Disk:               t85d04
    Disk:               t85d05
#

In the above example, we can see that the failed drive (Tray.85.Drive.01) is associated with this Virtual Disk but that there is no configured capacity.
Delete and the Virtual Disk:

# ./sscs delete -a 6180-1 vdisk 1
# ./sscs list -a 6180-1 vdisk
#

Note: so long as no volumes are associated with the Virtual Disk - no data will be lost.

Wait for at least 5 minutes for the problem to clear, if the problem persists, please contact Oracle support for further assistance.

Attachments

This solution has no attachment