Hello, total noob here. I have managed to get Truenas running and have 4 disks installed. Now i need to change one of the drives and it is part of the media pool. I thinks
Type:
FILESYSTEM
Sync: STANDARD
Compression Level: LZ4
Enable Atime: OFF
ZFS Deduplication: OFF
Case Sensitivity: ON
Path: media
Whats the correct procedure to change it ?
EDIT:
What is strange tho, under Manage devices its not listed as faulty ?
Before replacing the drive (which may need replacing), letās see what the drive statistics are saying. However replacing a drive is fairly easy, just read the User Guide for your version of TrueNAS (It would have been nice to add the version of TrueNAS you are using). If you feel that you have two left thumbs, then backup your data first so some place safe until after the drive has been replaced.
But first, the data: could you go to the command line (SSH or GUI Shell if available) and enter the command smarctl -x /dev/sde and then post the output in the code brackets </> listed above.
Thanks for answering 
Finding version of the truenas, where i might find it ? In update tab im on scale dragonfish 24.04 train, and no updates so i assume its 24.04 ?
How do i install smartctl command ? It seems i dont have it ā¦
-bash: smarctl: command not found
Spell the command correctly, it will work.
Not strange at all. I donāt know why people assume that a bad sector (and IMO, a single bad sector isnāt grounds to immediately replace a disk) has any necessary connection to a pool error, but thereās simply no reason to do so.
Aaah, need to use sudo.
@truenas:~$ sudo smartctl -x /dev/sde
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.6.32-production+truenas] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: SAMSUNG SpinPoint F4 EG (AF)
Device Model: SAMSUNG HD204UI
Serial Number: S2H7JD1B106218
LU WWN Device Id: 5 0024e9 00494475a
Firmware Version: 1AQ10001
User Capacity: 2,000,398,934,016 bytes [2.00 TB]
Sector Size: 512 bytes logical/physical
Rotation Rate: 5400 rpm
Form Factor: 3.5 inches
Device is: In smartctl database 7.3/5528
ATA Version is: ATA8-ACS T13/1699-D revision 6
SATA Version is: SATA 2.6, 3.0 Gb/s
Local Time is: Sat Sep 14 17:35:41 2024 EEST
==> WARNING: Using smartmontools or hdparm with this
drive may result in data loss due to a firmware bug.
****** THIS DRIVE MAY OR MAY NOT BE AFFECTED! ******
Buggy and fixed firmware report same version number!
See the following web pages for details:
http://knowledge.seagate.com/articles/en_US/FAQ/223571en
https://www.smartmontools.org/wiki/SamsungF4EGBadBlocks
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM level is: 0 (vendor specific), recommended: 254
APM feature is: Disabled
Rd look-ahead is: Enabled
Write cache is: Enabled
DSN feature is: Unavailable
ATA Security is: Disabled, frozen [SEC2]
Wt Cache Reorder: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
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: (20460) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No 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: ( 341) 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 FLAGS VALUE WORST THRESH FAIL RAW_VALUE
1 Raw_Read_Error_Rate POSR-K 100 100 051 - 0
2 Throughput_Performance -OS--K 252 252 000 - 0
3 Spin_Up_Time PO---K 067 067 025 - 10109
4 Start_Stop_Count -O--CK 093 093 000 - 7976
5 Reallocated_Sector_Ct PO--CK 252 252 010 - 0
7 Seek_Error_Rate -OSR-K 252 252 051 - 0
8 Seek_Time_Performance --S--K 252 252 015 - 0
9 Power_On_Hours -O--CK 100 100 000 - 6960
10 Spin_Retry_Count -O--CK 252 252 051 - 0
11 Calibration_Retry_Count -O--CK 252 252 000 - 0
12 Power_Cycle_Count -O--CK 100 100 000 - 23
181 Program_Fail_Cnt_Total -O---K 100 100 000 - 16033688
191 G-Sense_Error_Rate -O---K 100 100 000 - 403
192 Power-Off_Retract_Count -O---K 252 252 000 - 0
194 Temperature_Celsius -O---- 064 059 000 - 33 (Min/Max 18/41)
195 Hardware_ECC_Recovered -O-RCK 100 100 000 - 0
196 Reallocated_Event_Count -O--CK 252 252 000 - 0
197 Current_Pending_Sector -O--CK 252 252 000 - 0
198 Offline_Uncorrectable ----CK 252 252 000 - 0
199 UDMA_CRC_Error_Count -OS-CK 200 200 000 - 0
200 Multi_Zone_Error_Rate -O-R-K 100 100 000 - 124
223 Load_Retry_Count -O--CK 252 252 000 - 0
225 Load_Cycle_Count -O--CK 100 100 000 - 7982
||||||_ K auto-keep
|||||__ C event count
||||___ R error rate
|||____ S speed/performance
||_____ O updated online
|______ P prefailure warning
General Purpose Log Directory Version 1
SMART Log Directory Version 1 [multi-sector log support]
Address Access R/W Size Description
0x00 GPL,SL R/O 1 Log Directory
0x01 SL R/O 1 Summary SMART error log
0x02 SL R/O 2 Comprehensive SMART error log
0x03 GPL R/O 2 Ext. Comprehensive SMART error log
0x06 SL R/O 1 SMART self-test log
0x07 GPL R/O 2 Extended self-test log
0x08 GPL R/O 2 Power Conditions log
0x09 SL R/W 1 Selective self-test log
0x10 GPL R/O 1 NCQ Command Error log
0x11 GPL R/O 1 SATA Phy Event Counters log
0x80-0x9f GPL,SL R/W 16 Host vendor specific log
0xe0 GPL,SL R/W 1 SCT Command/Status
0xe1 GPL,SL R/W 1 SCT Data Transfer
SMART Extended Comprehensive Error Log Version: 1 (2 sectors)
No Errors Logged
SMART Extended Self-test Log Version: 1 (2 sectors)
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed without error 00% 6943 -
# 2 Short offline Completed without error 00% 6919 -
# 3 Short offline Completed without error 00% 6895 -
# 4 Short offline Completed without error 00% 6871 -
# 5 Short offline Completed without error 00% 6847 -
# 6 Short offline Completed without error 00% 6823 -
# 7 Short offline Completed without error 00% 6801 -
# 8 Short offline Completed without error 00% 6775 -
# 9 Short offline Completed without error 00% 6751 -
#10 Short offline Completed without error 00% 6727 -
#11 Short offline Completed without error 00% 6703 -
#12 Short offline Completed without error 00% 6679 -
#13 Short offline Completed without error 00% 6655 -
#14 Short offline Completed without error 00% 6631 -
#15 Short offline Completed without error 00% 6607 -
#16 Short offline Completed without error 00% 6583 -
#17 Short offline Completed without error 00% 6559 -
#18 Short offline Completed without error 00% 6535 -
#19 Short offline Completed without error 00% 6511 -
#20 Short offline Completed without error 00% 6487 -
#21 Short offline Completed without error 00% 6463 -
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 Completed [00% left] (0-65535)
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.
SCT Status Version: 2
SCT Version (vendor specific): 256 (0x0100)
Device State: Active (0)
Current Temperature: 33 Celsius
Power Cycle Min/Max Temperature: 25/41 Celsius
Lifetime Min/Max Temperature: 19/61 Celsius
Specified Max Operating Temperature: 80 Celsius
Under/Over Temperature Limit Count: 0/0
SCT Temperature History Version: 2
Temperature Sampling Period: 5 minutes
Temperature Logging Interval: 5 minutes
Min/Max recommended Temperature: -5/80 Celsius
Min/Max Temperature Limit: -10/85 Celsius
Temperature History Size (Index): 128 (88)
Index Estimated Time Temperature Celsius
89 2024-09-14 07:00 33 **************
... ..( 82 skipped). .. **************
44 2024-09-14 13:55 33 **************
45 2024-09-14 14:00 32 *************
46 2024-09-14 14:05 33 **************
47 2024-09-14 14:10 33 **************
48 2024-09-14 14:15 34 ***************
49 2024-09-14 14:20 33 **************
... ..( 16 skipped). .. **************
66 2024-09-14 15:45 33 **************
67 2024-09-14 15:50 32 *************
68 2024-09-14 15:55 33 **************
69 2024-09-14 16:00 33 **************
70 2024-09-14 16:05 33 **************
71 2024-09-14 16:10 32 *************
72 2024-09-14 16:15 33 **************
73 2024-09-14 16:20 33 **************
74 2024-09-14 16:25 32 *************
75 2024-09-14 16:30 33 **************
76 2024-09-14 16:35 33 **************
77 2024-09-14 16:40 32 *************
78 2024-09-14 16:45 32 *************
79 2024-09-14 16:50 33 **************
80 2024-09-14 16:55 33 **************
81 2024-09-14 17:00 33 **************
82 2024-09-14 17:05 32 *************
83 2024-09-14 17:10 33 **************
84 2024-09-14 17:15 32 *************
85 2024-09-14 17:20 33 **************
86 2024-09-14 17:25 32 *************
87 2024-09-14 17:30 33 **************
88 2024-09-14 17:35 32 *************
SCT Error Recovery Control:
Read: Disabled
Write: Disabled
Device Statistics (GP/SMART Log 0x04) not supported
Pending Defects log (GP Log 0x0c) not supported
SATA Phy Event Counters (GP Log 0x11)
ID Size Value Description
0x0001 4 0 Command failed due to ICRC error
0x0002 4 0 R_ERR response for data FIS
0x0003 4 0 R_ERR response for device-to-host data FIS
0x0004 4 0 R_ERR response for host-to-device data FIS
0x0005 4 0 R_ERR response for non-data FIS
0x0006 4 0 R_ERR response for device-to-host non-data FIS
0x0007 4 0 R_ERR response for host-to-device non-data FIS
0x0008 4 0 Device-to-host non-data FIS retries
0x0009 4 14 Transition from drive PhyRdy to drive PhyNRdy
0x000a 4 14 Device-to-host register FISes sent due to a COMRESET
0x000b 4 0 CRC errors within host-to-device FIS
0x000d 4 0 Non-CRC errors within host-to-device FIS
0x000f 4 0 R_ERR response for host-to-device data FIS, CRC
0x0010 4 0 R_ERR response for host-to-device data FIS, non-CRC
0x0012 4 0 R_ERR response for host-to-device non-data FIS, CRC
0x0013 4 0 R_ERR response for host-to-device non-data FIS, non-CRC
0x8e00 4 0 Vendor specific
0x8e01 4 0 Vendor specific
0x8e02 4 0 Vendor specific
0x8e03 4 0 Vendor specific
0x8e04 4 0 Vendor specific
0x8e05 4 0 Vendor specific
0x8e06 4 0 Vendor specific
0x8e07 4 0 Vendor specific
0x8e08 4 0 Vendor specific
0x8e09 4 0 Vendor specific
0x8e0a 4 0 Vendor specific
0x8e0b 4 0 Vendor specific
0x8e0c 4 0 Vendor specific
0x8e0d 4 0 Vendor specific
0x8e0e 4 0 Vendor specific
0x8e0f 4 0 Vendor specific
0x8e10 4 0 Vendor specific
0x8e11 4 0 Vendor specific
Ok, im not familiar on these, but i presume it doesnt get any better either ? Its been saying this for few months now.
You have some Multi_Zone_Error_Rate to monitor, but if im not wrong i didnāt see any long smart testā¦ You should schedule at least one once a week.
If you already have a spare disk, replace this one before he can fail (your pool Is raidz1, you should preserve parity), then you can do all the test you need to desume if the disk Is failing, or Is Just a minor problem (cable issue, ecc)
No, not generallyābut I donāt see the offline/uncorrectable sector in the SMART output you postedāare you sure itās for the correct disk?
And as @oxyde said, you should be running regular long SMART tests as well, at least every few weeks. But I wouldnāt be in a hurry to replace this disk.
As the others have said:
@dan I completely agree with you and Iāve been seeing it a lot over the past few months. People assuming a ZFS error must be a drive failure, when they are two different things. Sure, a drive failure can cause a ZFS error however it is premature to state that without looking at all the data to support that outcome.
Added weekly long tests now to all drives, and monitoring that one more closely. Error was listed as ācriticalā, so i thought it was critical 
Gonna see if i find spare drive like this still, quite old drives i have
And it IS critical in the sense that the drive is not healthy. It may not completely fail soon, but it is not healthy and itās never going to get better.
You may replace the drive by a larger one. But if you are generally using old drives do not wait before addressing issues.
I managed to get 4TB drive to replace that 2TB faulty one, but. Do i need to have 2x4TB drives to get that increased space in use ? Now i have 1x4TB and 3x2TB and exactly same storage space as 4x2TB ? its raidz1.
Yes, all drives in the vdev have to be 4 TB (or more) for expansion to occur.
Ok, thats clear, Thanks