January 18, 201313 yr Hi all have had a great running system for almost a year. Overnight got email notifications that a drive was down. Went to tower and saw that disc eleven was red balled Shut down array, powered down, replaced with my pre cleared ready drive and restarted. New drive is now being rebuilt Silly question but what should I do with the old drive? Assume its totally dead? Or put in my pc and run some tests? Guess I'm wondering if unraid ever glitches out and mistakenly reports a working drive as dead Thoughts?
January 18, 201313 yr Wait till rebuilt has finished. Then parity check. If everything is ok, do several preclear runs on the old disk and check smart reports. A red ball happens even when 1 write failed. Is the disk still under warranty? You might try to RMA it.
January 18, 201313 yr A red ball happens even when 1 write failed. Is the disk still under warranty? You might try to RMA it. The "write" failure could be caused by almost anything, from a loose power cable, or loose data cable, or loose drive tray, or drive backplane, or bad memory, or a defective power supply, or a power supply unable to keep up with the demands of the disks connected to it, or a bad disk controller, or a defective data cable, or a defective power cable, or a defective power splitter, or a bad disk itself. All you need to do is a process of elimination (starting with a smart report from the disk itself) Joe L.
January 18, 201313 yr Author Ok so I'm currently writing data to the new replaced drive. Once completed it sounds like I should parity of array. After that I want to get a new drive pre cleared in case of emergency So for the removed drive can anyone advise how to get a smart report? It's now out of my system. I can put it back in but then what do I do?
January 20, 201313 yr Author Hi everyone, i put the 'bad' drive back in my system, and ran the following SMART info from UNMENU. Think there's anything really bad below? or should i preclear and try using again? SMART status Info for /dev/sdv smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright © 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Model Family: Western Digital Caviar Green (Adv. Format) family Device Model: WDC WD20EARS-00MVWB0 Serial Number: WD-WMAZA0669236 Firmware Version: 51.0AB51 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: Exact ATA specification draft version not indicated Local Time is: Sun Jan 20 12:28:38 2013 CST 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: ( 121) The previous self-test completed having the read element of the test failed. Total time to complete Offline data collection: (37980) 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: (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 199 199 051 Pre-fail Always - 762 3 Spin_Up_Time 0x0027 170 162 021 Pre-fail Always - 6458 4 Start_Stop_Count 0x0032 097 097 000 Old_age Always - 3076 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 083 083 000 Old_age Always - 12999 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 - 717 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 193 193 Load_Cycle_Count 0x0032 182 182 000 Old_age Always - 56442 194 Temperature_Celsius 0x0022 123 114 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 - 5 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 2 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 - 22 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: read failure 90% 12999 2334316832 # 2 Short offline Completed: read failure 90% 12996 2334316832 # 3 Short offline Completed: read failure 90% 12996 2334316832 # 4 Short offline Completed: read failure 90% 12996 2334316832 # 5 Short offline Completed: read failure 90% 12996 2334316832 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.
January 21, 201313 yr Pre-clear again. The Current_Pending_Sector RAW_VALUE should go to zero. If the Current_Pending_Sector RAW_VALUE is not zero after a pre-clear then RMA the drive.
January 22, 201313 yr Author so the preclear finished, and 4 of the 5 pending sector were reallocated, but one was not i could run preclear again and see, or just rma? hmmm never really had a drive gone bad before so i'm a little undecided whats the best thing to do!
January 22, 201313 yr so the preclear finished, and 4 of the 5 pending sector were reallocated, but one was not i could run preclear again and see, or just rma? hmmm never really had a drive gone bad before so i'm a little undecided whats the best thing to do! you can try again, but I'd just RMA. All 5 sectors were probably re-allocated, however one additional un-readable sector was identified on the post-read phase.
January 22, 201313 yr Author thanks joe, think you're right, i could maybe screw with it for awhile or just rma started the rma process. never done this before but seems pretty easy actually. only bummer is that i have to pay return shipping, but i guess that's a pretty small price for a (hopefully) new drive!
September 11, 201312 yr thanks joe, think you're right, i could maybe screw with it for awhile or just rma started the rma process. never done this before but seems pretty easy actually. only bummer is that i have to pay return shipping, but i guess that's a pretty small price for a (hopefully) new drive! and you may get lucky and get a 3TB as replacement, i know i did once from WD when i sent in a 2TB.
Archived
This topic is now archived and is closed to further replies.