Dak180 disk-burnin.sh script does not do any test writes—why?

TrueNAS General
1

Using @dak180’s disk-burnin.sh I am trying to burn in two 16-TB drives on a system running 25.10.1—Goldeye. The hardware is a QNAP TS-464eU with 32 GB of RAM. I am using the command

./disk-burnin-dak180.sh -t -m sdd -l .

Per my log file, the script never gets past the initial SMART offline test:

+-----------------------------------------------------------------------------
+ Started burn-in of /dev/sdc : Thu Jan 15 18:52:43 EST 2026
+-----------------------------------------------------------------------------
Host: qnaptruenas
Drive Model: ST16000NM001G-2KK103
Serial Number: ZL293VLE
Short test duration: 1 minutes
Short test sleep duration: 60 seconds
Conveyance test duration: 2 minutes
Conveyance test sleep duration: 120 seconds
Extended test duration: 1435 minutes
Extended test sleep duration: 86100 seconds
Log file: ./burnin-ST16000NM001G-2KK103-ZL293VLE-20260115-2352+0.log
Bad blocks file: ./burnin-ST16000NM001G-2KK103-ZL293VLE-20260115-2352+0.bb

SCT Error Recovery Control:
           Read:    100 (10.0 seconds)
          Write:    100 (10.0 seconds)

+-----------------------------------------------------------------------------
+ Run SMART offline test on drive /dev/sdc: Thu Jan 15 18:52:43 EST 2026.
+-----------------------------------------------------------------------------
Offline test started, sleeping 575 seconds until it finishes.

After writing this to the log file the process stops. What might be going wrong?

With the script running in a TMUX shell, I then ran the command again, only on sdd. Is that the cause of the problem, that the script cannot run on two drives concurrently?

Actually, no, that couldn’t be. I have another system, an AOOSTAR R7 running the same version of TrueNAS, with 32 GB of RAM installed. There two concurrently running burn-in scripts are proceeding nicely:

+-----------------------------------------------------------------------------
+ Run badblocks test on drive /dev/sda: Sat Jan 10 22:39:31 EST 2026
+-----------------------------------------------------------------------------
Checking for bad blocks in read-write mode
From block 0 to 3906469887
Testing with pattern 0xaa: done                                                 
Reading and comparing: done                                                 
Testing with pattern 0x55: done                                                 
Reading and comparing: done                                                 
Testing with pattern 0xff: done                                                 
Reading and comparing: 53.12% done, 117:15:09 elapsed. (0/0/0 errors)

I am puzzled.

2

Isn’t it waiting for the SMART test to finish?

1 Like
3

Yes, but only less than 10 min. After a couple of days I checked on the script by trying to re-attach the tmux shell, in which the command was running. However, tmux ls showed no active jobs. They had just ended and left the log file in the condition I showed in my original post. No writing of 0s and 1s ever had occurred.

4

The script shows a Extended test duration of 1435 minutes in the first post. Did you check to see if SMART tests are running? You are looking at about 1 day. Try checking on current tests with smartctl?

5

If the test had still been running at the point that I was checking on the status of the script, tmux ls would not have returned nothing.