How to Debug Event ID 55 Disk Corruption

 

clip_image002

Event ID 55 Analysis resulted in the following :

Hardware Diagnostics

No hardware issues reported ?

clip_image004

Chkdsk

Running chkdsk did not report any errors ?

EventLog

After analyzing the eventlog I saw a patern coming back.

The Event ID came back 3 times a day with approx. 8 hours in between :

5.45 AM /  13.45 PM  / 21.45 PM

This lead me to the fact that it had something to do with the VSS ?

VSSAdmin

Check for errors.

clip_image006

No Errors reported ?

So next I cleaned all the VSS copies and pushed the CREATE NOW button.

clip_image008

I saw again the NTFS events ID 55 ?

Next I checked the VSS Settings, to see the available capacity.

clip_image010

SOLUTION :

Check the available disk capacity and the size allocated for VSS.

=> C drive had 90 Gb available and the size allocated for VSS was 95 Gb ?

Once I changed the size below the available disk capacity and run the create Shadow Copy again.

No errors were reported in the event log

More info here for potential reasons of Event ID 55

VSS driver Issue ? https://support.microsoft.com/nl-be/kb/2754784

Symantec Backup Exec Issue ?https://www.veritas.com/support/en_US/article.TECH71661

Step by step guide to help ?

http://www.omerovic.nl/wordpress/2013/12/troubleshooting-event-55-file-system-structure-disk-corrupt/

Enjoy !

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: