Opened 3 years ago
Closed 2 years ago
#1522 closed defect (invalid)
Long test never completes on Western Digital Blue Mobile WDC WD20SPZX-60UA7T0
| Reported by: | Stéphane BARIZIEN | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | |
| Component: | all | Version: | 7.2 |
| Keywords: | ata | Cc: |
Description
I've just bought a Western Digital Blue Mobile WDC WD20SPZX-60UA7T0 and attempted to throw my health monitoring tooling at it (a set of PowerShell scripts that use smartmontools; the main test uses smartctl --test=long).
After more than 24 hours, the progress of the test is still at "10% remaining" -- see attached file. I have to abort the test with smartctl -X.
When running an "extended test" with Western Digital's "Data Lifeguard Diagnostic for Windows", the test does run to completion -- see screenshots.
Needless to say, I've never encountered this with any other drive.
Attachments (4)
Change History (8)
by , 3 years ago
| Attachment: | SG2TB-201509-2 test never completes 20210917.txt added |
|---|
by , 3 years ago
| Attachment: | Screenshot of on 2021-09-17 17-01-25.png added |
|---|
by , 3 years ago
| Attachment: | Screenshot of DLGDIAG - VIEW TEST RESULT on 2021-09-17 17-01-45.png added |
|---|
comment:1 by , 3 years ago
| Milestone: | → undecided |
|---|
by , 3 years ago
| Attachment: | smartctl-x.zip added |
|---|
Outputs of 'smartctl -x' captured before, during and after execution of WD's Data Lifeguard Diagnostic tool
comment:2 by , 3 years ago
It seems WD's tool doesn't use SMART test -- see attached outputs from smartctl -x
I'll check what test other than 'long' are available and/or see if the 'long' test completes at some point.
comment:3 by , 2 years ago
The before.txt and after_closed.txt do not show any self-test related changes, so it is very likely that the WD tool does not use SMART self-tests.
The during*.txt files lack important information as smartctl was not run with admin rights:
... Warning: Limited functionality due to missing admin rights ... Read SMART Self-test Log failed: Function requires admin rights ...
comment:4 by , 2 years ago
| Keywords: | ata added |
|---|---|
| Milestone: | undecided |
| Resolution: | → invalid |
| Status: | new → closed |
This is a drive firmware bug which cannot be fixed by smartctl.
Self-test problems cannot be fixed by smartctl. Self-tests are simply started by smartctl and then controlled by drive firmware. See related FAQ entries.
If a long test does not work, try to use several selective self-tests. See the various
-t select,...options on smartctl man page.Are the tests run by WD's tool visible in SMART data ?
Self-test execution statusduring a test ?SMART Self-testand/orSMART Extended Self-testlogs after a test ?If not, the WD tool performs the test without using SMART functionality.
PS: Please use
smartctl -xbecause-aonly prints the legacy SMART logs.