Due to bad ram, the drive has some corruption that scrubbing does not help with.

 

I want to get this drive back to a good state but I am not sure how to that while not losing any media on that drive. The parity check had no errors. It's just zfs pool status showing corruption.

 

What steps should I follow?

Post the output of

zpool status -v

 

We have talked about this in other posts as I tried to deal with data corruption from bad RAM. Figured a separate post makes sense since it's now the drive in the array and not the cache / docker setup. Status below. Scrubbing does nothing.

 

There is only one zfs drive in the pool. This drive was meant to only be used for appdata snapshots

 

root@HomeServer:/mnt/cache/system/libvirt# zpool status -v
  pool: apps
 state: ONLINE
config:

	NAME        STATE     READ WRITE CKSUM
	apps        ONLINE       0     0     0
	  sdc1      ONLINE       0     0     0

errors: No known data errors

  pool: cache
 state: ONLINE
config:

	NAME         STATE     READ WRITE CKSUM
	cache        ONLINE       0     0     0
	  nvme0n1p1  ONLINE       0     0     0

errors: No known data errors

  pool: disk3
 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:11:03 with 0 errors on Tue May 21 20:36:29 2024
config:

	NAME        STATE     READ WRITE CKSUM
	disk3       ONLINE       0     0     0
	  md3p1     ONLINE       0     0     0

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

        disk3/movies:<0x18e>

 

Edited May 24, 20242 yr by andyd

There appears to be metadata corruption, would recommend backing up what you can and reformatting that disk.

But what does backing up what you can mean here though? There is media backed by parity. Are you saying that data is potentially problematic as well? That I should back up all data on the drive and delete the data from the array?

Edited May 24, 20242 yr by andyd

You should backup all the data from that disk, you can move to other array disks if there's enough space, then re-format the disk and copy the data back.

 

parity cannot help with filesystem issues.

I get that.

 

What I'm not clear on is if the data needs to be backed up from the array enitrely and then deleted. Then format the failed drive.

 

But based on what you mentioned, it sounds like I don't have to delete fully.

 

1. I backed up what's on there which wasn't a lot anyway 

2. Will turn off array

3. Format the drive

4. Add back the data

5. turn on the array

Edited May 24, 20242 yr by andyd

If by turn off the array you mean stop it, then that's it, to format the disk you can change the filesystem to a different one, then start array and format, stop and change back to zfs if you still want that, and format again.