Server 2008 R2 machine with corruption SFC can't fix

[aef_wg]

Hi everyone,

Found you guys while looking for a fix for SFC issues and wanted to see if you can help. A client of ours has a 2008 R2 box (don't worry, it's being decomm'd, just...slowly) and has recently begun having VSS issues despite the VSS writers not reporting any errors. Their backups are failing and previous versions internally are also affected. Chkdsk didn't do anything, SFC just reports it can't fix what it found, and DISM apparently doesn't have the /RestoreHealth flag like on newer systems. I ran SFCFix and it was also unable to fix the issue, so I've attached the log for review. Thanks in advance!

 

[Sysnative Windows Update]

Hi!


GSmartControl
Follow the instructions below to check your SMART status with GSmartControl:

• Download the portable version of GSmartControl and save it on your Desktop;
• Extract the zip file to your Desktop. Open the folder gsmartcontrol-1.1.3-win64 which should be located on your Desktop and double-click gsmartcontrol.exe to launch the program.
• Identify your drive in the list (if recognized by the tool), and hover your mouse over it.
• You should see something called: SMART status. It will either read: Enabled, in which case you should do the following:
• Double-click on it to bring up its window (usually you'll find your drive by its size or its brand name);
• Go to the Self-Tests tab, then select Extended Self-test in the Test type drop-down list and click on Execute (this test can take a few hours to complete);
• Once the test is over, the results will be displayed at the bottom of the window. Please copy and paste these results in your next reply or take a screenshot;
• Also, go in the Attributes tab and if you have any entries highlighted in red or pink, take a screenshot of the GSmartControl window and attach it in your next reply;
• Please note: If the SMART Status reads: Unsupported, stop and let me know.
  
  

 

[aef_wg]

Hi softwaremaniac,

GSmart says SMART is unsupported. The server is running a raid5, so that might be why. We're aware of issues on the drives that are reported in the DRAC and have already replaced one. A replacement for the other drive is en route. We're pretty sure the drive issues are related to this issue, but I've been looking into repairing the SFC issues in the meantime/if replacing the drives doesn't resolve the issue. LMK your thoughts.

Thanks.

 

[Sysnative Windows Update]

If the drives have issues, you can't really completely and reliably repair SFC as the damage had already been done.