Jump to content

Recommended Posts

Posted

Last night I remotely rebooted all my servers, having done a Windows update. My student server failed to come back up, with a message it was "Scanning and repairing drive E:". This is a hyper-v virtual server. Never mind, I thought, we replicate for just this eventuality, so I powered on the replica - which had the exact same error message. One restless night later, the scan has completed, and I have a working server, albeit with a "found.000" directory on the E drive. the event log is remarkably clear on both the virtual server and the host - no relevant errors I can find.

 

So, what happened, and how do I prevent it happening again?

Posted

Sounds like the previous boot may have had a disk error scan aborted and this has been replicated.

 

I would take another replica and boot it off the network and check it now comes up clean.

 

TT

  • Thanks 1
Posted
Thanks for that suggestion - the replica booted without incident, which has set my mind at rest. Still not sure what triggered a disk scan in the first place - there are no disk errors on the host, so it can't be a physical problem.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...