June 7, 201412 yr Got a red ball on a drive. Here's the smart report...drive looks okay (although it is an old drive). Would appreciate an old hand's evaluation of the drive. Replace or put back into the array as is? === START OF INFORMATION SECTION === Model Family: Western Digital Caviar Green (AF) Device Model: WDC WD20EARS-00S8B1 Serial Number: WD-WCAVY2919978 LU WWN Device Id: 5 0014ee 2597ffb41 Firmware Version: 80.00A80 User Capacity: 2,000,398,934,016 bytes [2.00 TB] Sector Size: 512 bytes logical/physical Device is: In smartctl database [for details use: -P show] ATA Version is: ATA8-ACS (minor revision not indicated) SATA Version is: SATA 2.6, 3.0 Gb/s Local Time is: Sat Jun 7 11:14:22 2014 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: (40800) 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: ( 464) 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 150 142 021 Pre-fail Always - 9500 4 Start_Stop_Count 0x0032 096 096 000 Old_age Always - 4197 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 091 091 000 Old_age Always - 7272 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 099 099 000 Old_age Always - 1300 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 87 193 Load_Cycle_Count 0x0032 138 138 000 Old_age Always - 186453 194 Temperature_Celsius 0x0022 125 101 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 - 2 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 - 3 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.
June 7, 201412 yr Got a red ball on a drive. Here's the smart report...drive looks okay (although it is an old drive). Would appreciate an old hand's evaluation of the drive. Replace or put back into the array as is? 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 2 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 2 Neither, yet. The drive may turn out to still be ok, but without further testing who knows. Depending on the state of your backups and urgency to get the server running, it may be a good idea to put in a new drive. However, until the new drive is tested, you don't know if you are in better or worse shape than you are now. My best advice is to keep the server shut down, preclear a new drive for a couple cycles to make sure it's good, then rebuild onto the new drive. After that's done and everything looks good, preclear the old drive for at least 2 cycles and make sure the smart stats don't get worse, and the current pending goes to 0. Keep the old drive intact until the new drive is rebuilt in case you need to recover something from the old drive. If the old drive seems to handle the preclear cycles ok, it would make a good spare. If you don't care about your data, just put the drive back and follow the procedure to rebuild onto itself.
June 7, 201412 yr Author Thanks. I don't have a spare drive on hand, nor a spare bay to do pre-clears in...this particular server is the archive of my DVD/Blu-ray rips. Loss of the data wouldn't be catastrophic, just really inconvenient. I think I'll take a chance and rebuild onto itself if the drive doesn't clearly indicate that its bad. While I would normally follow your best advice, I'm actually looking to move away from unRAID as my file storage. Getting way too complex and needy for my limited time/skills. Investment in more hard drives for either of my servers is really undesirable. Have decided to go with a Synology rack mount solution - would rather put new drives in it. Again, appreciate your advice - will let you know how it goes to add to the body of knowledge.
June 8, 201412 yr Author So, when I restarted the array as part of the process outlined in the rebuild instructions, the disk showed up as unformatted, but the rebuild was happening anyway. So the rebuild finished and the disk still shows up as unformatted. I went ahead and set it to format the drive - will this cause me to lose my data anyway or will the array figure out the data is gone and try to rebuild it again?
June 8, 201412 yr Author Let me just go ahead and resolve this one - NO IT DID NOT. This is why I'm leaving unRAID. Great software, but even if you follow the instructions you'll lose your data. Not to mention lack of built-in notifications, UPS support, etc., which a lot of the community apparently feels is malware. Have fun fellas.
June 8, 201412 yr Let me just go ahead and resolve this one - NO IT DID NOT. This is why I'm leaving unRAID. Great software, but even if you follow the instructions you'll lose your data. Not to mention lack of built-in notifications, UPS support, etc., which a lot of the community apparently feels is malware. Have fun fellas. You should have waited - we would have told you NOT to do a format as that loses your data. There are lots of posts warning that a 'format' will lose the existing contents of the disk, and nothing I have seen posted or in the instructions that suggested you should do that to get back your data. FWIW: My experience is that if you get file system corruption on any NAS system you can lose the contents of the disk. Many provide no recovery path at all. The reiserfsck system used by unRAID is better than most at having enough information stored in the file system to recover most of the contents. It would have almost certainly been easy to recover from the 'unformatted' state using the reiserfsck utility as the 'unformatted' state often only indicates a failure to mount the disk due to some file system corruption. We have been asking for a new 'not mounted' status to be introduced for such cases and I believe this is being considered. If the data is important then I think that it might still be possible to recover much of the data using the reiserfsck command using the --rebuild-tree --scan-whole-disk options.
June 8, 201412 yr I concur that it is not too late to recover with reiserfsck and the rebuild tree option. Running an unRaid array is easy, but recovering is not. It takes extra knowledge and experience. We have a strong set of users here that can guide people, but people have to take advantage of it. Blindly following a "what happens if I do this" strategy is a recipe for data loss.
Archived
This topic is now archived and is closed to further replies.