zpool status -v -> Permanent errors have been detected

[Nordlicht-13]

My Truenas scale shows me that the ZFS is not healthy:

When I run zpool status -v in the shell, I get this:

root@truenas[~]# zpool status -v
pool: boot-pool
state: ONLINE
config:

NAME STATE READ WRITE CKSUM
boot-pool ONLINE 0 0 0
sda3 ONLINE 0 0 0

errors: No known data errors

pool: diskpool-1
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 09:45:46 with 0 errors on Wed Mar 6 21:01:28 2024
config:

NAME STATE READ WRITE CKSUM
diskpool-1 ONLINE 0 0 0
mirror-0 ONLINE 0 0 0
sdd2 ONLINE 0 0 0
sde2 ONLINE 0 0 0

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

diskpool-1/plexmedia:<0x6118c>
diskpool-1/plexmedia:<0x61097>
diskpool-1/plexmedia:<0x610a8>
diskpool-1/plexmedia:<0x610ca>
<0x20e5>:<0x809f>
root@truenas[~]#

those errors are leftovers from corrupted files that I deleted.
How can I get rid of these errors, back to a healthy ZFS again?

 

[NickF]

Do
Zpool scrub diskpool-1

You can check its progress by zpool status like above. When the scrub completes if the old removed files are still present you can do

Zpool clear diskpool-1

A bit of additional backstory on these files may also be relevant, this typically happens for good reason. Did you have a hardware failure of some kind?

 

[Nordlicht-13]

Thanks for reply.
I already did a scrub and clear of the pool.
Originally the zpool status showed some jpg and mp3 files that had errors.
I deleted those files and did the scrub and clear, but can`t get rid
of those errors.

Do I have to move everything to another pool and back to get it straight again?
dikpool-1 is on a mirror set with two WD Red 4TB.
I have two more 4 TB in the NAS that are not assigned jet.

 

[Nordlicht-13]

Now I added a second pool.
diskpool-1 uses sdd2 and sde2 as shown.
diskpool-2 uses sdb2 and sdc2 shown as
6c5d0819-6cb3-4f2f-b479-c772b9df0984 and
6f0dce8e-1f0d-4269-b0ea-c06652dfa817

root@truenas[~]# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 465.8G 0 disk
├─sda1 8:1 0 1M 0 part
├─sda2 8:2 0 512M 0 part
├─sda3 8:3 0 32G 0 part
└─sda4 8:4 0 16G 0 part
└─sda4 253:0 0 16G 0 crypt [SWAP]
sdb 8:16 0 3.6T 0 disk
└─sdb1 8:17 0 3.6T 0 part
sdc 8:32 0 3.6T 0 disk
└─sdc1 8:33 0 3.6T 0 part
sdd 8:48 0 3.6T 0 disk
├─sdd1 8:49 0 8G 0 part
└─sdd2 8:50 0 3.6T 0 part
sde 8:64 0 3.6T 0 disk
├─sde1 8:65 0 8G 0 part
└─sde2 8:66 0 3.6T 0 part
root@truenas[~]#

Code:

  pool: diskpool-1
 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 09:45:46 with 0 errors on Wed Mar  6 21:01:28 2024
config:

        NAME        STATE     READ WRITE CKSUM
        diskpool-1  ONLINE       0     0     0
          mirror-0  ONLINE       0     0     0
            sdd2    ONLINE       0     0     0
            sde2    ONLINE       0     0     0

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

        diskpool-1/plexmedia:<0x6118c>
        diskpool-1/plexmedia:<0x61097>
        diskpool-1/plexmedia:<0x610a8>
        diskpool-1/plexmedia:<0x610ca>
        <0x20e5>:<0x809f>

  pool: diskpool-2
 state: ONLINE
config:

        NAME                                      STATE     READ WRITE CKSUM
        diskpool-2                                ONLINE       0     0     0
          mirror-0                                ONLINE       0     0     0
            6c5d0819-6cb3-4f2f-b479-c772b9df0984  ONLINE       0     0     0
            6f0dce8e-1f0d-4269-b0ea-c06652dfa817  ONLINE       0     0     0

errors: No known data errors

 

[Nordlicht-13]

I moved the pool, now erverything is okay again.
After updating the ZFS of the old pool, the errors like this <0x20e5>:<0x809f> were gone.