unable to run autochk on C drive on a windows server 2008 R2 Domain Controller

I have a Windows server 2008 R2 and it's a Domain Controller; It's  running as a VM on an ESXi 5.5 host. All of the volumes on this server are on the host local hard disks in RAID5.  All 5 FSMO roles are on this DC.
Okay here is the issues:
It's currently experiencing issues with installing windows updates and Symantec Backup Excec 2010 is not able to back up its System State. I see in the system event log, Event ID 55 "The file system structure on disk is corrupt and unusable. Please run the chkdsk utility on the volume C." When I rebooted the server, it would automatically Autochk or chkdsk on C:. However, it would always stuck at this message. See attached.
Questions:
I wanted to know if it's safe to boot into Recovery Environment by going to "Repair My Computer" at the windows startup menu (by hitting F8 key at starup) and run chkdks /F or /R command from the command prompt. This is a DC so I wanted to be very careful. Has anyone done this before on a Windows server 2008 R2 DC in a similar situation?
C-drive---corrupt-error.docx
efrias01Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Lee W, MVPTechnology and Business Process AdvisorCommented:
You said this was a VM.  

Make a FULL BACKUP (copy the vmdk if you must) and then attach the drive to another VM and run CHKDSK from that.
0
efrias01Author Commented:
yes, it's a VM.
0
Seth SimmonsSr. Systems AdministratorCommented:
if you have other domain controller(s) you have another option - just rebuild this domain controller
otherwise, as lee stated, make sure you have a good backup before doing anything else (don't make a snapshot)
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
The Ultimate Tool Kit for Technolgy Solution Provi

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy for valuable how-to assets including sample agreements, checklists, flowcharts, and more!

efrias01Author Commented:
Thanks, Lee and Seth. I will put that on my list of options. Have you tried running "Repair MY computer" at F8 startup and run chkdsk /F or /R at the recovery command prompt? I wanted to do that but don't know how risky it is. It sounds like it might just be as risky as running chkdsk on it from another VM.
0
Seth SimmonsSr. Systems AdministratorCommented:
either that or boot from the media and choose recover and try chkdsk from there; might be less of a chance that way of C being in use.  shouldn't be any risk
0
noxchoGlobal Support CoordinatorCommented:
In regedit navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager
In the right pane find BootExecute. Double click on it.
What values does it have?
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.