Disk errors detected on Virtual Machine


I am in process of migrating from SBS2008 to Server 2012
I just deployed new Server 2012 R2 as VM on HYPERV. Old SBS2008 is removed from domain, and everything worked nice and smooth.

The existing host machine is "custom" build server that I inherited from previous IT consultant.
It has Server 2008 enterprise installed, and since customer does not have license for it - I will be reinstalling free Server HYPERV 2012 R2, as soon as I am finished with the migration from the SBS2008.


On the newly deployed Server 2012 R2 (VM)  - I get a message from "Action Center" :

"Scan drive for errors" - when I do that it tells me to restart the server. Server restarts, but I do not see any indication that the check disk starts. Eventually server comes back up, and "Scan drive for errors" message appears again. Mind you this is VM so the disk is VHD.

I can't try at the moment to scan the Hyperv host's hdd, as this is production machine and it would have to wait to next weekend.

Did anybody encountered similar issue on VHD? Is this indication of the problems on the HOST?


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.

JohnBusiness Consultant (Owner)Commented:
The machine is a file on a hard drive, so the error can happen if there is a drive error where the machine is located. So it is not an impossible error.  Try, as you suggest, to scan the host machine.

There could be an operating system error, although the above makes more sense to me. Try running System File Checker on the virtual machine.

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
Check the host's RAID controller utility and see if the disks in the array are fine. If they aren't, replace the bad disk and wait for it to finish syncing. If the disks are fine, run a chkdsk on the host.
pyotrekAuthor Commented:
Thanks for the comments - this will have to wait until the next weekend.
This "server" host doe not have any utility to look at the RAID's health other that on start-up.

In the mean time I am making sure that all my backups are good and working.
I will report next week.

It is just another reason to convince client to switch to "real" proven hardware.
10 Tips to Protect Your Business from Ransomware

Did you know that ransomware is the most widespread, destructive malware in the world today? It accounts for 39% of all security breaches, with ransomware gangsters projected to make $11.5B in profits from online extortion by 2019.

There must be a utility available you can install, provided it uses a proper RAID controller.
pyotrekAuthor Commented:

one would think so - but this is really low budget "server"
VB ITSSpecialist ConsultantCommented:
Look in Device Manager (right click Computer > Manage or click on Start > Run > type in devmgmt.mscOK) and then expand Storage controllers.

Let us know what you see there, we may be able to help you locate the storage management software where you can then see any obvious issues with the RAID array.
pyotrekAuthor Commented:
Previous consultant had build that "server" in a hurry from parts:

The Raid controller is:

Intel C600 Series Chipset SAS RAID (SATA mode)

Just an update with what I decided to do in the mean time.

I have created another VHD, and I am copying data from the "failing" drive to it. Afterwards I will "swap" the VHDs.
Since all of the data is is simple "flat" files - I hope it will work. If I still get the error than it must be RAID if not - then somehow the VHD developed an issue, and by copying data to new drive it will be fixed.

I will post the results.
maybe best to run a disk diag on the drive - it may be dying
i use ubcd for this :
Hardware diagnostic CD    UBCD

go to the download page, scroll down to the mirror section, and  click on a mirror to start the download
Download the UBCD and make the cd   <<==on a WORKING PC, and boot the problem PC from it
Here 2 links, one to the general site, and a direct link to the download

since the downloaded file is an ISO file, eg ubcd527.iso - so you need to use an ISO burning tool
if you don't have that software, install cdburnerXP : http://cdburnerxp.se/

If you want also the Ram tested - run memtest86+ at least 1 full pass,  - you should have NO errors!
For disk Diagnostics run the disk diag for your disk brand (eg seagate diag for seagate drive)  from the HDD section -  long or advanced diag !  (runs at least for30 minutes)

http://www.ultimatebootcd.com/                        ultimate boot cd
http://www.ultimatebootcd.com/download.html             download page

**  you can make a bootable cd - or bootable usb stick
pyotrekAuthor Commented:
Surprise, surprise - creating new "fresh" VHD and copying files form the "faulty" VHD actually worked.

So far it looks like it was some kind of VHD corruption, and at this stage I do not think it was hardware related.

One thing that I had problems with was "Long File Names" - regular file copy did not work because of it. I had to use GoodSync utility. (great utility by the way and worth the money)

At this moment I do not know if the "errors" were related to the 'LFN" or was it something else ( ...and I may never know)

Never the less I will run diagnostics on the RAID this coming weekend, and will post the results.
JohnBusiness Consultant (Owner)Commented:
Thanks for the update. I pointed to operating system corruption in my first post way back, although from your description, it seemed like disk. Looks like it was the latter.
VB ITSSpecialist ConsultantCommented:
VHD files can get corrupted but it's quite rare. Nevertheless, it's good to hear you were able to copy across your data to the new VHD file.
One thing that I had problems with was "Long File Names" - regular file copy did not work because of it. I had to use GoodSync utility. (great utility by the way and worth the money)
Have a look at using Robocopy next time. It's free, can copy long file names without issues, and comes standard with Windows from Vista/2008 onwards.

As for repairing the old VHD file, have a look at this post: http://blogs.technet.com/b/tonyso/archive/2011/12/06/how-to-fix-a-corrupted-hyper-v-vhd-file.aspx

Take note of any additional links on that page as there's a number of different methods you can try to repair the VHD.
pyotrekAuthor Commented:
At the end I have found my own"solution" or rather workaround. Thank everyone for their suggestions.
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
Microsoft Legacy OS

From novice to tech pro — start learning today.