February 13, 201115 yr I completed my upgrade to 4.7 on 2/8/11. As part of the upgrade I replaced my old WD black 1Tb parity drive with a new 2.0TB WD Ears drive. I ran preclear.sh with the -A switch before installing and rebuilding. The new drive rebuilt parity and a successful parity check was completed after the data rebuild. Today at 11:09am in the syslog that is attached you will see the start of the errors. Can someone view my syslog and let me know what they think is wrong and how I should proceed? Thanks, Dan syslog-2011-02-12.zip
February 13, 201115 yr /dev/sdi has stopped responding, writes to it are failing and it is probably now showing as "disabled" on the web-management interface. Most likely cause on a new array is a cable that has come loose. Next most likely is a cable or drive that has failed. Can you get a SMART report on the failed disk? smartctl -d ata -a /dev/sdi Joe L.
February 13, 201115 yr Author Joe, I will check/replace the cable. Here is the results from the SMART report: root@Tower:~# smartctl -d ata -a /dev/sdi smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright © 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net Smartctl: Device Read Identity Failed (not an ATA/ATAPI device) A mandatory SMART command failed: exiting. To continue, add one or more '-T perm issive' options.
February 13, 201115 yr Joe, I will check/replace the cable. Here is the results from the SMART report: root@Tower:~# smartctl -d ata -a /dev/sdi smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright © 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net Smartctl: Device Read Identity Failed (not an ATA/ATAPI device) A mandatory SMART command failed: exiting. To continue, add one or more '-T perm issive' options. Basically, the drive did not respond. (for whatever reason... as I said, could be the cable, the drive, the disk controller.) EARS drives sometimes lock up and stop responding until power cycled. You might try powering down, then powering up again and see if it comes back to life. Joe L.
February 13, 201115 yr Author Joe, I rebooted the unraid server - the parity drive shows as a blue dot and says new parity disk installed??? I then ran the smart disk command see below. Do you have any suggestions on how to move forward? Thanks, Dan smartctl -d ata -a /dev/sdi smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright © 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: WDC WD20EARS-00MVWB0 Serial Number: WD-WMAZA3388631 Firmware Version: 51.0AB51 User Capacity: 2,000,398,934,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 Feb 13 08:31:59 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: (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: (36480) 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: (0x3035) 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 220 162 021 Pre-fail Always - 4000 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 59 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 100 100 000 Old_age Always - 253 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 - 14 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 11 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 481 194 Temperature_Celsius 0x0022 129 120 000 Old_age Always - 21 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 - 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 - 0 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] 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.
February 13, 201115 yr It is an EARS drive. They are known to lock up and stop responding. In my opinion, buggy firmware on the drive. They frequently will start responding again after a power cycle. I'd stop the array, power down, re-seat all the connectors and cables to that drive then re-start the array and let it re-build parity. nothing else you can do. For the parity drive to be "red" it indicates a "write" to it failed. It needs to be re-calculated, and since it is now showing as "new" that will occur when you next start the array. Joe L.
February 14, 201115 yr Author Joe, I replaced the cable (just to be sure) restarted the array and let it rebuild parity. Everything went fine... no errors. Can I expect this to keep happening since you mention buggy firmware? Thanks for your help! Dan
Archived
This topic is now archived and is closed to further replies.