February 2, 201412 yr One of my old suspect drives gave a red dot. It had changed from sdi to sdj since last reboot (not sure exactly when), and now shows the red dot. There's another drive on the same SATA card, so the card shouldn't be an issue. I checked the cabling, and it's ok. The drive had quite a few reallocated sectors after preclear, so it's no surprise it's failing. I have two larger precleared drives which I just assigned to the array earlier today. How do I re-assign one of them to the red dot drive's slot? I'd be ok re-formatting, as both of them are empty.
February 2, 201412 yr The array membership cannot be changed if one of the drives is disabled. Paste a SMART report for the drive. The contents of the disabled drive can be copied to one on the new drives and then the array config can be reset. A new config that doesn't include the disabled drive can then be built. See here: http://lime-technology.com/wiki/index.php/Troubleshooting#What_do_I_do_if_I_get_a_red_ball_next_to_a_hard_disk.3F
February 3, 201412 yr Author I've seen the link you gave, but that only gives instructions on how to replace the drive with a new drive. I don't have a new one, but I have two empty drives in the array. Do I really have to go buy a new drive to get my array up and running with parity protection? Is shrinking the array a viable option? Here's what I understand by copying the old drive to new: 1. Start array 2. Copy Disk4 to empty Disk9 using mc or similar 3. Stop array 4. Reassign drives somehow? Ensure Parity, Disk1-3 and 5-8 are in the same slots as earlier, what about 4 and 9? 5. Start array? Below SMART report for the drive in question. smartctl 6.2 2013-07-26 r3841 [i686-linux-3.9.11p-unRAID] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: SAMSUNG SpinPoint F1 DT Device Model: SAMSUNG HD103UJ Serial Number: S13PJ1KQ607541 LU WWN Device Id: 5 0000f0 00b065714 Firmware Version: 1AA01112 User Capacity: 1,000,204,886,016 bytes [1.00 TB] Sector Size: 512 bytes logical/physical Device is: In smartctl database [for details use: -P show] ATA Version is: ATA/ATAPI-7, ATA8-ACS T13/1699-D revision 3b Local Time is: Mon Feb 3 01:36:01 2014 CET 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 See vendor-specific Attribute list for marginal Attributes. General SMART Values: Offline data collection status: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. 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: (11920) 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: ( 200) minutes. Conveyance self-test routine recommended polling time: ( 21) minutes. SCT capabilities: (0x003f) SCT Status supported. SCT Error Recovery Control 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 0x000f 100 006 051 Pre-fail Always In_the_past 6 3 Spin_Up_Time 0x0007 076 076 011 Pre-fail Always - 7890 4 Start_Stop_Count 0x0032 094 094 000 Old_age Always - 6067 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 100 100 051 Pre-fail Always - 0 8 Seek_Time_Performance 0x0025 100 100 015 Pre-fail Offline - 0 9 Power_On_Hours 0x0032 096 096 000 Old_age Always - 20530 10 Spin_Retry_Count 0x0033 100 100 051 Pre-fail Always - 0 11 Calibration_Retry_Count 0x0012 100 100 000 Old_age Always - 1 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 371 13 Read_Soft_Error_Rate 0x000e 100 006 000 Old_age Always - 6 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 184 End-to-End_Error 0x0033 100 100 099 Pre-fail Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 16289 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 070 052 000 Old_age Always - 30 (Min/Max 27/30) 194 Temperature_Celsius 0x0022 068 050 000 Old_age Always - 32 (Min/Max 27/32) 195 Hardware_ECC_Recovered 0x001a 100 100 000 Old_age Always - 76 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 100 100 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x000a 100 100 000 Old_age Always - 0 201 Soft_Read_Error_Rate 0x000a 253 253 000 Old_age Always - 0 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 0 Warning: ATA Specification requires 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 Note: revision number not 1 implies that no selective self-test has ever been run 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 3, 201412 yr Author Decided to go the "proper" way. Picked up a new drive, stopped the array, took out the failing drive, replaced with new in the same slot, and am now doing two pre-clear cycles on it. I believe I should be able to use the array in unprotected form, but I'll probably keep it mostly in un-started state.
February 4, 201412 yr You could have used the array in a degraded state to copy and files you wanted off the disk. Then, you would do an array initialization before assigning the remaining drives how you wanted them and then starting the array and building parity.
February 4, 201412 yr Author You could have used the array in a degraded state to copy and files you wanted off the disk. Then, you would do an array initialization before assigning the remaining drives how you wanted them and then starting the array and building parity. By remaining drives do you mean the two empty drives? They were already added to the array. I'm not entirely surely how parity calculations work with empty drives, but I assume that even an empty drive becomes part of parity, and thus can't be pulled without impacting it. And I believe his is the reason why dgaschk recommended a new drive instead. Or do you mean shrinking the array method? I decided to skipt hat due to loss of parity protection.
February 4, 201412 yr Cleared drives have no impact on parity. That's the whole purpose of clearing them. But formatted drives actually have data on them even if "empty". The file system has been created and that file system contains data, just no actual files.
February 4, 201412 yr Author Cleared drives have no impact on parity. That's the whole purpose of clearing them. But formatted drives actually have data on them even if "empty". The file system has been created and that file system contains data, just no actual files. Ok, that's what I thought. The two drives were already formatted and added to the array by the time I noticed the red dot on another drive, so it was too late, then.
February 4, 201412 yr You could have used the array in a degraded state to copy and files you wanted off the disk. Then, you would do an array initialization before assigning the remaining drives how you wanted them and then starting the array and building parity. By remaining drives do you mean the two empty drives? They were already added to the array. I'm not entirely surely how parity calculations work with empty drives, but I assume that even an empty drive becomes part of parity, and thus can't be pulled without impacting it. And I believe his is the reason why dgaschk recommended a new drive instead. Or do you mean shrinking the array method? I decided to skipt hat due to loss of parity protection. I mean all the other drives in the array. Once you run the new config you assign the drives like you were setting up a new array except any drive with data keeps the data. You wouldn't assign the failing disk because you want it removed. Since you setup a new array you have to build parity again.
February 6, 201412 yr Author All is good. Replaced the drive with a new one, ran two rounds of pre-clearing on it, rebuild which took around 20 hours (1TB), and everything is back to green. Thanks for the help everyone, once again!
Archived
This topic is now archived and is closed to further replies.