To burn or not to burn?

[xaser]

Hi guys,

Running a 4x3tb vdev pool.. about to order a 3tb wd red drive, which together with 3 other 3tb wd red drives that I have from an old Synology box will allow me to create a new vdev and extend my pool.

The 3 old drives weren't used for about 4 years... last time I used them they were completely fine. The question is, should I do a typical burn in on them? They were used for 3-4 years, but since I didn't use them for 4 years, I am somewhat concerned about their state (stored in the Synology box at room temperature).

My plan is to burn-in the new 3tb red to make sure its not DOA.

Thoughts?

 

[garm]

Never put drives in a pool without a proper burn in

 

[xaser]

Thanks!

BB is currently running and it looks like one of the 3 old "drives" is done, but I never interpreted smart data before so I was hoping someone can confirm that I should not extend by pool by adding a new vdev with 4 drives if one of those drives has the following smart result:


=== START OF READ SMART DATA SECTION ===
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 - 19997
3 Spin_Up_Time 0x0027 182 180 021 Pre-fail Always - 5866
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 106
5 Reallocated_Sector_Ct 0x0033 137 137 140 Pre-fail Always FAILING_NOW 1876
7 Seek_Error_Rate 0x002e 195 195 000 Old_age Always - 1351
9 Power_On_Hours 0x0032 058 058 000 Old_age Always - 31168
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 - 101
192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 55
193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 50
194 Temperature_Celsius 0x0022 117 104 000 Old_age Always - 33
196 Reallocated_Event_Count 0x0032 118 118 000 Old_age Always - 82
197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 3
198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0
200 Multi_Zone_Error_Rate 0x0008 197 194 000 Old_age Offline - 1525

 

[Kevin Horton]

Some manufacturers (e.g. Seagate) encode some SMART attributes, so the raw value is meaningless. Which make and model disk is this data from?

 

[xaser]

Its a 3tb WD Red - its the same drive that now gives the badblocks error...

 

[Kevin Horton]

In that case it looks like a massively failing disk. It has a huge reallocated sector count (1876) and multi-zone error rate (1525). And the raw read error rate is scary too.

Note: that SMART output would be a lot easier to read if you had put it in between CODE blocks (in the formatting bar, click "..." and select "Code").