thimplicity
Dabbler
- Joined
- Jan 6, 2022
- Messages
- 28
Hi everyone,
I am running TrueNAS virtualized on Proxmox and yesterday morning I was greeted with the error message:
I have ran smartctl long overnight and this is the result:
I am also running scrutiny in my homelab and this is the "export".
Few questions on next steps:
I am running TrueNAS virtualized on Proxmox and yesterday morning I was greeted with the error message:
Code:
Pool data-pool state is DEGRADED: One or more devices are faulted in response to persistent errors. Sufficient replicas exist for the pool to continue functioning in a degraded state. The following devices are not healthy: Disk ATA ST4000VN008-2DR1 ZM417ZGZ is FAULTED
I have ran smartctl long overnight and this is the result:
Code:
root@truenas[~]# smartctl -a /dev/da2 smartctl 7.2 2021-09-14 r5236 [FreeBSD 13.1-RELEASE-p7 amd64] (local build) Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Seagate IronWolf Device Model: ST4000VN008-2DR166 Serial Number: ZM417ZGZ LU WWN Device Id: 5 000c50 0c647b36d Firmware Version: SC60 User Capacity: 4,000,787,030,016 bytes [4.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 5980 rpm Form Factor: 3.5 inches Device is: In smartctl database [for details use: -P show] ATA Version is: ACS-3 T13/2161-D revision 5 SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Thu Oct 19 06:54:39 2023 EDT 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: ( 113) The previous self-test completed having the read element of the test failed. Total time to complete Offline data collection: ( 581) 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: ( 636) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x50bd) SCT Status supported. SCT Error Recovery Control supported. SCT Feature Control supported. SCT Data Table 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 064 064 044 Pre-fail Always - 169631716 3 Spin_Up_Time 0x0003 094 093 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 59 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 095 060 045 Pre-fail Always - 3038528488 9 Power_On_Hours 0x0032 069 069 000 Old_age Always - 27370 (49 4 0) 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 57 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 068 068 000 Old_age Always - 32 188 Command_Timeout 0x0032 100 099 000 Old_age Always - 65537 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 062 051 040 Old_age Always - 38 (Min/Max 36/47) 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 - 64 193 Load_Cycle_Count 0x0032 030 030 000 Old_age Always - 141062 194 Temperature_Celsius 0x0022 038 049 000 Old_age Always - 38 (0 18 0 0 0) 197 Current_Pending_Sector 0x0012 100 099 000 Old_age Always - 72 198 Offline_Uncorrectable 0x0010 100 099 000 Old_age Offline - 72 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 26492h+49m+33.779s 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 142200168728 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 95282192711 SMART Error Log Version: 1 ATA Error Count: 32 (device log contains only the most recent five errors) CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 32 occurred at disk power-on lifetime: 27348 hours (1139 days + 12 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 ff ff ff 0f Error: WP at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 61 00 00 ff ff ff 4f 00 4d+19:29:01.942 WRITE FPDMA QUEUED 61 00 00 ff ff ff 4f 00 4d+19:29:01.941 WRITE FPDMA QUEUED 61 00 00 ff ff ff 4f 00 4d+19:29:01.941 WRITE FPDMA QUEUED 61 00 00 ff ff ff 4f 00 4d+19:29:01.940 WRITE FPDMA QUEUED 61 00 10 ff ff ff 4f 00 4d+19:29:01.939 WRITE FPDMA QUEUED Error 31 occurred at disk power-on lifetime: 27348 hours (1139 days + 12 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 00 ff ff ff 4f 00 4d+19:28:57.796 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 4d+19:28:57.791 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 4d+19:28:57.788 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 4d+19:28:57.785 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 4d+19:28:57.768 READ FPDMA QUEUED Error 30 occurred at disk power-on lifetime: 27348 hours (1139 days + 12 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 ff ff ff 0f Error: WP at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 61 00 00 ff ff ff 4f 00 4d+19:28:57.308 WRITE FPDMA QUEUED 61 00 00 ff ff ff 4f 00 4d+19:28:53.841 WRITE FPDMA QUEUED 61 00 00 ff ff ff 4f 00 4d+19:28:53.841 WRITE FPDMA QUEUED 60 00 00 ff ff ff 4f 00 4d+19:28:53.840 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 4d+19:28:53.840 READ FPDMA QUEUED Error 29 occurred at disk power-on lifetime: 27348 hours (1139 days + 12 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 00 ff ff ff 4f 00 4d+19:28:53.826 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 4d+19:28:50.186 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 4d+19:28:50.182 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 4d+19:28:50.130 READ FPDMA QUEUED 61 00 00 ff ff ff 4f 00 4d+19:28:49.863 WRITE FPDMA QUEUED Error 28 occurred at disk power-on lifetime: 27348 hours (1139 days + 12 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 00 ff ff ff 4f 00 4d+19:28:49.791 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 4d+19:28:46.178 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 4d+19:28:46.178 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 4d+19:28:46.166 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 4d+19:28:46.162 READ FPDMA QUEUED SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed: read failure 10% 27365 - # 2 Short offline Completed without error 00% 27359 - # 3 Extended offline Completed without error 00% 27279 - # 4 Short offline Completed without error 00% 27221 - # 5 Short offline Completed without error 00% 27053 - # 6 Short offline Completed without error 00% 26885 - # 7 Short offline Completed without error 00% 26717 - # 8 Extended offline Completed without error 00% 26558 - # 9 Short offline Completed without error 00% 26549 - #10 Short offline Completed without error 00% 26381 - #11 Short offline Completed without error 00% 26213 - #12 Short offline Completed without error 00% 26045 - #13 Short offline Completed without error 00% 25878 - #14 Extended offline Completed without error 00% 25819 - #15 Short offline Completed without error 00% 25717 - #16 Short offline Completed without error 00% 25549 - #17 Short offline Completed without error 00% 25381 - #18 Short offline Completed without error 00% 25212 - #19 Extended offline Completed without error 00% 25081 - #20 Short offline Completed without error 00% 25044 - #21 Short offline Completed without error 00% 24877 - 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
I am also running scrutiny in my homelab and this is the "export".
Few questions on next steps:
- Based on what I read in the forum, I assume the drive is done. Is that a correct assumption?
- I am running this drive in a mirror with an identical drive. Can I still use the other drive to save data?
- This drive is a 4TB drive. Can I combine a 3TB with it in a mirror? I am currently using 900GB of that mirror, but all the data is on the 4TB drive.