Sun Storage Flexline 240 Array
 
Sun Storage Flexline 380 Array
 
Sun Storage 6580 Array
 
Sun Storage Common Array Manager (CAM)
 
Sun Storage 6540 Array
 
Sun Storage Flexline 280 Array
 
Sun Storage 6180 Array
 
Sun Storage 2510 Array
 
Sun Storage 2540 Array
 
Sun Storage 6130 Array
 
Sun Storage 6780 Array
 
Sun Storage 2530 Array
 
Sun Storage 6140 Array
 

PLA-Support>Sun Systems>DISK>Arrays>SN-DK: 6130
 
.Old GCS Categories>Sun Microsystems>Storage Software>Modular Disk Device Software
 

Applies to:

Symptoms

A Critical Fault is generated similar to the following:

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.

1.  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 a 66.1074 or 66.1075 critical fault, continue to Step 2.
• If you do not have one of these faults, then the array has not detected any data loss, and no further work is required.

2.  Identify the Volume(s) that have the unreadable sectors. 

This can only be viewed by looking at the badBlocksData.txt file which is contained in a support collection.   Collect/Create this data and unzip it.  Then review the badBlocksData.txt file

• 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.

3.  Recover and Restore the volume(s) that have the LBA errors

The data in these volumes are considered corrupt and should be restored.  Whether this has impacted any application or not is unknown, however the data needs to be restored to recover the fault.  Once
the blocks have been written to again, the entries will be removed from the list and the fault will
clear.

If there are other faults for drive failures for the same volumes, then these should be handled prior to the restore of the data.  Any subsequent writes will cause any drives that may be marginal to fail
for replacement.

Once a restore has been completed for all volumes affected, continue to Step 4.

4.  Clear the unreadable sectors list if it has not been cleared by Step 3

For Sun Storage Common Array Manager (CAM)

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.

If the issue persists, collect a Support Data and contact the 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.

References

This solution has no attachment