zfs error: cannot open 'big_tank2': no such pool

[undik]

Hello.
I had a power outage recently, and after the power came back proxmox can't find my zfs pool "big_tank2".

Output of zfs list:

root@pve:~# zfs list
NAME                      USED  AVAIL     REFER  MOUNTPOINT
VMs                      84.6G   130G       96K  /VMs
VMs/docker-volumes         96K   130G       96K  /var/lib/docker/volumes
VMs/vm-100-disk-0        51.6G   165G     17.3G  -
VMs/vm-102-disk-0        33.0G   156G     7.88G  -
big_tank1                4.53T   769G       96K  /big_tank1
big_tank1/vm-101-disk-0  4.03T  4.68T     99.8G  -
big_tank1/vm-103-disk-0   516G  1.24T     10.7G  -
tank                     1.60T   159G      128K  /tank
tank/vm-102-disk-0       1.60T  1.58T      176G  -

Output of zpool import:

root@pve:~# zpool import
no pools available to import

Error message from when I'm trying to start my VM

()
zfs error: cannot open 'big_tank2': no such pool

zfs error: cannot open 'big_tank2': no such pool

TASK ERROR: could not activate storage 'big_tank2', zfs error: cannot open 'big_tank2': no such pool

I have checked cables and connectors inside the server. It all looks good.
Can anyone help me get my ZFS pool back?
Br, Undik.

 

[Dunuin]

Did you setup ZFS ontop of a HW raid?
Do you see the drives that should be part of your pool when you look at lsblk?
A power outage is always bad, because you always loose data if that happens. If you disabled write caches everywhere ZFS should only loose the last 5 seconds of async data. But if you for example use consumer SSDs without powerloss protection or a raid without backup battery you might loose way more because the controller/SSD/HDD is write caching too.

 

[undik]

Did you setup ZFS ontop of a HW raid?
Do you see the drives that should be part of your pool when you look at lsblk?

No, i didn't have any HW raid, only individual disks.

The disks are shown in lsblk, label sdg:

sda                  8:0    0 931.5G  0 disk
├─sda1               8:1    0 931.5G  0 part
└─sda9               8:9    0     8M  0 part
sdb                  8:16   0   5.5T  0 disk
├─sdb1               8:17   0   5.5T  0 part
└─sdb9               8:25   0     8M  0 part
sdc                  8:32   0 223.6G  0 disk
├─sdc1               8:33   0 223.6G  0 part
└─sdc9               8:41   0     8M  0 part
sdd                  8:48   0 232.9G  0 disk
├─sdd1               8:49   0  1007K  0 part
├─sdd2               8:50   0   512M  0 part
└─sdd3               8:51   0 232.4G  0 part
  ├─pve-swap       253:0    0     8G  0 lvm  [SWAP]
  ├─pve-root       253:1    0    58G  0 lvm  /
  ├─pve-data_tmeta 253:2    0   1.5G  0 lvm 
  │ └─pve-data     253:4    0 147.4G  0 lvm 
  └─pve-data_tdata 253:3    0 147.4G  0 lvm 
    └─pve-data     253:4    0 147.4G  0 lvm 
sde                  8:64   0 931.5G  0 disk
├─sde1               8:65   0 931.5G  0 part
└─sde9               8:73   0     8M  0 part
sdf                  8:80   0 931.5G  0 disk
├─sdf1               8:81   0 931.5G  0 part
└─sdf9               8:89   0     8M  0 part
sdg                  8:96   0   5.5T  0 disk
zd0                230:0    0   1.2T  0 disk
└─zd0p1            230:1    0   1.2T  0 part
zd16               230:16   0   3.9T  0 disk
├─zd16p1           230:17   0     1M  0 part
├─zd16p2           230:18   0     1G  0 part
└─zd16p3           230:19   0   3.9T  0 part
zd32               230:32   0    32G  0 disk
├─zd32p1           230:33   0    28G  0 part
├─zd32p2           230:34   0     1K  0 part
└─zd32p5           230:37   0     4G  0 part
zd48               230:48   0    50G  0 disk
├─zd48p1           230:49   0    50M  0 part
└─zd48p2           230:50   0    50G  0 part
zd64               230:64   0   500G  0 disk
├─zd64p1           230:65   0     1M  0 part
├─zd64p2           230:66   0     1G  0 part
└─zd64p3           230:67   0   499G  0 part

 

[Dunuin]

"sdg" got no partitions. If you created that pool using the GUI it should got a partition 1 + 9 like the other drives. So I guess the drive got problems or the partitiontable got corrupted. Whats your output of smartctl -a /dev/sdg and fdisk -l /dev/sdg?

 

[undik]

"sdg" got no partitions. If you created that pool using the GUI it should got a partition 1 + 9 like the other drives. So I guess the drive got problems or the partitiontable got corrupted. Whats your output of smartctl -a /dev/sdg and fdisk -l /dev/sdg?

Oh, that doesen't sound good. I created the pool using the gui.

smartctl -a /dev/sdg output:

root@pve:~# smartctl -a /dev/sdg
smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.4.73-1-pve] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Barracuda Compute
Device Model:     ST6000DM003-2CY186
Serial Number:    ZCT0X92G
LU WWN Device Id: 5 000c50 0b5ee8d1b
Firmware Version: 0001
User Capacity:    6,001,175,126,016 bytes [6.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:    Wed Nov  3 11:17:49 2021 CET
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:        ( 731) 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   076   064   006    Pre-fail  Always       -       39811932
  3 Spin_Up_Time            0x0003   093   092   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   094   094   020    Old_age   Always       -       7145
  5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   082   060   045    Pre-fail  Always       -       153189234
  9 Power_On_Hours          0x0032   084   084   000    Old_age   Always       -       14455 (84 179 0)
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       275
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
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   070   051   040    Old_age   Always       -       30 (Min/Max 28/30)
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       -       265
193 Load_Cycle_Count        0x0032   093   093   000    Old_age   Always       -       15524
194 Temperature_Celsius     0x0022   030   049   000    Old_age   Always       -       30 (0 15 0 0 0)
195 Hardware_ECC_Recovered  0x001a   076   064   000    Old_age   Always       -       39811932
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      -       7219 (240 18 0)
241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       22124161129
242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       19368342566

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]

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.

fdisk -l /dev/sdg output:

root@pve:~# fdisk -l /dev/sdg
Disk /dev/sdg: 5.5 TiB, 6001175126016 bytes, 11721045168 sectors
Disk model: ST6000DM003-2CY1
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: F4E46BA4-51C5-42EC-8F6F-BFA73D1BD35E

 

[Dunuin]

You could try to run gdisk /dev/sdg to see if that sees any corrupted GPT data. It can also be used to restore the GPT from the backup GPT. If there is a problem with the GPT it should show something like this: "Warning! Main partition table CRC mismatch! Loaded backup partition table instead of main partition table!"


The disk doesn't look that bad. But you could start a long selftest so see if it find any problems using smartctl -t long /dev/sdg. That will take several hours and you can check the progress and results with smartctl -a /dev/sdg.

 

[undik]

Thank you.

I can't see any corrupted GPT data running gdisk /dev/sdg. Output:

Partition table scan:
  MBR: protective
  BSD: not present
  APM: not present
  GPT: present

i- show detailed information on a partition. Output:

Command (? for help): i
No partitions

p- print the partition table. Output:

Command (? for help): p
Disk /dev/sdg: 11721045168 sectors, 5.5 TiB
Model: ST6000DM003-2CY1
Sector size (logical/physical): 512/4096 bytes
Disk identifier (GUID): F4E46BA4-51C5-42EC-8F6F-BFA73D1BD35E
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 11721045134
Partitions will be aligned on 2048-sector boundaries
Total free space is 11721045101 sectors (5.5 TiB)

I have to try getting the files off the drive somehow, most of it had backup but unfortunately not everything as the backup drive was full and I didn't notice. It may be off the current topic, but do you have any tips on how to do that?

 

[Dunuin]

I have to try getting the files off the drive somehow, most of it had backup but unfortunately not everything as the backup drive was full and I didn't notice. It may be off the current topic, but do you have any tips on how to do that?

No, not really. But before doing something with that drive to restore stuff you should back it up first doing a blocklevel copy to another disk or image file (for example using dd or clonezilla).

 

[undik]

No, not really. But before doing something with that drive to restore stuff you should back it up first doing a blocklevel copy to another disk or image file (for example using dd or clonezilla).

I will. Thank you. I ran the long test now, it will finish 00.30 tomorrow so I'll see then if I can find something.