Pool unhealthy due to corrupt files but they cannot be found

TrueNAS General
1

I have used both find and locate commands but they cannot find the two effected files. Since they are part of the old 11.3 install is there a way to just remove that release?

I would like to get this resolved as I’ve been at the rebuild of this server for two weeks. What I don’t understand is that zpool -v does find the two files but nothing else can.

root@Nero[~]# zpool status -v alldrives
  pool: alldrives
 state: ONLINE
status: One or more devices has experienced an error resulting in data
        corruption.  Applications may be affected.
action: Restore the file in question if possible.  Otherwise restore the
        entire pool from backup.
   see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-8A
  scan: scrub repaired 0B in 02:16:59 with 4 errors on Thu Apr  2 05:17:33 2026
config:

        NAME                                            STATE     READ WRITE CKSUM
        alldrives                                       ONLINE       0     0     0
          raidz2-0                                      ONLINE       0     0     0
            gptid/ef8ac90c-1efe-11f1-925d-0cc47a7cbb70  ONLINE       0     0     0
            gptid/069d66a6-11c8-11f1-be2d-0cc47a7cbb70  ONLINE       0     0     0
            gptid/384c1f28-11e3-11f1-83d0-0cc47a7cbb70  ONLINE       0     0     0
            gptid/db39a70c-1349-11f1-b7d5-0cc47a7cbb70  ONLINE       0     0     0
            gptid/f72710b1-131d-11f1-9dd9-0cc47a7cbb70  ONLINE       0     0     0
            gptid/60a796c4-1335-11f1-929a-0cc47a7cbb70  ONLINE       0     0     0

errors: Permanent errors have been detected in the following files:

        alldrives/iocage/jails/emby/root@ioc_update_11.3-RELEASE-p14_2021-01-17_15-10-25:/var/db/emby-server/cache/images/resized-images/1/1776ef53-427d-0d87-6051-eb205972ae22.webp
        alldrives/iocage/jails/emby/root@ioc_update_11.3-RELEASE-p14_2021-01-01_07-41-13:/var/db/emby-server/logs/embyserver-63745056000.txt
root@Nero[~]#

Thanks

2

That’s not surprising; they’re in a snapshot, which neither of those tools would ordinarily search (and I don’t think the slocate database is updated on any kind of regular basis on TrueNAS in any event). Given that those snapshots are over five years old, they can probably be safely destroyed.

3 Likes
3

What timing! I was just reading something suggesting they might be in a snapshot.

I agree, I don’t need snapshots that old and I would not be able to do anything with them anyway.

I’ll report back.

4

I cant thank you enough! I removed snapshots and did a scrub.

root@Nero[~]# zpool status -v
  pool: alldrives
 state: ONLINE
status: Some supported and requested features are not enabled on the pool.
        The pool can still be used, but some features are unavailable.
action: Enable all features using 'zpool upgrade'. Once this is done,
        the pool may no longer be accessible by software that does not support
        the features. See zpool-features(7) for details.
  scan: scrub repaired 0B in 01:27:29 with 0 errors on Fri Apr 17 10:46:32 2026
config:

        NAME                                            STATE     READ WRITE CKS                                                                                                             UM
        alldrives                                       ONLINE       0     0                                                                                                                  0
          raidz2-0                                      ONLINE       0     0                                                                                                                  0
            gptid/ef8ac90c-1efe-11f1-925d-0cc47a7cbb70  ONLINE       0     0                                                                                                                  0
            gptid/069d66a6-11c8-11f1-be2d-0cc47a7cbb70  ONLINE       0     0                                                                                                                  0
            gptid/384c1f28-11e3-11f1-83d0-0cc47a7cbb70  ONLINE       0     0                                                                                                                  0
            gptid/db39a70c-1349-11f1-b7d5-0cc47a7cbb70  ONLINE       0     0                                                                                                                  0
            gptid/f72710b1-131d-11f1-9dd9-0cc47a7cbb70  ONLINE       0     0                                                                                                                  0
            gptid/60a796c4-1335-11f1-929a-0cc47a7cbb70  ONLINE       0     0                                                                                                                  0

errors: No known data errors

  pool: boot-pool
 state: ONLINE
  scan: scrub repaired 0B in 00:00:04 with 0 errors on Fri Apr 17 03:45:04 2026
config:

        NAME        STATE     READ WRITE CKSUM
        boot-pool   ONLINE       0     0     0
          mirror-0  ONLINE       0     0     0
            da5p2   ONLINE       0     0     0
            da7p2   ONLINE       0     0     0

errors: No known data errors

It’s been eight months since my house fire (everything was running when the wires in the attic melted down, and then everything got hosed down, then everything got knocked down). But I feel lucky that some corrupt files was (to this point) the worst of it. I still have my desktop, Linux box and a guest computer to rebuild. Saving my Synology backup boxes was the first thing to happen.

Thanks again, I do make a great effort to figure it out myself and I have learned something.

5

Completely off topic@ locacoyote: Is your sig accurate re: the mirrored SSD storage capacity?

6

Thanks for the heads up. I’ll get that fixed.