locked
file corruption RRS feed

  • Question

  • Serious problem!

     

    I had just recently re-installed the beta 2 WHS on my server.  It currently had a raid 5 array attached via raid controller.  The WHS software was installed on a separate hard drive.  The install went fine, and after I installed the drivers I proceeded to windows update to update the OS.  After installing the updates, the computer rebooted, and proceeded to enter a low-level process... I think this is where it began the chkdsk function.  In any case it went through and did something mentioning index entries for thousands of files.  Now that the OS is back up, my raid array (which was not in the WHS pool btw) is still accessible, but all the files seem to have corruption!!  Some movie files won't play, and others will play with weird artifacts and such. 

     

    This is not looking promising for me.  Why would the OS modify files not in its pool?  What could have happened?

     

    Does this mean that my files are unrecoverable?  Is it the OS interpretation of the files that are causing corruption, or did it actually modify the files themselves?  Could I reinstall the newer CTP and be able to access these files normally?  Someone please help! 

     

    //UPDATE//

     

    I've found this log for Winlogon:

     

    I've found that this is what happened:

    Event Type: Information
    Event Source: Winlogon
    Event Category: None
    Event ID: 1001
    Date:  5/17/2007
    Time:  12:45:30 AM
    User:  N/A
    Computer: SERVER
    Description:
    Checking file system on F:
    The type of the file system is NTFS.
    Volume label is Media Server.


    One of your disks needs to be checked for consistency. You
    may cancel the disk check, but it is strongly recommended
    that you continue.
    Windows will now check the disk.                        
    The multi-sector header signature for VCN 0x8 of index $O
    in file 0x19 is incorrect.
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    The multi-sector header signature for VCN 0xb of index $O
    in file 0x19 is incorrect.
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    Correcting error in index $O for file 25.
    The index bitmap $O in file 0x19 is incorrect.
    Correcting error in index $O for file 25.
    The down pointer of current index entry with length 0x60 is invalid.
    20 00 38 00 00 00 00 00 60 00 10 00 01 00 00 00   .8.....`.......
    cb 7d e4 71 fb f9 db 11 be 80 00 50 8d d7 78 a1  .}.q.......P..x.
    47 1b 00 00 00 00 01 00 17 bb 58 8c 9e 12 f3 4b  G.........X....K
    ad 63 94 6e 98 4b ff c3 64 10 e1 19 44 b6 da 11  .c.n.K..d...D...
    9a 3d 00 0c 41 e1 de 2d 00 00 00 00 00 00 00 00  .=..A..-........
    00 00 00 00 00 00 00 00 ff ff ff ff ff ff ff ff  ................
    20 00 38 00 00 00 00 00 60 00 10 00 01 00 00 00   .8.....`.......
    Sorting index $O in file 25.
    The object id index entry in file 0x19 points to file 0x2a69
    but the file has no object id in it.
    Deleting an index entry from index $O of file 25.
    The object id index entry in file 0x19 points to file 0xa3e0
    but the file has no object id in it.

     

    etc... for some reason it seemed to have thought my multi-sector header signatures were wrong???  Is there anyway I can fix this?

     

    Thursday, May 17, 2007 9:55 PM