![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||||||||||
Solution Type Problem Resolution Sure Solution 2019567.1 : Sun StorageTek RAID Manager : How to Handle Bad Stripe Entries On a Logical Device
In this Document
Created from <SR 3-10751529721> Applies to:Sun Storage J4500 Array - Version All Versions to All Versions [Release All Releases]Sun Storage J4400 Array - Version All Versions to All Versions [Release All Releases] Sun Storage J4200 Array - Version All Versions to All Versions [Release All Releases] Sun Storage 3Gb SAS RAID HBA, External - Version Not Applicable to Not Applicable [Release N/A] Information in this document applies to any platform. SymptomsSun StorageTek RAID Manager will report errors similar to the following due to media errors on multiple drives. From the RAID event logs : May 15, 2015 2:57:47 PM CEST WRN 215:A01C-S--L-- <...> One or more logical devices contain a bad stripe: controller 1. From arcconf getconfig output : Logical device number 2 The above errors indicate bad stripes on logical device 2. The Sun StorageTek RAID Manager GUI will display a yellow exclamation point on the logical device. Right-click on the icon and select Properties to find the error. ChangesThe Bad Stripe Table tracks stripes across a logical drive that contains invalid or incomplete data.The table is stored in an area that is reserved for configuration information on each physical disk grouped into an array that hosts one or more logical drives. There is a separate table for each logical drive. CauseA bad stripe entry can occur primarily due to one of the following scenarios:
In the instances when a bad stripe has occurred, the data contained within that stripe is incomplete, invalid, or inconsistent between the data and parity and a Bad Stripe Table entry is created to block that stripe to prevent hidden data corruption. Solution
Replace the underlying faulty disks. Verify the data integrity and restore data if required. This action will not clear the Bad Stripe Table entries. There is no procedure or tool for clearing or repairing bad stripes while maintaining the existing array. In order to clear the bad stripe entries there are only two methods (both are destructive).
The customer is 100% responsible for backing up and restoring the data within the array as this procedure will erase the existing data. Remove or delete the existing array configuration from the physical disks associated to the array with the affected logical drive, and then create an identical new configuration, which will overwrite any previous existing configuration data. The Bad Stripe table will be re-written and will start with zero entries. Method two: This is identical to method one, but has an additional step. After the existing configuration is removed from the physical disks, do a low-level format on each physical disk, and then create an identical new configuration. This provides an additional benefit of verifying that the drives are error-free. Once the selected operation is completed, check the Array/Logical Device health to ensure "Bad Stripes" are no longer present,
# /Opt/StorMan/arcconf getconfig 1
Logical device number 2
References<NOTE:1312847.1> - Oracle Explorer Data Collector Resource Center<NOTE:1296274.1> - How to Download Common Array Manager (CAM) Software and Patches Attachments This solution has no attachment |
||||||||||||||||||||
|