Hi,
I purchased ESET virus protection for WHS (original), which I was told was compatible by their sales group. Unfortunately, I believe that may not be true as I ran it on my system and it deleted 44 files and caused a number of file conflicts on my system.
I have been attempting to resolve the issues caused by the ESET program since mid Dec as I have had time to deal with it. Unfortunately, the ESET log is very large and was somehow corrupted. I have been working with their support to figure out what it did, but they can only partially read the log themselves so I have had to resort to other means to figure out what happened.
I used the Conflict Resolver add-in to get a handle on the WHS's problems - it is a wonderful program - and have corrected those problems. WHS Console noted that one of my shared drives was in an unhealthy state, so I ran chkdsk using Ken Warren's script (see below)
net stop pdl
net stop whsbackup
chkdsk D: /x /r
chkdsk C: /x /r
for /d %%1 in (C:\fs\*) do start chkdsk /x /r %%1
Ken notes that "rather than watch like a hawk for errors, let all the chkdsk runs finish unmonitored, then (on your server) check the applicaiton event log, source winlogon, for chkdsk reports."
Since I can only devote small amounts of time to this endeavour at a time, I followed his advice.
Here is where my latest problem is. There are entries for chkdsk in the application log, but none with source winlogon for the date I ran it. There are the normal chkdsk entries for the daily ones scheduled by WHS. I now have no idea what chkdsk found and fixed - sigh.
I did periodically check the status on the master command window, and noted that chkdsk did correct some file errors, but I didn't write them down and the command windows started by the " for /d %%1 in (C:\fs\*) do start chkdsk /x /r %%1" part of the script close once the chkdsk is complete.
I have not yet closed the master command window that I ran the original .bat file.
Does anyone know why chkdsk didn't leave a log entry? Is there another way to get it? Do I need to close the master command window first? Am I just hosed?
Also, if I am just hosed, is there a way to modify Ken's script to keep the command windows from "for /d %%1 in (C:\fs\*) do start chkdsk /x /r %%1" from closing in the future?
Thanks in advance for your comments and advise.
Forrest