publicENEMY Posted December 26, 2016 Share Posted December 26, 2016 I got yellow icon on disk 2. Here are the drive attributes. What does this means? Quote Link to comment
garycase Posted December 26, 2016 Share Posted December 26, 2016 It means two parameters that are set to flag if non-zero are both non-zero. You need to look at the actual SMART report to see the raw values to see the actual values -- neither is "bad" from SMART's perspective, as both of the values are fine (200 = essentially perfect). A few reallocated sectors is no big deal -- modern disks are designed to reallocate sectors that have issues. However, a pending sector isn't good ... but whether it's a problem or not depends on whether it subsequently gets reallocated or not. In any event, I'd do a parity check to see if you get any read errors on that disk -- if not, you're likely fine ... although I'd monitor the actual values for those parameters and see if they change. Quote Link to comment
JorgeB Posted December 26, 2016 Share Posted December 26, 2016 If doing a parity check do a non correcting one or you risk corrupting it if there are read errors. Alternatively you can do an extended SMART test on that disk, if it fails it should be replaced. Quote Link to comment
publicENEMY Posted December 27, 2016 Author Share Posted December 27, 2016 This are the smart error log. However, the last smart result are Completed without error. Should I be worried? smartctl 6.5 2016-05-07 r4318 [x86_64-linux-4.4.30-unRAID] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Western Digital Green Device Model: WDC WD30EZRX-00DC0B0 Serial Number: WD-WMC1T3153031 LU WWN Device Id: 5 0014ee 6589b20e4 Firmware Version: 80.00A80 User Capacity: 3,000,592,982,016 bytes [3.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical 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: 3.0 Gb/s) Local Time is: Tue Dec 27 17:06:14 2016 SGT SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x82) Offline data collection activity was completed without error. Auto Offline Data Collection: Enabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: (38940) 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: ( 391) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x70b5) SCT Status supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: 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 - 7726 3 Spin_Up_Time 0x0027 181 178 021 Pre-fail Always - 5950 4 Start_Stop_Count 0x0032 098 098 000 Old_age Always - 2243 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 1 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 061 061 000 Old_age Always - 28945 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 145 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 45 193 Load_Cycle_Count 0x0032 032 032 000 Old_age Always - 506970 194 Temperature_Celsius 0x0022 108 089 000 Old_age Always - 42 196 Reallocated_Event_Count 0x0032 199 199 000 Old_age Always - 1 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 6 198 Offline_Uncorrectable 0x0030 200 200 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 194 000 Old_age Offline - 0 SMART Error Log Version: 1 ATA Error Count: 58 (device log contains only the most recent five errors) CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] 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 58 occurred at disk power-on lifetime: 14215 hours (592 days + 7 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 08 d0 f9 c2 e6 Error: UNC 8 sectors at LBA = 0x06c2f9d0 = 113441232 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 08 d0 f9 c2 e6 08 3d+23:34:29.854 READ DMA c8 00 08 28 7c c2 e6 08 3d+23:34:29.852 READ DMA c8 00 08 e0 fd c1 e6 08 3d+23:34:29.844 READ DMA c8 00 08 10 a0 c1 e6 08 3d+23:34:29.841 READ DMA c8 00 08 50 02 c1 e6 08 3d+23:34:29.829 READ DMA Error 57 occurred at disk power-on lifetime: 14215 hours (592 days + 7 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 08 70 d0 9d e6 Error: UNC 8 sectors at LBA = 0x069dd070 = 111005808 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 08 70 d0 9d e6 08 3d+23:34:25.177 READ DMA ca 00 08 58 52 9d e6 08 3d+23:34:24.500 WRITE DMA ef 10 02 00 00 00 a0 08 3d+23:34:23.762 SET FEATURES [Enable SATA feature] Error 56 occurred at disk power-on lifetime: 14215 hours (592 days + 7 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 08 58 52 9d e6 Error: UNC 8 sectors at LBA = 0x069d5258 = 110973528 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 08 58 52 9d e6 08 3d+23:34:21.069 READ DMA ca 00 08 e8 b4 9c e6 08 3d+23:34:20.941 WRITE DMA ef 10 02 00 00 00 a0 08 3d+23:34:20.905 SET FEATURES [Enable SATA feature] ec 00 00 00 00 00 a0 08 3d+23:34:20.905 IDENTIFY DEVICE Error 55 occurred at disk power-on lifetime: 14215 hours (592 days + 7 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 08 e8 b4 9c e6 Error: UNC 8 sectors at LBA = 0x069cb4e8 = 110933224 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 08 e8 b4 9c e6 08 3d+23:34:18.195 READ DMA ca 00 08 68 56 9c e6 08 3d+23:34:17.485 WRITE DMA ef 10 02 00 00 00 a0 08 3d+23:34:16.779 SET FEATURES [Enable SATA feature] Error 54 occurred at disk power-on lifetime: 14215 hours (592 days + 7 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 08 68 56 9c e6 Error: UNC 8 sectors at LBA = 0x069c5668 = 110909032 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 08 68 56 9c e6 08 3d+23:34:14.076 READ DMA ca 00 08 88 93 9b e6 08 3d+23:34:13.940 WRITE DMA ef 10 02 00 00 00 a0 08 3d+23:34:13.914 SET FEATURES [Enable SATA feature] ec 00 00 00 00 00 a0 08 3d+23:34:13.914 IDENTIFY DEVICE SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed without error 00% 28943 - 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. Quote Link to comment
JorgeB Posted December 27, 2016 Share Posted December 27, 2016 Disk is fine at the moment and the last issues were some time ago: Error 58 occurred at disk power-on lifetime: 14215 hours Disk has now 28945 power on hours, but keep an eye on it, in my experience a disk with previous issues it's much more likely to give more problems in the future. Quote Link to comment
garycase Posted December 27, 2016 Share Posted December 27, 2016 A single reallocated sector is nothing to be concerned about. However, 6 "pending sectors" isn't good. That means there are 6 sectors that the SMART system has identified as problematic and should be reallocated. Unfortunately there's no simply way to force that reallocation -- it will do it the next time the sector is written to ... but that's not easy to force. What I'd do is (a) replace the disk and let UnRAID rebuild it; (b) AFTER you've done a successful rebuild with a new disk, then either attach the drive to another system and use a good disk diagnostic (e.g. WD's Data Lifeguard or HDTune) to write zeroes to the entire disk -- then look at the SMART status and see if the pending sectors are gone [They may have written okay; or they may have simply been reallocated -- either is fine]. Then you can use the disk again if you want; or just relegate it to backups, etc. Quote Link to comment
JorgeB Posted December 27, 2016 Share Posted December 27, 2016 Those pending sectors are false positives or the extended SMART test would have failed, in my experience they are fairly common on WD disks. Quote Link to comment
garycase Posted December 27, 2016 Share Posted December 27, 2016 Those pending sectors are false positives or the extended SMART test would have failed, in my experience they are fairly common on WD disks. Interesting. What I used to do to get rid of them was run a full Level 2 pass with Spinrite, which will read and re-write every sector ... thus forcing any pending sector to be reallocated unless it successfully rewrites. This often results in an increase in the reallocated sector count, which I assume means the pending sector was successfully reallocated. But this doesn't work with modern drives, as Steve Gibson has never released the long-promised v6.1 of Spinrite to handle drives > 2TB [if anyone thinks LimeTech has been slow with their release cycles, trust me -- they're greased lightning compared to the Spinrite release cycle over the years !!]. What I do instead these days is destructive -- I write zeroes to the entire disk, which will generally clear the pending sectors one way or another (reallocate them, or just clear them). The problem, of course, is that this is destructive, so it takes a bit more work, since, for example, if it's an UnRAID disk you have to first replace it. On a desktop machine, you can simply copy all the data to another disk first. But if they're just false positives, is there a utility that will clear them?? [Perhaps by forcing a read/write of the flagged sectors -- which should force SMART to reset the "pending" flag for the sector.] Quote Link to comment
JorgeB Posted December 27, 2016 Share Posted December 27, 2016 When they are like there's no way to clear them, I believe in these situations the sectors are reallocated but the firmware doesn't correctly update the SMART info. Quote Link to comment
gubbgnutten Posted December 27, 2016 Share Posted December 27, 2016 But this doesn't work with modern drives, as Steve Gibson has never released the long-promised v6.1 of Spinrite to handle drives > 2TB [if anyone thinks LimeTech has been slow with their release cycles, trust me -- they're greased lightning compared to the Spinrite release cycle over the years !!]. I'm sure there is a perfectly reasonable explanation for the slow release cycles. But I truly love programming. It's what I do. It fulfills me and sustains me . . . and I'm never in a hurry to "just be done with it." I can't stand sloppiness in my work, so for me that means writing the smallest, tightest, fastest, most economical computer programs possible. And THAT means authoring Windows applications in Assembly Language. Quote Link to comment
garycase Posted December 27, 2016 Share Posted December 27, 2016 But this doesn't work with modern drives, as Steve Gibson has never released the long-promised v6.1 of Spinrite to handle drives > 2TB [if anyone thinks LimeTech has been slow with their release cycles, trust me -- they're greased lightning compared to the Spinrite release cycle over the years !!]. I'm sure there is a perfectly reasonable explanation for the slow release cycles. But I truly love programming. It's what I do. It fulfills me and sustains me . . . and I'm never in a hurry to "just be done with it." I can't stand sloppiness in my work, so for me that means writing the smallest, tightest, fastest, most economical computer programs possible. And THAT means authoring Windows applications in Assembly Language. I had a chance to spend some time with Steve over 2 decades ago, and it was a very interesting couple hours. I've used Spinrite for well over 2 decades, and it's been a great tool. However, it's now been over a decade since the last release; and while it still works very nicely for drives up to 2TB (they have to be MBR drives -- it doesn't support GPT), there was also a long-promised v6.1 that was planned to add GPT support ... and it's now been over 10 years since that was announced. Somehow I think Steve has become distracted by his many other projects Quote Link to comment
Recommended Posts
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.