Can anyone confirm this is correct for what a burn-in log would look like?

TrueNAS General
,
1

Hey all,
I’m using this disk-burnin-and-testing script from @dak180 (thank you Dak!), and I just have a question on what the final output of a log file should look like after a successful burn-in run?

  1. The included log example seems quite different than what I have for log files that have generating for my in-progress jobs.
  2. I am not sure if a .bb file should have data in it or not? Would it only log something if there was an error?

Thanks for the help. Here is an example of what I have for my in-progress tests:

+-----------------------------------------------------------------------------
+ Started burn-in of /dev/sdb : Sun Aug 24 08:40:30 PDT 2025
+-----------------------------------------------------------------------------
Host: truenas
Drive Model: WDC WD80EFPX-68C4ZN0
Serial Number: WD-xxxxxxxxx
Short test duration: 2 minutes
Short test sleep duration: 120 seconds
Conveyance test duration: 5 minutes
Conveyance test sleep duration: 300 seconds
Extended test duration: 794 minutes
Extended test sleep duration: 47640 seconds
Log file: ./burnin-WDC WD80EFPX-68C4ZN0-WD-xxxxxxx-20250824-1540+0.log
Bad blocks file: ./burnin-WDC WD80EFPX-68C4ZN0-WD-xxxxxx-20250824-1540+0.bb

SCT Error Recovery Control:
           Read:     70 (7.0 seconds)
          Write:     70 (7.0 seconds)

+-----------------------------------------------------------------------------
+ Run SMART short test on drive /dev/sdb: Sun Aug 24 08:40:30 PDT 2025
+-----------------------------------------------------------------------------
Short test started, sleeping 120 seconds until it finishes
SMART self-test complete
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.12.15-production+truenas] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF READ SMART DATA SECTION ===
SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%         0         -

Finished SMART short test on drive /dev/sdb: Sun Aug 24 08:42:30 PDT 2025
+-----------------------------------------------------------------------------
+ Run SMART conveyance test on drive /dev/sdb: Sun Aug 24 08:42:30 PDT 2025.
+-----------------------------------------------------------------------------
Conveyance test started, sleeping 300 seconds until it finishes.
SMART self-test complete
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.12.15-production+truenas] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF READ SMART DATA SECTION ===
SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Conveyance offline  Completed without error       00%         0         -
# 2  Short offline       Completed without error       00%         0         -

Finished SMART conveyance test on drive /dev/sdb: Sun Aug 24 08:47:30 PDT 2025.
+-----------------------------------------------------------------------------
+ Run SMART extended test on drive /dev/sdb: Sun Aug 24 08:47:30 PDT 2025
+-----------------------------------------------------------------------------
Extended test started, sleeping 47640 seconds until it finishes
SMART self-test complete
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.12.15-production+truenas] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF READ SMART DATA SECTION ===
SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed without error       00%        14         -
# 2  Conveyance offline  Completed without error       00%         0         -
# 3  Short offline       Completed without error       00%         0         -

Finished SMART extended test on drive /dev/sdb: Sun Aug 24 22:04:32 PDT 2025
+-----------------------------------------------------------------------------
+ Run SMART offline test on drive /dev/sdb: Sun Aug 24 22:04:32 PDT 2025.
+-----------------------------------------------------------------------------
Offline test started, sleeping 11804 seconds until it finishes.
SMART self-test complete
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.12.15-production+truenas] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF ENABLE/DISABLE COMMANDS SECTION ===
SMART Automatic Offline Testing Enabled every four hours.

smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.12.15-production+truenas] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF READ SMART DATA SECTION ===
SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed without error       00%        14         -
# 2  Conveyance offline  Completed without error       00%         0         -
# 3  Short offline       Completed without error       00%         0         -

Finished SMART offline test and activated automated testing (if supported) on drive /dev/sdb: Mon Aug 25 01:21:17 PDT 2025.
+-----------------------------------------------------------------------------
+ Run badblocks test on drive /dev/sdb: Mon Aug 25 01:21:17 PDT 2025
+-----------------------------------------------------------------------------
2

I do not see the last part of the output whcih should say something like Finished badblocks test on drive /dev/sdb date&time Badblocks takes a long time to run. Are you sure it is not running?

1 Like
3

@joeschmuck you da bess. You are correct it is still running - just wondering what I’m looking for to indicate ‘success’. I appreciate you passing what the final line to check for in my logs should be.

I’m jumping between vim and tmux checking the running processes, and just trying to figure it out as I go. I appreciate your help! :slight_smile:

PS - since I’m just building this - I’m looking forward to trying to get your monitoring scripts running as well. Looks cool!

4

I have not run the @dak180 script myself, I just took a quick look at it yesterday. You will get a line that tells you things are done and I think it tells you how many errors it found, if any. But it take a long time to run badblocks, especially if you have a large capacity drive. Very very long! The test has a lot of hard drive to test. I believe there are four test patterns in badblocks so it needs to write a test pattern, read that test pattern back, then write the next test pattern… you get the point. If a SMART Extended test (read only test) takes 14 hours, imagine this time 8 at a minimum. This is just a guess.

Both .log and .bb files I suspect are text files. I would expect both to be present once done.

Sorry I could not be of more help.

5

Just getting the confirmation is very helpful, so thanks for that! Yes I’m on 66 hours for one of the drives! Honestly…I love this stuff. :slight_smile: So much to learn.

+-----------------------------------------------------------------------------
+ Run badblocks test on drive /dev/sdb: Sun Aug 24 21:43:42 PDT 2025
+-----------------------------------------------------------------------------
Checking for bad blocks in read-write mode
From block 0 to 1953506645
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: 86.56% done, 62:56:26 elapsed. (0/0/0 errors) errors). (0/0/0 errors). (0/0/0 errors). (0/0/0 errors). (0/0/0 errors). (0/0/0 errors)(0/0/0 errors)s)