![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||||||||||||||||||
Solution Type Problem Resolution Sure Solution 1967469.1 : How to fix a Failed Stripe in an Adaptec Card Stripe Array
In this Document
Created from <SR 3-10201302871> Applies to:Sun Fire X4275 Server - Version All Versions to All Versions [Release All Releases]Sun Fire X4450 Server - Version All Versions to All Versions [Release All Releases] Sun Fire X4140 Server - Version Not Applicable to Not Applicable [Release NA] Sun Fire X4240 Server - Version All Versions to All Versions [Release All Releases] Sun Fire X4170 Server - Version All Versions to All Versions [Release All Releases] Information in this document applies to any platform. SymptomsArcconf command 'arcconf getconfig 1' reports a Failed/bad stripe in a Logical Device (array) CauseA bad stripe is essentially a stripe level RAID failure, although instead of taking the entire logical drive off-line, only the data within the stripe becomes unavailable. A bad stripe entry is then made to the Bad Stripe Table and becomes a part of the array and logical drive configuration. How does a Bad Stripe Table (BST) entry occur? A BST entry can occur primarily due to one of the following scenarios:
SolutionImportant InformationThe customer is 100% responsible for backing up and restoring the data within the array as this procedure will erase the existing data. There is no procedure or tool available for clearing or repairing a bad stripe while maintaining the existing array. 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. There are only two suggested methods for clearing the reserved areas of the drives and both are destructive to the data stored on the physical disks. Backing up the good data on the drives is recommended before any changes to the configuration are made. The first method is to remove or delete the existing array configuration from the physical disks associated to the array with the affected logical drive, then create an identical new configuration, which will overwrite any previous existing configuration data. The BST will be rewritten and will start with zero entries. The second method has one 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 the drives are error free. To destroy the array, format the drives and re-create the array, follow these instructions:
Destroy the array- Enter the Array Configuration Utility
Format / Secure Erase the Hard Drives- Enter the Array Configuration Utility
Create a new Stripe array- Enter the Array Configuration Utility
ResultOnce this operation is completed, you will see the new Array in the 'Manage Arrays' menu. After this, you can exit the configuration utility and reboot the system. ---------------------------------------------------------------------- Logical device information ---------------------------------------------------------------------- Logical device number 0 Logical device name : RAID level : 10 Status of logical device : Optimal <<<<<<<< Size : 1142784 MB Stripe-unit size : 256 KB Read-cache mode : Enabled Write-cache mode : Enabled (write-back) Write-cache setting : Enabled (write-back) when protected by battery Partitioned : Yes Protected by Hot-Spare : No Bootable : Yes Failed stripes : No <<<<<<<<
References<NOTE:1598315.1> - Resolving "One or more logical devices contain a bad stripe" issue reported from "Adaptec RAID Controller" (aka Cougar or Prometheus) logical drive.Attachments This solution has no attachment |
||||||||||||||||||||||||||||
|