Dell PowerVault MD3420 - Manual (Page 379)

Parameter Description
parameter is set to disk,
the peer RAID controller
module initiates a block
check.
• When the
sourceLocation
parameter is set to
cache, the peer RAID
controller module
initiates a record check.
contentCheck This option performs a deep
analysis of each record's
contents.
The default value is fileSystem.
raidControllerModule The RAID controller module that has the database
on which you want to run the diagnostic tests.
Valid RAID controller module identifiers are 0 or 1,
where 0 is the RAID controller module in slot 0,
and 1 is the RAID controller module in slot 1.
Enclose the RAID controller module identifier in
square brackets ([ ]).
Notes
This command runs a consistency check against a configuration database. All database records are
checked. Error data is written to a file in the data folder on disk automatically. You do not need to specify
an output file.
NOTE: Executing a consistency check with the diagnosticType parameter set to a value other
than filesystem, and with the sourceLocation parameter set to onboard, can cause the
operation to run for a long time. This can have adverse effects on host I/O processing. This
operation should be done only under direction from the support organization.
Upon completion of the diagnostic test, the RAID controller firmware returns one of these results:
• Diagnosis completed without errors. No ZIP file created.
• Diagnosis completed with errors. Refer to the ZIP file created at:
...\Install_dir\data\FirmwareUpgradeReports\timestamp_buildNo.zip
If the diagnostic test detects an inconsistency in the configuration database, the RAID controller module
firmware performs these actions:
• Returns a description of the inconsistency
• Saves a ZIP file containing raw binary data
The RAID controller module firmware saves the ZIP file to this location:...\Install_dir\data
\FirmwareUpgradeReports\timestamp_buildNo.zip
You can use the binary data to help determine the cause of the problem, or you can send the file
containing the binary data to a Technical Support representative.
379