March 29, 201115 yr Hi, I'm trying not to panic, especially since this is the 2nd time I've tried to post this message. I'm running unRaid Pro 4.5.4 for almost a year now with no problems. Earlier today there was a power failure while I was at work that must have lasted awhile because it drained the backups battery and shut everything down and unfortunately there was no powerdown script. When power came back on, I turned everything back on and was seemingly normal and a parity check started. Last I checked at around 9pm it was at 50% and no errors all drives blinking green. Well I just check a bit ago and all drives are blinking green except 12 which is blinking red with 576 errors next to it. I checked unMenu and it reported "STARTED, 19 disks in array. Parity is Valid:. Last parity check < 1 day ago with no sync errors." so I'm assuming something must have happened in the last 1-2 hours? like drive 12 randomly died? I downloaded the syslog from unmenu. It's late, it's been awhile since I've been on the forum, my mind is blank and I'm trying not to panic. I have 20, 2TB drives in the tower, 18 part active, 1 parity, 1 plugged in but not part of the array. My question: What to do next? Please and thank you!! syslog-2011-03-29.zip
March 29, 201115 yr Hi, I'm trying not to panic, especially since this is the 2nd time I've tried to post this message. I'm running unRaid Pro 4.5.4 for almost a year now with no problems. Earlier today there was a power failure while I was at work that must have lasted awhile because it drained the backups battery and shut everything down and unfortunately there was no powerdown script. When power came back on, I turned everything back on and was seemingly normal and a parity check started. Last I checked at around 9pm it was at 50% and no errors all drives blinking green. Well I just check a bit ago and all drives are blinking green except 12 which is blinking red with 576 errors next to it. I checked unMenu and it reported "STARTED, 19 disks in array. Parity is Valid:. Last parity check < 1 day ago with no sync errors." so I'm assuming something must have happened in the last 1-2 hours? like drive 12 randomly died? I downloaded the syslog from unmenu. It's late, it's been awhile since I've been on the forum, my mind is blank and I'm trying not to panic. I have 20, 2TB drives in the tower, 18 part active, 1 parity, 1 plugged in but not part of the array. My question: What to do next? Please and thank you!! Basically, do not panic. There are only two types of hard disks in the world. No, not IDE and SATA. The two types are: Those disks that have crashed/failed. Those disks that have not yes crashed/failed. (just give them time... they will) It looks like disk12 (/dev/sde) has stopped responding. You can try to see if you can get a smart report from it. If not, you can stop the array, power down, re-seat the cables to it, power up and see if a smart report can be obtained. If not, you can try swapping the cable to it, or switching it with another disk to see if it is the disk controller port. In any case, if the drive has failed, just stop the array, put a new replacement drive into place (or use the "devices" page to assign a different spare drive to the slot in the array) and then press "Start" The contents of the drive will be re-constructed onto the replacement. When done you'll be parity protected once more. Joe L.
March 29, 201115 yr Author Thanks for your response! I took your advice, stopped array, powered down, changed the Y splitter power cable and reseated the sata cable (note: the Sata cable is one of the ones that splits into 4 from the SAS-LP-MV8 card, so I'm assuming the cable isn't the issue or all 4 drives would have a problem? and the sata power was from a Y splitter off a main plug on the power supply, so this may not have been the issue either since other drive power is fine?) Everything booted fine and all drives solid green except 12 which is solid red. From unMenu, I ran a short smart test of drive 12 and the the smart report is below: I'm not 100% sure how to interpret it. It says a test is in progress with 10% left, and has said that even after multiple refreshes over 15 minutes? So, my new question... Was this all just a fluke or a bad power cable and now all is well and just bring that drive back online? Or is this a bad drive and let the parity rebuild on the warm spare and just RMA this drive? Thanks so much! Statistics for /dev/sde SAMSUNG_HD203WI_S1UYJ1KZ403015 smartctl -a -d ata /dev/sde smartctl version 5.38 [i486-slackware-linux-gnu] Copyright © 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Device Model: SAMSUNG HD203WI Serial Number: S1UYJ1KZ403015 Firmware Version: 1AN10002 User Capacity: 2,000,398,934,016 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 8 ATA Standard is: Not recognized. Minor revision code: 0x28 Local Time is: Tue Mar 29 17:02:54 2011 GMT+5 ==> WARNING: May need -F samsung or -F samsung2 enabled; see manual for details. 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: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. Self-test execution status: ( 241) Self-test routine in progress... 10% of test remaining. Total time to complete Offline data collection: (26340) seconds. Offline data collection capabilities: (0x5b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. No 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. SCT capabilities: (0x003f) 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 100 100 051 Pre-fail Always - 292 2 Throughput_Performance 0x0026 252 252 000 Old_age Always - 0 3 Spin_Up_Time 0x0023 060 060 025 Pre-fail Always - 12264 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 372 5 Reallocated_Sector_Ct 0x0033 252 252 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 252 252 051 Old_age Always - 0 8 Seek_Time_Performance 0x0024 252 252 015 Old_age Offline - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 612 10 Spin_Retry_Count 0x0032 252 252 051 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 252 252 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 10 191 G-Sense_Error_Rate 0x0022 100 100 000 Old_age Always - 420 192 Power-Off_Retract_Count 0x0022 252 252 000 Old_age Always - 0 194 Temperature_Celsius 0x0002 064 064 000 Old_age Always - 27 (Lifetime Min/Max 18/31) 195 Hardware_ECC_Recovered 0x003a 100 100 000 Old_age Always - 0 196 Reallocated_Event_Count 0x0032 252 252 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 100 100 000 Old_age Always - 1 198 Offline_Uncorrectable 0x0030 252 252 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0036 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x002a 100 100 000 Old_age Always - 33 223 Load_Retry_Count 0x0032 252 252 000 Old_age Always - 0 225 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 2595 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 (0) should be 1 SMART Selective self-test log data structure revision number 0 Warning: ATA Specification requires selective self-test log data structure revision number = 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Self_test_in_progress [10% left] (0-65535) 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.
March 29, 201115 yr I notice you have a pending sector for reallocation. Keep an eye on that. It should either disappear or become reallocated (reallocated event probably) and no new ones should pop-up It will not fix itself. You probably need to stop, unassign the drive, start, stop, assign the drive and start again. The drive will be rebuilt onto itself and if the drive is OK then the array will come back with everything happy again. The rebuild should fail if the drive is bad and just never complete. Peter
March 29, 201115 yr Author Thanks. On closer inspection, I heard a faint whinning/clicking noise from that drive number 12, one that sounds like impending doom. So I guess that solves the problem? I unplugged the sata cable from that and placed it into the warm spare and started data rebuild onto it. With that drive out, there is no more noise, and I'll just RMA it. Maybe the power outage helped it along to its grave? Seems like the drive should have lasted longer than 10 months... oh well. I guess it's time to start looking through the forums for a rec for a new 2TB drive. Thanks for all the help!
Archived
This topic is now archived and is closed to further replies.