登入
Microsoft.com
 
Microsoft
 
 
 

locked
The file system structure on the disk is corrupt and unusable RRS feed

 > 

  • 問題

  • Question
    登入以投票
    0
    登入以投票

    Dear all,

     

    When I made a fresh installation on a IBMx3650 server with Raid 5 with MS Windows Server 2003, I got the following message when I do a NT backup on the system state:

     

    Event Type: Error
    Event Source: Ntfs
    Event Category: Disk
    Event ID: 55
    Date:  8/8/2008
    Time:  1:01:29 PM
    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\HarddiskVolumeShadowCopy1.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    Data:
    0000: 00 00 04 00 02 00 52 00   ......R.
    0008: 02 00 00 00 37 00 04 c0   ....7..?
    0010: 00 00 00 00 02 01 00 c0   .......?
    0018: 00 00 00 00 00 00 00 00   ........
    0020: 00 00 00 00 00 00 00 00   ........
    0028: c2 00 22 00               ?".   

    In fact, I have many experience on server installation with the same situaiton but I never get this error message before. Also I clear all array settings and made the IBM server reinstalled with a fresh MS Windows 2003 server but the problem still existed. Please kindly advice and thanks in advanced.

     

    Chris Lo

    2008年8月8日 上午 06:07

解答

  • Question
    登入以投票
    0
    登入以投票

    Dear Customer,

     

    Regarding your question, event 55 error usually indicates hardware related issue on the hard drive or controller or  NTFS volumes'' Master File Table (MFT) is corrupted. For example, the short and long file name pairs that are stored in the directory index record and the file names that are stored in the associated File Record Segment (FRS) contain case-sensitive characters that do not match.

     

    It is usually difficulty to trace this event because it is logged by file system driver in kernel layer. Usually a live debug of kernel is necessary is needed if we want to find the exact stuff occurs. To isolate a hardware related issue, I suggest that you back up the volume that contains the corrupted file(s) and exclude the corrupted file(s) from the backup job.

     

    Reformat the volume, and then restore from the backup.

     

    I suggest that you refer to the following article for more related information:

     

    246026 Cannot Delete or Repair Corrupted File on NTFS Volume

    http://support.microsoft.com/?id=246026

     

    320866 Chkdsk.exe Is Scheduled After You Run Disk Defragmenter on Your NTFS

    http://support.microsoft.com/?id=320866

     

    If anything is unclear or you have further questions on the issue, please feel free to let me know. I am looking forward to your reply.

     

    Sincerely,

    Tom Zhang, MCSE 2003

     

    2008年8月21日 上午 09:49
    版主

所有回覆

  • Question
    登入以投票
    0
    登入以投票

    Not that it helps. 

     

    I see this problem as well.  In my case I have one large raid volume, with three logical volumes on top of it.  One of the logical  vol's (drive C) always gets the corruption.  (we run checkdsk, reboot), problem goes away.  We run a caching disk controller along with onlien hot spares for the raid araay (so no hardware failure)

     

    Just started happening in june, not gettign it every day

     

    Have you found out why?

     

    matt k.

    2008年8月14日 下午 12:26
  • Question
    登入以投票
    0
    登入以投票

    Dear Customer,

     

    Regarding your question, event 55 error usually indicates hardware related issue on the hard drive or controller or  NTFS volumes'' Master File Table (MFT) is corrupted. For example, the short and long file name pairs that are stored in the directory index record and the file names that are stored in the associated File Record Segment (FRS) contain case-sensitive characters that do not match.

     

    It is usually difficulty to trace this event because it is logged by file system driver in kernel layer. Usually a live debug of kernel is necessary is needed if we want to find the exact stuff occurs. To isolate a hardware related issue, I suggest that you back up the volume that contains the corrupted file(s) and exclude the corrupted file(s) from the backup job.

     

    Reformat the volume, and then restore from the backup.

     

    I suggest that you refer to the following article for more related information:

     

    246026 Cannot Delete or Repair Corrupted File on NTFS Volume

    http://support.microsoft.com/?id=246026

     

    320866 Chkdsk.exe Is Scheduled After You Run Disk Defragmenter on Your NTFS

    http://support.microsoft.com/?id=320866

     

    If anything is unclear or you have further questions on the issue, please feel free to let me know. I am looking forward to your reply.

     

    Sincerely,

    Tom Zhang, MCSE 2003

     

    2008年8月21日 上午 09:49
    版主