PassMark Software

Announcement

Collapse
No announcement yet.

Butterfly Seek Test with "Seek size requested not equal to actual" error

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Butterfly Seek Test with "Seek size requested not equal to actual" error

    Hi ,
    I found an issue during running HDD test on passmark BurnIn V.8.1 with

    ******************
    DETAILED EVENT LOG
    ******************
    LOG NOTE: 2017-10-02 15:00:57, Status, PassMark BurnInTest V8.1 Pro 1024 (64-bit)
    LOG NOTE: 2017-10-02 15:01:00, Status, Main Tests started
    SERIOUS: 2017-10-05 16:36:14, Disk, F: Seek size requested not equal to actual
    LOG NOTE: 2017-10-05 16:36:14, Disk, Disk Error (F: Seek size requested not equal to actual in Cycle 4751 with pattern Butterfly seeking
    LOG NOTE: 2017-10-05 16:36:23, Status, Test run stopped

    Seek size requested not equal to actual. I have found some answer that
    ================================================== ==========
    This error is logged when BurnInTest has requested the disk the seek to a specific location in the test file and the actual seek call by the device driver has failed to seek to that requested location.
    ================================================== ==========

    Would it be the disk report different location (LBA) compare to Host expected? So it's not related on data write, right? Could you elaborate more on actual seek call by the device driver?

    During the failure, we do observe the system event viewer log fail at the same time of failure 16:36.

    Event log ================================================== ======================
    The IO operation at logical block address 0x2abd9e6d for Disk 1 (PDO name: \Device\00000052) failed due to a hardware error.
    ================================================== =============================

    Thanks.

  • #2
    This error is logged when BurnInTest makes a call to SetFilePointer and the call has failed. If you set trace level logging in the logging options to level 2 more information about the failure will be logged in the trace log (such as the offset location in the file it was trying to seek to).

    We can't elaborate on how the actual device driver in use is handling the seek call but as you are seeing event log entries as well it seems like this it is a fairly serious failure.

    Comment

    Working...
    X