carbonbase
asked on
The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume \Device\HarddiskVolumeShadowCopy
I have a Windows 2008 Standard server with SP2. A couple of the
drives on the server are configured to create shadow copies 3 times a
day.
I get lots of errors similar to one below when the shadow copies are
being created. The errors all seem to relate to one drive (drive E:)
which is spanned across two dynamic disks giving a total volume size
of 1.8TB
Log Name: System
Source: Ntfs
Date: 23/03/2012 10:01:59
Event ID: 55
Task Category: (2)
Level: Error
Keywords: Classic
User: N/A
Computer: <server name>
Description:
The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume \Device\HarddiskVolumeShad owCopy154.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Ntfs" />
<EventID Qualifiers="49156">55</Eve ntID>
<Level>2</Level>
<Task>2</Task>
<Keywords>0x80000000000000 </Keywords >
<TimeCreated SystemTime="2012-03-23T10: 01:59.925Z " />
<EventRecordID>216034</Eve ntRecordID >
<Channel>System</Channel>
<Computer>server name</Computer>
<Security />
</System>
<EventData>
<Data>
</Data>
<Data>\Device\HarddiskVolu meShadowCo py154</Dat a>
<Binary>0D000C000200380002 0000003700 04C0000000 00020100C0 0000000000 0000000000 0000000000 007E0C1400 0500000000 000500</Bi nary>
</EventData>
</Event>
I have read a couple articles on this issue and have run the chkntfs
command and it came back with a result the drive is "not dirty". I have also run the "vssadmin list writers" command and no errors were reported
Not sure what's going on whether there is a problem on the drive or
problem with the shadowcopy. Multiple shadowcopies are listed in
eventlog so I don't want to just delete them all but I would like to
correct the underlying problem so that the server doesn't keep
generating these errors.
Any help appreciated. Thanks
drives on the server are configured to create shadow copies 3 times a
day.
I get lots of errors similar to one below when the shadow copies are
being created. The errors all seem to relate to one drive (drive E:)
which is spanned across two dynamic disks giving a total volume size
of 1.8TB
Log Name: System
Source: Ntfs
Date: 23/03/2012 10:01:59
Event ID: 55
Task Category: (2)
Level: Error
Keywords: Classic
User: N/A
Computer: <server name>
Description:
The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume \Device\HarddiskVolumeShad
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Ntfs" />
<EventID Qualifiers="49156">55</Eve
<Level>2</Level>
<Task>2</Task>
<Keywords>0x80000000000000
<TimeCreated SystemTime="2012-03-23T10:
<EventRecordID>216034</Eve
<Channel>System</Channel>
<Computer>server name</Computer>
<Security />
</System>
<EventData>
<Data>
</Data>
<Data>\Device\HarddiskVolu
<Binary>0D000C000200380002
</EventData>
</Event>
I have read a couple articles on this issue and have run the chkntfs
command and it came back with a result the drive is "not dirty". I have also run the "vssadmin list writers" command and no errors were reported
Not sure what's going on whether there is a problem on the drive or
problem with the shadowcopy. Multiple shadowcopies are listed in
eventlog so I don't want to just delete them all but I would like to
correct the underlying problem so that the server doesn't keep
generating these errors.
Any help appreciated. Thanks
Are you running on the most updated RAID Drivers and firmware as well for your hard drives?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Forgot to mention that this is a VMware (ESX 3.5) virtual server
ASKER
what does setting the the drive as dirty give me?
Have you run chkdsk /r?
ASKER
I get a message that the volume is in use and I have the option to either dismount the volume or schedule check disk to run next time the server is rebooted. I'll try setting the volume to dirty then schedule chkdsk to run at next reboot.
ASKER
Didn't try the solution in then end but will note for future reference. Thanks