locked
Disk NTFS Error Event ID 55 - problems with power saving? RRS feed

  • Question

  •  

    To install the RTM I have built up a brand new system. But having big problems with NTFS errors after a while (a day or so). Could this be related to energy saving mode when the disks spin down and it has problems to wake them up again?

    The system then freezes somehow. I cannot log on then anymore - neither via network nor the console. Ping still works. Then I need to push the hardware reset button.

     

    If running chkdsk /f against C and D, it found sometimes indexing issues, but nothing else.

     

    Error examples:

    Event Type: Error
    Event Source: Ntfs
    Event Category: Disk
    Event ID: 55
    Date:  27.10.2007
    Time:  12:03:22
    User:  N/A
    Computer: OBELIX
    Description:
    The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume C:\fs\H.

    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: 17 0b 14 00               ....   

     

    and

    Event Type: Error
    Event Source: Ntfs
    Event Category: Disk
    Event ID: 55
    Date:  27.10.2007
    Time:  12:04:22
    User:  N/A
    Computer: OBELIX
    Description:
    The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume DATA.

    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: 17 0b 14 00               ....   

     

    That here is my hardware:

     

    Operating System Microsoft Windows Server 2003, Standard Edition
    OS Service Pack Service Pack 2
    DirectX 4.09.00.0904 (DirectX 9.0c)
    Computer Name OBELIX


    Motherboard 
    CPU Type AMD Athlon 64X2 3800+ EE 65W, 2000 MHz
    Motherboard Name: Gigabyte GA-M61-S3 rev. 1.0
    Motherboard Chipset: nForce 430
    System Memory 1984 MB
    BIOS Type Award Modular (06/21/07)
     
    Display 
    Video Adapter NVIDIA GeForce 6150SE  (256 MB) onboard
     
    Multimedia 
    Audio Adapter Microsoft RDP Audio Driver
     
    Storage 
    IDE Controller NVIDIA MCP61 Serial ATA Controller
    IDE Controller NVIDIA MCP61 Serial ATA Controller
    IDE Controller Standard Dual Channel PCI IDE Controller
    SCSI/RAID Controller Promise Technology Inc. Ultra IDE Controller
    Disk Drive ST3250823AS  (250 GB, 7200 RPM, SATA)
    Disk Drive ST3250310AS  (232 GB, IDE) (System)
    Disk Drive WDC WD2500JB-00GVC0  (232 GB, IDE)
    Disk Drive Maxtor 4 D080H4 SCSI Disk Device  (80 GB, 5400 RPM, Ultra-ATA/100)
    Disk Drive IC35L080 AVVA07-0 SCSI Disk Device  (80 GB, 7200 RPM, Ultra-ATA/100)
    Optical Drive AOPEN DVD1648/AAP  (16x/48x DVD-ROM)
    SMART Hard Disks Status OK
     
    Partitions 
    C: (NTFS) 20481 MB (14768 MB free)
    D: (NTFS) 217983 MB (217599 MB free)
    Total Size 232.9 GB (226.9 GB free)
     
    Network 
    Network Adapter NVIDIA nForce Networking Controller  (192.168.1.160)
     
    Peripherals 
    USB1 Controller Standard OpenHCD USB Host Controller [NoDB]
    USB2 Controller Standard Enhanced PCI to USB Host Controller [NoDB]

    Saturday, October 27, 2007 10:58 AM

Answers

All replies

  • Are you running WHS or Server 2003? Both are indicated in your post.

    What happens if you disable the power saving mode, does it still happen and does it always happen on the same volumes. If so, maybe try changing that particular disk. SMART info is only an indicator and shouldn't be relied on to judge whether a disk is OK or not. Maybe also try running something like Spin-rite on it, which is far more detailed.

     

    Colin

     

    Saturday, October 27, 2007 2:29 PM
  • WHS (licensed). Fyi, WHS is based on Windows Server 2003, just with some modifications (feature-limited, some automatic tasks like in 2003 Small Business Server). Thats why error messages and these kind of internal things are quite similar to W2k3.

     

    Well, I am going to find out what happens if disk disabling is switched off. This will take some days at least.

     

    >>does it always happen on the same volumes

    That looks a bit difficult, because how to precisely identify the disk? Up to now I have not found a proper way to identify it. Remember: I have logical drives C and D, but 5 physical disks.

     

    Do you have an idea?

     

     

     

    Saturday, October 27, 2007 3:27 PM
  • Actually, you can identify the disk that's giving you problems. Secondary storage pool disks (everything except the D: partition) are all mounted under C:\fs. So:
    • Log on to WHS via Remote Desktop.
    • Right click My Computer, select Manage.
    • Click on Disk Management. Warning: Don't change anything in Disk Management!
    • For each volume listed as DATA with no drive letter, right click and select Change Drive Letter and Paths...
    • One of those disks will have the path you quoted in your original post: C:\fs\H. That disk is the source of your problem.
    You can find ou somewhat more about your error here.
    Saturday, October 27, 2007 4:16 PM
    Moderator
  • Hi,

    Another point about this error is a quote from Microsoft:

    When the hard disk plug-and-play (PnP) arrival event occurs, the NTFS file system immediately tries to mount the file system. This operation creates several Input Output Control (IOCTL) function calls and several I/O procedures. Immediately after the NTFS file system begins the mounting sequence, the Clusdisk responds to the PnP arrival event and blocks all I/O operations to the disk subsystem. This blocks all IOCTL and I/O requests, including the pending requests. Because of this behavior, the volume manager disk driver (ftdisk) interprets the block as an I/O error and records the event ID 57, event ID 55, and event ID 50 entries.

    This error can be ignored.

     

    However,

    This article suggests another answer. The disk in question hasn't been in use on another Computer or has been formatted before?

     

    HTH,

     

    Colin

     

    Saturday, October 27, 2007 5:12 PM
  •  

    You might want to check this: http://support.microsoft.com/kb/932578/
    Wednesday, November 7, 2007 2:51 PM
  • The problems are sorted. It was the NVidia nForce4 SATA driver which caused the problem. I switched back to the origninal built-in Windows driver and since then it is rock-solid. Same disk(s).

     

    The Nvidia driver has very low quality :-(

     

    See this thread as well:

    http://forums.microsoft.com/WindowsHomeServer/ShowPost.aspx?PostID=2363313&SiteID=50

     

    Saturday, November 24, 2007 11:17 AM
  • I sent an email to gigabyte. This was their reply.

    Dear Sir,

    Thank you for your kindly mail and supporting GIGABYTE.
    About the issue you mentioned in your earlier mail, due to chipset manufacturer (Nvidia) does not provide any RAID driver for Windows 2003 Standard edition 64 bit, therefore , it does not support raid on WINDOWS 2003 64 bit system.

    Raid 1 seems to work using the xp 64 bit drivers but the minute you go raid 5 the system will become unstable. This is on the M61P-S3 v1.0 MB.

    They say it should work great on Windows xp 64bit just not server editions. Looks Like I am heading back to the store Sad
    Sunday, February 24, 2008 11:49 AM
  • Ron, why would you be loading a 64 bit driver on your WHS? It's a 32 bit operating system, so you should only use a 32 bit driver.
    Sunday, February 24, 2008 4:23 PM
    Moderator
  • I was installing Windows 2003 Server 64 Standard Edition. Thats why.
    Sunday, February 24, 2008 4:31 PM