Opened 3 years ago

Last modified 3 years ago

#1504 new defect

defect - WD Elements external hard drive errors with "not capable of SMART self-check"

Reported by: kageurufu Owned by:
Priority: major Milestone: undecided
Component: all Version:
Keywords: Cc:

Description (last modified by Christian Franke)

I get the following error from smartd with one of my external drives, connected over USB.

Device: /dev/sdf [SAT], not capable of SMART self-check
Device: /dev/sdf [SAT], failed to read SMART Attribute Data

I am able to query using smartctl, execute short and long tests, and get the results

smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.10.40-1-lts] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke,
Device Model:     WDC WD140EDFZ-11A0VA0
Serial Number:    [redacted]
LU WWN Device Id: 5 000cca 290c402e0
Firmware Version: 81.00A81
User Capacity:    14,000,519,643,136 bytes [14.0 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Form Factor:      3.5 inches
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   ACS-2, ATA8-ACS T13/1699-D revision 4
SATA Version is:  SATA 3.2, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Thu Jun 24 11:59:23 2021 MST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

Attachments (1)

smartctl.txt (14.0 KB ) - added by kageurufu 3 years ago.

Download all attachments as: .zip

Change History (4)

comment:1 by Christian Franke, 3 years ago

Description: modified (diff)

comment:2 by Christian Franke, 3 years ago

Milestone: undecided

The smartd message not capable of SMART self-check means that the SMART RETURN STATUS command (smartctl -H) did not work. This is unrelated to short and long self-tests (smartctl -t ...).

The smartctl -i output above is not sufficient for diagnostics. Please provide output of

smartctl -q noserial -x -a /dev/sdf

as an attachment to this ticket.

by kageurufu, 3 years ago

Attachment: smartctl.txt added

comment:3 by kageurufu, 3 years ago

Attached that log for you!

Note: See TracTickets for help on using tickets.