December 30, 2025Dec 30 Hello, unfortunately my flash drive has died, and I thought I had a backup, but sadly the backup is from a point in time before I had set up the zpool.In my current configuration, I had one SSD as a ZFS cache and three HDDs as a zpool in RAIDZ1.When mounting, I had no issues with the cache and I can access it again, but the zpool is causing problems. Unfortunately, it is unmountable, so I have no access to my data.Is there a way to simply re-import the zpool or at least recover my data so that I can then create a new zpool, or do I have to pay the price for my mistake and the data is lost? okabe-diagnostics-20251230-0942.zip
December 31, 2025Dec 31 Author 15 minutes ago, JorgeB said:Please post the output from zpool importroot@Okabe:~# zpool import pool: cache id: 11273674506066081776 state: ONLINEstatus: Some supported features are not enabled on the pool. (Note that they may be intentionally disabled if the 'compatibility' property is set.)action: The pool can be imported using its name or numeric identifier, though some features will not be available without an explicit 'zpool upgrade'.config: cache ONLINE sdb1 ONLINEroot@Okabe:~#
December 31, 2025Dec 31 Author 28 minutes ago, JorgeB said:There's no other pool detected, post the output from blkidThanks a lot for your Help!Here is the Output:root@Okabe:~# blkid/dev/sdb1: LABEL="cache" UUID="11273674506066081776" UUID_SUB="15309590862456780816" BLOCK_SIZE="4096" TYPE="zfs_member"/dev/sda1: LABEL_FATBOOT="UNRAID" LABEL="UNRAID" UUID="1EFA-1D6A" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="d3c3b7bd-01"/dev/loop1: BLOCK_SIZE="131072" TYPE="squashfs"/dev/loop0: BLOCK_SIZE="131072" TYPE="squashfs"root@Okabe:~#
December 31, 2025Dec 31 Community Expert Something is missing; just losing the flash drive would not touch the devices, and they don't have any filesystem signature. Post the output from:fdisk -l /dev/sdcfdisk -l /dev/sddfdisk -l /dev/sde
December 31, 2025Dec 31 Author 6 minutes ago, JorgeB said:Something is missing; just losing the flash drive would not touch the devices, and they don't have any filesystem signature. Post the output from:fdisk -l /dev/sdcfdisk -l /dev/sddfdisk -l /dev/sdeI thought so, the one single SSD is fine, thats why i am so suprised that the zpool is not working.root@Okabe:~# fdisk -l /dev/sdcDisk /dev/sdc: 14.55 TiB, 16000900661248 bytes, 31251759104 sectorsDisk model: WDC WD160EDGZ-11Units: sectors of 1 * 512 = 512 bytesSector size (logical/physical): 512 bytes / 4096 bytesI/O size (minimum/optimal): 4096 bytes / 4096 bytesroot@Okabe:~# fdisk -l /dev/sddDisk /dev/sdd: 14.55 TiB, 16000900661248 bytes, 31251759104 sectorsDisk model: WDC WD160EDGZ-11Units: sectors of 1 * 512 = 512 bytesSector size (logical/physical): 512 bytes / 4096 bytesI/O size (minimum/optimal): 4096 bytes / 4096 bytesroot@Okabe:~# fdisk -l /dev/sdeDisk /dev/sde: 14.55 TiB, 16000900661248 bytes, 31251759104 sectorsDisk model: WDC WD160EDGZ-11Units: sectors of 1 * 512 = 512 bytesSector size (logical/physical): 512 bytes / 4096 bytesI/O size (minimum/optimal): 4096 bytes / 4096 bytes
December 31, 2025Dec 31 Community Expert None of the disks has partitions. Any idea what happened there?Also run this on one of the pool disks and post any output that shows up. Normally, and if there's still a ZFS filesystem there, it should show something after a few minutes tops; you can abort any time with CTRL + CLC_ALL=C grep -obaP '\x0c\xb1\xba\x00' /dev/sdc
December 31, 2025Dec 31 Author 58 minutes ago, JorgeB said:None of the disks has partitions. Any idea what happened there?Also run this on one of the pool disks and post any output that shows up. Normally, and if there's still a ZFS filesystem there, it should show something after a few minutes tops; you can abort any time with CTRL + CLC_ALL=C grep -obaP '\x0c\xb1\xba\x00' /dev/sdcUnfortunately, I have no idea what might have happened there.I can only tell you what originally happened and what I did.I had to shut down the server due to work on the power grid. When I tried to turn it back on afterward, it did not boot. I then checked the flash drive and realized that I could not access it. After that, I did nothing for many weeks. A few days ago, I started taking care of the problem by getting a new flash drive and loading the old backup onto it.At that point, I noticed that the hard drives were still in an array and not yet in a zpool. I didn't start the array and instead put a completely fresh Unraid installation with the current version onto the USB stick. Then I put the three hard drives into a pool and set the filesystem to ZFS with RAIDZ1 and compression enabled. After that, I started the array and received the message that the hard drives were unmountable.I then read through the forum a bit and saw that the settings should be left on Auto, so I deleted the configuration again and put the three drives into a pool without changing any settings and left the filesystem set to Auto. I got the same result as before.This is the Output I got (the full output from about 30min ist in the .txt file):root@Okabe:~# LC_ALL=C grep -obaP '\x0c\xb1\xba\x00' /dev/sdc163840:167936:172032:176128:180224:184320:188416:192512:196608:200704:204800:208896:212992:217088:221184:225280:229376:233472:237568:241664:245760:249856:253952:258048:262144:266240:270336:274432:278528: LC_ALL=C_sdc.txt
December 31, 2025Dec 31 Community Expert 16 minutes ago, Cookio said:so I deleted the configurationThis is fine as long as you clicked the "remove" button, not the "erase" one.The dd output suggests the zfs signature is still there, and apparently starting on standard Unraid 64 sector, to confirm, type:losetup -f --offset 32768 /dev/sdclosetup -f --offset 32768 /dev/sddlosetup -f --offset 32768 /dev/sdeThen try again zpool import
December 31, 2025Dec 31 Author 7 minutes ago, JorgeB said:This is fine as long as you clicked the "remove" button, not the "erase" one.The dd output suggests the zfs signature is still there, and apparently starting on standard Unraid 64 sector, to confirm, type:losetup -f --offset 32768 /dev/sdclosetup -f --offset 32768 /dev/sddlosetup -f --offset 32768 /dev/sdeThen try again zpool importI used "new config" in Unraid.root@Okabe:~# losetup -f --offset 32768 /dev/sdcroot@Okabe:~# losetup -f --offset 32768 /dev/sddroot@Okabe:~# losetup -f --offset 32768 /dev/sderoot@Okabe:~# zpool import pool: cache id: 11273674506066081776 state: ONLINEstatus: Some supported features are not enabled on the pool. (Note that they may be intentionally disabled if the 'compatibility' property is set.)action: The pool can be imported using its name or numeric identifier, though some features will not be available without an explicit 'zpool upgrade'.config: cache ONLINE sdb1 ONLINE
December 31, 2025Dec 31 Community Expert New config would not delete the partitions, so not sure what happened there.Sector 64 is not showing any results, which is not good news. Type losetup and look for the 3 highest loop devices and post the output for zdb -l /dev/loop# for one of them.Also trylosetup -f --offset 65536 /dev/sdclosetup -f --offset 65536 /dev/sddlosetup -f --offset 65536 /dev/sdeand again zpool import
December 31, 2025Dec 31 Author 20 minutes ago, JorgeB said:New config would not delete the partitions, so not sure what happened there.Sector 64 is not showing any results, which is not good news. Type losetup and look for the 3 highest loop devices and post the output for zdb -l /dev/loop# for one of them.Also trylosetup -f --offset 65536 /dev/sdclosetup -f --offset 65536 /dev/sddlosetup -f --offset 65536 /dev/sdeand again zpool importEven if its not gonna work, I am really thankful for your help!root@Okabe:~# losetupNAME SIZELIMIT OFFSET AUTOCLEAR RO BACK-FILE DIO LOG-SEC/dev/loop1 0 0 1 1 /boot/bzmodules 0 512/dev/loop8 0 32768 0 0 /dev/sdc 0 512/dev/loop6 0 32768 0 0 /dev/sdd 0 512/dev/loop4 0 32768 0 0 /dev/sde 0 512/dev/loop2 0 32768 0 0 /dev/sdc 0 512/dev/loop0 0 0 1 1 /boot/bzfirmware 0 512/dev/loop9 0 32768 0 0 /dev/sdd 0 512/dev/loop7 0 32768 0 0 /dev/sde 0 512/dev/loop5 0 32768 0 0 /dev/sdc 0 512/dev/loop3 0 32768 0 0 /dev/sdd 0 512/dev/loop10 0 32768 0 0 /dev/sde 0 512root@Okabe:~# zdb -l /dev/loop10failed to unpack label 0failed to unpack label 1failed to unpack label 2failed to unpack label 3root@Okabe:~# losetup -f --offset 65536 /dev/sdcroot@Okabe:~# losetup -f --offset 65536 /dev/sddroot@Okabe:~# losetup -f --offset 65536 /dev/sderoot@Okabe:~# zpool import pool: cache id: 11273674506066081776 state: ONLINEstatus: Some supported features are not enabled on the pool. (Note that they may be intentionally disabled if the 'compatibility' property is set.)action: The pool can be imported using its name or numeric identifier, though some features will not be available without an explicit 'zpool upgrade'.config: cache ONLINE sdb1 ONLINE
December 31, 2025Dec 31 Community Expert I suspect it's not just the partitions that are missing; possibly part of the zfs labels was also deleted, although the dd output doesn't suggest that. Try sector 2048, which is the other common starting sector used by Unraid:losetup -f --offset 1048576 /dev/sdclosetup -f --offset 1048576 /dev/sddlosetup -f --offset 1048576 /dev/sdeThen zpool import again, if it still doesn't show the pool, I'm afraid the only option may be using a data recovery software like UFS Explorer, but while that's not very expensive for single device zfs filesystems, it's much more for pools, still, depending on the data and backup situation, it may be worth a try, the free trial should show if it can recover anything.
December 31, 2025Dec 31 Author 1 minute ago, JorgeB said:I suspect it's not just the partitions that are missing; possibly part of the zfs labels was also deleted, although the dd output doesn't suggest that. Try sector 2048, which is the other common starting sector used by Unraid:losetup -f --offset 1048576 /dev/sdclosetup -f --offset 1048576 /dev/sddlosetup -f --offset 1048576 /dev/sdeThen zpool import again, if it still doesn't show the pool, I'm afraid the only option may be using a data recovery software like UFS Explorer, but while that's not very expensive for single device zfs filesystems, it's much more for pools, still, depending on the data and backup situation, it may be worth a try, the free trial should show if it can recover anything.Something Changed!It shows that one of the harddrives is unaviable.I looked at the provided link and if I understand it correctly my data is lost.root@Okabe:~# losetup -f --offset 1048576 /dev/sdcroot@Okabe:~# losetup -f --offset 1048576 /dev/sddroot@Okabe:~# losetup -f --offset 1048576 /dev/sderoot@Okabe:~# zpool import pool: cache id: 11273674506066081776 state: ONLINEstatus: Some supported features are not enabled on the pool. (Note that they may be intentionally disabled if the 'compatibility' property is set.)action: The pool can be imported using its name or numeric identifier, though some features will not be available without an explicit 'zpool upgrade'.config: cache ONLINE sdb1 ONLINE pool: zfs id: 15202079825433258580 state: FAULTEDstatus: One or more devices contains corrupted data.action: The pool cannot be imported due to damaged devices or data. The pool may be active on another system, but can be imported using the '-f' flag. see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-5Econfig: zfs FAULTED corrupted data raidz1-0 DEGRADED loop15 ONLINE loop16 ONLINE ata-WDC_WD160EDGZ-11B2DA0_2CKUTT7J UNAVAIL
December 31, 2025Dec 31 Community Expert If two devices are online, the pool should be recoverable. I missed the corrupted data part. but post the output of losetup to confirm the current loop devices.
December 31, 2025Dec 31 Author 8 minutes ago, JorgeB said:If two devices are online, the pool should be recoverable. I missed the corrupted data part. but post the output of losetup to confirm the current loop devices.root@Okabe:~# losetupNAME SIZELIMIT OFFSET AUTOCLEAR RO BACK-FILE DIO LOG-SEC/dev/loop1 0 0 1 1 /boot/bzmodules 0 512/dev/loop8 0 32768 0 0 /dev/sdc 0 512/dev/loop15 0 1048576 0 0 /dev/sdd 0 512/dev/loop6 0 32768 0 0 /dev/sdd 0 512/dev/loop13 0 65536 0 0 /dev/sde 0 512/dev/loop4 0 32768 0 0 /dev/sde 0 512/dev/loop11 0 65536 0 0 /dev/sdc 0 512/dev/loop2 0 32768 0 0 /dev/sdc 0 512/dev/loop0 0 0 1 1 /boot/bzfirmware 0 512/dev/loop9 0 32768 0 0 /dev/sdd 0 512/dev/loop16 0 1048576 0 0 /dev/sde 0 512/dev/loop7 0 32768 0 0 /dev/sde 0 512/dev/loop14 0 1048576 0 0 /dev/sdc 0 512/dev/loop5 0 32768 0 0 /dev/sdc 0 512/dev/loop12 0 65536 0 0 /dev/sdd 0 512/dev/loop3 0 32768 0 0 /dev/sdd 0 512/dev/loop10 0 32768 0 0 /dev/sde 0 512
December 31, 2025Dec 31 Community Expert 2 minutes ago, Cookio said:/dev/loop14 0 1048576 0 0 /dev/sdc 0 512OK, just wanted to confirm this disk was present as a loop device with the same sector.So whatever happened did more than just delete the partitions; it erased the labels from sdc and looks like it also corrupted more stuff on the other disks, pool will likely fail to import, but it won't hurt to try:zpool import -F -o readonly=on zfsIf it shows an error, post the output fromtail -n 100 /proc/spl/kstat/zfs/dbgmsg
December 31, 2025Dec 31 Author 1 minute ago, JorgeB said:OK, just wanted to confirm this disk was present as a loop device with the same sector.So whatever happened did more than just delete the partitions; it erased the labels from sdc and looks like it also corrupted more stuff on the other disks, pool will likely fail to import, but it won't hurt to try:zpool import -F -o readonly=on zfsIf it shows an error, post the output fromtail -n 100 /proc/spl/kstat/zfs/dbgmsgroot@Okabe:~# zpool import -F -o readonly=on zfscannot import 'zfs': one or more devices is currently unavailableroot@Okabe:~# tail -n 100 /proc/spl/kstat/zfs/dbgmsg1767190044 ffff88810687e300 spa_misc.c:2405:spa_import_progress_set_notes_impl(): 'cache' Verifying pool data1767190044 ffff88810687e300 spa_misc.c:2405:spa_import_progress_set_notes_impl(): 'cache' Calculating deflated space1767190044 ffff88810687e300 spa_misc.c:2405:spa_import_progress_set_notes_impl(): 'cache' Starting import1767190044 ffff88810687e300 spa.c:9320:spa_async_request(): spa=$import-ffff88810687e300-cache async request task=20481767190044 ffff88810687e300 spa_misc.c:430:spa_load_note(): spa_load($import-ffff88810687e300-cache, config trusted): LOADED1767190044 ffff88810687e300 spa_misc.c:430:spa_load_note(): spa_load($import-ffff88810687e300-cache, config trusted): UNLOADING1767190044 ffff88810687e300 metaslab.c:1703:spa_set_allocator(): spa allocator: dynamic1767190044 ffff88810687e300 spa.c:6921:spa_tryimport(): spa_tryimport: importing zfs1767190044 ffff88810687e300 spa_misc.c:430:spa_load_note(): spa_load($import-ffff88810687e300-zfs, config trusted): LOADING1767190044 ffff888101540000 vdev.c:184:vdev_dbgmsg(): disk vdev '/dev/loop15': probe done, cant_read=0 cant_write=11767190044 ffff888101540000 vdev.c:184:vdev_dbgmsg(): disk vdev '/dev/loop16': probe done, cant_read=0 cant_write=11767190045 ffff888161670000 vdev.c:184:vdev_dbgmsg(): disk vdev '/dev/disk/by-id/ata-WDC_WD160EDGZ-11B2DA0_2CKUTT7J-part1': open error=2 timeout=1000092898/10000000001767190045 ffff88810687e300 vdev.c:184:vdev_dbgmsg(): disk vdev '/dev/loop15': best uberblock found for spa $import-ffff88810687e300-zfs. txg 17011767190045 ffff88810687e300 spa_misc.c:430:spa_load_note(): spa_load($import-ffff88810687e300-zfs, config untrusted): using uberblock with txg=17011767190045 ffff88810687e300 spa_misc.c:416:spa_load_failed(): spa_load($import-ffff88810687e300-zfs, config untrusted): FAILED: couldn't get 'config' value in MOS directory [error=52]1767190045 ffff88810687e300 spa_misc.c:430:spa_load_note(): spa_load($import-ffff88810687e300-zfs, config untrusted): UNLOADING1767192370 ffff8881719fd280 metaslab.c:1703:spa_set_allocator(): spa allocator: dynamic1767192370 ffff8881719fd280 spa.c:6921:spa_tryimport(): spa_tryimport: importing zfs1767192370 ffff8881719fd280 spa_misc.c:430:spa_load_note(): spa_load($import-ffff8881719fd280-zfs, config trusted): LOADING1767192370 ffff8881433ad280 vdev.c:184:vdev_dbgmsg(): disk vdev '/dev/loop15': probe done, cant_read=0 cant_write=11767192370 ffff8881433ad280 vdev.c:184:vdev_dbgmsg(): disk vdev '/dev/loop16': probe done, cant_read=0 cant_write=11767192371 ffff888100c01080 vdev.c:184:vdev_dbgmsg(): disk vdev '/dev/disk/by-id/ata-WDC_WD160EDGZ-11B2DA0_2CKUTT7J-part1': open error=2 timeout=1002851272/10000000001767192371 ffff8881719fd280 vdev.c:184:vdev_dbgmsg(): disk vdev '/dev/loop15': best uberblock found for spa $import-ffff8881719fd280-zfs. txg 17011767192371 ffff8881719fd280 spa_misc.c:430:spa_load_note(): spa_load($import-ffff8881719fd280-zfs, config untrusted): using uberblock with txg=17011767192371 ffff8881719fd280 spa_misc.c:416:spa_load_failed(): spa_load($import-ffff8881719fd280-zfs, config untrusted): FAILED: couldn't get 'config' value in MOS directory [error=52]1767192371 ffff8881719fd280 spa_misc.c:430:spa_load_note(): spa_load($import-ffff8881719fd280-zfs, config untrusted): UNLOADING1767192371 ffff8881719fd280 metaslab.c:1703:spa_set_allocator(): spa allocator: dynamic1767192371 ffff8881719fd280 spa.c:6768:spa_import(): spa_import: importing zfs, max_txg=-1 (RECOVERY MODE)1767192371 ffff8881719fd280 spa_misc.c:430:spa_load_note(): spa_load(zfs, config trusted): LOADING1767192371 ffff888165135280 vdev.c:184:vdev_dbgmsg(): disk vdev '/dev/loop15': probe done, cant_read=0 cant_write=11767192371 ffff888165135280 vdev.c:184:vdev_dbgmsg(): disk vdev '/dev/loop16': probe done, cant_read=0 cant_write=11767192372 ffff8883a6bc0000 vdev.c:184:vdev_dbgmsg(): disk vdev '/dev/disk/by-id/ata-WDC_WD160EDGZ-11B2DA0_2CKUTT7J-part1': open error=2 timeout=1000461701/10000000001767192372 ffff8881719fd280 vdev.c:184:vdev_dbgmsg(): disk vdev '/dev/loop15': best uberblock found for spa zfs. txg 17011767192372 ffff8881719fd280 spa_misc.c:430:spa_load_note(): spa_load(zfs, config untrusted): using uberblock with txg=17011767192372 ffff8881719fd280 spa_misc.c:416:spa_load_failed(): spa_load(zfs, config untrusted): FAILED: couldn't get 'config' value in MOS directory [error=52]1767192372 ffff8881719fd280 spa_misc.c:430:spa_load_note(): spa_load(zfs, config untrusted): UNLOADING1767192372 ffff8881719fd280 spa_misc.c:430:spa_load_note(): spa_load(zfs, config untrusted): spa_load_retry: rewind, max txg: 17001767192372 ffff8881719fd280 spa_misc.c:430:spa_load_note(): spa_load(zfs, config untrusted): LOADING1767192372 ffff8881089db180 vdev.c:184:vdev_dbgmsg(): disk vdev '/dev/loop16': probe done, cant_read=0 cant_write=11767192372 ffff8881089db180 vdev.c:184:vdev_dbgmsg(): disk vdev '/dev/loop15': probe done, cant_read=0 cant_write=11767192373 ffff88810152e300 vdev.c:184:vdev_dbgmsg(): disk vdev '/dev/disk/by-id/ata-WDC_WD160EDGZ-11B2DA0_2CKUTT7J-part1': open error=2 timeout=1003017133/10000000001767192373 ffff8881719fd280 vdev.c:184:vdev_dbgmsg(): disk vdev '/dev/loop15': best uberblock found for spa zfs. txg 17001767192373 ffff8881719fd280 vdev.c:184:vdev_dbgmsg(): disk vdev '/dev/loop15': label discarded as txg is too large (1701 > 1700)1767192373 ffff8881719fd280 vdev.c:184:vdev_dbgmsg(): disk vdev '/dev/loop15': failed to read label config1767192373 ffff8881719fd280 spa_misc.c:430:spa_load_note(): spa_load(zfs, config untrusted): using uberblock with txg=17001767192373 ffff8881719fd280 spa_misc.c:416:spa_load_failed(): spa_load(zfs, config untrusted): FAILED: label config unavailable1767192373 ffff8881719fd280 spa_misc.c:430:spa_load_note(): spa_load(zfs, config untrusted): UNLOADING1767192373 ffff8881719fd280 spa_misc.c:430:spa_load_note(): spa_load(zfs, config untrusted): spa_load_retry: rewind, max txg: 16991767192373 ffff8881719fd280 spa_misc.c:430:spa_load_note(): spa_load(zfs, config untrusted): LOADING1767192373 ffff88810871a100 vdev.c:184:vdev_dbgmsg(): disk vdev '/dev/loop15': probe done, cant_read=0 cant_write=11767192373 ffff88810871a100 vdev.c:184:vdev_dbgmsg(): disk vdev '/dev/loop16': probe done, cant_read=0 cant_write=11767192374 ffff8881514bd280 vdev.c:184:vdev_dbgmsg(): disk vdev '/dev/disk/by-id/ata-WDC_WD160EDGZ-11B2DA0_2CKUTT7J-part1': open error=2 timeout=1000873254/10000000001767192374 ffff8881719fd280 vdev.c:184:vdev_dbgmsg(): disk vdev '/dev/loop15': best uberblock found for spa zfs. txg 16981767192374 ffff8881719fd280 vdev.c:184:vdev_dbgmsg(): disk vdev '/dev/loop15': label discarded as txg is too large (1701 > 1698)1767192374 ffff8881719fd280 vdev.c:184:vdev_dbgmsg(): disk vdev '/dev/loop15': failed to read label config1767192374 ffff8881719fd280 spa_misc.c:430:spa_load_note(): spa_load(zfs, config untrusted): using uberblock with txg=16981767192374 ffff8881719fd280 spa_misc.c:416:spa_load_failed(): spa_load(zfs, config untrusted): FAILED: label config unavailable1767192374 ffff8881719fd280 spa_misc.c:430:spa_load_note(): spa_load(zfs, config untrusted): UNLOADING1767192387 ffff8881719f9080 metaslab.c:1703:spa_set_allocator(): spa allocator: dynamic1767192387 ffff8881719f9080 spa.c:6921:spa_tryimport(): spa_tryimport: importing zfs1767192387 ffff8881719f9080 spa_misc.c:430:spa_load_note(): spa_load($import-ffff8881719f9080-zfs, config trusted): LOADING1767192387 ffff888107dd0000 vdev.c:184:vdev_dbgmsg(): disk vdev '/dev/loop16': probe done, cant_read=0 cant_write=11767192387 ffff888107dd0000 vdev.c:184:vdev_dbgmsg(): disk vdev '/dev/loop15': probe done, cant_read=0 cant_write=11767192388 ffff888101540000 vdev.c:184:vdev_dbgmsg(): disk vdev '/dev/disk/by-id/ata-WDC_WD160EDGZ-11B2DA0_2CKUTT7J-part1': open error=2 timeout=1000621421/10000000001767192388 ffff8881719f9080 vdev.c:184:vdev_dbgmsg(): disk vdev '/dev/loop15': best uberblock found for spa $import-ffff8881719f9080-zfs. txg 17011767192388 ffff8881719f9080 spa_misc.c:430:spa_load_note(): spa_load($import-ffff8881719f9080-zfs, config untrusted): using uberblock with txg=17011767192388 ffff8881719f9080 spa_misc.c:416:spa_load_failed(): spa_load($import-ffff8881719f9080-zfs, config untrusted): FAILED: couldn't get 'config' value in MOS directory [error=52]1767192388 ffff8881719f9080 spa_misc.c:430:spa_load_note(): spa_load($import-ffff8881719f9080-zfs, config untrusted): UNLOADING1767192388 ffff8881719f9080 metaslab.c:1703:spa_set_allocator(): spa allocator: dynamic1767192388 ffff8881719f9080 spa.c:6768:spa_import(): spa_import: importing zfs, max_txg=-1 (RECOVERY MODE)1767192388 ffff8881719f9080 spa_misc.c:430:spa_load_note(): spa_load(zfs, config trusted): LOADING1767192388 ffff888100c55280 vdev.c:184:vdev_dbgmsg(): disk vdev '/dev/loop16': probe done, cant_read=0 cant_write=11767192388 ffff888100c55280 vdev.c:184:vdev_dbgmsg(): disk vdev '/dev/loop15': probe done, cant_read=0 cant_write=11767192389 ffff8881009eb180 vdev.c:184:vdev_dbgmsg(): disk vdev '/dev/disk/by-id/ata-WDC_WD160EDGZ-11B2DA0_2CKUTT7J-part1': open error=2 timeout=1001281462/10000000001767192389 ffff8881719f9080 vdev.c:184:vdev_dbgmsg(): disk vdev '/dev/loop15': best uberblock found for spa zfs. txg 17011767192389 ffff8881719f9080 spa_misc.c:430:spa_load_note(): spa_load(zfs, config untrusted): using uberblock with txg=17011767192389 ffff8881719f9080 spa_misc.c:416:spa_load_failed(): spa_load(zfs, config untrusted): FAILED: couldn't get 'config' value in MOS directory [error=52]1767192389 ffff8881719f9080 spa_misc.c:430:spa_load_note(): spa_load(zfs, config untrusted): UNLOADING1767192389 ffff8881719f9080 spa_misc.c:430:spa_load_note(): spa_load(zfs, config untrusted): spa_load_retry: rewind, max txg: 17001767192389 ffff8881719f9080 spa_misc.c:430:spa_load_note(): spa_load(zfs, config untrusted): LOADING1767192389 ffff8883ac3fa100 vdev.c:184:vdev_dbgmsg(): disk vdev '/dev/loop15': probe done, cant_read=0 cant_write=11767192389 ffff8883ac3fa100 vdev.c:184:vdev_dbgmsg(): disk vdev '/dev/loop16': probe done, cant_read=0 cant_write=11767192390 ffff888106f55280 vdev.c:184:vdev_dbgmsg(): disk vdev '/dev/disk/by-id/ata-WDC_WD160EDGZ-11B2DA0_2CKUTT7J-part1': open error=2 timeout=1001363846/10000000001767192390 ffff8881719f9080 vdev.c:184:vdev_dbgmsg(): disk vdev '/dev/loop15': best uberblock found for spa zfs. txg 17001767192390 ffff8881719f9080 vdev.c:184:vdev_dbgmsg(): disk vdev '/dev/loop15': label discarded as txg is too large (1701 > 1700)1767192390 ffff8881719f9080 vdev.c:184:vdev_dbgmsg(): disk vdev '/dev/loop15': failed to read label config1767192390 ffff8881719f9080 spa_misc.c:430:spa_load_note(): spa_load(zfs, config untrusted): using uberblock with txg=17001767192390 ffff8881719f9080 spa_misc.c:416:spa_load_failed(): spa_load(zfs, config untrusted): FAILED: label config unavailable1767192390 ffff8881719f9080 spa_misc.c:430:spa_load_note(): spa_load(zfs, config untrusted): UNLOADING1767192390 ffff8881719f9080 spa_misc.c:430:spa_load_note(): spa_load(zfs, config untrusted): spa_load_retry: rewind, max txg: 16991767192390 ffff8881719f9080 spa_misc.c:430:spa_load_note(): spa_load(zfs, config untrusted): LOADING1767192390 ffff88810871a100 vdev.c:184:vdev_dbgmsg(): disk vdev '/dev/loop15': probe done, cant_read=0 cant_write=11767192390 ffff88810871a100 vdev.c:184:vdev_dbgmsg(): disk vdev '/dev/loop16': probe done, cant_read=0 cant_write=11767192391 ffff8883ac3fe300 vdev.c:184:vdev_dbgmsg(): disk vdev '/dev/disk/by-id/ata-WDC_WD160EDGZ-11B2DA0_2CKUTT7J-part1': open error=2 timeout=1000714637/10000000001767192391 ffff8881719f9080 vdev.c:184:vdev_dbgmsg(): disk vdev '/dev/loop15': best uberblock found for spa zfs. txg 16981767192391 ffff8881719f9080 vdev.c:184:vdev_dbgmsg(): disk vdev '/dev/loop15': label discarded as txg is too large (1701 > 1698)1767192391 ffff8881719f9080 vdev.c:184:vdev_dbgmsg(): disk vdev '/dev/loop15': failed to read label config1767192391 ffff8881719f9080 spa_misc.c:430:spa_load_note(): spa_load(zfs, config untrusted): using uberblock with txg=16981767192391 ffff8881719f9080 spa_misc.c:416:spa_load_failed(): spa_load(zfs, config untrusted): FAILED: label config unavailable1767192391 ffff8881719f9080 spa_misc.c:430:spa_load_note(): spa_load(zfs, config untrusted): UNLOADING
December 31, 2025Dec 31 Community Expert 3 minutes ago, Cookio said:FAILED: label config unavailableYep, I'm afraid the labels are damaged on the other devices as well, so ZFS can't recover.
December 31, 2025Dec 31 Author 6 minutes ago, JorgeB said:Yep, I'm afraid the labels are damaged on the other devices as well, so ZFS can't recover.Alright so I can't get my Data back or is recovery via UFS Explorer still worth a try?
December 31, 2025Dec 31 Community Expert You can try the free trial at least, and then decide if the price is worth it based on what it finds.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.