lezo

Yesterday I put some drives in my unraid server, and I left copying some data to them overnight. This morning I found that one of them was showing i/o errors in dmesg. On the dashboard in unraid it still says the drive is healthy - clicking on it and scrolling down to the 'Identity' section of the device page it shows something different to all my other healthy drives - "SMART health status:DATA" This led me to run smartctl on the device, output posted below. 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: SEAGATE Product: ST3000NM0063 Revision: G007 Compliance: SPC-4 User Capacity: 3,000,592,982,016 bytes [3.00 TB] Logical block size: 512 bytes LU is fully provisioned Rotation Rate: 7200 rpm Form Factor: 3.5 inches Logical Unit id: 0x5000c50062e608ab Serial number: Device type: disk Transport protocol: SAS (SPL-3) Local Time is: Tue Oct 12 11:18:15 2021 NZDT SMART support is: Available - device has SMART capability. SMART support is: Enabled Temperature Warning: Enabled === START OF READ SMART DATA SECTION === SMART Health Status: DATA CHANNEL IMPENDING FAILURE GENERAL HARD DRIVE FAILURE [asc=5d, ascq=30] Current Drive Temperature: 40 C Drive Trip Temperature: 60 C Manufactured in week 02 of year 2015 Specified cycle count over device lifetime: 10000 Accumulated start-stop cycles: 213 Specified load-unload count over device lifetime: 300000 Accumulated load-unload cycles: 2128 Elements in grown defect list: 684 Vendor (Seagate Cache) information Blocks sent to initiator = 55930900 Blocks received from initiator = 1462149538 Blocks read from cache and sent to initiator = 27613 Number of read and write commands whose size <= segment size = 12938 Number of read and write commands whose size > segment size = 4240 Vendor (Seagate/Hitachi) factory information number of hours powered up = 46233.90 number of minutes until next internal SMART test = 48 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: 82934029 0 0 82934029 0 28.637 0 write: 0 0 0 0 0 759.440 69 Non-medium error count: 1850 [GLTSD (Global Logging Target Save Disable) set. Enable Save with '-S on'] No Self-tests have been logged Is this possibly a bug in the way which unraid interprets the output from smartctl for the dashboard, or some sort of configuration issue on my end? Knowing that the drive knew itself that failure was imminent, I'd wish to be able to see that reflected in the dashboard.