FreeNAS newb needs help with failing disk

[Sith Empire]

Hi everyone. I have a very basic FreeNAS setup ( (1) 128GB SSD boot/FreeNAS disk and (2) 2TB Segate drives for jails, media storage, etc.); Unfortunately the 2 TB drives are in a striped configuration and one has started taking on errors:

Output from smartctl -a /dev/ada2:

smartctl 6.6 2017-11-05 r4594 [FreeBSD 11.1-STABLE amd64] (local build)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family: Seagate Barracuda 7200.14 (AF)
Device Model: ST2000DM001-1CH164
Serial Number: Z340V559
LU WWN Device Id: 5 000c50 066248858
Firmware Version: CC29
User Capacity: 2,000,398,934,016 bytes [2.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 7200 rpm
Form Factor: 3.5 inches
Device is: In smartctl database [for details use: -P show]
ATA Version is: ACS-2, ACS-3 T13/2161-D revision 3b
SATA Version is: SATA 3.1, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is: Mon Jun 18 00:32:46 2018 PDT
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: (0x82) Offline data collection activity
was completed without error.
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: ( 584) 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: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 225) minutes.
Conveyance self-test routine
recommended polling time: ( 2) minutes.
SCT capabilities: (0x3085) SCT Status supported.

SMART Attributes Data Structure revision number: 10
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 119 099 006 Pre-fail Always - 225269928
3 Spin_Up_Time 0x0003 095 094 000 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 199
5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0
7 Seek_Error_Rate 0x000f 080 060 030 Pre-fail Always - 101047145
9 Power_On_Hours 0x0032 077 077 000 Old_age Always - 20528
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 563
183 Runtime_Bad_Block 0x0032 095 095 000 Old_age Always - 5
184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0
187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0
188 Command_Timeout 0x0032 100 083 000 Old_age Always - 27 29 49
189 High_Fly_Writes 0x003a 098 098 000 Old_age Always - 2
190 Airflow_Temperature_Cel 0x0022 060 046 045 Old_age Always - 40 (Min/Max 29/43)
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 224
193 Load_Cycle_Count 0x0032 076 076 000 Old_age Always - 48639
194 Temperature_Celsius 0x0022 040 054 000 Old_age Always - 40 (0 21 0 0 0)
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 16
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 16
199 UDMA_CRC_Error_Count 0x003e 200 196 000 Old_age Always - 845
240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 18121h+28m+36.702s
241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 25189095044
242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 13052532725

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 Aborted by host 20% 2070 -

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.

root@nas1:~ #


Can I add a new 2TB disk and use the 'replace' feature to resilver the data from the failing drive to the new drive, then remove the failing drive once that is complete? If the answer is no, then would someone be kind enough to explain how I go about:
1. backing up all of my data
2. Adding two additional 2TB drives (for a total of 3 drives) and setting up RAIDZ1
3. Restoring my data to the new RAIDZ1 pool

I realize that this is probably a very tall order, but I really could use a hand with all of this.

Thanks in advance,

Mac

 

[danb35]

Can I add a new 2TB disk and use the 'replace' feature to resilver the data from the failing drive to the new drive

Probably. It's going to depend somewhat on how many other errors there are on the disk that it hasn't caught yet. You've got lots of problems going on: the striped configuration and bad blocks you already know about, but this disk is also running too hot, and it's never had a SMART test in its entire 20000-hour life. That doesn't bode well for your chances, but it's nonetheless the best thing to try right now, I think.

 

[Sith Empire]

Probably. It's going to depend somewhat on how many other errors there are on the disk that it hasn't caught yet. You've got lots of problems going on: the striped configuration and bad blocks you already know about, but this disk is also running too hot, and it's never had a SMART test in its entire 20000-hour life. That doesn't bode well for your chances, but it's nonetheless the best thing to try right now, I think.

Thanks for you reply. Honestly, I think I'd like to explore backing up my existing data, adding new drives, then import/restore the backed up data. Can you point me in the right direction please?

Thanks.

EDIT: I re-read my reply and realize what I was asking for.. which was asinine. My plan now is to backup my data to an external 2TB drive, destroy the pool, add a total of (3) 2TB drives in a RAIDZ1 configuration and copy my data back onto the new pool. I have three VM's running currently, would it be better to just recreate them? In addition, I'll be adding a new SATA controller card with more SATA ports so that I can run at least RAIDZ2. Am I on the right track?