So, I am proceeding to keep running the scf scannow.
2 Boservations:
1 - When I first ran it earlier in the day I saw many corrupt files which looked ancient. Then, I renumbered the dunsil drive that was left in the machine when the Dell guy left years ago. So, I decided to just go in and disconnect it as maybe the SCF was looking at it to find those corrupt files. I did so and the first Scf that I ran after that there were no longer any more corrupt file messages.
So, that seems to be good, but the first scf run after that sill found errors that could not be corrected. I am going to keep running it for up to x times. hehe
But, that is not all. After removing the dunsil J drive, there was only 1 drive left. So, somehow, the 2nd Dell guy that came go confused and took out my second RAID drive instead of the dunsil J drive. He was younger than the first guy as the first guy got tied up with something on the NYSE downtown. So, all these years I thought I was RAID protect but I was not. LOL
But, I will fix this once, I have a fixed system by writing a AOMEI backup and reinitializing two RAID drives then restoring. Until recently I have not had any problem with AOMEI --- better than Paragon and Acronis which I paid for but were not supported.
Boggin, you mentioned Marcum Reflex; I remember trying that like 5+ years ago and I could not get a full restore like AOMEI gave me. Maybe different now. Dunno.
2- The first time I ran the SCF while the J drive was there, the Windows drive was E. After removing the J dunsil the Windows drive was D.
But when the scf finished it said the CBS log file was on C:
Should I try scf using the C drive and the off and dir?