none
ESENT Event 508 A Request to write to the file .... bytes succeeded, but took an abnormaly long ime

    Question

  • Hi,

    Hoping to get a few ideas on what might be the cause of this issue we are having.

    Background

    We have two hyper-v clusters running Server 2012R2.

    Our AD environment is a mix of 2008R2 and one 2012R2 DC's.

    We have both 2008R2 and 2012R2 DC's running virtualised on the Hyper-V clusters.

    2008R2 DC is on a VHD disk.

    2012R2 DC is on VHDX disk.

    We have a number of other 2012R2 and 2008R2 servers on the clusters.

    Issue

    We have started seeing the above error being logged on the 2012R2 DC only. The 2008R2 DC's do not show this error at all.

    Event ID: 508

    Source: ESENT

    Level: Warning

    svchost (2568) A request to write to the file "C:\Windows\system32\LogFiles\Sum\Svc.log" at offset 2023424 (0x00000000001ee000) for 4096 (0x00001000) bytes succeeded, but took an abnormally long time (15 seconds) to be serviced by the OS. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.

    lsass (628) A request to write to the file "\\?\Volume{538f044f-9c00-11e3-80c2-00155d1c0903}\Windows\NTDS\ntds.dit" at offset 31342592 (0x0000000001de4000) for 8192 (0x00002000) bytes succeeded, but took an abnormally long time (15 seconds) to be serviced by the OS. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.

    Source: NTDS ISAM

    NTDS (628) NTDSA: A request to write to the file "E:\Windows\NTDS\edb.log" at offset 1306624 (0x000000000013f000) for 4096 (0x00001000) bytes succeeded, but took an abnormally long time (21 seconds) to be serviced by the OS. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.

    Event ID 509

    Source: NTDS ISAM

    NTDS (628) NTDSA: A request to read from the file "E:\Windows\NTDS\ntds.dit" at offset 243572736 (0x000000000e84a000) for 8192 (0x00002000) bytes succeeded, but took an abnormally long time (21 seconds) to be serviced by the OS. In addition, 0 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 23679 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.

    Troubleshooting So Far

    AV exceptions are in place for scanning

    Backup (DPM 2012) disabled for testing

    Moved 2012R2 DC to another virtual host

    Moved 2012R2 DC to another storage server

    The server is fully patched with all latest updates available from windows update.

    Any assistance is appreciated.


    Regards,

    Denis Cooper

    MCITP EA - MCT

    Help keep the forums tidy, if this has helped please mark it as an answer

    My Blog

    LinkedIn:



    Monday, February 24, 2014 9:22 AM

Answers

All replies