asked on

The file system structure on the disk is corrupt \device\harddiskvolumeshadowcopy

I recently installed an HP Proliant Server running SBS 2003, it has two hard drives (one drive and a mirror)
Both are showing as healthy in "disk management" The system seems to run OK but we are plagued by the same message coming up over and over again.
In the event viewer there are multiple items saying
"The file system structure on the disk is corrupt and unusable. Please run chkdsk utility on the volume \device\harddiskvolumeshadowcopy" we have rin chkdsk several time but it does not find any errors.
Other details are
ID 55
Source ntfs
Version 5.0
Symbolic name IO_FILE_SYSTEM_CORRUPT_WITH_NAME

Is it possible that the main drive is OK but the Mirror is faulty?

We use a USB hard drive to backup some files (I mention this only because other messages on this site seem to have simular problems and ext. USB's

Philip Elder

Software mirror managed by the OS?
One of your drives has bad sectors.
Get two replacements and replace one at a time. Rebuild the first one, then replace the second one and rebuild it.
You MUST have good backups at this point because things are precariously close to disaster.
http://blog.mpecsinc.ca/2008/04/sbs-shadowprotect-and-event-id-55-ntfs.html
Philip

Insideview

ASKER

Thanks, but are you saying that an HP server less than 3 months old has both hard drives failing?

Jeffrey Kane - TechSoEasy

"We use a USB hard drive to backup some files"

The FIRST thing you need to do is run a FULL BACKUP, not just "some files". Use the Built-in SBS Backup to do this so that you will have something to restore should the server fail. Then make sure that backup runs daily.

Then... it appears that you aren't the only person with this problem. http:Q_23665871.html

Jeff
TechSoEasy

ASKER CERTIFIED SOLUTION

Jeffrey Kane - TechSoEasy

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

venom96737

To add to techsoeasy also you will see this if you are using windows cluster as described here http://support.microsoft.com/kb/885688

To sum it up looks like a bogus event and if the hot fix doesnt fix it just ignore and move on.

Philip Elder

No, not necessarily. One drive is probably the culprit.
Age is nothing when it comes to hard drives. We have seen all gamut of failures from immediate to hours, to days, to months, and in some cases years.
Philip

Jeffrey Kane - TechSoEasy

SBS doesn't support Windows Cluster, so http:#22517307 isn't applicable. Plus I would never ignore a CORRUPT error warning. Because even if it wasn't a major issue, it could turn into one, so it's much better to do a decent analysis and to be prepared by having the appropriate backups.

Jeff
TechSoEasy

Insideview

ASKER

Apollogies for the delay in responding as I have been out of the UK until this week, a strange thing has happened, on my return I contacted the client who said they tought I had fixed it as its not happening any more!
I know these thing dont just "go away" but until I can track down whats going on I am reluctant to implement the possible solutions you have all contributed. I will obviously award the points as soon as I can figure out whats going on.

Jeffrey Kane - TechSoEasy

Well the best thing to do would be at least to run a Chkdsk.exe.

Jeff
TechSoEasy

Insideview

ASKER

I have choosen your solution as it made the most sence, the problem has not reoccured and the solution you provided was not actually implemented, right or wrong I am taking no action as the event logs are clean now! Thanks for your help.