When I run a manual test in the GUI, I get an error, no real description to be given here cause there's no error number or description besides the smarttest version, but then it says the test is starting. But the test is running in the background, the GUI doesn't display it at all (can't view test results either, different matter I think).
I've chalked this up to the possibility of it being WD DC550 SAS drives in the server. As tests on my boot drives and standard SATA disk function as expected. The SAS drives mount fine, I can make pools/volumes, everything is great, but the GUI can't really do any form of useful health communication with them. Short tests in smartctl just say "completed" with no table information like SATA drives usually provide.
I'm running a long test in terminal now just to see what it spits back, but that takes about 18 hours.
But here is the drive information:
I guess what I'm trying to ask, is this a bug in TrueNAS? Do does the gui side for smartctl just not support standard SATA drives? What would be the suggest best practice for checking on health of the server periodically? ideally the entire purpose of using truenas for me is to have a stable GUI to interact with, but without getting drive scans/health checks on a regular basis, if I'm going to be living in terminal all the time...maybe it doesn't make much sense besides user management?
I've chalked this up to the possibility of it being WD DC550 SAS drives in the server. As tests on my boot drives and standard SATA disk function as expected. The SAS drives mount fine, I can make pools/volumes, everything is great, but the GUI can't really do any form of useful health communication with them. Short tests in smartctl just say "completed" with no table information like SATA drives usually provide.
Code:
=== START OF READ SMART DATA SECTION ===
Self-test execution status: 41% of test remaining
SMART Self-test log
Num Test Status segment LifeTime LBA_first_err [SK ASC ASQ]
Description number (hours)
# 1 Background long Self test in progress ... - NOW - [- - -]
# 2 Background short Completed - 0 - [- - -]
Long (extended) Self-test duration: 65535 seconds [1092.2 minutes]
I'm running a long test in terminal now just to see what it spits back, but that takes about 18 hours.
But here is the drive information:
Code:
root@anton[~]# smartctl -a /dev/da1
smartctl 7.2 2020-12-30 r5155 [FreeBSD 12.2-RELEASE-p6 amd64] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Vendor: WDC
Product: WUH721818AL5201
Revision: B232
Compliance: SPC-5
User Capacity: 18,000,207,937,536 bytes [18.0 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:
Serial number:
Device type: disk
Transport protocol: SAS (SPL-3)
Local Time is: Sun May 2 12:49:58 2021 PDT
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: 31 C
Drive Trip Temperature: 85 C
Accumulated power on time, hours:minutes 13:56
Manufactured in week 50 of year 2020
Specified cycle count over device lifetime: 50000
Accumulated start-stop cycles: 2
Specified load-unload count over device lifetime: 600000
Accumulated load-unload cycles: 2
Elements in grown defect list: 0
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 0 0 0 1 0.013 0
write: 0 0 0 0 126 1.923 0
verify: 0 0 0 0 115 0.000 0
Non-medium error count: 0
Self-test execution status: 41% of test remaining
SMART Self-test log
Num Test Status segment LifeTime LBA_first_err [SK ASC ASQ]
Description number (hours)
# 1 Background long Self test in progress ... - NOW - [- - -]
# 2 Background short Completed - 0 - [- - -]
Long (extended) Self-test duration: 65535 seconds [1092.2 minutes]I guess what I'm trying to ask, is this a bug in TrueNAS? Do does the gui side for smartctl just not support standard SATA drives? What would be the suggest best practice for checking on health of the server periodically? ideally the entire purpose of using truenas for me is to have a stable GUI to interact with, but without getting drive scans/health checks on a regular basis, if I'm going to be living in terminal all the time...maybe it doesn't make much sense besides user management?
