I had a 6 wide Z1 VDEV i extended with another 20TB drive.
Unfortunately somewhere in the process it stopped extending.
Now it shows the drive with an error and all my apps wont show because of a docker error, but they all still work.
Does anyone have an idea what went wrong or how to fix it?
My system:
As already stated on Reddit, I have no idea why RAIDZ expansion would cause this - unless the pool is now offline.
Understanding the state of the pool and your configuration might help so please run the following commands and post the output back here with each command in a separate </> box:
lsblk -bo NAME,MODEL,ROTA,PTTYPE,TYPE,START,SIZE,PARTTYPENAME,PARTUUIDlspcisudo sas2flash -listsudo sas3flash -listsudo zpool status -vsudo zpool importP.S. A 6x20TB RAIDZ pool should really have been RAIDZ2 - but it is too late to convert it now - you are stuck with RAIDZ1.
Thanks for the reply. Here the results.
NAME MODEL ROTA PTTYPE TYPE START SIZE PARTTYPENAME PARTUUID
sda ST20000NM007D-3DJ103 1 gpt disk 20000588955648
└─sda1 1 gpt part 2048 20000586858496 Solaris /usr & Apple ZFS a238b596-47c6-4fbd-a831-da6f35053c9f
sdb ST20000NM007D-3DJ103 1 gpt disk 20000588955648
└─sdb1 1 gpt part 4096 20000586841600 Solaris /usr & Apple ZFS 46789880-6932-429a-8e37-5c9f368ca23c
sdc ST20000NM007D-3DJ103 1 gpt disk 20000588955648
└─sdc1 1 gpt part 4096 20000586841600 Solaris /usr & Apple ZFS 3bfb07ef-c4ca-4ac8-b458-1cfefd82578a
sdd ST20000NM007D-3DJ103 1 gpt disk 20000588955648
└─sdd1 1 gpt part 2048 20000587890176 Solaris /usr & Apple ZFS aff30a52-9d06-48d6-bc26-6b4ce57f3055
sde ST20000NM007D-3DJ103 1 gpt disk 20000588955648
└─sde1 1 gpt part 4096 20000586841600 Solaris /usr & Apple ZFS 85367f74-0401-4e3c-8f9d-d0eac0ecb266
sdf ST20000NM007D-3DJ103 1 gpt disk 20000588955648
└─sdf1 1 gpt part 4096 20000586841600 Solaris /usr & Apple ZFS 022662b0-e6bc-49b4-9ad5-9e0fbc1afd34
sdg ST20000NM007D-3DJ103 1 gpt disk 20000588955648
└─sdg1 1 gpt part 4096 20000586841600 Solaris /usr & Apple ZFS 6b54881f-9855-4c0d-8a50-eb29e24d9116
nvme0n1 KINGSTON SNV2S1000G 0 gpt disk 1000204886016
├─nvme0n1p1 0 gpt part 4096 1048576 BIOS boot b9f13970-efdc-4e29-ba31-95adf1dd4ccd
├─nvme0n1p2 0 gpt part 6144 536870912 EFI System ad2e38d1-e354-4f14-924c-c5df0e032369
├─nvme0n1p3 0 gpt part 34609152 982484983296 Solaris /usr & Apple ZFS 9f9a3b67-09c5-4fd0-8744-e061a99a860e
└─nvme0n1p4 0 gpt part 1054720 17179869184 Linux swap 222567ac-07fe-4677-a111-686b8a3b55c9
nvme1n1 KINGSTON SNV2S1000G 0 gpt disk 1000204886016
├─nvme1n1p1 0 gpt part 4096 1048576 BIOS boot a658ba02-d492-4cd4-953b-b5407221f4d6
├─nvme1n1p2 0 gpt part 6144 536870912 EFI System 64964f1d-6db5-497e-9103-cf4496a6f119
├─nvme1n1p3 0 gpt part 34609152 982484983296 Solaris /usr & Apple ZFS b12cd586-9d09-4a17-9564-d4453a0e110a
└─nvme1n1p4 0 gpt part 1054720 17179869184 Linux swap 116f3ba1-8649-4be6-89bc-140ff746dc38
LSI Corporation SAS2 Flash Utility
Version 20.00.00.00 (2014.09.18)
Copyright (c) 2008-2014 LSI Corporation. All rights reserved
No LSI SAS adapters found! Limited Command Set Available!
ERROR: Command Not allowed without an adapter!
ERROR: Couldn't Create Command -list
Avago Technologies SAS3 Flash Utility
Version 16.00.00.00 (2017.05.02)
Copyright 2008-2017 Avago Technologies. All rights reserved.
No Avago SAS adapters found! Limited Command Set Available!
ERROR: Command Not allowed without an adapter!
ERROR: Couldn't Create Command -list
Exiting Program.
pool: boot-pool
state: ONLINE
scan: scrub repaired 0B in 00:00:12 with 0 errors on Fri Jan 24 03:45:13 2025
config:
NAME STATE READ WRITE CKSUM
boot-pool ONLINE 0 0 0
mirror-0 ONLINE 0 0 0
nvme1n1p3 ONLINE 0 0 0
nvme0n1p3 ONLINE 0 0 0
errors: No known data errors
pool: volume1
state: ONLINE
status: One or more devices has experienced an unrecoverable error. An
attempt was made to correct the error. Applications are unaffected.
action: Determine if the device needs to be replaced, and clear the errors
using 'zpool clear' or replace the device with 'zpool replace'.
see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-9P
scan: scrub in progress since Fri Jan 24 13:15:03 2025
53.3T / 82.8T scanned at 339M/s, 52.8T / 82.8T issued at 336M/s
0B repaired, 63.75% done, 1 days 02:01:11 to go
expand: expansion of raidz1-0 in progress since Wed Jan 22 12:06:54 2025
53.3T / 82.9T copied at 163M/s, 64.21% done, 2 days 04:53:06 to go
config:
NAME STATE READ WRITE CKSUM
volume1 ONLINE 0 0 0
raidz1-0 ONLINE 0 0 0
3bfb07ef-c4ca-4ac8-b458-1cfefd82578a ONLINE 0 0 0
46789880-6932-429a-8e37-5c9f368ca23c ONLINE 0 0 0
85367f74-0401-4e3c-8f9d-d0eac0ecb266 ONLINE 0 0 0
022662b0-e6bc-49b4-9ad5-9e0fbc1afd34 ONLINE 0 0 0
6b54881f-9855-4c0d-8a50-eb29e24d9116 ONLINE 0 0 0
aff30a52-9d06-48d6-bc26-6b4ce57f3055 ONLINE 0 0 0
a238b596-47c6-4fbd-a831-da6f35053c9f ONLINE 0 0 1
errors: No known data errors
no pools available to import
It is possible that the docker service was the process that had the unrecoverable error and so it didn’t start on this occasion, but it will start on a reboot.
Also, the zpool status and lsblk commands point to the problematic disks, so please run the following and post the results:
sudo smartctl -x /dev/sdaP.S. Also, if you can wait 2 days for the expand to complete without having Docker running, then that would be best, but if you need to reboot after running the above command, then the expansion should pick up from where it was before the reboot.
Funny enough all my installed apps are working perfectly i just dont see them in the app section and get the error.
Here the copy paste:
sudo smartctl -x /dev/sda
Warning: the supported mechanisms for making configuration changes
are the TrueNAS WebUI, CLI, and API exclusively. ALL OTHERS ARE
NOT SUPPORTED AND WILL RESULT IN UNDEFINED BEHAVIOR AND MAY
RESULT IN SYSTEM FAILURE.
admin@truenas[~]$ sudo smartctl -x /dev/sda
[sudo] password for admin:
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.6.44-production+truenas] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Device Model: ST20000NM007D-3DJ103
Serial Number: ZVT2QL73
LU WWN Device Id: 5 000c50 0e52e8068
Firmware Version: SN01
User Capacity: 20,000,588,955,648 bytes [20.0 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 7200 rpm
Form Factor: 3.5 inches
Device is: Not in smartctl database 7.3/5528
ATA Version is: ACS-4 (minor revision not indicated)
SATA Version is: SATA 3.3, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Sun Jan 26 11:26:10 2025 CET
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is: Unavailable
APM feature is: Unavailable
Rd look-ahead is: Enabled
Write cache is: Enabled
DSN feature is: Disabled
ATA Security is: Disabled, frozen [SEC2]
Write SCT (Get) Feature Control Command failed: Connection timed out
Wt Cache Reorder: Unknown (SCT Feature Control command failed)
=== 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: ( 559) 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: (1675) minutes.
Conveyance self-test routine
recommended polling time: ( 2) minutes.
SCT capabilities: (0x70bd) 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 FLAGS VALUE WORST THRESH FAIL RAW_VALUE
1 Raw_Read_Error_Rate POSR-- 083 064 044 - 192916944
3 Spin_Up_Time PO---- 098 098 000 - 0
4 Start_Stop_Count -O--CK 100 100 020 - 2
5 Reallocated_Sector_Ct PO--CK 100 100 010 - 0
7 Seek_Error_Rate POSR-- 075 060 045 - 28310552
9 Power_On_Hours -O--CK 100 100 000 - 93
10 Spin_Retry_Count PO--C- 100 100 097 - 0
12 Power_Cycle_Count -O--CK 100 100 020 - 2
18 Unknown_Attribute PO-R-- 100 100 050 - 0
187 Reported_Uncorrect -O--CK 100 100 000 - 0
188 Command_Timeout -O--CK 100 100 000 - 0
190 Airflow_Temperature_Cel -O---K 048 046 000 - 52 (Min/Max 34/54)
192 Power-Off_Retract_Count -O--CK 100 100 000 - 1
193 Load_Cycle_Count -O--CK 100 100 000 - 4
194 Temperature_Celsius -O---K 052 054 000 - 52 (0 22 0 0 0)
197 Current_Pending_Sector -O--C- 100 100 000 - 0
198 Offline_Uncorrectable ----C- 100 100 000 - 0
199 UDMA_CRC_Error_Count -OSRCK 200 200 000 - 0
200 Multi_Zone_Error_Rate PO---K 100 100 001 - 0
240 Head_Flying_Hours ------ 100 100 000 - 93 (115 54 0)
241 Total_LBAs_Written ------ 100 253 000 - 17103697360
242 Total_LBAs_Read ------ 100 253 000 - 582640225375
||||||_ 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 5 Comprehensive SMART error log
0x03 GPL R/O 5 Ext. Comprehensive SMART error log
0x04 GPL R/O 256 Device Statistics log
0x04 SL R/O 8 Device Statistics log
0x06 SL R/O 1 SMART self-test log
0x07 GPL R/O 1 Extended self-test log
0x08 GPL R/O 2 Power Conditions log
0x09 SL R/W 1 Selective self-test log
0x0a GPL R/W 8 Device Statistics Notification
0x0c GPL R/O 2048 Pending Defects log
0x10 GPL R/O 1 NCQ Command Error log
0x11 GPL R/O 1 SATA Phy Event Counters log
0x13 GPL R/O 1 SATA NCQ Send and Receive log
0x21 GPL R/O 1 Write stream error log
0x22 GPL R/O 1 Read stream error log
0x24 GPL R/O 768 Current Device Internal Status Data log
0x2f GPL R/O 1 Set Sector Configuration
0x30 GPL,SL R/O 9 IDENTIFY DEVICE data log
0x80-0x9f GPL,SL R/W 16 Host vendor specific log
0xa1 GPL,SL VS 160 Device vendor specific log
0xa2 GPL VS 16320 Device vendor specific log
0xa4 GPL,SL VS 160 Device vendor specific log
0xa6 GPL VS 192 Device vendor specific log
0xa8-0xa9 GPL,SL VS 136 Device vendor specific log
0xab GPL VS 1 Device vendor specific log
0xad GPL VS 16 Device vendor specific log
0xb1 GPL,SL VS 160 Device vendor specific log
0xb6 GPL VS 1920 Device vendor specific log
0xbe-0xbf GPL VS 65535 Device vendor specific log
0xc1 GPL,SL VS 8 Device vendor specific log
0xc3 GPL,SL VS 24 Device vendor specific log
0xc6 GPL VS 5184 Device vendor specific log
0xc7 GPL,SL VS 8 Device vendor specific log
0xc9 GPL,SL VS 8 Device vendor specific log
0xca GPL,SL VS 16 Device vendor specific log
0xcd GPL,SL VS 1 Device vendor specific log
0xce GPL VS 1 Device vendor specific log
0xcf GPL VS 512 Device vendor specific log
0xd1 GPL VS 656 Device vendor specific log
0xd2 GPL VS 10256 Device vendor specific log
0xd4 GPL VS 2048 Device vendor specific log
0xda GPL,SL VS 1 Device 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 (5 sectors)
No Errors Logged
SMART Extended Self-test Log Version: 1 (1 sectors)
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed without error 00% 82 -
# 2 Short offline Completed without error 00% 47 -
# 3 Short offline Completed without error 00% 46 -
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.
SCT Status Version: 3
SCT Version (vendor specific): 522 (0x020a)
Device State: Active (0)
Current Temperature: 52 Celsius
Power Cycle Min/Max Temperature: 34/54 Celsius
Lifetime Min/Max Temperature: 22/54 Celsius
Under/Over Temperature Limit Count: 0/47
SMART Status: 0xc24f (PASSED)
Vendor specific:
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 02 00 00 00 00 00 00 00 00 00 00 00
SCT Temperature History Version: 2
Temperature Sampling Period: 4 minutes
Temperature Logging Interval: 59 minutes
Min/Max recommended Temperature: 10/40 Celsius
Min/Max Temperature Limit: 5/60 Celsius
Temperature History Size (Index): 128 (98)
Index Estimated Time Temperature Celsius
99 2025-01-21 05:59 ? -
... ..( 27 skipped). .. -
127 2025-01-22 09:31 ? -
0 2025-01-22 10:30 52 *********************************
1 2025-01-22 11:29 ? -
2 2025-01-22 12:28 22 ***
3 2025-01-22 13:27 48 *****************************
4 2025-01-22 14:26 52 *********************************
... ..( 35 skipped). .. *********************************
40 2025-01-24 01:50 52 *********************************
41 2025-01-24 02:49 53 **********************************
42 2025-01-24 03:48 52 *********************************
... ..( 3 skipped). .. *********************************
46 2025-01-24 07:44 52 *********************************
47 2025-01-24 08:43 53 **********************************
48 2025-01-24 09:42 52 *********************************
49 2025-01-24 10:41 52 *********************************
50 2025-01-24 11:40 ? -
51 2025-01-24 12:39 34 ***************
52 2025-01-24 13:38 44 *************************
53 2025-01-24 14:37 49 ******************************
54 2025-01-24 15:36 51 ********************************
55 2025-01-24 16:35 52 *********************************
56 2025-01-24 17:34 52 *********************************
57 2025-01-24 18:33 53 **********************************
... ..( 4 skipped). .. **********************************
62 2025-01-24 23:28 53 **********************************
63 2025-01-25 00:27 52 *********************************
64 2025-01-25 01:26 52 *********************************
65 2025-01-25 02:25 52 *********************************
66 2025-01-25 03:24 51 ********************************
67 2025-01-25 04:23 52 *********************************
... ..( 2 skipped). .. *********************************
70 2025-01-25 07:20 52 *********************************
71 2025-01-25 08:19 53 **********************************
... ..( 8 skipped). .. **********************************
80 2025-01-25 17:10 53 **********************************
81 2025-01-25 18:09 52 *********************************
82 2025-01-25 19:08 53 **********************************
83 2025-01-25 20:07 53 **********************************
84 2025-01-25 21:06 52 *********************************
85 2025-01-25 22:05 53 **********************************
86 2025-01-25 23:04 54 ***********************************
87 2025-01-26 00:03 53 **********************************
... ..( 5 skipped). .. **********************************
93 2025-01-26 05:57 53 **********************************
94 2025-01-26 06:56 52 *********************************
95 2025-01-26 07:55 52 *********************************
96 2025-01-26 08:54 52 *********************************
97 2025-01-26 09:53 53 **********************************
98 2025-01-26 10:52 52 *********************************
SCT Error Recovery Control:
Read: 100 (10.0 seconds)
Write: 100 (10.0 seconds)
Device Statistics (GP Log 0x04)
Page Offset Size Value Flags Description
0x01 ===== = = === == General Statistics (rev 1) ==
0x01 0x008 4 2 --- Lifetime Power-On Resets
0x01 0x010 4 93 --- Power-on Hours
0x01 0x018 6 17103698144 --- Logical Sectors Written
0x01 0x020 6 1438885276 --- Number of Write Commands
0x01 0x028 6 582640225391 --- Logical Sectors Read
0x01 0x030 6 24869942 --- Number of Read Commands
0x01 0x038 6 - --- Date and Time TimeStamp
0x03 ===== = = === == Rotating Media Statistics (rev 1) ==
0x03 0x008 4 93 --- Spindle Motor Power-on Hours
0x03 0x010 4 93 --- Head Flying Hours
0x03 0x018 4 4 --- Head Load Events
0x03 0x020 4 0 --- Number of Reallocated Logical Sectors
0x03 0x028 4 0 --- Read Recovery Attempts
0x03 0x030 4 0 --- Number of Mechanical Start Failures
0x03 0x038 4 0 --- Number of Realloc. Candidate Logical Sectors
0x03 0x040 4 1 --- Number of High Priority Unload Events
0x04 ===== = = === == General Errors Statistics (rev 1) ==
0x04 0x008 4 0 --- Number of Reported Uncorrectable Errors
0x04 0x010 4 0 --- Resets Between Cmd Acceptance and Completion
0x04 0x018 4 0 -D- Physical Element Status Changed
0x05 ===== = = === == Temperature Statistics (rev 1) ==
0x05 0x008 1 52 --- Current Temperature
0x05 0x010 1 52 --- Average Short Term Temperature
0x05 0x018 1 - --- Average Long Term Temperature
0x05 0x020 1 54 --- Highest Temperature
0x05 0x028 1 35 --- Lowest Temperature
0x05 0x030 1 52 --- Highest Average Short Term Temperature
0x05 0x038 1 51 --- Lowest Average Short Term Temperature
0x05 0x040 1 - --- Highest Average Long Term Temperature
0x05 0x048 1 - --- Lowest Average Long Term Temperature
0x05 0x050 4 0 --- Time in Over-Temperature
0x05 0x058 1 60 --- Specified Maximum Operating Temperature
0x05 0x060 4 0 --- Time in Under-Temperature
0x05 0x068 1 5 --- Specified Minimum Operating Temperature
0x06 ===== = = === == Transport Statistics (rev 1) ==
0x06 0x008 4 15 --- Number of Hardware Resets
0x06 0x010 4 3 --- Number of ASR Events
0x06 0x018 4 0 --- Number of Interface CRC Errors
0xff ===== = = === == Vendor Specific Statistics (rev 1) ==
0xff 0x008 7 0 --- Vendor Specific
0xff 0x010 7 0 --- Vendor Specific
0xff 0x018 7 0 --- Vendor Specific
|||_ C monitored condition met
||__ D supports DSN
|___ N normalized value
Pending Defects log (GP Log 0x0c)
No Defects Logged
SATA Phy Event Counters (GP Log 0x11)
ID Size Value Description
0x000a 2 3 Device-to-host register FISes sent due to a COMRESET
0x0001 2 0 Command failed due to ICRC error
0x0003 2 0 R_ERR response for device-to-host data FIS
0x0004 2 0 R_ERR response for host-to-device data FIS
0x0006 2 0 R_ERR response for device-to-host non-data FIS
0x0007 2 0 R_ERR response for host-to-device non-data FIS
Seagate FARM log (GP Log 0xa6) supported [try: -l farm]
I don’t mind waiting 2 days. But it doesn’t show me that something is expanding in the “Job” overview.
One point I missed but I think you need to address is that you are running a scrub concurrently with the expansion. I think the ongoing scrub should be cancelled and any scheduled scrubs turned off until expansion completes.
Smart doesn’t show anything specific. The LBAs read seem high for 93 hours at 291TiB, and the temperature is stable but higher than I would really like to see (airflow issues), but these are very minor points.
IMO (and others may differ in their opinions) a sudo zpool clear volume1 is warranted.
So i did stop the scrubbing. I know about the temperature, but there since it is stable and within range i leave it that for the moment.
How do you see my system is still on a expansion? I don’t see it anywhere.
What does a sudo zpool clear volume1 do?
sudo zpool status -v volume1 says it is still expanding.
zpool clear resets the error log for the poll - so the one error will go down to zero.
Hopefully none of this data is important, you are putting all your eggs in a raidz1 basket. The moment one disk fails you are at the brink of total data loss.
With that many drives of that size (20TB) you stand a fair risk of that happening.
See it now, thank you for showing.
About 1-2 TB of data is important but backed up on a few different locations. The rest is somewhat not important but still would be a big loss. I also always have a spare hard disk at home if one fails.
What would your recommendation be in my situation? From what i know the only way would be to start over with new disks and do Z2 but that would mean i need to have a second system and at least 7 new 20TB disks right?
A raidz2. It can still fail, but at least you have an disk as a buffer when one of them does.
You would need to vacate the drives and remake the pool, so yes, you will need some form of temporary storage place.
I waited 2 days for the expanding to finish, did a restart and the scrub and now everything is back to normal again.
Many thanks you all for helping.
If you always have a “spare” then you probably should’ve used RaidZ2.
But yes, hindsight is a fantastic thing.
To go from RaidZ1 to Z2, the most efficient approach is unfortunately a full backup and restore.
I guess so, certainly didn’t seem so when i started this server.
A backup of about 70TB sounds really painful and expensive but i’m gonna start looking.
