chk820 instructions 1.3a

8/3/2019 Chk820 Instructions 1.3a

1/4

EMC Proprietary

Copyright EMC Corporation 2011. All rights reserved.

Chk820 Instructions V1.2

1. Create a directory structure where you have subdirectories for each set of SPcollects that you wish to run this toolagainst.

2. Extract Chk820.exe from the zip archive along with these instructions. The password for the executable is: EMC(upper case only)

3. Place the executable into each folder of SPcollects4. Copy a set of recent SPcollects (SPA/SPB) for each individual array to the appropriate subdirectory.

that you wish to run this tool against.

IMPORTANT: KEEP THE SPCOLLECT FILENAME STRUCTURE - Do not rename them

(Subdirectory filenames are used in recursive mode to name Excel files and error files) SPA and SPB have more or less

the same log information but there can be differences due to time of execution, there are no unique identifiers for each

log entry, so there is no way to filter some out duplicates.

To execute chk820.exe, start at the command prompt :

Change directory to your SP collect folder (ensure your chk820 executable is there)o For reference I usedC:\Check820\Spcollects for VNX5700>chk820 in this Document

Execute chk820.exe with the -efd switch

Or you can execute chk820.exe with the -r recursive command

The tool will output various findings during execution.


2/4

EMC Proprietary


When it has completed, you will have a listing of .xls files in the SP collect folder like the following image:

Examine the "Errors sheet" in the xls files and verify the drive errors. If you only interested in EFD drives, use the efd command line option when you run the tool and it will search

for the strings SSD, Flash and efd in disk type field.

NOTE:There will be no XLS file if no errors were found.

APPENDIX:Regarding a customers plan to use the tool for continuous checks, we believe the monitoring Knowledgebase Solution

emc283186 is much better. This tool should be utilized as a historical check, where as emc283186 actively monitors

these events.

There may be customers that cant use emc283186 due to mail restrictions, so a few new parameters [date] and [

last [ -force ] [checklast]] have been added.

Use h to display help and syntax options.


3/4

EMC Proprietary


date Enter an earliest start date like 2011/12/01

Example

Chk820.exe r -date 2011/11/22

Ifdate is specified it will be used. The first run on a file will always be checked fully or according todate parameter

If SP collects from new Array serial numbers are added to directory structure, all errors will be checked fully or

according todate parameter. NOTE: New SP collects from the same Array should be saved in same directory as theprevious set of files.

-totalerror andtotaldegradedare all 820 errors in a SP collect file for a specific disk.

last [ -force - checklast ] Will check new SP collect files you copy into the directory structure with a start time equal

to the last event found during a previous run. To find the last recorded events it is required that the Directory name

(Customer), Serial number and SP are the same.

NOTE: Make sure you leave Chk820.dbm.dir and Chk820.dbm.pag, these 2 files keep track oflast functionality

NOTE: If you dont use recursive mode then the Directory name is not used to find the last recorded event, only Serial

number and SP.

Files already checked will be skipped on the second and subsequent executions, unlessforce used

-force The optional argumentforce will clear the history and make a new run on all files in you directory structure.

Delete the 2 db files created in the SPcollect folder and make a clean run

checklast Use this to check an already checked file, chk820 should find no errors in the files because the last saved

timestamp was found in previous run.

NOTE: You might want to move the generated xls and errors.txt files out of you main directory between runs.

The optional argumentchecklast can be used to check functionality of the last recorded event. If you do the

following without adding new files between the 2 executions, the second run will not be able to find any 820 errors.

Notice the difference between the executions of the following 2 commands that are in screenshot below:

C:\ chk820

C:\ chk820 last -checklast


4/4

EMC Proprietary


chk820 instructions 1.3a

Documents