Hi Stephan , please could you support to us in the following question ?
we have a system 5.0 sp2 Rev C , If we need to do a health check of the system and we run the script E144_Show_ChkDisk.exe , you know we have the name of the nodes into Nodes txt file usually there are all the nodes written into , when we run the chkDisk script do we need to stop the Process Portal A from every connectivity nodes, when we run the script ? and it would be better to run it manually on each connectivity server at least this script , I mean to execute it on each connectivity server node manually one at the time , no all at the same time
Thanks for your support
when running the chkdsk BAT file (in a running 800xA node) you get a result in Excel showing which nodes having problems, which can be solved with chkdsk /f.
The operating system can only do chkdsk /f when restarting the computer,
so you write chkdsk /f and answer Y when the program ask you to do so.
Then you restart the computer.
The E144_Show_ChkDisk.exe runs in non-intrusive (checking only) mode and can be scheduled in a running system; there will be a performance loss, but since the script is sequential, only one computer at a time is targeted.
My experience of CHKDSK is that you often get FALSE positives, i.e. the check report an error which is either harmless, or not possible to fix with CHKDSK /F. I suggest preparing the owner of the system that there may be a lot of warnings, but that might not be so dangerous after all.
So, check if you like. Any repair (CHKDSK /F) will have to wait until you can perform Maintenance Stop, possibly also reboot since repairing C:\ need to be done before Windows startup.
I recommend to search in Windows Event Log for other disk related errors, e.g. "DISK Event ID 7" = bad block found. SATA disks may have S.M.A.R.T. attributes giving more details. A SCSI/SAS disk have counters as well, but you might need tools like a RAID controller to examine them.
In later SHCs of mine, I have elected to not run the diskcheck, rather look for evidence in Windows Event log and System Event List of 800xA.