Resolving Scrub Errors - HP P2000 Reference Manual

Resolving scrub errors

Certain conditions such as bad blocks in a disk, the failure of multiple disks at the same time, or an
enclosure failure can cause the scrub utility to find a parity discrepancy error. Follow the directions below
to recover from such events.
NOTE: This procedure will not correct scrub errors caused by a failing or failed disk. This would typically
be taken care of by letting vdisk reconstruction complete. Do not follow this procedure when reconstruction
is running or needs to run. Let reconstruction complete before taking further action. Parity errors caused by
a failing disk may be corrected by replacing the failed disk. Disks that have logged SMART events or
Unrecoverable Read Errors may be candidates for replacement.
To resolve scrub issues
1. Ensure that the storage system's firmware version is one of the following or newer:
J200P39, J210P19, J300P20, M1 10R21, TS100
2. Ensure that the storage system's hardware is healthy and stable.
3. Create a full backup of all data in the vdisk. HP recommends enabling all available verification
options. Use tools to verify the data integrity of the backup.
4. Correct any hardware issues. Failed or failing controllers, power supplies, I/O modules, or other
components all contribute to causing scrub to log an error.
5. After completing the above steps, if parity errors continue to be reported, perform the procedure below.
To fix parity errors reported by the scrub utility
In this procedure you will use the CLI verify vdisk command with its fix parameter, hereafter referred
to as "verify-fix." Verify-fix corrects parity based on the data in the stripe at the present time.
NOTE:
• Verify-fix recalculates parity for the failed stripe.
• Verify-fix does not compare parity to data.
• If there is a problem with the data prior to running verify-fix it will make parity match the incorrect data.
• Running verify-fix before checking data validity has the potential to correct the parity on bad data. Take
extreme care to protect data before correcting the parity.
1. Complete the steps in
2. Save the current logs from the storage system in a safe location:
a. Log in to the system's FTP interface.
b. Enter:
get logs file-name.zip
3. Disable background scrub:
a. Log in to the CLI.
b. Enter:
set job-parameters background-scrub off
4. Verify that scrub is not running on the affected vdisk. If scrub is running on the vdisk, either:
• Wait for it to complete.
• Manually abort the scrub by logging in to the CLI and entering:
abort scrub vdisk vdisk
46
To resolve scrub issues above.