Попробуйте включить trust. Но это ничего не гарантирует.
Подключись консолью к контроллеру
#
help trust
DESCRIPTION
Enables an offline vdisk to be brought online for emergency data recovery.
This command must be enabled before each use. If used improperly this command
can cause unstable operation and data loss; before use, carefully read the
cautions and procedures below.
The trust command provides an opportunity to recover data from a vdisk that has
gone offline due to disk failure. The command forces a resynchronization of the
metadata (as well as time and date stamps) that unifies members of a vdisk, and
essentially puts the vdisk back into an accessible state. As long as the failed
disks are operable, data can be read from the disks and restored to another
location.
From examining the state of the disks, if the command determines that the trust
operation is unsafe--that it may result in an unstable vdisk with data
corruption--the command will fail. You may then seek assistance from technical
support or run the command with a special parameter to acknowledge the risk of
proceeding. Otherwise, if the command determines the operation to be safe, the
command will proceed.
When the "trusted" vdisk is back online, back up its data and audit the data
to make sure that it is intact. Then delete that vdisk, create a new vdisk, and
restore data from the backup to the new vdisk. Using a trusted vdisk is only a
disaster-recovery measure; the vdisk has no tolerance for any additional
failures.
The following procedure outlines the general steps for performing a trust
operation. Before starting this procedure, consult the online
troubleshooting guide at
https://www.hp.com/go/p2000/troubleshooting to
Press any key to continue (Q to quit)
determine if the trust operation is applicable to your situation and for
guidance to perform it.
Caution:
1. Do not use the trust command when the storage system is unstable; for
example, if there are many power or topology-change events.
2. The trust command cannot be run on a quarantined vdisk. In many cases the
vdisk will be automatically dequarantined. If you cannot resolve the issue
that caused the disk to become quarantined such that it is automatically
dequarantined, and if the trust operation is applicable to your situation,
dequarantine the vdisk, confirm it is in offline state by using the "show
vdisks" command, and then proceed to trust.
3. Never update controller-module, expansion-module, or disk firmware when the
vdisk is offline.
4. Never clear unwritten data cache when a vdisk is offline.
5. Do not use the trust command on a vdisk that went offline during vdisk
expansion.
6. Do not use the trust command on a vdisk with status CRIT. Instead, add
spares and let the system reconstruct the vdisk.
Steps for running the trust command:
1. Disable background scrub of disks and vdisks to avoid running scrubs
automatically.
2. Identify the cause for the vdisk going offline.
3. If an external issue (power, cabling, and so forth) caused the vdisk to go
offline, fix the external issue before continuing to the next step.
4. Disable host access to the offline vdisk. In a single-controller
configuration, disconnect the host-port cables. In a dual-controller
configuration:
a. Determine the owning controller of the offline vdisk.
b. As a precautionary measure, remove the host-port cables of the owning
controller of the offline vdisk.
5. Unseat the spare disks associated with the vdisk to prevent reconstruction.
Caution: It is recommended to avoid reconstruction after using the trust
command. Reconstruction causes heavy usage of disks that were already
reporting errors. This usage could cause the disks to fail during
reconstruction, which can cause data to be unrecoverable.
6. Enable the trust command.
7. Run the trust command on the vdisk.
8. If the trust command determines that it would be unsafe to proceed, it will
fail. If this happens you can either:
- Contact Support for further assistance. This is recommended.
- Proceed by re-enabling trust and running trust with the "unsafe"
parameter. This is not recommended because in most cases it will result in
an unstable vdisk with data corruption.
After running the trust command:
1. Reinsert the host-port cables.
2. Perform a complete backup of the vdisk.
3. Delete the vdisk.
4. Replace the failed disks with new disks.
5. Re-create the vdisk.
6. Restore the data from the backup performed in step 2.
7. Restore original vdisk ownership.
8. Re-enable background scrub operations.
INPUT
trust
[enable|disable]
[vdisk <vdisk>]
[unsafe]
enable|disable
Optional.
- enable: Enables the trust command before use.
- disable: Disables the trust command if it is not used after being enabled.
If trust is not explicitly disabled, it will be automatically disabled when
the user's CLI session ends.
vdisk <vdisk>
Optional. The name or serial number of the vdisk to trust. For vdisk syntax,
type "help syntax".
unsafe
Optional. Specifies to proceed with a trust operation that is determined to
be unsafe because it must use out-of-sync or partially reconstructed disks,
which in most cases will result in an unstable vdisk with data corruption.
OUTPUT (WITH THE UNSAFE PARAMETER)
Location
The enclosure ID and slot number of the disk.
Serial Number
The serial number of the disk.
Type
SAS: Dual-port SAS
SAS-S: Single-port SAS
SATA: Dual-port SATA
SATA-S: Single-port SATA
State
AVAIL: Available
FAILED: The disk is unusable. Reasons for this status include: excessive
media errors; SMART error; disk hardware failure; unsupported disk.
GLOBAL SP: Global spare
LEFTOVR: Leftover
VDISK: Used in a vdisk
VDISK SP: Spare assigned to a vdisk
Partially Recon Target
- True: The disk contains partially reconstructed data.
- False: The disk does not contain partially reconstructed data.
Out Of Sync
- True: The disk data is out of sync with other disks in the vdisk.
- False: The disk data is in sync with other disks in the vdisk.
Age
The age of the disk in the vdisk. The age value starts at 1 and is
incremented for all good disks in the vdisk each time there is a change in
the disk configuration of the vdisk, such as when a disk is detected to have
failed or be missing. Therefore, if a disk has a lower age than other disks
in the vdisk, that disk is out-of-sync with the other vdisk members. This
value can be used as a guide to decide which disks to physically remove
before doing the trust operation to minimize the amount of corrupt data in
the trusted vdisk if you want to use the "unsafe" parameter.
EXAMPLE
Trust a vdisk which has enough good disks to complete the trust operation. The
vdisk may have out-of-sync or partially reconstructed disks but they are not
needed to complete the trust operation. The command completes successfully.
# trust enable
Success: Command completed successfully. - Trust is enabled. (2013-09-17
04:29:28)
# trust vdisk VD1
Success: Command completed successfully. (VD1) - Trust operation completed
successfully for this vdisk. (2013-09-17 04:29:35)
Trust a vdisk which does not have enough good disks available to complete the
trust operation. The command fails.
# trust enable
Success: Command completed successfully. - Trust is enabled. (2013-09-17
04:12:49)
# trust vdisk VD1
Error: The trust operation failed because the vdisk has an insufficient
number of in-sync disks. - Please contact Support for further assistance.
(2013-09-17 04:13:13)
Trust a vdisk which has out-of-sync or partially reconstructed disks that would
be needed to complete the trust operation. The command fails.
# trust enable
Success: Command completed successfully. - Trust is enabled. (2013-09-17
09:06:41)
# trust vdisk VD1
Error: Command failed. - The vdisk specified contains out-of-sync or
partially reconstructed disks that are necessary to restore the vdisk to an
accessible state. Continuing with the trust operation may lead to data
corruption. Please contact Support for further assistance. (2013-09-08
09:06:46)
Continuing the previous example, you decide to re-enable trust and proceed by
specifying the unsafe parameter.
# trust enable
Success: Command completed successfully. - Trust is enabled. (2013-09-17
09:06:48)
# trust vdisk VD1 unsafe
Location Serial Number Type State Partially Reconstructed Out Of Sync Age
-----------------------------------------------------------------------------
1.2 <SN> SAS LEFTOVR False True 6
1.4 <SN> SAS VDISK False False 7
1.5 <SN> SAS LEFTOVR True False 4
-----------------------------------------------------------------------------
WARNING: Found partially reconstructed and out-of-sync disk(s). Using these
disks for trust will in most cases cause data corruption.
Because of the risk of data corruption, it is recommended that you continue
the trust operation only with the supervision of Support personnel. If you
are ready to continue, enter "continue" at the prompt or enter "abort" to
abort the operation and leave the vdisk offline.
> continue
If you continue with the trust operation, you risk corrupting data in this
vdisk. Enter "accept" at the prompt if you intend to accept this risk and
proceed with the trust operation or enter "abort" to abort the operation and
leave the vdisk offline.
> accept
Success: Command completed successfully. (VD1) - Trust operation completed
successfully for this vdisk. (2013-09-17 09:07:31)
Abort an unsafe trust operation when you decide not to risk using bad disks.
# trust enable
Success: Command completed successfully. - Trust is enabled. (2013-09-17
09:05:37)
# trust vdisk vdr5 unsafe
Location Serial Number Type State Partially Reconstructed Out Of Sync Age
-----------------------------------------------------------------------------
1.2 <SN> SAS LEFTOVR False True 6
1.4 <SN> SAS VDISK False False 7
1.5 <SN> SAS LEFTOVR True False 4
-----------------------------------------------------------------------------
WARNING: Found partially reconstructed and out-of-sync disk(s). Using these
disks for trust will in most cases cause data corruption.
Because of the risk of data corruption, it is recommended that you continue
the trust operation only with the supervision of Support personnel. If you
are ready to continue, enter "continue" at the prompt or enter "abort" to
abort the operation and leave the vdisk offline.
> continue
If you continue with the trust operation, you risk corrupting data in this
vdisk. Enter "accept" at the prompt if you intend to accept this risk and
proceed with the trust operation or enter "abort" to abort the operation and
leave the vdisk offline.
> abort
Error: Command was aborted by user. (2013-09-17 09:05:49)
After enabling trust, disable it if you decide not to run "trust vdisk".
# trust disable
Success: Command completed successfully. - Trust is disabled. (2013-09-17
17:40:01)
RELATED COMMANDS
show vdisks
verify vdisk
#
