Is my hard disk dying ?

trapanator · 2021-06-27 10:02:58

Can you tell if my hard disk is to be replaced?

KDE reports that my hard disk is "unstable". The smartctl reports (complete smartctl log is here https://pastebin.com/raw/E899jmaZ )

- ALL smartctl values are OK (no unrecoverable sector errors, etc).
- But there are these warnings:

Error 808 occurred at disk power-on lifetime: 5419 hours (225 days + 19 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  04 51 00 02 00 00 e0

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  b4 20 00 6b 4c 72 e0 00      00:00:05.870  SANITIZE DEVICE
  f5 00 00 00 00 00 e0 00      00:00:05.870  SECURITY FREEZE LOCK

trapanator · 2021-06-27 10:03:28

note: I noticed that this error appears when I power on my PC

seth · 2021-06-27 12:47:32

Looks more like something™ unconditionally calls "hdparm --sanitize-freeze-lock" (or equivalent)
What's the output of

sudo hdparm --sanitize-status /dev/sdwherever
sudo hdparm -I /dev/sdwherever

?

Do not issue random hdparm commands to try them w/o knowing what you do!

trapanator · 2021-06-27 15:04:02

seth wrote:

Looks more like something™ unconditionally calls "hdparm --sanitize-freeze-lock" (or equivalent)
What's the output of
sudo hdparm --sanitize-status /dev/sdwherever
?
Do not issue random hdparm commands to try them w/o knowing what you do!

$ sudo hdparm --sanitize-status /dev/sda

/dev/sda:
Issuing SANITIZE_STATUS command
Sanitize status:
    State:    SD0 Sanitize Idle

$ sudo hdparm -I /dev/sda

/dev/sda:

ATA device, with non-removable media
        Model Number:       WDC WD5000LPLX-60ZNTT1                  
        Serial Number:      WD-WXB1AB6LF07N
        Firmware Revision:  02.01A02
        Transport:          Serial, SATA 1.0a, SATA II Extensions, SATA Rev 2.5, SATA Rev 2.6, SATA Rev 3.0
Standards:
        Used: unknown (minor revision code 0x001f) 
        Supported: 9 8 7 6 5 
        Likely used: 9
Configuration:
        Logical         max     current
        cylinders       16383   16383
        heads           16      16
        sectors/track   63      63
        --
        CHS current addressable sectors:    16514064
        LBA    user addressable sectors:   268435455
        LBA48  user addressable sectors:   976773168
        Logical  Sector size:                   512 bytes
        Physical Sector size:                  4096 bytes
        Logical Sector-0 offset:                  0 bytes
        device size with M = 1024*1024:      476940 MBytes
        device size with M = 1000*1000:      500107 MBytes (500 GB)
        cache/buffer size  = unknown
        Form Factor: 2.5 inch
        Nominal Media Rotation Rate: 7200
Capabilities:
        LBA, IORDY(can be disabled)
        Queue depth: 32
        Standby timer values: spec'd by Standard, with device specific minimum
        R/W multiple sector transfer: Max = 16  Current = 0
        Advanced power management level: 254
        DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6 
             Cycle time: min=120ns recommended=120ns
        PIO: pio0 pio1 pio2 pio3 pio4 
             Cycle time: no flow control=120ns  IORDY flow control=120ns
Commands/features:
        Enabled Supported:
           *    SMART feature set
                Security Mode feature set
           *    Power Management feature set
           *    Write cache
           *    Look-ahead
           *    WRITE_BUFFER command
           *    READ_BUFFER command
           *    NOP cmd
           *    DOWNLOAD_MICROCODE
           *    Advanced Power Management feature set
                Power-Up In Standby feature set
           *    SET_FEATURES required to spinup after power up
           *    48-bit Address feature set
           *    Device Configuration Overlay feature set
           *    Mandatory FLUSH_CACHE
           *    FLUSH_CACHE_EXT
           *    SMART error logging
           *    SMART self-test
           *    General Purpose Logging feature set
           *    64-bit World wide name
           *    IDLE_IMMEDIATE with UNLOAD
           *    WRITE_UNCORRECTABLE_EXT command
           *    {READ,WRITE}_DMA_EXT_GPL commands
           *    Segmented DOWNLOAD_MICROCODE
           *    Gen1 signaling speed (1.5Gb/s)
           *    Gen2 signaling speed (3.0Gb/s)
           *    Gen3 signaling speed (6.0Gb/s)
           *    Native Command Queueing (NCQ)
           *    Phy event counters
           *    Idle-Unload when NCQ is active
           *    READ_LOG_DMA_EXT equivalent to READ_LOG_EXT
           *    DMA Setup Auto-Activate optimization
                Device-initiated interface power management
           *    Software settings preservation
           *    SMART Command Transport (SCT) feature set
           *    SCT Write Same (AC2)
           *    SCT Error Recovery Control (AC3)
           *    SCT Features Control (AC4)
           *    SCT Data Tables (AC5)
                unknown 206[12] (vendor specific)
                unknown 206[13] (vendor specific)
           *    SANITIZE feature set
           *    OVERWRITE_EXT command
           *    DOWNLOAD MICROCODE DMA command
           *    WRITE BUFFER DMA command
           *    READ BUFFER DMA command
Security: 
        Master password revision code = 65534
                supported
        not     enabled
        not     locked
                frozen
        not     expired: security count
                supported: enhanced erase
        70min for SECURITY ERASE UNIT. 70min for ENHANCED SECURITY ERASE UNIT.
Logical Unit WWN Device Identifier: 50014ee6b1ec5454
        NAA             : 5
        IEEE OUI        : 0014ee
        Unique ID       : 6b1ec5454
Checksum: correct

seth · 2021-06-27 19:53:40

Does

hdparm --security-freeze /dev/sdsomehwere

get you a new error for "SECURITY FREEZE LOCK"?

The state currely is frozen (which is good) and all buffered errors occurred within 12h before the smartctl query with 5,2 & 3 hours inbetween - not sure whether this is due to some boot script or whether there's a periodic call that fails for being idempotent, but the call must have succeeed at some point (or is blocked and the drive statically frozen)

trapanator · 2021-06-28 05:14:04

$ sudo hdparm --security-freeze /dev/sda

/dev/sda:
 issuing security freeze command

this command (and neither the following) doesn't add a new SECURITY FREEZE LOCK error.

seth · 2021-06-28 06:00:05

Do the error times correlate w/ the system booting?

trapanator · 2021-06-28 07:25:01

seth wrote:

Do the error times correlate w/ the system booting?

The few one I checked, yes.

ATA Error Count: 815 (device log contains only the most recent five errors)

815 errors like this, because KDE Notified me about this and I checked the last 10.

seth · 2021-06-28 12:08:38

Check your system jorunal - I suspect that some startup script/system service triggers this and fails.
This is a firmware thing and ultimately succeeds, so maybe some race condition but *not* indicative of your disk falling apart.

trapanator · 2021-06-28 13:53:57

I found this:

giu 27 19:30:26 hp800 smartd[1073]: Device: /dev/sda [SAT], SMART Usage Attribute: 188 Command_Timeout changed from 100 to 99
giu 27 19:30:26 hp800 smartd[1073]: Device: /dev/sda [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 60 to 61
giu 27 19:30:26 hp800 smartd[1073]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 103 to 104
giu 27 19:30:26 hp800 smartd[1073]: Device: /dev/sda [SAT], ATA error count increased from 812 to 815

seth · 2021-06-28 14:01:27

cat /etc/smartd.conf

?

trapanator · 2021-06-28 15:15:35

Removing all comments, smartd.conf contains this only one row:

DEVICESCAN -d removable -n standby -m root -M exec /usr/share/smartmontools/smartd-runner

seth · 2021-06-28 15:47:36

smartd might default to that (iirc there was some bug/request) - try to disable the smartd service, reboot, check whether there's a new error.
If not, you may need to delay the service a bit to mitigate a race condition - or ignore the errors.

Arch Linux

#1 2021-06-27 10:02:58

Is my hard disk dying ?

#2 2021-06-27 10:03:28

Re: Is my hard disk dying ?

#3 2021-06-27 12:47:32

Re: Is my hard disk dying ?

#4 2021-06-27 15:04:02

Re: Is my hard disk dying ?

#5 2021-06-27 19:53:40

Re: Is my hard disk dying ?

#6 2021-06-28 05:14:04

Re: Is my hard disk dying ?

#7 2021-06-28 06:00:05

Re: Is my hard disk dying ?

#8 2021-06-28 07:25:01

Re: Is my hard disk dying ?

#9 2021-06-28 12:08:38

Re: Is my hard disk dying ?

#10 2021-06-28 13:53:57

Re: Is my hard disk dying ?

#11 2021-06-28 14:01:27

Re: Is my hard disk dying ?

#12 2021-06-28 15:15:35

Re: Is my hard disk dying ?

#13 2021-06-28 15:47:36

Re: Is my hard disk dying ?

Board footer