Skip to main content

Repair Data Parity

The Repair Data Parity command repairs data parity errors.

Supported Arrays​

This command applies to an individual DE2000H, DE4000H, DE4000F, DE6000H, or DE6000F storage array.

Roles​

To execute this command on an storage array, you must have the Storage Admin role.

Context​

Before utilizing this command, consult with Lenovo Support for guidance on the affected firmware, drives, and RAID stripe.

Syntax​

repair volume[volumeName] parity
   [startingLBA=LBAvalue]
   [endingLBA=LBAvalue]
   [repairMethods=(repairMethod . . . repairMethod)]
           Space delimited list where possible repair methods are: reconstruct, unmap, updateP, updateQ, updateData, and writeZeros
   [repairPI=(TRUE|FALSE)]
   [suspectDrives=(trayID1,[drawerID1,]slotID1 . . . trayIDn,[drawerIDn,]slotIDn)]
   [timeout=(0-65535)]

Parameters​

ParameterDescription
volumeThe name of the volume for which you are repairing parity. Enclose the volume name in square brackets ([ ])
startingLBAThe starting logical block address.
endingLBAThe ending logical block address.
repairMethodsThe method used to repair the parity error. Available methods include:
  • reconstruct: Reconstructs drives specified under the suspectDrives parameter.
  • unmap: For R5/R6 dulbe volumes, used to make a R5/R6 RAID stripe unmapped
  • updateP: Used to fix the data parity mismatch type.
  • updateQ: Used to fix the data parity mismatch type.
  • updateData: Used to fix the data parity mismatch type.
  • writeZeros: For R5/R6 dulbe volumes, used when an unexpected RAID5/6 stripe containing a mix of mapped and unmapped data is found. Takes the unmapped blocks in the stripe and write zeros to it and then updates parity
repairPISet to TRUE to repair PI in the extent beginning at startingLBA.
suspectDrivesUsed to specify the drives for reconstruction.
timeoutThe length of time in minutes that you want to run the operation.

Minimum Firmware Level​

11.60.3