And it is still going with some more corrections, this process has to complete as there is not a better time to handle it and it is abusing the server CPU as it tries to correct it during loads, having to log stats for awstats on a few sites it is using far excesses of CPU
Stage3 is taking far longer than I or anyone else could have ever guessed at this point, however it is NOT stuck as I can see progress and action correcting on files as it goes.
At this point it seems as if the security scan must be fixing the ACL on a good 50% of the files on the server, which is the reason for it taking so long, well beyond any time I ever could have imagined. It is still moving along quite swiftly but taking time.
My fear in stopping it where it is now is that it will have the problem still and require to be taken down during a weekday when traffic is much higher.
I am quite apologetic that this maintenance is still going on, however as you can see from the screenshot the security scan is fixing many errors that are being detected.
I have never seen before a stage3 of a scan do so much, it is typically one of the faster stages of the chkdsk process giving you a percentage complete and then continuing on rather quickly.
What happened to cause this was a few days back some abuse was really bogging the server down, and it was being so slow our only choice after 10 minute of work was to reboot the server, and ever since then it has been giving errors about needing to chkdsk and correct some entries for some awstats logsfiles. If did that in the first 2 stages of the process and now in the 3rd stage it is finding and correcting what seems to be large groups of files that were accessed between that reboot and now. It will sometimes skip a large section, then hit a section where it does many corrections again.
Win21 has been up for the last 10 minutes, we are just doing some checks to see if any of the awstats or 2 sites with errors are still having any trouble, and they seem to be working just fine now.