Show burn in Disk error(Disk C,D is full) with Burnin 10.2 build 1014 loop test.

[David (PassMark)]

There are three reasons that we are aware of for file not being deleted
1) BurnInTest crashed before the test completes. The software can't delete the files if the software isn't running anymore.
2) Some third party software locked the files (this is only in theory, we have never actually seen this happen, but in theory it is possible).
3) The -K command line option was used.

If we don't run Burnin test, the disk size won't be added

I don't understand what you mean by this. Sorry.

BurnInTest can report the disk is full while the test is running, but only if the disk is full. i.e. some third party software is also writing files, filling up the disk.

[hsiuyan]

Hello Sir,
Sorry and I post a wrong picture and the log is for C disk only. We can see the files are removed after closing Burnin app and then wait a while. If we don't run Burnin test, the disk size won't be added. For the reason, I can't know why the files can't be removed if C disk's size will be full. Are there some reasons for that?

[David (PassMark)]

The log contains many errors saying C: drive is full. We suspect this is correct, and C: really is full. Meaning that the test can't complete.
This can happen if some other 3rd party software (or Windows itself) starts using up a lot of disk space while the test is running.

The log doesn't contain any errors for D:

The test files should be removed after the test is complete. But there is a command line option (-K) that will force BurnInTest to keep the files. This is useful when you need to examine the files for corruption (e.g. in the case of bit flips). Maybe you are using this option?

[hsiuyan]

The files should be deleted if disk size will be full. But from the result, the disk error due to the test file can't be clear.
(Please refer the logs as the attachment.)
------------------
SERIOUS: 2024-09-15 09:51:03, Disk, C: Error writing to disk - Disk is full
LOG NOTE: 2024-09-15 09:51:03, Disk, Write File Block: C:\BurnInTest test files\~bittestC00001, Block Size: 524288, Block Num: 15576, Ops: 230485727379456 (B)
LOG NOTE: 2024-09-15 09:51:03, Disk, There is not enough space on the disk. (112)
SERIOUS: 2024-09-15 09:51:18, Disk, C: Error writing to disk - Disk is full
LOG NOTE: 2024-09-15 09:51:18, Disk, Write File Block: C:\BurnInTest test files\~bittestC00001, Block Size: 524288, Block Num: 15576, Ops: 230493697081344 (B)
LOG NOTE: 2024-09-15 09:51:18, Disk, There is not enough space on the disk. (112)
INFORMATION: 2024-09-15 09:51:18, Disk, C: Butterfly seeking skipped for this disk (SSD/NVMe)
LOG NOTE: 2024-09-15 09:51:18, Disk, Disk Error (C: Butterfly seeking skipped for this disk (SSD/NVMe) in Cycle 10690 with pattern High Low freq data overwrite
SERIOUS: 2024-09-15 09:51:37, Disk, C: Error writing to disk - Disk is full
LOG NOTE: 2024-09-15 09:51:37, Disk, Write File Block: C:\BurnInTest test files\~bittestC00001, Block Size: 524288, Block Num: 15576, Ops: 230501809389568 (B)
LOG NOTE: 2024-09-15 09:51:37, Disk, There is not enough space on the disk. (112)
LOG NOTE: 2024-09-15 09:51:37, Disk, Disk Error (C: Error writing to disk - Disk is full in Cycle 10691 with pattern Binary data pattern 1 (1010)
SERIOUS: 2024-09-15 09:52:15, Disk, C: Error writing to disk - Disk is full
LOG NOTE: 2024-09-15 09:52:15, Disk, Write File Block: C:\BurnInTest test files\~bittestC00001, Block Size: 524288, Block Num: 15575, Ops: 230510573387776 (B)
LOG NOTE: 2024-09-15 09:52:15, Disk, There is not enough space on the disk. (112)
LOG NOTE: 2024-09-15 09:52:15, Disk, Disk Error (C: Error writing to disk - Disk is full in Cycle 10692 with pattern Binary data pattern 2 (0101)
SERIOUS: 2024-09-15 09:52:35, Disk, C: Error writing to disk - Disk is full
LOG NOTE: 2024-09-15 09:52:35, Disk, Write File Block: C:\BurnInTest test files\~bittestC00001, Block Size: 524288, Block Num: 15575, Ops: 230518156165120 (B)