Murac
Dabbler
- Joined
- Mar 18, 2015
- Messages
- 46
Hello friends!
EDIT: i've updated the post to include the full smart results for all drives and output from dmesg describing CAM errors from /dev/da3 and /dev/da4
I'm currently running another long test on all the drives, will update when they finish
I've a SUPERMICRO 4U 846E16-R1200B 2x Xeon L5640, with 3 vdevs containing 6 WD Red 4TB drives in RAIDZ2 in my zpool.
It might be relevant to mention that i recently upgraded to 11.1 and also decided to upgrade my pool at the same time.
So one of my drives failed a smart test last week but didn't fail additional tests afterwards. I then deleted about 4TB from my .recycle folder in the midst of troubleshooting this, and then ran a scrub. I got an alert for an error, and the same drive which failed the one smart test was being resilvered and now the zpool status says all is well but reports errors under the read and write columns.
From my reading around, the Raw_Read_Error_Rate and Multi_Zone_Error_Rate can be an indicator of a drive going bad. I've noticed this number beginning to creep up in a few of the other drives as well. Luckily most of these drives are still under warranty.
So, is my /dev/da3 drive going bad and best to just RMA for a refurbished now, or do I wait? After a full year of solid performance, could this be caused by something like a cable or controller gone bad?
Also, would it be wise to reorganize my vdevs so that the ages of the drives in the vdev are evenly distributed? I purchased and installed each of the 6 drive vdevs around the same time so they are all grouped together. I wonder if it would be worth the hassle of moving drives around and resilvering. Thoughts?
Thanks for your time in helping me in advance!
Here are some diagnostics:
My guess is the problem drive is either /dev/da3 or /dev/da4 or both, so look there first
Because the output is too long, I'm including the full outputs for /dev/da3 and linking the full output for all drives to the gist noted above
EDIT: i've updated the post to include the full smart results for all drives and output from dmesg describing CAM errors from /dev/da3 and /dev/da4
I'm currently running another long test on all the drives, will update when they finish
dmesg | grep mpr can be found here: https://gist.github.com/murac/07d1e798ea60968a6e822bf8635bb956 smartctl -x /dev/daX for all drives in order from da0 to da17 can be found here: https://gist.github.com/murac/0cccf40e4bc7a9adf11a18214ecb1246I've a SUPERMICRO 4U 846E16-R1200B 2x Xeon L5640, with 3 vdevs containing 6 WD Red 4TB drives in RAIDZ2 in my zpool.
It might be relevant to mention that i recently upgraded to 11.1 and also decided to upgrade my pool at the same time.
So one of my drives failed a smart test last week but didn't fail additional tests afterwards. I then deleted about 4TB from my .recycle folder in the midst of troubleshooting this, and then ran a scrub. I got an alert for an error, and the same drive which failed the one smart test was being resilvered and now the zpool status says all is well but reports errors under the read and write columns.
From my reading around, the Raw_Read_Error_Rate and Multi_Zone_Error_Rate can be an indicator of a drive going bad. I've noticed this number beginning to creep up in a few of the other drives as well. Luckily most of these drives are still under warranty.
So, is my /dev/da3 drive going bad and best to just RMA for a refurbished now, or do I wait? After a full year of solid performance, could this be caused by something like a cable or controller gone bad?
Also, would it be wise to reorganize my vdevs so that the ages of the drives in the vdev are evenly distributed? I purchased and installed each of the 6 drive vdevs around the same time so they are all grouped together. I wonder if it would be worth the hassle of moving drives around and resilvering. Thoughts?
Thanks for your time in helping me in advance!
Here are some diagnostics:
Code:
########## ZPool status report for unimatrix_zero ########## pool: unimatrix_zero state: ONLINE status: One or more devices has experienced an unrecoverable error. An attempt was made to correct the error. Applications are unaffected. action: Determine if the device needs to be replaced, and clear the errors using 'zpool clear' or replace the device with 'zpool replace'. see: http://illumos.org/msg/ZFS-8000-9P scan: resilvered 4.44M in 0 days 00:00:45 with 0 errors on Thu Dec 28 10:55:10 2017 config: NAME STATE READ WRITE CKSUM unimatrix_zero ONLINE 0 0 0 raidz2-0 ONLINE 0 0 0 gptid/6b1ff6e5-7d76-11e6-b037-0025903595b8 ONLINE 0 0 0 gptid/6c495fa0-7d76-11e6-b037-0025903595b8 ONLINE 0 0 0 gptid/6d6cb121-7d76-11e6-b037-0025903595b8 ONLINE 0 0 0 gptid/6e8a65aa-7d76-11e6-b037-0025903595b8 ONLINE 114 176 0 gptid/6fa9e749-7d76-11e6-b037-0025903595b8 ONLINE 0 0 0 gptid/70d0abe4-7d76-11e6-b037-0025903595b8 ONLINE 0 0 0 raidz2-1 ONLINE 0 0 0 gptid/20f3c5c1-835d-11e6-9cd1-0025903595b8 ONLINE 0 0 0 gptid/21b71d50-835d-11e6-9cd1-0025903595b8 ONLINE 0 0 0 gptid/2278ede6-835d-11e6-9cd1-0025903595b8 ONLINE 0 0 0 gptid/233cd3b3-835d-11e6-9cd1-0025903595b8 ONLINE 0 0 0 gptid/24060f46-835d-11e6-9cd1-0025903595b8 ONLINE 0 0 0 gptid/24d18aa6-835d-11e6-9cd1-0025903595b8 ONLINE 0 0 0 raidz2-2 ONLINE 0 0 0 gptid/fd72a841-3f3a-11e7-a5d2-0025903595b8 ONLINE 0 0 0 gptid/ff9faac2-3f3a-11e7-a5d2-0025903595b8 ONLINE 0 0 0 gptid/019be4ef-3f3b-11e7-a5d2-0025903595b8 ONLINE 0 0 0 gptid/039e876d-3f3b-11e7-a5d2-0025903595b8 ONLINE 0 0 0 gptid/0589dd2c-3f3b-11e7-a5d2-0025903595b8 ONLINE 0 0 0 gptid/07ae2cde-3f3b-11e7-a5d2-0025903595b8 ONLINE 0 0 0 errors: No known data errors
My guess is the problem drive is either /dev/da3 or /dev/da4 or both, so look there first
Because the output is too long, I'm including the full outputs for /dev/da3 and linking the full output for all drives to the gist noted above
Code:
########## SMART status report for da3 drive (Western Digital Red: WD-WCC4E3TEFCJX) ########## smartctl 6.5 2016-05-07 r4318 [FreeBSD 11.1-STABLE amd64] (local build) SMART overall-health self-assessment test result: PASSED ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 53 3 Spin_Up_Time 0x0027 185 180 021 Pre-fail Always - 7725 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 85 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 085 085 000 Old_age Always - 10998 10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 85 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 83 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 176 194 Temperature_Celsius 0x0022 120 105 000 Old_age Always - 32 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 4 No Errors Logged smartctl 6.5 2016-05-07 r4318 [FreeBSD 11.1-STABLE amd64] (local build) === START OF INFORMATION SECTION === Model Family: Western Digital Red Device Model: WDC WD40EFRX-68WT0N0 Serial Number: WD-WCC4E3TEFCJX LU WWN Device Id: 5 0014ee 2b7eccc0b Firmware Version: 82.00A82 User Capacity: 4,000,787,030,016 bytes [4.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 5400 rpm Device is: In smartctl database [for details use: -P show] ATA Version is: ACS-2 (minor revision not indicated) SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Thu Dec 28 23:12:25 2017 EST SMART support is: Available - device has SMART capability. SMART support is: Enabled AAM feature is: Unavailable APM feature is: Unavailable Rd look-ahead is: Enabled Write cache is: Enabled ATA Security is: Disabled, NOT FROZEN [SEC1] Wt Cache Reorder: Enabled SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. Self-test execution status: ( 244) Self-test routine in progress... 40% of test remaining. Total time to complete Offline data collection: (52380) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 2) minutes. Extended self-test routine recommended polling time: ( 524) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x703d) SCT Status supported. SCT Error Recovery Control supported. SCT Feature Control supported. SCT Data Table supported. ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 1 Raw_Read_Error_Rate POSR-K 200 200 051 - 53 3 Spin_Up_Time POS--K 185 180 021 - 7725 4 Start_Stop_Count -O--CK 100 100 000 - 85 5 Reallocated_Sector_Ct PO--CK 200 200 140 - 0 7 Seek_Error_Rate -OSR-K 200 200 000 - 0 9 Power_On_Hours -O--CK 085 085 000 - 10998 10 Spin_Retry_Count -O--CK 100 253 000 - 0 11 Calibration_Retry_Count -O--CK 100 253 000 - 0 12 Power_Cycle_Count -O--CK 100 100 000 - 85 192 Power-Off_Retract_Count -O--CK 200 200 000 - 83 193 Load_Cycle_Count -O--CK 200 200 000 - 176 194 Temperature_Celsius -O---K 120 105 000 - 32 196 Reallocated_Event_Count -O--CK 200 200 000 - 0 197 Current_Pending_Sector -O--CK 200 200 000 - 0 198 Offline_Uncorrectable ----CK 100 253 000 - 0 199 UDMA_CRC_Error_Count -O--CK 200 200 000 - 0 200 Multi_Zone_Error_Rate ---R-- 200 200 000 - 4 ||||||_ K auto-keep |||||__ C event count ||||___ R error rate |||____ S speed/performance ||_____ O updated online |______ P prefailure warning General Purpose Log Directory Version 1 SMART Log Directory Version 1 [multi-sector log support] Address Access R/W Size Description 0x00 GPL,SL R/O 1 Log Directory 0x01 SL R/O 1 Summary SMART error log 0x02 SL R/O 5 Comprehensive SMART error log 0x03 GPL R/O 6 Ext. Comprehensive SMART error log 0x06 SL R/O 1 SMART self-test log 0x07 GPL R/O 1 Extended self-test log 0x09 SL R/W 1 Selective self-test log 0x10 GPL R/O 1 SATA NCQ Queued Error log 0x11 GPL R/O 1 SATA Phy Event Counters log 0x21 GPL R/O 1 Write stream error log 0x22 GPL R/O 1 Read stream error log 0x80-0x9f GPL,SL R/W 16 Host vendor specific log 0xa0-0xa7 GPL,SL VS 16 Device vendor specific log 0xa8-0xb6 GPL,SL VS 1 Device vendor specific log 0xb7 GPL,SL VS 39 Device vendor specific log 0xbd GPL,SL VS 1 Device vendor specific log 0xc0 GPL,SL VS 1 Device vendor specific log 0xc1 GPL VS 93 Device vendor specific log 0xe0 GPL,SL R/W 1 SCT Command/Status 0xe1 GPL,SL R/W 1 SCT Data Transfer SMART Extended Comprehensive Error Log Version: 1 (6 sectors) Device Error Count: 25 (device log contains only the most recent 24 errors) CR = Command Register FEATR = Features Register COUNT = Count (was: Sector Count) Register LBA_48 = Upper bytes of LBA High/Mid/Low Registers ] ATA-8 LH = LBA High (was: Cylinder High) Register ] LBA LM = LBA Mid (was: Cylinder Low) Register ] Register LL = LBA Low (was: Sector Number) Register ] DV = Device (was: Device/Head) Register DC = Device Control Register ER = Error register ST = Status register Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 25 [0] occurred at disk power-on lifetime: 10986 hours (457 days + 18 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 00 00 00 00 09 52 cb a8 40 00 Error: UNC at LBA = 0x0952cba8 = 156421032 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 60 01 00 00 38 00 00 09 52 d5 40 40 00 14d+14:36:36.432 READ FPDMA QUEUED 60 01 00 00 30 00 00 09 52 d4 40 40 00 14d+14:36:36.432 READ FPDMA QUEUED 60 01 00 00 28 00 00 09 52 d3 40 40 00 14d+14:36:36.432 READ FPDMA QUEUED 60 01 00 00 20 00 00 09 52 d2 40 40 00 14d+14:36:36.432 READ FPDMA QUEUED 60 01 00 00 18 00 00 09 52 d1 40 40 00 14d+14:36:36.432 READ FPDMA QUEUED Error 24 [23] occurred at disk power-on lifetime: 10986 hours (457 days + 18 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 00 00 00 00 09 52 33 d8 40 00 Error: WP at LBA = 0x095233d8 = 156382168 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 61 00 40 00 28 00 00 2c 00 52 88 40 00 14d+14:36:25.310 WRITE FPDMA QUEUED 61 00 40 00 20 00 00 2c 00 52 c8 40 00 14d+14:36:25.310 WRITE FPDMA QUEUED 60 00 80 00 18 00 00 09 52 35 d8 40 00 14d+14:36:25.310 READ FPDMA QUEUED 60 01 00 00 10 00 00 09 52 34 d8 40 00 14d+14:36:25.309 READ FPDMA QUEUED 60 01 00 00 08 00 00 09 52 33 d8 40 00 14d+14:36:25.309 READ FPDMA QUEUED Error 23 [22] occurred at disk power-on lifetime: 10986 hours (457 days + 18 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 00 00 00 00 09 52 32 70 40 00 Error: WP at LBA = 0x09523270 = 156381808 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 61 00 40 00 30 00 00 2c 00 52 88 40 00 14d+14:36:21.953 WRITE FPDMA QUEUED 61 00 40 00 00 00 00 2c 00 52 c8 40 00 14d+14:36:21.953 WRITE FPDMA QUEUED 60 00 80 00 28 00 00 09 52 35 d8 40 00 14d+14:36:21.556 READ FPDMA QUEUED 60 01 00 00 20 00 00 09 52 34 d8 40 00 14d+14:36:21.556 READ FPDMA QUEUED 60 01 00 00 18 00 00 09 52 33 d8 40 00 14d+14:36:21.556 READ FPDMA QUEUED Error 22 [21] occurred at disk power-on lifetime: 10986 hours (457 days + 18 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 00 00 00 00 09 50 29 c0 40 00 Error: UNC at LBA = 0x095029c0 = 156248512 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 60 00 10 00 58 00 01 d1 c0 bc 90 40 00 14d+14:36:11.237 READ FPDMA QUEUED 60 00 10 00 50 00 01 d1 c0 ba 90 40 00 14d+14:36:11.237 READ FPDMA QUEUED 60 00 10 00 48 00 00 00 40 02 90 40 00 14d+14:36:11.237 READ FPDMA QUEUED 60 00 80 00 40 00 00 09 50 2f 18 40 00 14d+14:36:11.237 READ FPDMA QUEUED 60 01 00 00 38 00 00 09 50 2e 18 40 00 14d+14:36:11.237 READ FPDMA QUEUED Error 21 [20] occurred at disk power-on lifetime: 10986 hours (457 days + 18 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 00 00 00 00 09 50 27 f0 40 00 Error: UNC at LBA = 0x095027f0 = 156248048 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 60 00 10 00 70 00 01 d1 c0 bc 90 40 00 14d+14:36:07.317 READ FPDMA QUEUED 60 00 10 00 68 00 01 d1 c0 ba 90 40 00 14d+14:36:07.317 READ FPDMA QUEUED 60 00 10 00 60 00 00 00 40 02 90 40 00 14d+14:36:07.317 READ FPDMA QUEUED 60 00 80 00 58 00 00 09 50 2f 18 40 00 14d+14:36:07.317 READ FPDMA QUEUED 60 01 00 00 50 00 00 09 50 2e 18 40 00 14d+14:36:07.317 READ FPDMA QUEUED Error 20 [19] occurred at disk power-on lifetime: 10986 hours (457 days + 18 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 00 00 00 00 09 50 24 30 40 00 Error: UNC at LBA = 0x09502430 = 156247088 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 60 00 c8 00 40 00 00 09 50 2b 50 40 00 14d+14:36:03.575 READ FPDMA QUEUED 60 01 00 00 38 00 00 09 50 2a 50 40 00 14d+14:36:03.575 READ FPDMA QUEUED 60 01 00 00 30 00 00 09 50 29 50 40 00 14d+14:36:03.575 READ FPDMA QUEUED 60 01 00 00 28 00 00 09 50 28 50 40 00 14d+14:36:03.575 READ FPDMA QUEUED 60 01 00 00 20 00 00 09 50 27 50 40 00 14d+14:36:03.575 READ FPDMA QUEUED Error 19 [18] occurred at disk power-on lifetime: 10986 hours (457 days + 18 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 00 00 00 00 09 50 16 08 40 00 Error: UNC at LBA = 0x09501608 = 156243464 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 60 00 c0 00 08 00 00 09 50 16 d8 40 00 14d+14:35:59.821 READ FPDMA QUEUED 60 01 00 00 00 00 00 09 50 15 d8 40 00 14d+14:35:59.821 READ FPDMA QUEUED ea 00 00 00 00 00 00 00 00 00 00 40 00 14d+14:35:59.821 FLUSH CACHE EXT ea 00 00 00 00 00 00 00 00 00 00 40 00 14d+14:35:59.821 FLUSH CACHE EXT ea 00 00 00 00 00 00 00 00 00 00 40 00 14d+14:35:59.821 FLUSH CACHE EXT Error 18 [17] occurred at disk power-on lifetime: 10986 hours (457 days + 18 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 00 00 00 00 09 50 13 58 40 00 Error: WP at LBA = 0x09501358 = 156242776 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 61 00 40 00 48 00 00 2b ff f8 d0 40 00 14d+14:35:56.406 WRITE FPDMA QUEUED 61 00 40 00 40 00 00 2b ff f8 90 40 00 14d+14:35:56.406 WRITE FPDMA QUEUED 61 00 10 00 38 00 00 2b ff f8 80 40 00 14d+14:35:56.405 WRITE FPDMA QUEUED 61 00 40 00 30 00 00 2b ff f8 40 40 00 14d+14:35:56.405 WRITE FPDMA QUEUED 60 00 c0 00 28 00 00 09 50 16 d8 40 00 14d+14:35:56.405 READ FPDMA QUEUED SMART Extended Self-test Log Version: 1 (1 sectors) Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 10994 - # 2 Short offline Completed without error 00% 10930 - # 3 Extended offline Completed without error 00% 10843 - # 4 Short offline Completed without error 00% 10763 - # 5 Extended offline Completed without error 00% 10759 - # 6 Extended offline Completed without error 00% 10714 - # 7 Extended offline Completed: read failure 90% 10565 32332392 # 8 Short offline Completed without error 00% 10495 - # 9 Short offline Completed without error 00% 10279 - #10 Extended offline Completed without error 00% 10191 - #11 Short offline Completed without error 00% 10111 - #12 Short offline Completed without error 00% 9943 - #13 Extended offline Completed without error 00% 9856 - #14 Short offline Completed without error 00% 9775 - #15 Short offline Completed without error 00% 9534 - #16 Extended offline Completed without error 00% 9447 - #17 Short offline Completed without error 00% 9221 - #18 Extended offline Completed without error 00% 9134 - 1 of 1 failed self-tests are outdated by newer successful extended offline self-test # 3 SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay. SCT Status Version: 3 SCT Version (vendor specific): 258 (0x0102) SCT Support Level: 1 Device State: DST executing in background (3) Current Temperature: 32 Celsius Power Cycle Min/Max Temperature: 26/35 Celsius Lifetime Min/Max Temperature: 20/47 Celsius Under/Over Temperature Limit Count: 0/0 Vendor specific: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 SCT Temperature History Version: 2 Temperature Sampling Period: 1 minute Temperature Logging Interval: 1 minute Min/Max recommended Temperature: 0/60 Celsius Min/Max Temperature Limit: -41/85 Celsius Temperature History Size (Index): 478 (374) Index Estimated Time Temperature Celsius 375 2017-12-28 15:15 32 ************* ... ..( 20 skipped). .. ************* 396 2017-12-28 15:36 32 ************* 397 2017-12-28 15:37 30 *********** ... ..( 4 skipped). .. *********** 402 2017-12-28 15:42 30 *********** 403 2017-12-28 15:43 29 ********** ... ..(208 skipped). .. ********** 134 2017-12-28 19:12 29 ********** 135 2017-12-28 19:13 30 *********** ... ..( 3 skipped). .. *********** 139 2017-12-28 19:17 30 *********** 140 2017-12-28 19:18 31 ************ ... ..( 13 skipped). .. ************ 154 2017-12-28 19:32 31 ************ 155 2017-12-28 19:33 32 ************* ... ..(218 skipped). .. ************* 374 2017-12-28 23:12 32 ************* SCT Error Recovery Control: Read: 70 (7.0 seconds) Write: 70 (7.0 seconds) Device Statistics (GP/SMART Log 0x04) not supported SATA Phy Event Counters (GP Log 0x11) ID Size Value Description 0x0001 2 0 Command failed due to ICRC error 0x0002 2 0 R_ERR response for data FIS 0x0003 2 0 R_ERR response for device-to-host data FIS 0x0004 2 0 R_ERR response for host-to-device data FIS 0x0005 2 0 R_ERR response for non-data FIS 0x0006 2 0 R_ERR response for device-to-host non-data FIS 0x0007 2 0 R_ERR response for host-to-device non-data FIS 0x0008 2 0 Device-to-host non-data FIS retries 0x0009 2 4 Transition from drive PhyRdy to drive PhyNRdy 0x000a 2 5 Device-to-host register FISes sent due to a COMRESET 0x000b 2 0 CRC errors within host-to-device FIS 0x000f 2 0 R_ERR response for host-to-device data FIS, CRC 0x0012 2 0 R_ERR response for host-to-device non-data FIS, CRC 0x8000 4 1306459 Vendor specific
Last edited:
