November 9, 201510 yr - I have this 2TB WD drive showing lots of pending/offline - it seems likely that I should replace it? 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 169 167 021 Pre-fail Always - 6550 4 Start_Stop_Count 0x0032 092 092 000 Old_age Always - 8760 5 Reallocated_Sector_Ct 0x0033 199 199 140 Pre-fail Always - 6 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 040 040 000 Old_age Always - 44147 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 - 127 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 57 193 Load_Cycle_Count 0x0032 178 178 000 Old_age Always - 67686 194 Temperature_Celsius 0x0022 115 104 000 Old_age Always - 35 196 Reallocated_Event_Count 0x0032 196 196 000 Old_age Always - 4 197 Current_Pending_Sector 0x0032 197 196 000 Old_age Always - 1249 198 Offline_Uncorrectable 0x0030 199 197 000 Old_age Offline - 629 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 192 183 000 Old_age Offline - 2245 - I have a 4TB hot spare that is precleared and ready - is it better to: - Stop the array, reassign the new disk into the slot, and let unRAID rebuild - Assign the drive as a new drive, copy the files over the old fashioned way (cp -r or rsync), and then remove the old disk?
November 9, 201510 yr If it were me, I think I'd assign the 4TB as a new drive and use rsync with file verification to copy stuff over. That way you hopefully won't run into a surprise second drive failure while rebuilding. Downside is that you will continue to be at risk of an unanticipated second drive failure until you have the bad drive completely out of the array.
November 9, 201510 yr I'd let UnRAID do it's magic and rebuild the drive directly onto your new drive. That gets the drive out of your system IMMEDIATELY ... and at the same time provides you with a backup of the data that's on it (since you'll still have the drive) in the event some other drive fails during the rebuild. It also eliminates any possibility of making a mistake and losing data due to the user share copy issue.
November 9, 201510 yr I presume you know the process ... but just in case: (a) Disable Auto-Start of the array; (b) Stop the array and unassign the drive you want to rebuild; © Start the array so it's seen as missing; then Stop the array; (d) Assign the new drive [You can power down and physically swap the drive at this point if necessary; then boot back to UnRAID and do the assignment]; (e) Start the array and let it do the rebuild.
November 10, 201510 yr Author So it's rebuilding a 2TB onto a 4TB drive... It's past 2TB now, so I'd imagine the rest of the drive is 0's... why are all drives (even 1.5TB and 2.0TB) still spun up and being used to rebuild?
November 10, 201510 yr I've no idea why the smaller drives are still spinning; but it does continue to actually computer the value for the new drive from the other 4TB drives in the system -- even though you KNOW the result is going to be zero. [At least that's my assumption, having watched it continue to increment the # of reads on other drives in this process.] Are the smaller (1.5TB and 2TB) drives actually being accessed -- or are they just still spinning? [Refresh the display a couple times and see if the read counters increment] They may have just not yet timed out -- what's your spindown setting ??
Archived
This topic is now archived and is closed to further replies.