You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for the great script! It works like a charm!
One minor issue I felt might be worth reporting: After completing the badblocks section it started the extended SMART test. The SMART test was supposed to run for 784 minutes but took longer. After around 1022 minutes the script reported "Finished SMART long test." But the test was still running. The threshold had been exceeded.
It's just cosmetics but: Why is there a threshold in the first place? And if the threshold is the reason for ending the script should it not report something different than "Finished SMART long test."?
OS: Debian 12.6/Openmediavault 7
Tested drive: Western Digital Red Plus 8 TB WD80EFPX
Excerpt from the log (I had done a long self test before discovering this script and starting it):
Finished badblocks test
+-----------------------------------------------------------------------------
+ Running SMART long test: Do 1. Aug 02:42:07 CEST 2024
+-----------------------------------------------------------------------------
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.1.0-23-amd64] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF OFFLINE IMMEDIATE AND SELF-TEST SECTION ===
Sending command: "Execute SMART Extended self-test routine immediately in off-line mode".
Drive command "Execute SMART Extended self-test routine immediately in off-line mode" successful.
Testing has begun.
Please wait 784 minutes for test to complete.
Test will complete after Thu Aug 1 15:46:08 2024 CEST
Use smartctl -X to abort test.
SMART long test started, awaiting completion for 47040 seconds ...
SMART self-test timeout threshold exceeded
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.1.0-23-amd64] (local build)
Copyright (C) 2002-22, 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% 75 -
# 2 Short offline Completed without error 00% 74 -
# 3 Extended offline Aborted by host 90% 74 -
# 4 Short offline Completed without error 00% 74 -
# 5 Extended offline Completed without error 00% 57 -
Finished SMART long test
+-----------------------------------------------------------------------------
+ Drive information: Do 1. Aug 19:48:36 CEST 2024
+-----------------------------------------------------------------------------
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.1.0-23-amd64] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Western Digital Red (CMR)
Device Model: WDC WD80EFPX-68C4ZN0
Serial Number: WD-RD03L7ME
LU WWN Device Id: 5 0014ee 2c0c28f7a
Firmware Version: 81.00A81
User Capacity: 8.001.563.222.016 bytes [8,00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 5640 rpm
Form Factor: 3.5 inches
Device is: In smartctl database 7.3/5610
ATA Version is: ACS-3 T13/2161-D revision 5
SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Thu Aug 1 19:48:36 2024 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is: Unavailable
APM feature is: Unavailable
Rd look-ahead is: Enabled
Write cache is: Enabled
DSN feature is: Unavailable
ATA Security is: Disabled, NOT FROZEN [SEC1]
Wt Cache Reorder: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x80) Offline data collection activity
was never started.
Auto Offline Data Collection: Enabled.
Self-test execution status: ( 245) Self-test routine in progress...
50% of test remaining.
Total time to complete Offline
data collection: (10964) seconds.
Offline data collection
capabilities: (0x7b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 784) minutes.
Conveyance self-test routine
recommended polling time: ( 5) minutes.
SCT capabilities: (0x0039) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.
Thanks again for the very helpful script!
The text was updated successfully, but these errors were encountered:
Thanks for the great script! It works like a charm!
One minor issue I felt might be worth reporting: After completing the badblocks section it started the extended SMART test. The SMART test was supposed to run for 784 minutes but took longer. After around 1022 minutes the script reported "Finished SMART long test." But the test was still running. The threshold had been exceeded.
It's just cosmetics but: Why is there a threshold in the first place? And if the threshold is the reason for ending the script should it not report something different than "Finished SMART long test."?
OS: Debian 12.6/Openmediavault 7
Tested drive: Western Digital Red Plus 8 TB WD80EFPX
Excerpt from the log (I had done a long self test before discovering this script and starting it):
Thanks again for the very helpful script!
The text was updated successfully, but these errors were encountered: