JorgeB

See here for some recovery options, if successful then format cache.

Strange, it's not trying to remove the missing device, add it back again.

If the drive doesn't show up in Unraid either there's a connection problem or it's failing. This suggest the latter.

Cache filesystem is corrupt, best bet is to backup, re-format and restore the data.

Stop array, unassign cache1, start array, wait a couple of minutes and grab new diags.

Lots of checksum failures, you should run memtest.

Try without -z (compression)

Difficult to say without previous diags, but looks like at least one of the devices was wiped, possibly by trying to re-add it to the pool.

This error is happening to multiple devices: Dec 18 00:38:48 Tower kernel: sd 1:0:4:0: Power-on or device reset occurred This is usually a power/connection problem, if you already checked/replaced cables try with different PSU if available.

Probably caused by this unmount: Dec 18 03:10:27 NNVault rpc.mountd[4373]: authenticated unmount request from 192.168.1.10:708 for /mnt/user/NNVault (/mnt/user/NNVault) Dec 18 03:13:31 NNVault shfs: shfs: ../lib/fuse.c:1451: unlink_node: Assertion `node->nlookup > 1' failed. Dec 20 03:10:25 NNVault rpc.mountd[4465]: authenticated unmount request from 192.168.1.10:732 for /mnt/user/NNVault (/mnt/user/NNVault) Dec 20 03:14:05 NNVault shfs: shfs: ../lib/fuse.c:1451: unlink_node: Assertion `node->nlookup > 1' failed. See if it happens always a few minutes after that.

Checkbox is just an icon, but I see what you mean.

If parity was valid and you check that box it won't be overwritten, good to run a parity check anyway.

Spindown fixes are already coming with rc3, probably best to wait for that and retest.

Click on the thumbs down and select acknowledge.

That's usually a bad SATA cable, replace but if it doesn't fix it please post the diagnostics, could also be a different issue, like a bad LSI firmware.

Btrfs is known to have a higher write amplification, mostly because of being COW and checksummed, it can reach 25x IIRC, there's a study about that.

Instead of rebooting try stopping the dockers one by to see if you find the culprit, but it does look like it's Plex.

Yes to both.

Looks more like a connection problem, replace/swap both cables on disk7.

Should be enough.

Looking at the syslog it appears that the pool was not redundant (possible due to a bug if it was created on v6.7) and one of the devices is missing/wiped, so difficult to recover any data.

No balance found just means no balance is running at the moment, i.e., the normal status, and when you upgrade to v6.9 it will report correct usage stats.

This looks like an ECC memory error, IPMI/system event log might have more info.

Changed Status to Closed Changed Priority to Other

This is a general support issue, please continue here: