NTFS/55 error on volume \Device\HarddiskVolumeShadowCopyXXX

A brand new Dell server running Windows 2008 R2 now issues the following errors in the event log :

Log Name:      System
Source:        Ntfs
Date:          26-8-2010 5:00:50
Event ID:      55
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      gsd-sv001.goesdeen.local
The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume \Device\HarddiskVolumeShadowCopy2.

There are two similar messages for HarddiskVolumeShadowCopy2 and ..7.

Looking at the time stamps, Windows Server Backup seems to trigger these errors, as Windows Server Backup is scheduled to run at 5:00.

The server is used as a Hyper-V host only, and is very critical.

I do not know how  \Device\HarddiskVolumeShadowCopy2/7 relates to actual volumes like C: and D: on which you can run CHKDSK.

I obviously did this already, and on all the volumes CHKDSK completed without any errors.

Does anyone know how critical this is, and how to fix this ?

Who is Participating?
rlaningConnect With a Mentor Author Commented:
This error seems relatively harmless. We tested several backups and the restores are flawless although the error is triggered by the Windows Server Backup on the Hyper-V host.

The cause of this error seems to be the external USB-drive which goes in to a "sleep"-mode (see http://social.technet.microsoft.com/Forums/en/windowsbackup/thread/6f31dd04-10df-4ac4-8051-bfdb37ade838).
The error seems to be generated by the slow response of the external HDU in "sleep"-mode, without any severe consequences.
Krzysztof PytkoSenior Active Directory EngineerCommented:
I have no solution for your problem but maybe event id would be helpful
rlaningAuthor Commented:
Looking a bit further a found pages mentioning a tool DOSDEV.exe that allow you to mount a Shadow Copy volume as mentioned in the message on a drive letter. Having done that, CHKDSK could be run.
I do not know where to find this tool, however.

The question how serious this is, and if this needs to be fixed remains....
rlaningAuthor Commented:
Root cause has been found, no solution / workaround required (relatively harmless event).
See also my last comment in case.
rlaningAuthor Commented:
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.