Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Removing Corrupted Files from Pool (ZFS-8000-8A)

Featured Replies

Hi,

 

I was running some disk parity checks and a new found disk scrub, when I found that I had couple corrupted files in the pool, most likely from forced shutdowns.

 

I haven't lost any critical data, but I would like the corrupted files to be removed so I can restore the files properly.

 

I've went into the web terminal and used

zpool status -xv

to find out which files were corrupted, and removed them via terminal.

 

However, there are couple of files that does not have directories, such as /mnt/cache/blahblahblah, but is instead formatted as such;

cache/appdata:<0x3c324>

 

 

I'm assuming this is a bad sector or something on the drive itself? If not what is it?

 

And are there any guidelines on removing this?

 

I looked at https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-8A/ to find out what I can do, but it says if the file metadata is corrupt, it cannot be removed. Is this what this is?

 

Any insight would be helpful.

 

Thanks!

 

P.S.

The result of zpool stat -xv after removing valid directories/ files;

zpool status -xv
  pool: cache
 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 00:08:57 with 16 errors on Thu Oct 24 02:52:31 2024
config:

        NAME         STATE     READ WRITE CKSUM
        cache        ONLINE       0     0     0
          nvme0n1p1  ONLINE       0     0    16
          nvme1n1p1  ONLINE       0     0     2

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

        cache/appdata:<0x3c324>
        cache/appdata:<0x3d2c0>
        cache/system:<0x80>
        cache/Backups:<0x3bf00>
        cache/Backups:<0x48902>
        cache/Backups:<0x37704>
        cache/Backups:<0x4df0a>
        cache/Backups:<0x3770c>
        cache/Backups:<0x4860c>
        cache/Backups:<0x3bd0c>
        cache/Backups:<0x4df0c>
        cache/Backups:<0x37712>
        cache/Backups:<0x37714>
        cache/Backups:<0x37716>
        cache/Backups:<0x3761e>
        cache/Backups:<0x37622>
        cache/Backups:<0x3bc32>
        cache/Backups:<0x3bd3c>
        cache/Backups:<0x3753e>
        cache/Backups:<0x44a44>
        cache/Backups:<0x3bc56>
        cache/Backups:<0x37462>
        cache/Backups:<0x3bc62>
        cache/Backups:<0x48a6e>
        cache/Backups:<0x3ba70>
        cache/Backups:<0x43172>
        cache/Backups:<0x48572>
        cache/Backups:<0x3b87c>
        cache/Backups:<0x37686>
        cache/Backups:<0x3be88>
        cache/Backups:<0x3be8e>
        cache/Backups:<0x44b92>
        cache/Backups:<0x4dd9e>
        cache/Backups:<0x3bda0>
        cache/Backups:<0x373a2>
        cache/Backups:<0x3bfa2>
        cache/Backups:<0x373a6>
        cache/Backups:<0x3bcaa>
        cache/Backups:<0x4dcac>
        cache/Backups:<0x3bcae>
        cache/Backups:<0x48cb2>
        cache/Backups:<0x375c0>
        cache/Backups:<0x434ce>
        cache/Backups:<0x374dc>
        cache/Backups:<0x485e2>
        cache/Backups:<0x373e8>
        cache/Backups:<0x48bea>
        cache/Backups:<0x3bbec>
        cache/Backups:<0x45af0>
        cache/Media:<0x358>
        cache/Downloads:<0x500>
        cache/Downloads:<0x910>
        cache/Downloads:<0x214>
        cache/Downloads:<0x42a>
        cache/Downloads:<0x33e>
        cache/Downloads:<0x25c>
        cache/Downloads:<0x662>
        cache/Downloads:<0x58a>
        cache/Downloads:<0x89c>
        cache/Downloads:<0x8a0>
        cache/Downloads:<0x8ac>
        cache/Downloads:<0x2da>
        cache/Downloads:<0x5e0>
        cache/Downloads:<0x5ec>

  pool: disk2
 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 23:17:31 with 13 errors on Fri Oct 25 01:59:28 2024
config:

        NAME        STATE     READ WRITE CKSUM
        disk2       ONLINE       0     0     0
          md2p1     ONLINE       0     0     0

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

        disk2/Backups:<0x1c00a>
        disk2/Backups:<0x1bf1a>
        disk2/Backups:<0x1bf24>
        disk2/Backups:<0x1c084>
        disk2/Backups:<0x1e4e4>
        disk2:<0x3e90>
        disk2:<0x3db2>

 

  • Community Expert
15 hours ago, clambake-stolid said:

most likely from forced shutdowns.

That should not cause data corruption.

 

15 hours ago, clambake-stolid said:

but is instead formatted as such;

cache/appdata:<0x3c324>

This usually means metadata corruption, or artifacts from snapshots, try deleting them if they exist, and run a couple of scrubs, if the errors remain recommend recreating the pools.

 

Also, since there are multiple pools detecting data corruption, would recommend running memtest first.

 

  • Author

Well, by forced shutdowns I mean yanking the power cable lol

 

How would I delete said metadata corruption or snapshot artifacts?

 

Also, I do believe I have found the cause of the problem... Which is sad as this stick is less than a year old...

 

 

[27.10.2024 15:15:20 CET] /usr/bin/memtester 12G 5
=============================================================================================

memtester version 4.6.0 (64-bit)
adapted for use on Unraid installations

Copyright (C) 2001-2020 Charles Cazabon
Copyright (C) 2024 desertwitch (modifications for Unraid)

THIS PROGRAM IS PROVIDED AS IS AND WITHOUT ANY WARRANTIES
It is licensed under GNU General Public License Version 2

pagesize is 4096
pagesizemask is 0xfffffffffffff000
want 12288MB (12884901888 bytes)
got  12288MB (12884901888 bytes), trying mlock ...locked.

Loop 1/5:
  Stuck Address            : Testing...           failed
  Random Value             : Testing...           failed
  Compare XOR              : Testing...           failed
  Compare SUB              : Testing...           failed
  Compare MUL              : Testing...           failed
  Compare DIV              : Testing...           failed
  Compare OR               : Testing...           failed
  Compare AND              : Testing...           failed
  Sequential Increment     : Testing...           failed
  Solid Bits               : Testing...           failed
  Block Sequential         : Testing...           failed
  Checkerboard             : Testing...           failed
  Bit Spread               : Testing...           failed
  Bit Flip                 : Testing...           failed
  Walking Ones             : Testing...           failed
  Walking Zeroes           : Testing...           failed
  8-bit Writes             : Testing...           failed
  16-bit Writes            : Testing...           failed

Loop 2/5:
  Stuck Address            : Testing...           failed
  Random Value             : Testing...           
=============================================================================================
[27.10.2024 15:18:49 CET] The operation was interrupted and has not finished.
[27.10.2024 15:18:49 CET] Code: SIGTERM - Program Interrupt.

 

  • Community Expert
38 minutes ago, clambake-stolid said:

How would I delete said metadata corruption

If it's the metadata and it doesn't go away with a couple of scrubs after resolving the RAM issue, you will need to re-format and recreate the pool

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.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.