November 18, 20223 yr Hi, I resized 3 SAS drives to 512b using sgtools. Two have been recognized and are now part of the array; one failed to be recognized as its "read capacity failed" according to the system log. It does not show-up under unassigned devices field. I understood from others posts in the forum with a similar issue that It is probably due to smart test not starting. Therefore I did run it and attached the report below. Maybe you can help me to figure out where the issue comes from and how to solve it? Thank you in advance. root@Terre:~# smartctl -x /dev/sdk 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: X477_SMEGX04TA07 Revision: NA02 Compliance: SPC-4 LU is fully provisioned Rotation Rate: 7200 rpm Form Factor: 3.5 inches Logical Unit id: 0x5000c50084cb983b Serial number: Z1ZA8MZW Device type: disk Transport protocol: SAS (SPL-3) Local Time is: Fri Nov 18 16:15:51 2022 JST 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: 38 C Drive Trip Temperature: 40 C Manufactured in week 52 of year 2015 Specified cycle count over device lifetime: 10000 Accumulated start-stop cycles: 181 Specified load-unload count over device lifetime: 300000 Accumulated load-unload cycles: 2314 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: 4227547249 0 0 4227547249 0 891888.766 0 write: 0 0 0 0 0 441676.035 0 verify: 1471458830 0 0 1471458830 0 105526.086 1 Non-medium error count: 53 No Self-tests have been logged scsiPrintBackgroundResults Failed [medium or hardware error (serious)] Protocol Specific port log page for SAS SSP relative target port id = 1 generation code = 2 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 = 0x5000c50084cb9839 attached SAS address = 0x590b11c04ec58905 attached phy identifier = 7 Invalid DWORD count = 0 Running disparity error count = 0 Loss of DWORD synchronization = 11 Phy reset problem = 0 Phy event descriptors: Invalid word count: 0 Running disparity error count: 0 Loss of dword synchronization count: 11 Phy reset problem count: 0 relative target port id = 2 generation code = 2 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 = 0x5000c50084cb983a 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 root@Terre:~# terre-diagnostics-20221118-1607.zip
November 18, 20223 yr Author 11 minutes ago, JorgeB said: Run a long SMART test on that drive. Here you have it. Does not look promising... root@Terre:~# sudo smartctl -t long /dev/sdk 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 Long (extended) offline self test failed [medium or hardware error (serious)]
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.