Saving server but corrupt files brought over from previous drives

TrueNAS General
, ,
1

I’ve been working on restoring my servers and personal computers for months and about half way there. after replacing all 12 drives and 4 ssd i have a problem with one server that says it is “online unhealthy” below is the readout of zpool status -v alldrives
I thought at first that I could remove the old 11.3 which might clear up most of it, but only the most recent installation is listed.

So I’m seeking advice on clearing this up.

 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 01:32:32 with 37 errors on Wed Apr  1 08:31:42 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    74
            gptid/069d66a6-11c8-11f1-be2d-0cc47a7cbb70  ONLINE       0     0    74
            gptid/384c1f28-11e3-11f1-83d0-0cc47a7cbb70  ONLINE       0     0    74
            gptid/db39a70c-1349-11f1-b7d5-0cc47a7cbb70  ONLINE       0     0    74
            gptid/f72710b1-131d-11f1-9dd9-0cc47a7cbb70  ONLINE       0     0    74
            gptid/60a796c4-1335-11f1-929a-0cc47a7cbb70  ONLINE       0     0    74

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
        /var/db/system/configs-ee21f3733ab34d689aed5079e9ac663b/FreeNAS-11.3-U2.1/20201026.db
        /var/db/system/configs-ee21f3733ab34d689aed5079e9ac663b/FreeNAS-11.3-U2.1/20201029.db
        /var/db/system/configs-ee21f3733ab34d689aed5079e9ac663b/FreeNAS-11.3-U2.1/20201102.db
        /var/db/system/configs-ee21f3733ab34d689aed5079e9ac663b/FreeNAS-11.3-U5/20201103.db
        /var/db/system/configs-ee21f3733ab34d689aed5079e9ac663b/FreeNAS-11.3-U5/20201104.db
        /var/db/system/configs-ee21f3733ab34d689aed5079e9ac663b/FreeNAS-11.3-U5/20201109.db
        /var/db/system/configs-ee21f3733ab34d689aed5079e9ac663b/FreeNAS-11.3-U5/20201117.db
        /var/db/system/configs-ee21f3733ab34d689aed5079e9ac663b/FreeNAS-11.3-U5/20201220.db
        /var/db/system/configs-ee21f3733ab34d689aed5079e9ac663b/FreeNAS-11.3-U5/20201221.db
        /var/db/system/configs-ee21f3733ab34d689aed5079e9ac663b/FreeNAS-11.3-U5/20201222.db
        /mnt/alldrives/iocage/jails/emby/root/var/db/emby-server/metadata/people/Louis Koo-tmdb-78875/folder.jpg
        /mnt/alldrives/iocage/jails/emby/root/var/db/emby-server/metadata/people/Philip Keung Ho-Man-tmdb-140478/folder.jpg
        alldrives/iocage/jails/emby/root@ioc_update_11.3-RELEASE-p14_2021-01-01_07-41-13:/var/db/emby-server/logs/embyserver-6374                         5056000.txt
2

You need to:

  1. Delete all the listed files.
  2. After those files are deleted, run zpool clear alldrives
  3. Next run zpool status -v alldrives and verify the errors are cleared. This is not “fixed” yet.
  4. Two more steps, run zpool scrub alldrives
  5. Last step, periodically run zpool status -v alldrives to check the status of the scrub and when it is completed, you should still have no errors listed.

Good Luck.

3

I’m very great full for the help joeschmuck! I thought a manual deletion of the files was the way to go, but wanted to be sure. Considering how deep those files are in the folder tree , does anyone have a recommendation on something that may be a bit easier than putty? I remember I had some sort of ssh file explorer on my desktop but it’s the next one line for repairs and can’t recall the name.

Many thanks!

4

Actually I like WinSCP, if the files are exposed that way, which I doubt. Putty (SSH) may be the way to go. Thankfully it isn’t 100 files.

5

Joeschmuck (or anyone). I was able to delete most of the corrupted files (and winscp is what I was trying to remember been using it for years) however if you look at the first and last lines of the code post you will see they are very long paths and contain an @root. My point is I was not able to find those two files the directory structure stoped somewhere before that @root.