New build, 8TB HGST HE10 SAS3 drives showing a running SMART Long test running after power cycle(s).

Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.

billbillw

New Member
Feb 5, 2018
22
12
3
53
I asked this question over at the TrueNAS Community and haven't gotten any responses. I have a curious situation with a new server build.

I have 5x 8TB SAS drives that I purchased used, model HUH721008AL5200. I put these into a Supermicro X10SRH-CF build using the embedded SAS3008 (IT mode) controller in a Supermicro CSE-826 case (with a SAS3 backplane). I installed TrueNAS Scale (Bluefin) last week and started doing some drive tests before creating the pool, and migrating data. I started a set of SMART Long tests individually using the GUI. I got some error messages that made it sound like I could only run one test at at time. I tried to abort the running tests, but I got a messages like this:

root@truenas[~]# smartctl -X /dev/sda
smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.15.79+truenas] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

Abort self test failed [unsupported field in scsi command]
root@truenas[~]#

I went ahead and ran a simultaneous SMART Long test on all drives after doing a power off cycle, which I had read would cancel any running SMART tests.

Funny thing is, the drives still show the previous SMART Long test in progress. It has been like this for several days and other power cycles.

The GUI shows this (for each of the SAS drives)
SMART Long still running.jpg

smartctl -a also shows the test is in progress. Here is an example:
root@truenas[~]# smartctl -a /dev/sda
smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.15.79+truenas] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor: HGST
Product: HUH721008AL5200
Revision: A384
Compliance: SPC-4
User Capacity: 8,001,563,222,016 bytes [8.00 TB]
Logical block size: 512 bytes
Physical block size: 4096 bytes
LU is fully provisioned
Rotation Rate: 7200 rpm
Form Factor: 3.5 inches
Logical Unit id: 0x5000cca2520beba0
Serial number: 7SG6K74C
Device type: disk
Transport protocol: SAS (SPL-3)
Local Time is: Sat Jan 21 11:46:51 2023 EST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
Temperature Warning: Enabled

=== START OF READ SMART DATA SECTION ===
SMART Health Status: OK

Grown defects during certification <not available>
Total blocks reassigned during format <not available>
Total new blocks reassigned <not available>
Power on minutes since format <not available>
Current Drive Temperature: 28 C
Drive Trip Temperature: 85 C

Accumulated power on time, hours:minutes 38718:40
Manufactured in week 12 of year 2017
Specified cycle count over device lifetime: 50000
Accumulated start-stop cycles: 95
Specified load-unload count over device lifetime: 600000
Accumulated load-unload cycles: 1583
Elements in grown defect list: 0

Vendor (Seagate Cache) information
Blocks sent to initiator = 22030695324975104

Error counter log:
Errors Corrected by Total Correction Gigabytes Total
ECC rereads/ errors algorithm processed uncorrected
fast | delayed rewrites corrected invocations [10^9 bytes] errors
read: 0 4463 0 4463 73165473 209169.321 0
write: 0 0 0 0 4775605 183118.763 0
verify: 0 2013 0 2013 3100719 341980.772 0

Non-medium error count: 0

SMART Self-test log
Num Test Status segment LifeTime LBA_first_err [SK ASC ASQ]
Description number (hours)
# 1 Background long Completed - 38684 - [- - -]
# 2 Background long Self test in progress ... - NOW - [- - -]
# 3 Background short Completed - 38647 - [- - -]
# 4 Background short Completed - 38623 - [- - -]
# 5 Background short Completed - 38599 - [- - -]
# 6 Background short Completed - 38575 - [- - -]
# 7 Background short Completed - 38556 - [- - -]

Long (extended) Self-test duration: 60592 seconds [1009.9 minutes]

root@truenas[~]#

Can anyone explain this? Is it anything to be concerned about or is it just a weird anomaly? I've proceeded with running Badblocks on all the drives and so far, there are no errors (about 70% completed). I will run another set of long tests after badblocks is finished. If that comes back fine, should these drives be OK for use?

As far as timing, the server sat idle for over 24 hours before I started the badblocks test which should have let any running SMART test to finish. The successfull tests that I ran only took 16hrs.
 
Last edited:

CyklonDX

Well-Known Member
Nov 8, 2022
784
255
63
in enterprise disks most often you get only good, warn or bad indicator
They only supply whats needed for raid controller in mind. (your disk reports as OK, which means the disk is working great)

Its perfectly normal.
 

billbillw

New Member
Feb 5, 2018
22
12
3
53
in enterprise disks most often you get only good, warn or bad indicator
They only supply whats needed for raid controller in mind. (your disk reports as OK, which means the disk is working great)

Its perfectly normal.
Thanks for confirming.