May 23, 201115 yr If an error shows up on the web interface (next to reads and writes) does that mean: -you've lost some data -your drive has an issue, but unraid detected it and put the data on a diff drive -nothing at all, just FYI so you can check smart etc? I've got 80 errors (and dmesg shows the typical linuxy error messages when a drive or controller is on the way out) but want to know what that really means. I know that either way I need to check cables and replace either card or disk (if cable isn't loose).
May 24, 201115 yr Author Drive showing errors: smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: WDC WD15EARS-00Z5B1 Serial Number: WD-WMAVU2375378 Firmware Version: 80.00A80 User Capacity: 1,500,300,828,160 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Tue May 24 18:09:31 2011 EST 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: (32400) 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: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x3031) 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 - 0 3 Spin_Up_Time 0x0027 186 183 021 Pre-fail Always - 5691 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 086 086 000 Old_age Always - 10294 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 - 32 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 21 193 Load_Cycle_Count 0x0032 179 179 000 Old_age Always - 65906 194 Temperature_Celsius 0x0022 123 108 000 Old_age Always - 27 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 20 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 7 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 - 52 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 7466 - 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.
May 24, 201115 yr Drive showing errors: smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: WDC WD15EARS-00Z5B1 Serial Number: WD-WMAVU2375378 Firmware Version: 80.00A80 User Capacity: 1,500,300,828,160 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Tue May 24 18:09:31 2011 EST 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: (32400) 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: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x3031) 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 - 0 3 Spin_Up_Time 0x0027 186 183 021 Pre-fail Always - 5691 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 086 086 000 Old_age Always - 10294 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 - 32 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 21 193 Load_Cycle_Count 0x0032 179 179 000 Old_age Always - 65906 194 Temperature_Celsius 0x0022 123 108 000 Old_age Always - 27 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 20 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 7 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 - 52 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 7466 - 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. You have 20 sectors that were un-readable. They should be re-allocated when next written. 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 20 Are you running with a parity drive? Normally, if you have parity established and a read error occurs the correct data will be re-constructed from parity and the remaining data drives and re-written to the drive whose sector could not be read. This is intended to allow the SMART firmware on the disk to re-allocate the sector. If the read error occurred when no parity is in effect, the corrective action cannot occur and you may lose data.
May 24, 201115 yr Author You have 20 sectors that were un-readable. They should be re-allocated when next written. 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 20 Are you running with a parity drive? Normally, if you have parity established and a read error occurs the correct data will be re-constructed from parity and the remaining data drives and re-written to the drive whose sector could not be read. This is intended to allow the SMART firmware on the disk to re-allocate the sector. If the read error occurred when no parity is in effect, the corrective action cannot occur and you may lose data. I'm running parity, and have not noticed any issues in files (but I guess how would I know?) Is this a -"replace drive NOW" problem -"replace drive in the next month or two" problem or -"don't worry, the disk will heal itself by reallocation and you're protected by parity" problem ? Thanks
May 25, 201115 yr Is this a -"replace drive NOW" problem This is the safest course. -"replace drive in the next month or two" problem This is risky if another disk were to fail. or -"don't worry, the disk will heal itself by reallocation and you're protected by parity" problem ? The Current_Pending_Sector will be decremented upon the next write to it. The sector will be reallocated and the Reallocated_Sector_Ct will increase if the write fails again. If the write is successful it will not be reallocated. Parity is correcting the failed reads. This is not a safe condition because if another drive fails it cannot be reconstructed correctly because this drive can't be read. There are 2 options: 1. Rebuild this disk onto itself and see how the Current_Pending_Sector count resolves. 2. Rebuild onto a new pre-cleared disk and then pre-clear this disk to see how the Current_Pending_Sector count resolves.
May 25, 201115 yr Author Is this a -"replace drive NOW" problem This is the safest course. There are 2 options: 1. Rebuild this disk onto itself and see how the Current_Pending_Sector count resolves. 2. Rebuild onto a new pre-cleared disk and then pre-clear this disk to see how the Current_Pending_Sector count resolves. ~9 years ago I had an awesome raid5 system. 4x250gb disks for 750gb usable using mdadm. I used it for 1.5 years, then started getting errors. I ignored them. 1 week later 2 disks died at once and I lost ALL of my data. WD-WMAVU2375378 is going in the bin, to be replaced by a new drive.
Archived
This topic is now archived and is closed to further replies.