Error Disk Mark Drive 6

[Dtrfj]

Thanks for the help.

[David (PassMark)]

If the error was not enough disk space, then I think it is likely that there was not enough disk space on the disk being tested. Or the software is corrupted.

So
1) Check what drive is selected for testing in the Edit / Preferences window.
2) Check it has some free space (e.g. 5GB)
3) Download and install a clean copy of the PerformanceTest software from our site (don't use a hacked / corrupted copy from a 3rd party site)

[Dtrfj]

Hello. I have the same problem! Performance Test 10.2

There is not enough free space on drive 6:
to run the disk test
1.05 GB is required, 0.00 MB is available.
Please select another drive in the Preferences dialog box.

Explain how to solve this problem.

[David (PassMark)]

The one you just sent us,

Delete this file,
C:\Users\<your user name>\AppData\Local\PassMark\PerformanceTest9\Last Used.cfg

[SimPos]

Thanks for that, there are some invalid values saved in the config file which is causing the disk test to be started incorrectly.

We're looking into what might have caused it but for now could you please try deleting the config file and then starting PerformanceTest again, this will recreate the file with default values.

What would this configuration file be?

[Tim (PassMark)]

Thanks for that, there are some invalid values saved in the config file which is causing the disk test to be started incorrectly.

We're looking into what might have caused it but for now could you please try deleting the config file and then starting PerformanceTest again, this will recreate the file with default values.

[SimPos]

You can email us the log file. Could you also please include the C:\Users\<your user name>\AppData\Local\PassMark\PerformanceTest9\Last Used.cfg as well, at the moment we're speculating there is an invalid value saved in the config file that might be messing up the selected disk name.

If you have selected a different disk in the preferences and exited PerformanceTest then the next time it is started the same disk should be selected, if not then this too would seem to point to an issue with the config file (or access to the config file).

I do not know if this can help.

[SimPos]

You can email us the log file. Could you also please include the C:\Users\<your user name>\AppData\Local\PassMark\PerformanceTest9\Last Used.cfg as well, at the moment we're speculating there is an invalid value saved in the config file that might be messing up the selected disk name.

If you have selected a different disk in the preferences and exited PerformanceTest then the next time it is started the same disk should be selected, if not then this too would seem to point to an issue with the config file (or access to the config file).

I sent this very moment, I did not specify the problem, I believe you will see now.

[Tim (PassMark)]

You can email us the log file. Could you also please include the C:\Users\<your user name>\AppData\Local\PassMark\PerformanceTest9\Last Used.cfg as well, at the moment we're speculating there is an invalid value saved in the config file that might be messing up the selected disk name.

If you have selected a different disk in the preferences and exited PerformanceTest then the next time it is started the same disk should be selected, if not then this too would seem to point to an issue with the config file (or access to the config file).

[SimPos]

Thanks, there should also be a "SysInfoLog.txt" file, can you please attach that too as well as a screenshot of the available hard drives in the "Drive under test" drop down list.

"SysInfoLog.txt
Your file of 258.7 KB exceeds the limit of 146.5 KB."

and now?

Print share.

[Tim (PassMark)]

Thanks, there should also be a "SysInfoLog.txt" file, can you please attach that too as well as a screenshot of the available hard drives in the "Drive under test" drop down list.

[SimPos]

The specific error indicated in the log is "Path not found", could you please launch this build in debug mode, https://www.passmark.com/ftp/temp/petst_debug-2.exe, try to run the disk test again and send us the log files so we can see what the exact path is at this point (which should be the same as the "Drive under test" selected in the preferences).

Hi friend, I made your test, first removed the current PerformanceTest and restarted the notebook, then installed this PerformanceTest that you provided.

I have refined the test and accused the same error, I am sending the attached log.

If in "Driver under test" the option "C: Windows [Local Drive]" was fixed, probably this error would not return, because as I said, it stays in this option until the first test runs, the next test the option returns to "User appData [C: ...] ".

I also add that if you enter the preferences and simply give "OK", it is also possible to run the first test, but in the following test the error returns.

[Tim (PassMark)]

The specific error indicated in the log is "Path not found", could you please launch this build in debug mode, https://www.passmark.com/ftp/temp/petst_debug-2.exe, try to run the disk test again and send us the log files so we can see what the exact path is at this point (which should be the same as the "Drive under test" selected in the preferences).

[SimPos]

Well I'm here again, I reinstalled and returned the problem. I had resolved disabling the HD slave and restarting, but this time my method did not work.

Well, now I have the DEBUGMODE, Attached in the PerfTestlog attachment (SysInfoLog has 300KB and the limit is 150 KB), and I repeat, I have enough space.

[SimPos]

The log shows you didn't run the disk test.

Can you leave DEBUGMODE on, then run the disk test to get the error. Then post the log.

Well before I see your answer, I solved it in a palatable way, the error was in "Drive 6" with insufficient space, and my notebook has 6 partitions, some partitions have a few MB (EFI System, Recovery, WinRE etc ...) , so I thought ... PerformanceTest was pointing to one of these partitions.

So I decided to disable the HD, and re-run the test, the error continued, I uninstalled the PerformanceTest and reinstalled again, and then the bug stopped.

I also add, this notebook has factory configurations and partitions, I have not formatted yet, I have recently.