Jump to content

HDD read errors , Failed segment in smart test - What should I do?

Featured Replies

Posted

Hi All, 

 

I'm new to the unraid community, still learning and trying to figure it out, so please be gentle :) I've listed my questions below but please add anything else if needed. 

 

I've just noticed that I have some read errors on one of my drives. When I noticed I tried to run a SMART extended test (twice) but it failed in segment both times.

 

I have 5 x 4tb hard drives installed in my system, they are old server drives so I expected they may not be the most stable of drives so I have set 2 of them up as a parity.  

 

1. Should I replace the drive with read errors, or perform some other tests? I have other spare drives available

2. My parity check was done 30 days ago, will this have any effect on my rebuilding the cache 

 

 

image.thumb.png.a4c96bc2bbde5e518058fa4a6515737b.png

  • Author
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.1.79-Unraid] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor:               HGST
Product:              HUS724040ALS640
Revision:             A280
Compliance:           SPC-4
User Capacity:        4,000,787,030,016 bytes [4.00 TB]
Logical block size:   512 bytes
LU is fully provisioned
Rotation Rate:        7200 rpm
Form Factor:          3.5 inches
Logical Unit id:      0x5000cca07356ee1c
Serial number:        PEHJU1ZX
Device type:          disk
Transport protocol:   SAS (SPL-4)
Local Time is:        Thu Aug 15 13:36:39 2024 AEST
SMART support is:     Available - device has SMART capability.
SMART support is:     Enabled
Temperature Warning:  Enabled
Read Cache is:        Enabled
Writeback Cache is:   Disabled

=== START OF READ SMART DATA SECTION ===
SMART Health Status: OK

Current Drive Temperature:     39 C
Drive Trip Temperature:        85 C

Manufactured in week 44 of year 2015
Specified cycle count over device lifetime:  50000
Accumulated start-stop cycles:  38
Specified load-unload count over device lifetime:  600000
Accumulated load-unload cycles:  1892
Elements in grown defect list: 132

Vendor (Seagate Cache) information
  Blocks sent to initiator = 5113223527268352

Error counter log:
           Errors Corrected by           Total   Correction     Gigabytes    Total
               ECC          rereads/    errors   algorithm      processed    uncorrected
           fast | delayed   rewrites  corrected  invocations   [10^9 bytes]  errors
read:    1097210       45         0   1097255   205385743     389969.089         101
write:         0        0         0         0      17266      26205.738           0
verify:        6        0         0         6      19624          0.000           0

Non-medium error count:        0

SMART Self-test log
Num  Test              Status                 segment  LifeTime  LBA_first_err [SK ASC ASQ]
     Description                              number   (hours)
# 1  Background long   Failed in segment -->       7   50961         536858403 [0x3 0x5d 0x1]
# 2  Background long   Failed in segment -->       7   50961         536845737 [0x3 0x5d 0x1]
# 3  Background long   Completed                   -   50471                 - [-   -    -]
# 4  Background long   Failed in segment -->       7   50461         593312290 [0x3 0x5d 0x1]

Long (extended) Self-test duration: 37452 seconds [10.4 hours]

Background scan results log
  Status: waiting until BMS interval timer expires
    Accumulated power on time, hours:minutes 50962:13 [3057733 minutes]
    Number of background scans performed: 136,  scan progress: 0.00%
    Number of background medium scans performed: 136

   #  when        lba(hex)    [sk,asc,ascq]    reassign_status
   1 50533:40  00000000d9f2047f  [3,11,0]   Recovered via rewrite in-place
   2 50529:35  00000000235ecaf8  [3,11,0]   Reassigned by app, has valid data
   3 50529:35  00000000235ebf3a  [3,11,0]   Reassigned by app, has valid data
   4 50529:35  00000000235eb37c  [3,11,0]   Recovered via rewrite in-place
   5 50529:35  00000000235e9c00  [3,11,0]   Reassigned by app, has valid data
   6 50529:35  00000000235e9042  [3,11,0]   Reassigned by app, has valid data
   7 50529:35  00000000235e8483  [3,11,0]   Reassigned by app, has valid data
   8 50529:35  00000000235e78c5  [3,11,0]   Reassigned by app, has valid data
   9 50529:35  00000000235e6d07  [3,11,0]   Reassigned by app, has valid data
  10 50529:35  00000000235e6149  [3,11,0]   Reassigned by app, has valid data
  11 50529:35  00000000235e558b  [3,11,0]   Reassigned by app, has valid data
  12 50529:35  00000000235e3185  [3,11,0]   Reassigned by app, has valid data
  13 50529:35  00000000235da49c  [3,11,0]   Reassigned by app, has valid data
  14 50529:35  00000000235d98de  [3,11,0]   Reassigned by app, has valid data
  15 50529:35  00000000235d691a  [3,11,0]   Reassigned by app, has valid data
  16 50529:35  00000000235d5d5c  [3,11,0]   Reassigned by app, has valid data
  17 50529:35  00000000235d519e  [3,11,0]   Reassigned by app, has valid data
  18 50529:35  00000000235d2e64  [3,11,0]   Reassigned by app, has valid data
  19 50529:35  00000000235d16e8  [3,11,0]   Reassigned by app, has valid data
  20 50529:35  00000000235cf3ad  [3,11,0]   Reassigned by app, has valid data
  21 50529:35  00000000235ce7ef  [3,11,0]   Reassigned by app, has valid data
  22 50529:35  00000000235cd073  [3,11,0]   Reassigned by app, has valid data
  23 50529:35  00000000235cb82b  [3,11,0]   Reassigned by app, has valid data
  24 50529:34  00000000235cac6d  [3,11,0]   Reassigned by app, has valid data
  25 50529:34  00000000235ca0af  [3,11,0]   Reassigned by app, has valid data
  26 50529:34  00000000235c94f1  [3,11,0]   Reassigned by app, has valid data
  27 50529:34  00000000235c8933  [3,11,0]   Reassigned by app, has valid data
  28 50529:34  00000000235c7d75  [3,11,0]   Reassigned by app, has valid data
  29 50529:34  00000000235c71b7  [3,11,0]   Reassigned by app, has valid data
  30 50529:34  000000002330b070  [3,11,0]   Reassigned by app, has valid data
  31 50529:34  000000002330a4b2  [3,11,0]   Reassigned by app, has valid data
  32 50529:34  0000000023308c6b  [3,11,0]   Reassigned by app, has valid data
  33 50529:34  00000000233080ad  [3,11,0]   Reassigned by app, has valid data
  34 50529:34  00000000233074ef  [3,11,0]   Reassigned by app, has valid data
  35 50529:34  0000000023306931  [3,11,0]   Reassigned by app, has valid data
  36 50529:34  0000000023305d73  [3,11,0]   Reassigned by app, has valid data
  37 50529:34  00000000233051b4  [3,11,0]   Reassigned by app, has valid data
  38 50529:34  00000000233016fe  [3,11,0]   Reassigned by app, has valid data
  39 50529:34  0000000023300b40  [3,11,0]   Reassigned by app, has valid data
  40 50529:34  00000000232ff3c4  [3,11,0]   Reassigned by app, has valid data
  41 50529:34  00000000232fe805  [3,11,0]   Reassigned by app, has valid data
  42 50529:34  00000000232fc400  [3,11,0]   Reassigned by app, has valid data
  43 50529:34  00000000232fb842  [3,11,0]   Reassigned by app, has valid data
  44 50529:34  00000000232fac84  [3,11,0]   Reassigned by app, has valid data
  45 50529:34  00000000232fa0c6  [3,11,0]   Reassigned by app, has valid data
  46 50529:34  00000000232f9507  [3,11,0]   Reassigned by app, has valid data
  47 50529:33  00000000232f8949  [3,11,0]   Reassigned by app, has valid data
  48 50529:33  00000000232f7d8b  [3,11,0]   Reassigned by app, has valid data
  49 50529:33  00000000232f660f  [3,11,0]   Recovered via rewrite in-place
  50 50529:30  000000002001ccbf  [3,11,0]   Reassigned by app, has valid data
  51 50529:30  000000002001c060  [3,11,0]   Reassigned by app, has valid data
  52 50529:30  000000002001b402  [3,11,0]   Reassigned by app, has valid data
  53 50529:30  000000002001a7a4  [3,11,0]   Reassigned by app, has valid data
  54 50529:30  0000000020010604  [3,11,0]   Reassigned by app, has valid data
  55 50529:29  000000002000f9a5  [3,11,0]   Reassigned by app, has valid data
  56 50529:29  000000002000ed47  [3,11,0]   Reassigned by app, has valid data
  57 50529:29  000000002000e0e9  [3,11,0]   Reassigned by app, has valid data
  58 50529:29  0000000020004ba8  [3,11,0]   Reassigned by app, has valid data
  59 50529:29  0000000020003f49  [3,11,0]   Reassigned by app, has valid data
  60 50529:29  00000000200032eb  [3,11,0]   Reassigned by app, has valid data
  61 50529:29  000000002000268c  [3,11,0]   Recovered via rewrite in-place
  62 50529:29  000000001fffb666  [3,11,0]   Recovered via rewrite in-place
  63 50529:29  000000001fff84ed  [3,11,0]   Reassigned by app, has valid data
  64 50529:29  000000001fff6c30  [3,11,0]   Recovered via rewrite in-place
  65 50529:29  000000001fff5373  [3,11,0]   Recovered via rewrite in-place
  66 50461:34  00000000235e25c7  [3,11,0]   Reassigned by app, has valid data

General statistics and performance log page:
  General access statistics and performance:
    Number of read commands: 953716376
    Number of write commands: 304771872
    number of logical blocks received: 51183082305
    number of logical blocks transmitted: 761658377039
    read command processing intervals: 0
    write command processing intervals: 0
    weighted number of read commands plus write commands: 0
    weighted read command processing plus write command processing: 0
  Idle time:
    Idle time intervals: 1842511514
      in seconds: 92125575.700
      in hours: 25590.437

Protocol Specific port log page for SAS SSP
relative target port id = 1
  generation code = 8
  number of phys = 1
  phy identifier = 0
    attached device type: SAS or SATA device
    attached reason: unknown
    reason: unknown
    negotiated logical link rate: phy enabled; 6 Gbps
    attached initiator port: ssp=1 stp=1 smp=1
    attached target port: ssp=0 stp=0 smp=0
    SAS address = 0x5000cca07356ee1d
    attached SAS address = 0x500605b005e43d54
    attached phy identifier = 7
    Invalid DWORD count = 299
    Running disparity error count = 284
    Loss of DWORD synchronization count = 75
    Phy reset problem count = 0
relative target port id = 2
  generation code = 8
  number of phys = 1
  phy identifier = 1
    attached device type: no device attached
    attached reason: unknown
    reason: power on
    negotiated logical link rate: phy enabled; unknown
    attached initiator port: ssp=0 stp=0 smp=0
    attached target port: ssp=0 stp=0 smp=0
    SAS address = 0x5000cca07356ee1e
    attached SAS address = 0x0
    attached phy identifier = 0
    Invalid DWORD count = 0
    Running disparity error count = 0
    Loss of DWORD synchronization count = 0
    Phy reset problem count = 0

 

 

 

 

 

  • Community Expert

That disk is failing the SMART test, so it should be replaced.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...