Event ID 55 when creating Volume Shadow copies

Discussion in 'Windows Small Business Server' started by wnouri, May 26, 2008.

  1. wnouri

    wnouri Guest

    Hello to all,
    a client has a small business server 2003, Intel Entry level, SATA RAID1,
    installed on may 2007. Until the first days of may 2008 there where no
    problems. It serves as a Exchange and File Server.

    Since 3 Weeks we get event id 55 on every creation of a volume shadow copy
    suggesting to run CHKDSK on "\Device\HarddiskVolumeShadowCopyXX". Where XX is
    the number of the actual Shadow copy.

    ***************
    Event Type: Error
    Event Source: Ntfs
    Event Category: Disk
    Event ID: 55
    Date: 5/25/2008
    Time: 22:20:10
    User: N/A
    Computer: ******
    Description:
    The file system structure on the disk is corrupt and unusable. Please run
    the chkdsk utility on the volume \Device\HarddiskVolumeShadowCopy75.

    This event occurs also during the nightly backup for many files in the event
    log (one entry per file which could not be backed up). NTBACKUP states that
    the file is not readable or corrupt in the backup log.

    The files stated as corrupt in the backup log (mostly Word and
    Excel-documents) can be accessed without any problems.

    Running chkdsk states file attribute errors and lost files. Running chkdsk
    /f /r at system boot corrects some attribute errors but similar errors
    reoccur after the boot.

    Checking the harddisks with an intel utility states no physical error on
    both raid1 drives. everything is fine with the drives.

    Applying SP2 for Windows server 2003 has no effect

    Can any one help?
    Thanks!
     
    wnouri, May 26, 2008
    #1
    1. Advertisements

  2. There are many possible causes, and it is impossible to diagnose this from
    afar. Go to www.eventid.net, put in the event id and source and look
    through the possible causes listed there.

    Some examples:

    the drive is actually failing.... download and run the drive diagnostics,
    preferably from a boot disk

    the controller is failing... or you should update the firmware/drivers.
    Contact the mfg.

    please note that a discrete, add in controller is generally preferred over
    the on board ones, even those from Intel.

    In any case, do the best backup job you can, try not to overwrite any prior
    good backups, then run the various possible fixes.

    when you have what you think is a fix, it also would not hurt to run the
    SBSBPA.

    www.sbsbpa.com
     
    Larry Struckmeyer [SBS-MVP], May 26, 2008
    #2
    1. Advertisements

  3. wnouri

    Ex-Engineer Guest

    Sometime ago we too had a similar error on a low-end clone server (with
    on-board RAID 1) running SBS 2003 Std.
    As prompted by the advice within the error message, of course we ran CHKDSK.
    Big mistake! This made things totally worse, and trashed our Exchange IS,
    and we had to restore from a known good backup. (Phew!) But annoyingly, the
    Event 55 soon re-appeared. It looked like a faulty drive(s) perhaps or
    faulty RAID controller, or ...?

    From the benefit of hindsight what we should have done was remove the drives
    (we did have a backup) and put them in a test box to give them a good going
    over, but that's hindsight for you.

    What we did to confuse ourselves even further was to run "chkntfs" which
    reported that the volume was not dirty, and this seemed believable as there
    was no trouble actually accessing files.

    In the end we solved it by opening a command window ( not via the GUI) and
    running chkdsk /R - this took a long time but when finished the Event 55's
    did not reshow and the volume did net get trashed. Had this not worked we
    were going to replace both drives and restore from an earlier known good
    backup, or more drastically, we were prepared to migrate the installation to
    a new box, either via Swing Migration, or using ShadowProtect. Fortunately
    we did not need to. If anyone else has anything definitive about fixing this
    annoying error, and why CHDSK can do Bad Things to a volume, I'm all ears!

    Regards
    Ex-Engineer
     
    Ex-Engineer, May 26, 2008
    #3
  4. wnouri

    wnouri Guest

    Hello Larry, Hello Ex-Engineer,

    thank you for your advice and sorry for my late answer!

    I will give the "chkdsk /r" a try.

    To make things more worse.... i don't have a known good backup at hand!
    Thats bescause my client didn't take notice of the 50 page backup log which
    came out of the printer....the night shift just throwed them away without
    without telling some one about that strange paper output. I have noticed what
    is going on during a routine check when visiting the client!

    The problem is they work 24/5 so i can only access the Server for
    "experiments" at the weekend!

    Regards
    wnouri!
     
    wnouri, May 28, 2008
    #4
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.