Event 55 -The file system structure on disk is corrupt and unusable / Hyper-V

Hi,

We have a Hyper-V virtual server running server 2008. Recently we got an error in event logs. We did not see an impact on the server related to this issue yet. There are many errors and I know there is a hotfix for this issue for Server 2003 but I couldn't find any hotfixes for Windows Server 2008. What would be the solution for this issue? Also this is a virtual server, is it normal to get this kind of error on a virtual server?
Any help would be appreciated.

Thanks!
--------------------------------------------------------
Event 55, NTFS:
The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume C:.
--------------------------------------------------------
When I ran chkdsk:
The type of the file system is NTFS.

WARNING!  F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)...
 5 percent complete. (52480 of 104960 file records processed)
Attribute list entry with type code -1 in file 59479 is corrupt.
Attribute list for file 59479 is corrupt.
Attribute list for file 59479 is corrupt.
  104960 file records processed.
File verification completed.
File record segment 31878 is an orphan.
File record segment 41668 is an orphan.
File record segment 43164 is an orphan.
File record segment 43196 is an orphan.
File record segment 57979 is an orphan.
File record segment 59483 is an orphan.
File record segment 60100 is an orphan.
File record segment 60281 is an orphan.
File record segment 60282 is an orphan.
File record segment 60283 is an orphan.
File record segment 60284 is an orphan.
File record segment 60351 is an orphan.
File record segment 60433 is an orphan.
File record segment 60524 is an orphan.
File record segment 60826 is an orphan.
File record segment 60827 is an orphan.
File record segment 60845 is an orphan.
File record segment 60848 is an orphan.
File record segment 62389 is an orphan.
File record segment 62392 is an orphan.
File record segment 62395 is an orphan.
File record segment 63080 is an orphan.
File record segment 63161 is an orphan.
File record segment 63592 is an orphan.
File record segment 63600 is an orphan.
File record segment 64558 is an orphan.
File record segment 64564 is an orphan.
File record segment 64566 is an orphan.
File record segment 64570 is an orphan.
File record segment 64627 is an orphan.
File record segment 64628 is an orphan.
File record segment 64629 is an orphan.
File record segment 64745 is an orphan.
File record segment 64748 is an orphan.
File record segment 64752 is an orphan.
File record segment 64758 is an orphan.
File record segment 64913 is an orphan.
File record segment 64914 is an orphan.
File record segment 64916 is an orphan.
File record segment 64917 is an orphan.
File record segment 64918 is an orphan.
File record segment 64921 is an orphan.
File record segment 64922 is an orphan.
File record segment 64923 is an orphan.
File record segment 64924 is an orphan.
File record segment 64925 is an orphan.
File record segment 64926 is an orphan.
File record segment 64927 is an orphan.
File record segment 64928 is an orphan.
File record segment 64929 is an orphan.
File record segment 64930 is an orphan.
File record segment 64931 is an orphan.
File record segment 64932 is an orphan.
File record segment 64933 is an orphan.
File record segment 64934 is an orphan.
File record segment 64935 is an orphan.
File record segment 64936 is an orphan.
File record segment 64937 is an orphan.
File record segment 64938 is an orphan.
File record segment 64939 is an orphan.
File record segment 64940 is an orphan.
File record segment 64941 is an orphan.
File record segment 64942 is an orphan.
File record segment 64943 is an orphan.
File record segment 64944 is an orphan.
File record segment 64945 is an orphan.
File record segment 64946 is an orphan.
File record segment 64947 is an orphan.
File record segment 64948 is an orphan.
File record segment 64949 is an orphan.
File record segment 64951 is an orphan.
File record segment 64952 is an orphan.
File record segment 64954 is an orphan.
File record segment 64955 is an orphan.
File record segment 64973 is an orphan.
File record segment 64976 is an orphan.
File record segment 64977 is an orphan.
File record segment 64979 is an orphan.
File record segment 64981 is an orphan.
File record segment 64982 is an orphan.
File record segment 64984 is an orphan.
File record segment 64985 is an orphan.
File record segment 64986 is an orphan.
File record segment 64987 is an orphan.
  351 large file records processed.

Errors found.  CHKDSK cannot continue in read-only mode.
-------------------------------------------------------------
partners1998Asked:
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.

Twisted_LogicCommented:
Have you checked the vhd file itself for errors?
partners1998Author Commented:
We are going to rebuild the server.

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
partners1998Author Commented:
No resolutions provided.
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.