June 8, 20224 yr smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.10.28-Unraid] (local build) Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Vendor: NETAPP Product: X320_SMEGX04TA07 Revision: NA00 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: 0x5000c500864e19b3 Serial number: Z1ZBSBP2 Device type: disk Transport protocol: SAS (SPL-3) Local Time is: Wed Jun 8 08:40:44 2022 EDT 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: DATA CHANNEL IMPENDING FAILURE DATA ERROR RATE TOO HIGH [asc=5d, ascq=32] Current Drive Temperature: 38 C Drive Trip Temperature: 40 C Manufactured in week 46 of year 2016 Specified cycle count over device lifetime: 10000 Accumulated start-stop cycles: 190 Specified load-unload count over device lifetime: 300000 Accumulated load-unload cycles: 788 Elements in grown defect list: 2 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: 2687287801 320 0 2687288121 324 420177.275 3 write: 0 0 0 0 0 14940.312 0 verify: 1744269895 0 0 1744269895 0 4803.854 1 Non-medium error count: 25 SMART Self-test log Num Test Status segment LifeTime LBA_first_err [SK ASC ASQ] Description number (hours) # 1 Background short Completed - 14770 - [- - -] Long (extended) Self-test duration: 32700 seconds [545.0 minutes] Background scan results log Status: waiting until BMS interval timer expires Accumulated power on time, hours:minutes 14793:04 [887584 minutes] Number of background scans performed: 200, scan progress: 0.00% Number of background medium scans performed: 200 # when lba(hex) [sk,asc,ascq] reassign_status 1 14744:45 000000014710d31a [1,17,1] Recovered via rewrite in-place 2 14744:45 000000014710dc60 [1,17,1] Recovered via rewrite in-place 3 14744:46 000000014710e6a1 [3,11,0] Recovered via rewrite in-place 4 14744:46 000000014710eec4 [1,17,1] Recovered via rewrite in-place 5 14744:46 000000014710f878 [3,11,0] Successfully reassigned 6 14744:46 000000014710f8fb [1,17,1] Recovered via rewrite in-place 7 14744:48 000000014713dec3 [1,17,1] Recovered via rewrite in-place 34560 14740:26 0000000147141f95 [0,0,0] Reserved [0x0] 34561 14740:26 0000000147141fc7 [0,0,0] Reserved [0x0] Protocol Specific port log page for SAS SSP relative target port id = 1 generation code = 1 number of phys = 1 phy identifier = 0 attached device type: SAS or SATA device attached reason: power on 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 = 0x5000c500864e19b1 attached SAS address = 0x500148500073a530 attached phy identifier = 0 Invalid DWORD count = 7028158 Running disparity error count = 6654797 Loss of DWORD synchronization = 793 Phy reset problem = 0 Phy event descriptors: Invalid word count: 7028158 Running disparity error count: 6654797 Loss of dword synchronization count: 793 Phy reset problem count: 0 relative target port id = 2 generation code = 1 number of phys = 1 phy identifier = 1 attached device type: no device attached attached reason: unknown reason: unknown 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 = 0x5000c500864e19b2 attached SAS address = 0x0 attached phy identifier = 0 Invalid DWORD count = 0 Running disparity error count = 0 Loss of DWORD synchronization = 0 Phy reset problem = 0 Phy event descriptors: Invalid word count: 0 Running disparity error count: 0 Loss of dword synchronization count: 0 Phy reset problem count: 0
June 8, 20224 yr I don't know much about SAS drives. But the report does not look good : === START OF READ SMART DATA SECTION === SMART Health Status: DATA CHANNEL IMPENDING FAILURE DATA ERROR RATE TOO HIGH [asc=5d, ascq=32]
June 8, 20224 yr 35 minutes ago, ChatNoir said: But the report does not look good : It doesn't, this is also not a good sign: 53 minutes ago, DannyG said: Elements in grown defect list: 2 And the total uncorrected errors as well.
June 8, 20224 yr Author Now that i think of it, Should I ever bother replacing it? or should I wait until it dies? if I replace it now or later, it needs to rebuild from my parity drive.
June 9, 20224 yr 5 hours ago, DannyG said: Now that i think of it, Should I ever bother replacing it? or should I wait until it dies? if I replace it now or later, it needs to rebuild from my parity drive. Do you have backups of everything you care about on the server? What happens if a drive you think is fine suddenly dies without warning? Would you trust this drive to participate in that rebuild? Keep in mind it's not just the parity drive needed for a rebuild, it's the remaining data drives as well.
June 9, 20224 yr Author 17 hours ago, JonathanM said: Do you have backups of everything you care about on the server? What happens if a drive you think is fine suddenly dies without warning? Would you trust this drive to participate in that rebuild? Keep in mind it's not just the parity drive needed for a rebuild, it's the remaining data drives as well. ya, that makes sense. I have other drives in there that should be dead but aren't.
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.