Announcement

Collapse
No announcement yet.

BIT6-test file could not be created

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

  • BIT6-test file could not be created

    Passmark,

    1.We get a error message as "test file could not be created. check access privilage" when running BIT6 on USB devices.Could you suggest us the possible cause for debugging?

    2.If we want to skip the seeking test,is it correct that using parameter "-J" to run the test?.

    Thanks.

  • #2
    Passmark,

    1.The problem 1 seems to happen when testing four(or above)USB devices on one computer.

    2.For the problem 2,can we set seek count as zero to skip the test? If the method is effective, Does the method has any different from using paremeter "-J "?

    Thanks.
    Last edited by rakorei; Feb-17-2012, 06:32 AM.

    Comment


    • #3
      1. The log file should give you an additional error string (and error code number). Can you post the log file?

      2. When disk test mode is set to "Default (Cyclic)" and the "-J" command line parameter is used, the cycling between test patterns will occur after each test file, rather than after a scan of the disk. In this case, the Random data with random seeking, buttery seeking and Random test modes are skipped.

      Setting the number of seeks to 0 will mean no seeks are performed. In the case of Butterfly seeking, it turns out that the test does start, it collects disk geometry information, then skips the seeking.

      So either method will skip seeking.

      Comment


      • #4
        Passmark,
        1.We uploaded the error message here.Thanks for your help.
        http://www.mediafire.com/?vr2imlb2ar7i7b2

        2.We get passed with 30 USB flash drivers after setting seek count as zero. Does this mean that the seeking test is not recommended to run with USB flash drivers?

        Thanks.
        Last edited by rakorei; Feb-20-2012, 09:06 AM.

        Comment


        • #5
          The trace file does not actually include the test information (like,
          Open File to verify block failed: Error code <123> ).

          Could you send us the trace file showing the test run and errors?

          You can email it to us as shown here:
          http://www.passmark.com/support/index.htm

          Comment

          Working...
          X