Critical Faults for Unreadable Sectors on a Sun Storage[TM] RAID Array

Asset ID:	1-72-1019826.1
Update Date:	2011-05-10
Keywords:

Solution Type Problem Resolution Sure

Solution 1019826.1 : Critical Faults for Unreadable Sectors on a Sun Storage[TM] RAID Array

Applies to:

Sun Storage 6140 Array
Sun Storage 6540 Array
Sun Storage Flexline 240 Array
Sun Storage Flexline 280 Array
Sun Storage Flexline 380 Array
All Platforms
***Checked for relevance on 10-May-2011***

Symptoms

A Critical Fault is generated similar to the following:

Alarm ID  
: alarm1
Description: The unreadable sectors database is full. 
Sector count is 1000
Severity   : Critical
Element   
: 
GridCode   : 57.66.1074
Date      
: 2008-12-03 12:33:53

Alarm ID   :
alarm2
Description: Unreadable sectors exist.  Current count
is 1024
Severity   : Critical
Element   
: 
GridCode   : 57.66.1075
Date      
: 2008-12-03 12:33:55

Cause

The term Unreadable Sector refers to a volume logical block address that has been rendered completely unreadable due to a disk media-related double fault condition on redundant volumes or a disk media-related single fault condition on non-redundant volumes (RAID 0). Any user data contained within the unreadable sector is unrecoverable and should be considered lost.

Once an unreadable sector is detected and an entry is placed in the database for it, all future reads to that sector result in a media error being returned for the read. The entries in the database persist until the affected sectors are written by a host or internal write command, or explicitly cleared by a user action.

Solution

The unreadable sector database is used to count the number of logical block allocations (LBA) on a given volume. It can only hold around 1024 entries total.

Verify the Critical Fault. Refer <Document 1021057.1> Verify Sun StorageTek[TM] 2500 and Sun Storage[TM] 6000 and J4000 Critical Faults via the User Interface.
- If you have unreadable sectors on your array and have identified the cause, take the necessary action to resolve the cause and go to Step 2.
- If you have unreadable sectors on your array, but have not identified the cause, go to Step 3.
- If you have no alarm, go to Step 3.
Clear the unreadable sectors list:
- For Common Array Manager (CAM).
  
  Location for sscs:
  
  Solaris: /opt/SUNWstkcam/bin/
  Linux: /opt/sun/cam/bin/
  Windows: C:\Program Files\Sun\Common Array Manager\bin
  
  Location for service:
  
  Solaris: /opt/SUNWsefms/bin/
  Linux: /opt/sun/cam/private/fms/bin/
  Windows: C:\Program Files\Sun\Common Array Manager\Component\fms\bin\
  1. Get the array name:
    
    Example:
    # sscs list array Array: myarray #
  2. Clear the unreadable sectors list:
    
    service -d <arrayname> -c reset -q usm -t <volume name>
    
    Example:
    # service -d myarray -c reset -q usm -t myvol
- For Santricity.
  1. Open the Array Management Window.
  2. Open the Advanced Menu.
  3. Open the recovery Sub-Menu.
  4. Select "unreadable sectors".
  5. Select all and clear them.
Collect a Support Data and contact Oracle Support:
- Refer <Document 1014074.1> Collecting Support Data for Arrays Using Sun StorageTek[TM] SANtricity Storage Manager.
- Refer <Document 1002514.1> Collecting Sun StorageTek[TM] Common Array Manager Array Support Data.

Attachments

This solution has no attachment