Opened 4 months ago

Closed 3 months 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)

SG2TB-201509-2 test never completes 20210917.txt (9.5 KB) - added by Stéphane BARIZIEN 4 months ago.
Screenshot of on 2021-09-17 17-01-25.png (257.0 KB) - added by Stéphane BARIZIEN 4 months ago.
Screenshot of DLGDIAG - VIEW TEST RESULT on 2021-09-17 17-01-45.png (60.7 KB) - added by Stéphane BARIZIEN 4 months ago.
smartctl-x.zip (12.4 KB) - added by Stéphane BARIZIEN 3 months ago.
Outputs of 'smartctl -x' captured before, during and after execution of WD's Data Lifeguard Diagnostic tool

Download all attachments as: .zip

Change History (8)

Changed 4 months ago by Stéphane BARIZIEN

Changed 4 months ago by Stéphane BARIZIEN

comment:1 Changed 4 months ago by Christian Franke

Milestone: undecided

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 ?

  • A valid Self-test execution status during a test ?
  • A new entry in SMART Self-test and/or SMART Extended Self-test logs after a test ?

If not, the WD tool performs the test without using SMART functionality.

PS: Please use smartctl -x because -a only prints the legacy SMART logs.

Changed 3 months ago by Stéphane BARIZIEN

Attachment: smartctl-x.zip added

Outputs of 'smartctl -x' captured before, during and after execution of WD's Data Lifeguard Diagnostic tool

comment:2 Changed 3 months ago by Stéphane BARIZIEN

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 Changed 3 months ago by Christian Franke

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 Changed 3 months ago by Christian Franke

Keywords: ata added
Milestone: undecided
Resolution: invalid
Status: newclosed

This is a drive firmware bug which cannot be fixed by smartctl.

Note: See TracTickets for help on using tickets.