Scrub didn't clear the error?

[ISJ]

Hello,

I have an "Online" volume with the status:
One or more devices has experienced an error resulting in data corruption. Applications may be affected.

I deleted the file (I dont care about it) and ran the following command to scrub the pool, it completed but there is no change to the status.
zpool scrub DiskArray-4TB

This is the result:

Code:

  pool: DiskArray-4TB
 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: http://illumos.org/msg/ZFS-8000-8A
  scan: scrub repaired 0 in 0 days 12:01:59 with 0 errors on Tue Jan 12 04:24:28 2021
config:

        NAME                                            STATE     READ WRITE CKSUM
        DiskArray-4TB                                   ONLINE       0     0     0
          raidz1-0                                      ONLINE       0     0     0
            gptid/f15eb26b-603e-11ea-88cd-0015173f9cdd  ONLINE       0     0     0
            gptid/f328a231-603e-11ea-88cd-0015173f9cdd  ONLINE       0     0     0
            gptid/f41570bf-603e-11ea-88cd-0015173f9cdd  ONLINE       0     0     0
            gptid/f4f4e3fa-603e-11ea-88cd-0015173f9cdd  ONLINE       0     0     0
            gptid/f5cf106a-603e-11ea-88cd-0015173f9cdd  ONLINE       0     0     0
            gptid/f7324f80-603e-11ea-88cd-0015173f9cdd  ONLINE       0     0     0
            gptid/f8bc0c4a-603e-11ea-88cd-0015173f9cdd  ONLINE       0     0     0
            gptid/fa73b0e0-603e-11ea-88cd-0015173f9cdd  ONLINE       0     0     0
            gptid/fc3eca0c-603e-11ea-88cd-0015173f9cdd  ONLINE       0     0     0
            gptid/fdea4c34-603e-11ea-88cd-0015173f9cdd  ONLINE       0     0     0
        cache
          gptid/c078b438-cb99-11ea-9eba-0015173f9cdd    ONLINE       0     0     0

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

        DiskArray-4TB/NextCloud:<0x563a>

  pool: freenas-boot
 state: ONLINE
  scan: scrub repaired 0 in 0 days 00:00:08 with 0 errors on Tue Jan 12 03:45:08 2021
config:

        NAME        STATE     READ WRITE CKSUM
        freenas-boot  ONLINE       0     0     0
          ada1p2    ONLINE       0     0     0

errors: No known data errors

I've ran the commands required ( I thought ) to correct this issue but it persists. Any ideas?

Thanks!

 

[Chris Moore]

Usually, if there is a problem with the pool where data was corrupted, there is a cause.
Sometimes that cause may be a faulty disk.
Have you checked the health of your disk drives?

 

[ISJ]

Good idea, I did check the smartctl data and didn't see any failures or CRC counts over 0. All the drives are low hour count but not so low that were likely looking ta at a cradle death.

I appreciate your thoughts on this im sort of lost on next steps. The file thats indicated now is not addressable so.

 

[Samuel Tai]

The error is in the Nextcloud plugin's metadata. You could try destroying that plugin, rescrubbing, and then recreating the plugin.

 

[Dan Tudora]

hello
raidZ1 with 10 (ten) hdd
be serious

 

[Samuel Tai]

raidZ1 with 10 (ten) hdd
be serious

@Dan Tudora, please be less sarcastic. I agree this pool isn't laid out optimally, but I would offer specific recommendations; i.e., rebuilding it as RAIDZ2, to enable it to survive the loss of 2 drives instead of having no safety net with RAIDZ1.

 

[Dan Tudora]

hello
sarcastic is MY second name (in IT and data security, sorry)
let's help this user and forget that
greets

 

[Dan Tudora]

welcome back
is some lack without you
just dig in

 

[Samuel Tai]

Thanks. I was busy at work for a time.

 

[Dan Tudora]

helo
do goooooood something at yours work
I am glead to heAR that
becouse what what WE do count
I HOPE

 

[Dan Tudora]

hello
shutdown system
think
think again
read documnetation (I fave not rhtigth to say F*** doc

I appreciate your thoughts on this im sort of lost on next steps. The file thats indicated now is not addressable so.

 

[Dan Tudora]

hello
something for OP ??
please help !!

 

[Samuel Tai]

@Dan Tudora, see my post #4 in this thread.

 

[ISJ]

@Dan Tudora
Troll less hard off the bat, it's less obvious and you'll get people to actually bite. RAID5 for home use is fine, you don't even know my backup methods lol

@Samuel Tai
Thanks unfortunately I don't see that file on the drive. This also appeared after deleting the previous file. Is this perhaps some sort of garbage file? I've never seen anything like it.

 

[ISJ]

Here's a SS of a LS command, I dont have any NextCloud plugins removable without breaking it.

 

[ISJ]

This was the original screen:

 

[ISJ]

This was what I did to correct the file issue:

 

[Samuel Tai]

OK, if you've already deleted the file, try rescrubbing the pool again. If you have snapshots that refer to the deleted file, you should delete those too. Once there are no more references to the corrupt file, scrub your pool again. It may take multiple scrubs before ZFS is happy again.

 

[ISJ]

@Samuel Tai It looks like it relates to this sir: https://utcc.utoronto.ca/~cks/space/blog/solaris/ZFSPermanentErrorsMeaning

I'll do as you say however it takes al most a day to scrub so I want to be sure.

 

[ISJ]

Looks like a second scan will clear it as you said sir.

EDIT: You did mean "zfs scrub {PoolName}" yes?