Announcement

Collapse
No announcement yet.

About "Seek size requested not equal to actual" Error.

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

  • About "Seek size requested not equal to actual" Error.

    I am using BurnInTest to test my USB dump drive, but "Seek size requested not equal to acture" error is founded. This error message is Write error(write file fail), Read error(read file fail) or Compare error(write and read file compare error)? 3Q~

  • #2
    Is this in Windows or Linux?
    What version of BIT was used?
    What were the test settings in the test preferences window for the disk test?
    Did the error happen right at the start of the test, or after some period of time?
    What make and size was the USB drive?
    Is there any possibility it might be a counterfeit drive?

    Comment


    • #3
      (1) Windows 7 Home Premium Edition.
      (2) BurnInTest V6.0 Pro 1019
      (3) Disk Test.
      (4) After 33H.
      (5) 64GB.
      (6) not counterfeit drive.
      ================================================== ======
      All Log information:
      Log file - http://www.passmark.com
      ================================================== ======
      Date: 12/20/12 10:39:56
      BurnInTest V6.0 Pro 1019
      Logging detail level: Normal
      **************
      SYSTEM SUMMARY
      **************
      Windows 7 Home Premium Edition Service Pack 1 build 7601 (64-bit),
      1 x Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz,
      7.9GB RAM,
      Intel(R) HD Graphics 4000,
      932GB HDD,
      CD-RW/DVDRW,
      GENERAL
      System Name: USB-PC
      Motherboard Manufacturer: Acer
      Motherboard Name: Aspire M3985
      Motherboard Serial Number: 115248170000318
      BIOS Manufacturer: American Megatrends Inc.
      BIOS Version: ACRSYS - 1072009
      BIOS Release Date: 2012/03/12
      CPU
      CPU manufacturer: GenuineIntel
      CPU Type: Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz
      CPUID: Family 6, Model 3A, Stepping 9
      Physical CPU's: 1
      Cores per CPU: 4
      Hyperthreading: Enabled
      CPU features: MMX SSE SSE2 SSE3 SSSE3 SSE4.1 SSE4.2 DEP PAE Intel64 VMX SMX
      Clock frequencies:
      Cache per CPU package:
      L1 Instruction Cache: 4 x 32 KB
      L1 Data Cache: 4 x 32 KB
      L2 Cache: 4 x 256 KB
      L3 Cache: 8 MB
      MEMORY
      Total Physical Memory: 8073MB
      Available Physical Memory: 6522MB
      Virtual memory: C:\pagefile.sys (allocated base size 8072MB)
      GRAPHICS
      Intel(R) HD Graphics 4000
      Chip Type: Intel(R) HD Graphics Family
      DAC Type: Internal
      Memory: 2112MB
      BIOS: Intel Video BIOS
      Driver provider: Intel Corporation
      Driver version: 8.15.10.2598
      Driver date: 12-15-2011
      Monitor 1: 1920x1200x32 59Hz (Primary monitor)
      DISK VOLUMES
      C: Local drive, Acer, NTFS, (458.45GB total, 390.74GB free)
      D: Local drive, DATA, NTFS, (458.96GB total, 458.86GB free)
      E: Optical drive, DVDRAM GH70N
      F: Removable
      G: Removable
      H: Removable
      I: Removable
      J: Removable
      K: Removable
      L: Removable
      DISK DRIVES
      : Model ST31000524AS (Size: 931.51GB)


      : Model TOSHIBA TransMemory-Ex USB Device (Size: 58.13GB)
      : Model TOSHIBA TransMemory-Ex USB Device (Size: 58.13GB)
      OPTICAL DRIVES
      E: HL-DT-ST DVDRAM GH70N (CD-RW/DVDRW)
      NETWORK
      Intel(R) 82579V Gigabit Network Connection
      PORTS
      Intel(R) 7 Series/C216 Chipset Family USB Enhanced Host Controller - 1E2D
      Intel(R) 7 Series/C216 Chipset Family USB Enhanced Host Controller - 1E26
      Ce(R) USB 3.0 eXtensible zXgERg[[
      - TOSHIBA TransMemory-Ex (SN: 1C6F65FE723BECC0B0000047)
      - TOSHIBA TransMemory-Ex (SN: 1C6F65FE723BECC0B0000046)
      ******************
      DETAILED EVENT LOG
      ******************
      LOG NOTE: 2012-12-20 10:39:56, Status, PassMark BurnInTest V6.0 Pro 1019
      LOG NOTE: 2012-12-20 10:39:56, Status, Main Tests started
      SERIOUS: 2012-12-21 20:29:06, Disk, M: Seek size requested not equal to actual
      LOG NOTE: 2012-12-21 20:29:06, Disk, Disk Error (M: Seek size requested not equal to actual in Cycle 816 with pattern High Low freq overwrite
      LOG NOTE: 2012-12-21 20:29:15, Status, Test run stopped
      **************
      RESULT SUMMARY
      **************
      Test Start time: Thu Dec 20 10:39:56 2012 (Accumulated results start time: Thu Dec 20 10:39:56 2012)
      Test Stop time: Fri Dec 21 20:29:13 2012
      Test Duration: 033h 49m 17s (Accumulated results duration: 000h 49m 17s)
      Test Name Cycles Operations Result Errors Last Error
      Disk (K 824 2.753 Trillion PASS 0 No errors
      Disk (L 817 2.731 Trillion PASS 0 No errors
      Disk (M 817 2.731 Trillion FAIL 1 Seek size requested not equal to actual
      Disk (N 825 2.755 Trillion PASS 0 No errors
      TEST RUN FAILED
      *******************************************
      SERIOUS ERROR SUMMARY FOR THE LAST TEST RUN
      *******************************************
      SERIOUS: 2012-12-21 20:29:06, Disk, SERIOUS: Seek size reques

      Comment


      • #4
        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.

        This is not a common error so we can't say for sure what the cause of such an error would be.

        Comment


        • #5
          Originally posted by Tim (PassMark) View Post
          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.

          This is not a common error so we can't say for sure what the cause of such an error would be.
          So, we can say this is because read the specific location data fail (Read Fail)?

          Comment


          • #6
            we can say this is because read the specific location data fail (Read Fail)
            You could say that, but it would be wrong. We didn't say anything about a read failing.

            The seek operation failed. Which is strange as as seek doesn't do much for a USB drive. So there isn't many ways to imagine how it can fail. Seeking beyond the end of the drive, or before the start, would be one possibility. But it is unlikely. Corruption of the MFT might be another reason. Would be hard to know for sure without a forensic analysis and further tests.

            It might be just a one off error. Computers (and flash drives) aren't 100% stable when running over periods of days.

            Comment


            • #7
              Hi,

              A lot of time has passed since this entry was originally posted by Fangli_33 back in 2013 - any chance there is any new information about such errors?

              I am getting the same error:
              "LOG NOTE: 2019-06-03 05:37:04, Disk, Disk Error (C: Seek size requested not equal to actual in Cycle 454607 with pattern Butterfly seeking."

              This is also a SSD (eMMC form factor in my case). And also a Toshiba device(?) (similar maybe to Fangli_33?)

              My log file follows; (I have multiple more of the same errors since this first one was captured. I can get that log file update if it is useful)

              PassMark BurnInTest Log file - http://www.passmark.com
              ================================================== ======

              Date: Mon Jun 03 08:49:49 2019

              BurnInTest V8.1 Std 1013 (64-bit)

              System summary:
              Windows 10 build 14393 (64-bit),
              1 x Intel(R) Atom(TM) Processor E3930 @ 1.30GHz [1798.5 MHz],
              3.8GB RAM,
              Intel(R) HD Graphics,
              116GB HDD,


              General:
              System Name: DESKTOP-A1IDOJ9
              Motherboard Manufacturer: Intel Corp.
              Motherboard Name: Apollolake I Platform
              Motherboard Version: B
              Motherboard Serial Number: YB1734J3201-RA0A00038
              BIOS Manufacturer: PTEC - 3
              BIOS Release Date: 2017/11/17
              BIOS Serial Number: System Serial Number

              CPU:
              CPU manufacturer: GenuineIntel
              CPU Type: Intel(R) Atom(TM) Processor E3930 @ 1.30GHz
              CPUID: Family 6, Model 5C, Stepping 9
              Physical CPU's: 1
              Cores per CPU: 2
              Hyperthreading: Disabled
              CPU features: MMX SSE SSE2 SSE3 SSSE3 SSE4.1 SSE4.2 DEP PAE Intel64 VMX AES XOP FMA3
              Clock frequencies:
              - Measured CPU speed: 1798.5 MHz
              Cache per CPU package:
              - L1 Instruction Cache: 16 x 32 KB
              - L1 data cache: 16 x 24 KB
              - L2 cache: 4 x 1024 KB
              - L3 cache: Not applicable

              Memory
              Total Physical Memory: 3928MB
              Available Physical Memory: 2926MB
              Virtual memory: C:\pagefile.sys (allocated base size 704MB)

              Memory SPD:

              Graphics
              Intel(R) HD Graphics
              Chip Type: Intel(R) HD Graphics Family
              DAC Type: Internal
              Memory: 1024MB
              BIOS: Intel Video BIOS
              Driver provider: Intel Corporation
              Driver version: 21.20.16.4550
              Driver date: 11-11-2016
              Monitor 1: 1280x800x32 60Hz (Primary monitor)

              Disk volumes
              C: Local Drive, \\?\Volume{1887d79e-e25d-4b4b-b12c-65086a9ac1fa}\, Windows, NTFS, (108.11GB total, 96.89GB free)

              Disk drives
              Disk drive: Model: Toshiba 128G32 Serial: N/A (Disk: 0, Size: 116.48GB, Volumes: C)

              Optical drives

              Network
              Intel(R) I210 Gigabit Network Connection (MAC: 00:A0:A4:26:7C:32)
              Qualcomm Atheros QCA61x4A Wireless Network Adapter (MAC: F0:03:8C:AA:72:47)

              Ports

              USB
              USB xHCI Compliant Host Controller
              - Qualcomm Atheros Bluetooth 4.1
              - USB Composite Device
              - eGalax Inc. eGalaxTouch EXC3160-1721-07.00.00
              - UPEK Biometric Coprocessor


              **************
              RESULT SUMMARY
              **************
              Test Start time: Wed Feb 27 13:56:51 2019
              Test Stop time: Mon Jun 03 08:47:00 2019
              Test Duration: 2297h 50m 09s

              Test Name Cycles Operations Result Errors Last Error
              CPU 523464 3.1 Quadrillion PASS 0 No errors
              Memory (RAM) 88249 355 Trillion PASS 0 No errors
              2D Graphics 772995 395 Million PASS 0 No errors
              Temperature - - PASS 0 No errors
              Disk () 455182 1.1 Quadrillion FAIL 1 Seek size requested not equal to actual
              Network 1 125066 5.003 Billion PASS 0 No errors
              TEST RUN FAILED

              ******************
              DETAILED EVENT LOG
              ******************
              LOG NOTE: 2019-02-27 13:56:51, Status, Main Tests started
              LOG NOTE: 2019-02-27 13:56:51, CPU, SSE4a test(s) selected, but CPU feature not detected
              SERIOUS: 2019-06-03 05:37:04, Disk, C: Seek size requested not equal to actual
              LOG NOTE: 2019-06-03 05:37:04, Disk, Disk Error (C: Seek size requested not equal to actual in Cycle 454607 with pattern Butterfly seeking
              LOG NOTE: 2019-06-03 08:47:01, Status, Test run stopped



              Comment


              • #8
                Test Duration: 2297h 50m 09s
                Is this correct? More than 3 months of 24h non stop testing?
                Many machines won't run this long under load without getting a soft error.

                What's the quoted write endurance figure for the SSD?

                Also, you are running a old version of BurnInTest. In newer releases we don't bother running the butterfly seeking test as it doesn't really make much sense to do this for a SSD.
                Butterfly seeking moves the drive head from one edge of the platter to the other, but SSDs don't have platters. This should not cause an error for a SSD, but it isn't doing what the test was designed to do.

                Comment


                • #9
                  Yes indeed - the test has been running 100% for a long time now. (Actually, we started on 02 NOV 2018, running 100% on most sub-systems as stated.)

                  I can't find published endurance ratings for the specific device. We are trying to validate them against standard MLC device ratings.

                  These errors started just a few days ago, and are now recurring, so it appears that something is breaking down in the SSD... ON the 64GB size devices from the same family, the first failures that occurred were actual read/write failures, so I was expecting similar for this 128GB device.

                  Understood on the butterfly test no longer being truly valid on SSDs. I'll stop the test and restart it without the butterfly enabled if I can figure out how to do that.

                  Any other ideas or comments are appreciated.

                  Thanks.





                  Comment

                  Working...
                  X