October 31, 201015 yr So I'm running a parity check (actually it is still running) but one of my data disks currently shows 113 errors since starting the check. I checked smart and see the following: Disk 1: WARNING - Offline_Uncorrectable it is now 3 (warning threshold is 1) Here is some of my syslog: http://pastebin.com/xz6CxucC It is still running the parity check and just want to know what I should be doing.
November 1, 201015 yr unRAID is telling you that disk1 is not readable, and has removed it from the array. You can still access the data on that disk. unRAID will derive it from parity. But at this point you're not protected from further disk failures. You need to replace that disk ASAP and rebuild it from parity. Until that's complete, you'll be unprotected.
November 1, 201015 yr Author unRAID is telling you that disk1 is not readable, and has removed it from the array. You can still access the data on that disk. unRAID will derive it from parity. But at this point you're not protected from further disk failures. You need to replace that disk ASAP and rebuild it from parity. Until that's complete, you'll be unprotected. You sure? disk1 is still showing as green in the menu and the parity check is still going and I can see incrementing reads from it.
November 1, 201015 yr unRAID is telling you that disk1 is not readable, and has removed it from the array. You can still access the data on that disk. unRAID will derive it from parity. But at this point you're not protected from further disk failures. You need to replace that disk ASAP and rebuild it from parity. Until that's complete, you'll be unprotected. I'm not quite sure it has been marked as invalid. It looks more like it had some un-correctable read errors, and reported them (they are basically sectors that are candidates for re-allocation) When that occurs, even during a parity check, unRAID will re-construct the proper contents based on the other disks in the array in combination with the parity drive and write it back to the drive with the read failure. the SMART firmware on that drive can then re-allocate the sector since it knows what the content should be. If the drive has a RED indicator, then is it marked as invalid because a WRITE to it failed. A read failure will not remove a drive from the array. It actually is self-healing as long as the drive re-allocates the sector (or re-writes it in place and is then able to read it) Joe L.
November 1, 201015 yr unRAID is telling you that disk1 is not readable, and has removed it from the array. You can still access the data on that disk. unRAID will derive it from parity. But at this point you're not protected from further disk failures. You need to replace that disk ASAP and rebuild it from parity. Until that's complete, you'll be unprotected. You sure? disk1 is still showing as green in the menu and the parity check is still going and I can see incrementing reads from it. Exactly. It is not marked as invalid, and it was just a read failure. Get a SMART report from the drive for details of what is happening. An occasional un-readable sector is not a real problem. Today's disks have a reserve pool of several thousand spare sectors. If you see the number of re-allocated sectors increasing rapidly, then it is time to RMA the drive. Your syslog shows the error reported by the drive as a "media error" (an un-correctable read error) Oct 31 17:36:08 Media02 kernel: res 51/40:9f:57:b5:f7/00:01:6d:00:00/e0 Emask 0x9 (media error) Oct 31 17:36:08 Media02 kernel: ata3.00: status: { DRDY ERR } Oct 31 17:36:08 Media02 kernel: ata3.00: error: { UNC } Oct 31 17:36:08 Media02 kernel: ata3.00: configured for UDMA/133 Oct 31 17:36:08 Media02 kernel: sd 3:0:0:0: [sdc] Unhandled sense code Oct 31 17:36:08 Media02 kernel: sd 3:0:0:0: [sdc] Result: hostbyte=0x00 driverbyte=0x08 Oct 31 17:36:08 Media02 kernel: sd 3:0:0:0: [sdc] Sense Key : 0x3 [current] [descriptor] Oct 31 17:36:08 Media02 kernel: Descriptor sense data with sense descriptors (in hex): Oct 31 17:36:08 Media02 kernel: 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 Oct 31 17:36:08 Media02 kernel: 6d f7 b5 57 Oct 31 17:36:08 Media02 kernel: sd 3:0:0:0: [sdc] ASC=0x11 ASCQ=0x4 Oct 31 17:36:08 Media02 kernel: sd 3:0:0:0: [sdc] CDB: cdb[0]=0x28: 28 00 6d f7 b4 27 00 02 e0 00 Oct 31 17:36:08 Media02 kernel: end_request: I/O error, dev sdc, sector 1844950359 Oct 31 17:36:08 Media02 kernel: ata3: EH complete Oct 31 17:36:08 Media02 kernel: md: disk1 read error Oct 31 17:36:08 Media02 kernel: handle_stripe read error: 1844950296/1, count: 1 It is /dev/sdc. You can type: smartctl -d ata -a /dev/sdc to get a full report on the health of the drive. Joe L.
November 1, 201015 yr Author I'll have to keep an eye on this drive: root@Media02:/boot# smartctl -d ata -a /dev/sdc smartctl version 5.38 [i486-slackware-linux-gnu] Copyright (C) 2002-8 Bruce Alle n Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Device Model: WDC WD15EARS-00Z5B1 Serial Number: WD-WMAVU2145711 Firmware Version: 80.00A80 User Capacity: 1,500,301,910,016 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: Sun Oct 31 20:49:44 2010 EDT 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: (0x84) Offline data collection activity was suspended by an interrupting command from host. 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: (33000) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off supp ort. 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 177 175 021 Pre-fail Always - 6150 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 786 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 9 Power_On_Hours 0x0032 094 094 000 Old_age Always - 4803 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 - 275 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 11 193 Load_Cycle_Count 0x0032 198 198 000 Old_age Always - 6493 194 Temperature_Celsius 0x0022 128 117 000 Old_age Always - 22 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 200 200 000 Old_age Offline - 3 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 - 3 SMART Error Log Version: 1
November 1, 201015 yr this counter is similar to "reallocated sector count" but it was detected by device's offline scan facility that will be triggered when device is idle. device usually detects bad sectors when it is actively doing I/O.
Archived
This topic is now archived and is closed to further replies.