Pool Unavailable after upgrade from CORE 13 to SCALE 24

TrueNAS General
, ,
1

Hello community,

I’ve been using Truenas 12 for a while for a home backup. My setup is 5 x 4Tb HDs in Raid-z1 pool, called RAID35, and 1 x SSD drive for boot-pool. Hardware is basic home motherboard with AMD processor, 12Gb RAM, 6 SATA ports. All used with the disks.

Recently I upgraded from CORE 12 to 13 with no complications and was using it for some weeks, accessing my pool as usual.

The I upgraded from CORE 13 to SCALE 24, without same luck. My main pool has gone!!, so I went back and reinstalled CORE 13 to another disk and imported my config backup. But the Pool is not comming back!! It is not GELI encrypted, so I though the upgrade process could not be dangerous. But now I don’t know how to rebuild the pool without loosing its data. I’m stuck with the CORE 13 trying to follow some posts and guides, but not sure how to proceed.

I read many posts of your forums but I have not clear what will be the process to identify the disks and try to make it all to work.

I can provide the output of some commands I already tried, and screens of the Web UI. The RAID35 pool consists of a Raidz1 with 5 disks of 4Tb, but the systems says now only 3 are ONLINE.

I run some smartctl tests and all 5 disks seems to be healthy and respond. So not sure how to proceed. Any help will be much appreciated.

imagen
imagen1598×505 33.3 KB

Captura de pantalla de 2024-08-28 15-56-04
Captura de pantalla de 2024-08-28 15-56-04803×312 89.5 KB

backup# glabel status
                                      Name  Status  Components
gptid/9ed682a9-63b1-11ef-8c49-1c1b0d4b30b5     N/A  ada0p1
gptid/81893fcd-ebc2-11eb-b603-78e3b519df44     N/A  ada1p2
gptid/819fd7e2-ebc2-11eb-b603-78e3b519df44     N/A  ada2p2
gptid/81dd4768-ebc2-11eb-b603-78e3b519df44     N/A  ada3p2
gptid/82b868b6-ebc2-11eb-b603-78e3b519df44     N/A  ada4p2
gptid/82afd059-ebc2-11eb-b603-78e3b519df44     N/A  ada5p2
gptid/82968a9d-ebc2-11eb-b603-78e3b519df44     N/A  ada5p1
gptid/82a0763b-ebc2-11eb-b603-78e3b519df44     N/A  ada4p1
gptid/81b84b67-ebc2-11eb-b603-78e3b519df44     N/A  ada3p1
gptid/811f648b-ebc2-11eb-b603-78e3b519df44     N/A  ada2p1
gptid/8114ac1d-ebc2-11eb-b603-78e3b519df44     N/A  ada1p1

backup# zpool import -R /mnt RAID35
cannot import 'RAID35': pool was previously in use from another system.
Last accessed by tnsbuilds01.tn.ixsystems.net (hostid=62313330) at Thu Jan  1 01:00:00 1970
The pool can be imported, use 'zpool import -f' to import the pool.

backup# zpool import -f RAID35
cannot import 'RAID35': no such pool or dataset
	Destroy and re-create the pool from
	a backup source.
backup#

The N/A 3.6 TiB disks are the raid ones. the othe one 1.8 Tib is a new one I attached but can be unplugged.

I’ll update with more data as soon as possible.

R…

2

You will need to solve the problem with the missing disks. Check data cables and power supply cables. Then you can proceed as below.

The error message below;

is pretty simple. Run the command as specified;
zpool import -f -R /mnt RAID35
This is quite harmless. The GUI won’t recognize your pool because you did this import behind the middleware’s back. But, easily solved. Export the pool from the command line, and then use the GUI to import it.

Not sure why the GUI does not have a force option. But, this problem is rare, so it is understandable that it is not in the GUI. Basically ZFS is trying to prevent shared disks from being imported from 2 hosts at the same time. The change in software caused it to think the pool is in use by another host. Not the case for you.

Let us know how it goes.

3

Thanks for your reply @Arwen,

Both sda2 and sdb2 are connected and respond to hardware checks, but the pool is missing them. I run de command as you suggest:

backup# zpool import
   pool: RAID35
     id: 9465709294530972002
  state: UNAVAIL
status: The pool was last accessed by another system.
 action: The pool cannot be imported due to damaged devices or data.
   see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-EY
 config:

	RAID35                                          UNAVAIL  insufficient replicas
	  raidz1-0                                      UNAVAIL  insufficient replicas
	    gptid/81893fcd-ebc2-11eb-b603-78e3b519df44  ONLINE
	    gptid/819fd7e2-ebc2-11eb-b603-78e3b519df44  ONLINE
	    gptid/81dd4768-ebc2-11eb-b603-78e3b519df44  ONLINE
	    sdb2                                        UNAVAIL  cannot open
	    sda2

backup# zpool import -f -R /mnt RAID35
cannot import 'RAID35': no such pool or dataset
	Destroy and re-create the pool from
	a backup source.

backup# gpart show
=>       40  976773088  ada0  GPT  (466G)
         40     532480     1  efi  (260M)
     532520   33554432     3  freebsd-swap  (16G)
   34086952  942669824     2  freebsd-zfs  (450G)
  976756776      16352        - free -  (8.0M)

=>        40  7814037088  ada1  GPT  (3.6T)
          40          88        - free -  (44K)
         128     4194304     1  freebsd-swap  (2.0G)
     4194432  7809842696     2  freebsd-zfs  (3.6T)

=>        40  7814037088  ada2  GPT  (3.6T)
          40          88        - free -  (44K)
         128     4194304     1  freebsd-swap  (2.0G)
     4194432  7809842696     2  freebsd-zfs  (3.6T)

=>        40  7814037088  ada3  GPT  (3.6T)
          40          88        - free -  (44K)
         128     4194304     1  freebsd-swap  (2.0G)
     4194432  7809842696     2  freebsd-zfs  (3.6T)

=>        40  7814037088  ada4  GPT  (3.6T)
          40          88        - free -  (44K)
         128     4194304     1  freebsd-swap  (2.0G)
     4194432  7809842696     2  freebsd-zfs  (3.6T)

=>        40  7814037088  ada5  GPT  (3.6T)
          40          88        - free -  (44K)
         128     4194304     1  freebsd-swap  (2.0G)
     4194432  7809842696     2  freebsd-zfs  (3.6T)

backup# gpart status
  Name  Status  Components
ada0p1      OK  ada0
ada0p2      OK  ada0
ada0p3      OK  ada0
ada1p1      OK  ada1
ada1p2      OK  ada1
ada2p1      OK  ada2
ada2p2      OK  ada2
ada3p1      OK  ada3
ada3p2      OK  ada3
ada4p1      OK  ada4
ada4p2      OK  ada4
ada5p1      OK  ada5
ada5p2      OK  ada5

backup# gpart list
Geom name: ada0
modified: false
state: OK
fwheads: 16
fwsectors: 63
last: 976773127
first: 40
entries: 128
scheme: GPT
Providers:
1. Name: ada0p1
   Mediasize: 272629760 (260M)
   Sectorsize: 512
   Stripesize: 4096
   Stripeoffset: 0
   Mode: r0w0e0
   efimedia: HD(1,GPT,9ed682a9-63b1-11ef-8c49-1c1b0d4b30b5,0x28,0x82000)
   rawuuid: 9ed682a9-63b1-11ef-8c49-1c1b0d4b30b5
   rawtype: c12a7328-f81f-11d2-ba4b-00a0c93ec93b
   label: (null)
   length: 272629760
   offset: 20480
   type: efi
   index: 1
   end: 532519
   start: 40
2. Name: ada0p2
   Mediasize: 482646949888 (450G)
   Sectorsize: 512
   Stripesize: 4096
   Stripeoffset: 0
   Mode: r1w1e1
   efimedia: HD(2,GPT,9f1e1df4-63b1-11ef-8c49-1c1b0d4b30b5,0x2082028,0x38300000)
   rawuuid: 9f1e1df4-63b1-11ef-8c49-1c1b0d4b30b5
   rawtype: 516e7cba-6ecf-11d6-8ff8-00022d09712b
   label: (null)
   length: 482646949888
   offset: 17452519424
   type: freebsd-zfs
   index: 2
   end: 976756775
   start: 34086952
3. Name: ada0p3
   Mediasize: 17179869184 (16G)
   Sectorsize: 512
   Stripesize: 4096
   Stripeoffset: 0
   Mode: r1w1e1
   efimedia: HD(3,GPT,9efbed7a-63b1-11ef-8c49-1c1b0d4b30b5,0x82028,0x2000000)
   rawuuid: 9efbed7a-63b1-11ef-8c49-1c1b0d4b30b5
   rawtype: 516e7cb5-6ecf-11d6-8ff8-00022d09712b
   label: (null)
   length: 17179869184
   offset: 272650240
   type: freebsd-swap
   index: 3
   end: 34086951
   start: 532520
Consumers:
1. Name: ada0
   Mediasize: 500107862016 (466G)
   Sectorsize: 512
   Stripesize: 4096
   Stripeoffset: 0
   Mode: r2w2e4

Geom name: ada1
modified: false
state: OK
fwheads: 16
fwsectors: 63
last: 7814037127
first: 40
entries: 128
scheme: GPT
Providers:
1. Name: ada1p1
   Mediasize: 2147483648 (2.0G)
   Sectorsize: 512
   Stripesize: 4096
   Stripeoffset: 0
   Mode: r0w0e0
   efimedia: HD(1,GPT,8114ac1d-ebc2-11eb-b603-78e3b519df44,0x80,0x400000)
   rawuuid: 8114ac1d-ebc2-11eb-b603-78e3b519df44
   rawtype: 516e7cb5-6ecf-11d6-8ff8-00022d09712b
   label: (null)
   length: 2147483648
   offset: 65536
   type: freebsd-swap
   index: 1
   end: 4194431
   start: 128
2. Name: ada1p2
   Mediasize: 3998639460352 (3.6T)
   Sectorsize: 512
   Stripesize: 4096
   Stripeoffset: 0
   Mode: r0w0e0
   efimedia: HD(2,GPT,81893fcd-ebc2-11eb-b603-78e3b519df44,0x400080,0x1d180be08)
   rawuuid: 81893fcd-ebc2-11eb-b603-78e3b519df44
   rawtype: 516e7cba-6ecf-11d6-8ff8-00022d09712b
   label: (null)
   length: 3998639460352
   offset: 2147549184
   type: freebsd-zfs
   index: 2
   end: 7814037127
   start: 4194432
Consumers:
1. Name: ada1
   Mediasize: 4000787030016 (3.6T)
   Sectorsize: 512
   Stripesize: 4096
   Stripeoffset: 0
   Mode: r0w0e0

Geom name: ada2
modified: false
state: OK
fwheads: 16
fwsectors: 63
last: 7814037127
first: 40
entries: 128
scheme: GPT
Providers:
1. Name: ada2p1
   Mediasize: 2147483648 (2.0G)
   Sectorsize: 512
   Stripesize: 4096
   Stripeoffset: 0
   Mode: r0w0e0
   efimedia: HD(1,GPT,811f648b-ebc2-11eb-b603-78e3b519df44,0x80,0x400000)
   rawuuid: 811f648b-ebc2-11eb-b603-78e3b519df44
   rawtype: 516e7cb5-6ecf-11d6-8ff8-00022d09712b
   label: (null)
   length: 2147483648
   offset: 65536
   type: freebsd-swap
   index: 1
   end: 4194431
   start: 128
2. Name: ada2p2
   Mediasize: 3998639460352 (3.6T)
   Sectorsize: 512
   Stripesize: 4096
   Stripeoffset: 0
   Mode: r0w0e0
   efimedia: HD(2,GPT,819fd7e2-ebc2-11eb-b603-78e3b519df44,0x400080,0x1d180be08)
   rawuuid: 819fd7e2-ebc2-11eb-b603-78e3b519df44
   rawtype: 516e7cba-6ecf-11d6-8ff8-00022d09712b
   label: (null)
   length: 3998639460352
   offset: 2147549184
   type: freebsd-zfs
   index: 2
   end: 7814037127
   start: 4194432
Consumers:
1. Name: ada2
   Mediasize: 4000787030016 (3.6T)
   Sectorsize: 512
   Stripesize: 4096
   Stripeoffset: 0
   Mode: r0w0e0

Geom name: ada3
modified: false
state: OK
fwheads: 16
fwsectors: 63
last: 7814037127
first: 40
entries: 128
scheme: GPT
Providers:
1. Name: ada3p1
   Mediasize: 2147483648 (2.0G)
   Sectorsize: 512
   Stripesize: 4096
   Stripeoffset: 0
   Mode: r0w0e0
   efimedia: HD(1,GPT,81b84b67-ebc2-11eb-b603-78e3b519df44,0x80,0x400000)
   rawuuid: 81b84b67-ebc2-11eb-b603-78e3b519df44
   rawtype: 516e7cb5-6ecf-11d6-8ff8-00022d09712b
   label: (null)
   length: 2147483648
   offset: 65536
   type: freebsd-swap
   index: 1
   end: 4194431
   start: 128
2. Name: ada3p2
   Mediasize: 3998639460352 (3.6T)
   Sectorsize: 512
   Stripesize: 4096
   Stripeoffset: 0
   Mode: r0w0e0
   efimedia: HD(2,GPT,81dd4768-ebc2-11eb-b603-78e3b519df44,0x400080,0x1d180be08)
   rawuuid: 81dd4768-ebc2-11eb-b603-78e3b519df44
   rawtype: 516e7cba-6ecf-11d6-8ff8-00022d09712b
   label: (null)
   length: 3998639460352
   offset: 2147549184
   type: freebsd-zfs
   index: 2
   end: 7814037127
   start: 4194432
Consumers:
1. Name: ada3
   Mediasize: 4000787030016 (3.6T)
   Sectorsize: 512
   Stripesize: 4096
   Stripeoffset: 0
   Mode: r0w0e0

Geom name: ada4
modified: false
state: OK
fwheads: 16
fwsectors: 63
last: 7814037127
first: 40
entries: 128
scheme: GPT
Providers:
1. Name: ada4p1
   Mediasize: 2147483648 (2.0G)
   Sectorsize: 512
   Stripesize: 4096
   Stripeoffset: 0
   Mode: r0w0e0
   efimedia: HD(1,GPT,82a0763b-ebc2-11eb-b603-78e3b519df44,0x80,0x400000)
   rawuuid: 82a0763b-ebc2-11eb-b603-78e3b519df44
   rawtype: 516e7cb5-6ecf-11d6-8ff8-00022d09712b
   label: (null)
   length: 2147483648
   offset: 65536
   type: freebsd-swap
   index: 1
   end: 4194431
   start: 128
2. Name: ada4p2
   Mediasize: 3998639460352 (3.6T)
   Sectorsize: 512
   Stripesize: 4096
   Stripeoffset: 0
   Mode: r0w0e0
   efimedia: HD(2,GPT,82b868b6-ebc2-11eb-b603-78e3b519df44,0x400080,0x1d180be08)
   rawuuid: 82b868b6-ebc2-11eb-b603-78e3b519df44
   rawtype: 516e7cba-6ecf-11d6-8ff8-00022d09712b
   label: (null)
   length: 3998639460352
   offset: 2147549184
   type: freebsd-zfs
   index: 2
   end: 7814037127
   start: 4194432
Consumers:
1. Name: ada4
   Mediasize: 4000787030016 (3.6T)
   Sectorsize: 512
   Stripesize: 4096
   Stripeoffset: 0
   Mode: r0w0e0

Geom name: ada5
modified: false
state: OK
fwheads: 16
fwsectors: 63
last: 7814037127
first: 40
entries: 128
scheme: GPT
Providers:
1. Name: ada5p1
   Mediasize: 2147483648 (2.0G)
   Sectorsize: 512
   Stripesize: 4096
   Stripeoffset: 0
   Mode: r0w0e0
   efimedia: HD(1,GPT,82968a9d-ebc2-11eb-b603-78e3b519df44,0x80,0x400000)
   rawuuid: 82968a9d-ebc2-11eb-b603-78e3b519df44
   rawtype: 516e7cb5-6ecf-11d6-8ff8-00022d09712b
   label: (null)
   length: 2147483648
   offset: 65536
   type: freebsd-swap
   index: 1
   end: 4194431
   start: 128
2. Name: ada5p2
   Mediasize: 3998639460352 (3.6T)
   Sectorsize: 512
   Stripesize: 4096
   Stripeoffset: 0
   Mode: r0w0e0
   efimedia: HD(2,GPT,82afd059-ebc2-11eb-b603-78e3b519df44,0x400080,0x1d180be08)
   rawuuid: 82afd059-ebc2-11eb-b603-78e3b519df44
   rawtype: 516e7cba-6ecf-11d6-8ff8-00022d09712b
   label: (null)
   length: 3998639460352
   offset: 2147549184
   type: freebsd-zfs
   index: 2
   end: 7814037127
   start: 4194432
Consumers:
1. Name: ada5
   Mediasize: 4000787030016 (3.6T)
   Sectorsize: 512
   Stripesize: 4096
   Stripeoffset: 0
   Mode: r0w0e0

I did some smartctl tests on both disks without errors. I’m wondering why the zpool import command show sda2 and sdb2 on the missing disks, instead of the gptid. I noticed after the upgrade to SCALE that all disks were renamed to linux devices: sda, sdb, sdc, etc, but then I reinstalled CORE 13 and imported the backup config, and the missing disks still have the linux device names, but the attached ones are using the gptid.

Any ideas? Will you recommend to upgrade again to SCALE to manage the situation?, Or better try to solve first the missing disks from CORE? Does SCALE accept a backup config from CORE?

After comparing the gptids from the previous commands and the list for disks, I think that the pools is missing ada4p2 and ada5p2

gptid/82b868b6-ebc2-11eb-b603-78e3b519df44     N/A  ada4p2
gptid/82afd059-ebc2-11eb-b603-78e3b519df44     N/A  ada5p2

but it shows sda and sdb on the zpool import command.

Both ada4 and ada5 pass the smartctl tests:

backup# smartctl -a /dev/ada4
smartctl 7.2 2021-09-14 r5236 [FreeBSD 13.1-RELEASE-p9 amd64] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Seagate BarraCuda 3.5 (SMR)
Device Model:     ST4000DM004-2CV104
Serial Number:    ZTT0XFKP
LU WWN Device Id: 5 000c50 0c905afe7
Firmware Version: 0001
User Capacity:    4,000,787,030,016 bytes [4.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5425 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 Aug 29 09:49:44 2024 CEST
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:  (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: 		(    0) seconds.
Offline data collection
capabilities: 			 (0x73) SMART execute Offline immediate.
					Auto Offline data collection on/off support.
					Suspend Offline collection upon new
					command.
					No 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: 	 ( 492) minutes.
Conveyance self-test routine
recommended polling time: 	 (   2) minutes.
SCT capabilities: 	       (0x30a5)	SCT Status 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   080   064   006    Pre-fail  Always       -       92298627
  3 Spin_Up_Time            0x0003   096   096   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       118
  5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   086   060   045    Pre-fail  Always       -       409320868
  9 Power_On_Hours          0x0032   069   069   000    Old_age   Always       -       27649h+07m+13.436s
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       118
183 Runtime_Bad_Block       0x0032   100   100   000    Old_age   Always       -       0
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   100   000    Old_age   Always       -       0 0 0
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   061   059   040    Old_age   Always       -       39 (Min/Max 39/41)
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       -       1136
193 Load_Cycle_Count        0x0032   100   100   000    Old_age   Always       -       1638
194 Temperature_Celsius     0x0022   039   041   000    Old_age   Always       -       39 (0 22 0 0 0)
195 Hardware_ECC_Recovered  0x001a   080   064   000    Old_age   Always       -       92298627
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       27346h+38m+31.451s
241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       7925177655
242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       175827905194

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       Completed without error       00%     27589         -
# 2  Short offline       Completed without error       00%     27588         -

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.


backup# smartctl -a /dev/ada5
smartctl 7.2 2021-09-14 r5236 [FreeBSD 13.1-RELEASE-p9 amd64] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Blue
Device Model:     WDC WD40EZRZ-00GXCB0
Serial Number:    WD-WCC7K4YZ60ZN
LU WWN Device Id: 5 0014ee 2b9070052
Firmware Version: 80.00A80
User Capacity:    4,000,787,030,016 bytes [4.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 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 Aug 29 09:48:55 2024 CEST
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: 		(44340) 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: 	 (   2) minutes.
Extended self-test routine
recommended polling time: 	 ( 470) minutes.
Conveyance self-test routine
recommended polling time: 	 (   5) minutes.
SCT capabilities: 	       (0x3035)	SCT Status 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          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   200   200   051    Pre-fail  Always       -       0
  3 Spin_Up_Time            0x0027   194   160   021    Pre-fail  Always       -       5291
  4 Start_Stop_Count        0x0032   099   099   000    Old_age   Always       -       1407
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   200   200   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   038   038   000    Old_age   Always       -       45622
 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       -       171
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       91
193 Load_Cycle_Count        0x0032   181   181   000    Old_age   Always       -       59948
194 Temperature_Celsius     0x0022   114   100   000    Old_age   Always       -       36
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   200   200   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0008   200   200   000    Old_age   Offline      -       0

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       Completed without error       00%     45563         -
# 2  Short offline       Completed without error       00%     45562         -

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.

Thanks, R…

4

Update:

I booted from the disk with the SCALE 24 OS. This is what I see from the Web GUI and the CLI:

imagen
imagen1605×483 40.7 KB

All disks are detected and marked as exported.

root@backup:~# zpool import -f -R /mnt RAID35
cannot import 'RAID35': one or more devices is currently unavailable

root@backup:~# zpool import
   pool: RAID35
     id: 9465709294530972002
  state: UNAVAIL
status: One or more devices contains corrupted data.
 action: The pool cannot be imported due to damaged devices or data.
   see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-5E
 config:

	RAID35      UNAVAIL  insufficient replicas
	  raidz1-0  UNAVAIL  insufficient replicas
	    sdd2    ONLINE
	    sde2    ONLINE
	    sdf2    ONLINE
	    sdb2    UNAVAIL  invalid label
	    sda2    UNAVAIL  invalid label

Both sda and sdb pass smartctl tests, although I have not done any long test. For me it seems like a lost of partition information or something like that. But I don’t want to do experiments with the pool or de disks until some of you with more experience give me some advice on how to proceed.

I have now tested the CORE 13 and SCALE 24 OSs and both behave the same regarding to the pool and the disks. The disks are online, but the pool does not recognize them (sda and sdb). In CORE, the missing disks from the pool have a sda2 and sdb2 label, instead of a gptid. In SCALE all 5 disks have sd(x)2 labels.

Thanks. R…

5

Can you show the output of zdb -l sd(x)2 where x is the letter of your disk(s) with the invalid label error?

6

Is this a bare metal install or in a VM ?

7

Need to wait few hours til I get access to the server. It is not online. I’ll report in few hours from now.
Thanks for replying.

R…

8

Full small home server. Not VM. MB, RAM, CPU, Power, 6 sata ports. 1 x 500gb ssd for boot pool, 5 x 4tb hd in raidz1 for 2 datasets storage.

All 5 x hds are connected and pass any test. No cable or hardware problems that I know.

It all began after I upgraded from CORE 13 to SCALE 24. Just after the upgrade reboot, the RAID35 pool was OFFLINE, with the 2 x hds UNAVAIL, sda2 and sdb2.

Then I removed the ssd and inserted a new 500gb hd and installed a fresh CORE 13, uploaded the config backup I made before the upgrade, and rebooted as part of the process. All config was back, but the RAID35 pool was still OFFLINE, with the 2 missing disks with linux labels: sda2 and sdb2, and the other 3 online disks with gptid labels.

See all screenshots and commands outputs.

Thanks for joining the conversation. In few hours I’ll get back to the server to proceed with further commands.

R…

9

Hi @HoneyBadger,

See outputs for the 5 disks:

root@backup:~# zdb -l sda2
failed to unpack label 0
failed to unpack label 1
failed to unpack label 2
failed to unpack label 3

root@backup:~# zdb -l sdb2
failed to unpack label 0
failed to unpack label 1
failed to unpack label 2
failed to unpack label 3

root@backup:~# zdb -l sdd2
------------------------------------
LABEL 0 
------------------------------------
    version: 5000
    name: 'RAID35'
    state: 0
    txg: 17024806
    pool_guid: 9465709294530972002
    errata: 0
    hostid: 1647391536
    hostname: 'tnsbuilds01.tn.ixsystems.net'
    top_guid: 125808423353519921
    guid: 11733684447306156048
    vdev_children: 1
    vdev_tree:
        type: 'raidz'
        id: 0
        guid: 125808423353519921
        nparity: 1
        metaslab_array: 256
        metaslab_shift: 34
        ashift: 12
        asize: 19993173688320
        is_log: 0
        create_txg: 4
        children[0]:
            type: 'disk'
            id: 0
            guid: 11733684447306156048
            path: '/dev/sdd2'
            DTL: 4150
            create_txg: 4
        children[1]:
            type: 'disk'
            id: 1
            guid: 7464112125075314987
            path: '/dev/sde2'
            DTL: 4149
            create_txg: 4
        children[2]:
            type: 'disk'
            id: 2
            guid: 2733516778587658012
            path: '/dev/sdf2'
            DTL: 4146
            create_txg: 4
        children[3]:
            type: 'disk'
            id: 3
            guid: 4877622665579539791
            path: '/dev/sdb2'
            DTL: 4145
            create_txg: 4
        children[4]:
            type: 'disk'
            id: 4
            guid: 17179492470065376409
            path: '/dev/sda2'
            DTL: 4138
            create_txg: 4
    features_for_read:
        com.delphix:hole_birth
        com.delphix:embedded_data
    labels = 0 1 2 3 

root@backup:~# zdb -l sde2
------------------------------------
LABEL 0 
------------------------------------
    version: 5000
    name: 'RAID35'
    state: 0
    txg: 17024806
    pool_guid: 9465709294530972002
    errata: 0
    hostid: 1647391536
    hostname: 'tnsbuilds01.tn.ixsystems.net'
    top_guid: 125808423353519921
    guid: 7464112125075314987
    vdev_children: 1
    vdev_tree:
        type: 'raidz'
        id: 0
        guid: 125808423353519921
        nparity: 1
        metaslab_array: 256
        metaslab_shift: 34
        ashift: 12
        asize: 19993173688320
        is_log: 0
        create_txg: 4
        children[0]:
            type: 'disk'
            id: 0
            guid: 11733684447306156048
            path: '/dev/sdd2'
            DTL: 4150
            create_txg: 4
        children[1]:
            type: 'disk'
            id: 1
            guid: 7464112125075314987
            path: '/dev/sde2'
            DTL: 4149
            create_txg: 4
        children[2]:
            type: 'disk'
            id: 2
            guid: 2733516778587658012
            path: '/dev/sdf2'
            DTL: 4146
            create_txg: 4
        children[3]:
            type: 'disk'
            id: 3
            guid: 4877622665579539791
            path: '/dev/sdb2'
            DTL: 4145
            create_txg: 4
        children[4]:
            type: 'disk'
            id: 4
            guid: 17179492470065376409
            path: '/dev/sda2'
            DTL: 4138
            create_txg: 4
    features_for_read:
        com.delphix:hole_birth
        com.delphix:embedded_data
    labels = 0 1 2 3 

root@backup:~# zdb -l sdf2
------------------------------------
LABEL 0 
------------------------------------
    version: 5000
    name: 'RAID35'
    state: 0
    txg: 17024806
    pool_guid: 9465709294530972002
    errata: 0
    hostid: 1647391536
    hostname: 'tnsbuilds01.tn.ixsystems.net'
    top_guid: 125808423353519921
    guid: 2733516778587658012
    vdev_children: 1
    vdev_tree:
        type: 'raidz'
        id: 0
        guid: 125808423353519921
        nparity: 1
        metaslab_array: 256
        metaslab_shift: 34
        ashift: 12
        asize: 19993173688320
        is_log: 0
        create_txg: 4
        children[0]:
            type: 'disk'
            id: 0
            guid: 11733684447306156048
            path: '/dev/sdd2'
            DTL: 4150
            create_txg: 4
        children[1]:
            type: 'disk'
            id: 1
            guid: 7464112125075314987
            path: '/dev/sde2'
            DTL: 4149
            create_txg: 4
        children[2]:
            type: 'disk'
            id: 2
            guid: 2733516778587658012
            path: '/dev/sdf2'
            DTL: 4146
            create_txg: 4
        children[3]:
            type: 'disk'
            id: 3
            guid: 4877622665579539791
            path: '/dev/sdb2'
            DTL: 4145
            create_txg: 4
        children[4]:
            type: 'disk'
            id: 4
            guid: 17179492470065376409
            path: '/dev/sda2'
            DTL: 4138
            create_txg: 4
    features_for_read:
        com.delphix:hole_birth
        com.delphix:embedded_data
    labels = 0 1 2 3

Both sda2 and sdb2 have no label, and are the unavail disks of the pool. Any follow up commands to test?

Thanks. R…

10

Hey @rou

The missing labels on sda and sdb are definitely a problem, as with a RAIDZ1 you’re only allowed a single missing/unavail disk.

Can I see sfdisk -l /dev/sda and sdb to see if your partition table is mangled somehow?

11

I’ll be offline until monday. I run out of ideas on how to recover the missing labels of sda and sdb. I read lots of posts on different forums, and now I have a mix of data on my head.

How about cloning some of the running disk into sda or sdb? Kind of dd of all partitions and data? Or does it exists some gdisk command to recover labels from other disks on the pool?

12

If you’ve got an extra disk and can clone one of the original sda or sdb disks to it, then we can work on that - I’m hesitant to do “hacky repairs” on the only copy of a disk for sure.

13

I’ll buy some 4Tb disk asap to test things. Thanks for suggesting. What do you suggest to clone? dd? Clonezilla? Full clone of sda for example?

14

Clone sda 4Tb in progress with dd. It will take few hours. I’ll continue tomorrow after the clone is done.

15

Thanks @rou

Once you’ve got the disk cloned, remove the original drive, and we will only work with the cloned disk.

I would suggest having only the clone disk in, to ensure that it’s the only available target, and then run zhack label repair -cu /dev/sdX

16

Hi @HoneyBadger,

No output from the sgdisk -l /dev/sdb command, where sdb is the new 4Tb cloned disk from the UNAVAIL sda.

From now on, the system will only have the boot disk + the cloned disk attached through SATA, named: sdb. Until we make some advance.

root@blackice:~# zdb -l /dev/sdb2
failed to unpack label 0
failed to unpack label 1
failed to unpack label 2
failed to unpack label 3

root@backup:~# zhack label repair -cu /dev/sdb
Calculated filesize to be 4000787030016
error: label 0: Expected the nvlist checksum magic number to not be zero
There should already be a checksum for the label.
error: label 1: Expected the nvlist checksum magic number to not be zero
There should already be a checksum for the label.
error: cannot unpack nvlist label 2
error: cannot unpack nvlist label 3
label 0: uberblock: skipped checksum: skipped
label 1: uberblock: skipped checksum: skipped
label 2: uberblock: skipped checksum: skipped
label 3: uberblock: skipped checksum: skipped
17 
sgdisk -l /dev/sdb

From the man sgdisk page, the -l option is for loading a backup file, but I don’t have a backup file, so no output is displayed. Other outputs:

root@backup:~# sgdisk -p /dev/sdb
Disk /dev/sdb: 7814037168 sectors, 3.6 TiB
Model: ST4000DM004-2CV1
Sector size (logical/physical): 512/4096 bytes
Disk identifier (GUID): 827B5752-EBC2-11EB-B603-78E3B519DF44
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 40, last usable sector is 7814037127
Partitions will be aligned on 128-sector boundaries
Total free space is 88 sectors (44.0 KiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1             128         4194431   2.0 GiB     A502  
   2         4194432      7814037127   3.6 TiB     A504

I’ve found this topic from yourself, in a similar situation:
https://www.truenas.com/community/threads/possible-to-reattach-a-disconnected-drive-to-an-empty-pool.111270/page-2

After following the above threat, I made a dump of the partition table of the cloned disk (this time sda after reboot)… with:

sfdisk -d /dev/sda > sda_part_table.txt

made no changes into the file or disk. Then issued a:

root@backup:~# sfdisk /dev/sda < sda_part_table.txt
Checking that no-one is using this disk right now ... OK

The device contains 'zfs_member' signature and it may remain on the device. It is recommended to wipe the device with wipefs(8) or sfdisk --wipe, in order to avoid possible collisions.

Disk /dev/sda: 3.64 TiB, 4000787030016 bytes, 7814037168 sectors
Disk model: ST4000DM004-2CV1
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

>>> Script header accepted.
>>> Script header accepted.
>>> Script header accepted.
>>> Script header accepted.
>>> Script header accepted.
>>> Script header accepted.
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: 827B5752-EBC2-11EB-B603-78E3B519DF44).
The device contains 'zfs_member' signature and it may remain on the device. It is recommended to wipe the device with wipefs(8) or sfdisk --wipe, in order to avoid possible collisions.

/dev/sda1: Created a new partition 1 of type 'FreeBSD swap' and of size 2 GiB.
/dev/sda2: Created a new partition 2 of type 'FreeBSD ZFS' and of size 3.6 TiB.
Partition #2 contains a zfs_member signature.
/dev/sda3: Done.

New situation:
Disklabel type: gpt
Disk identifier: 827B5752-EBC2-11EB-B603-78E3B519DF44

Device       Start        End    Sectors  Size Type
/dev/sda1      128    4194431    4194304    2G FreeBSD swap
/dev/sda2  4194432 7814037127 7809842696  3.6T FreeBSD ZFS

The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

and now the disk has not written de partition table. It shows no partitions at all:

root@backup:~# sfdisk -l /dev/sda
Disk /dev/sda: 3.64 TiB, 4000787030016 bytes, 7814037168 sectors
Disk model: ST4000DM004-2CV1
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

root@backup:~# lsblk -fi
NAME     FSTYPE     FSVER LABEL     UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
sda      zfs_member 5000                                                                
sdb                                                                                     
|-sdb1   vfat       FAT16           7BD4-19FD                                           
|-sdb2   zfs_member 5000  boot-pool 17234886916710062326                                
`-sdb3                                                                                  
  `-sdb3 swap       1               4e97c9e1-8c1e-4413-a2ca-9c0fed3c2a20

sdb is the boot disk with TN Scale 24.

18

Given my little time to find a solution to the Labels error after the upgrade I might just try to run Klennet or SpyZfs to try to recover most of the files, if any.

I wonder what could have happened in these 2 disks, that ZFS labels vanished, and I don’t find the way to recover them. Both disks hardware are OK, no disk errors at all. There should be a method to recover those labels based on the other members lables, isn’t it?

Thanks. to all participants.

I’ll keep posting any advances. For now I’ll scan the 5 disks with the free version of Klennet to see if it finds anything, and if so, pay the License to recover whatever it finds.
I also found SpyZfs, but the github repo is > 5 years with no activity. Does anyone know a similar program Opensource or Licensed? I’m quite confident with Linux, not with MS, or FreeBSD.

R…