JorgeB

If it's configured as a redundant pool yes, you can post new diags to confirm.

Post the output of btrfs fi show

Once a disk gets disabled it needs to be rebuilt, but first post new diags to see if the ATA errors are gone.

Hmm, error may be caused by the file existing in a different pool, media share is set to use the pool "downloads", but those files are in the pool "server", change the share to use the pool server, other settings should remain the same, and run the mover again.

For both?

One of the NVMe devices dropped offline, power cycle the server, don't just reboot, to see if it comes back and post new diags after array start.

SMART test passed so the disk should be OK for now, keep monitoring, you can also replace/swap cables to rule that out if more errors occur.

Post the output of find /mnt -name 01\ -\ Cannonball.mp3 Search can take some time, wait until you get the cursor back before posting the output

Server is running out of RAM, see if you can fix that first by limiting the RAM to VMs/containers.

One possible explanation would be the first time that bit was wrongly correctly, like from a bit flip, so the second pass would correct it again, but you appear to be using ECC RAM, so that should not happen, possible an issue with one of the devices, run another check when possible to see if more errors are found.

Only one NVMe device is being detected by Linux: 21:00.0 Non-Volatile memory controller [0108]: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983 [144d:a808] Subsystem: Samsung Electronics Co Ltd SSD 970 EVO/PRO [144d:a801] Kernel driver in use: nvme Kernel modules: nvme This is not a software issue, try swapping both NVMe devices and see where the problem follows.

You just need to restore the complete /config folder, from a backup or from the old flash if still readable, then transfer the key.

Please post the diagnostics.

Yes.

Changed Status to Closed Changed Priority to Other

This is a plugin, not part of the OS, please use the existing plugin support thread:

Yes. For the array we recommend xfs for the typical user, if you want checksums/snapshots for the array then I would recommend btrfs over zfs, since there's currently a known write performance issue with zfs (on the array only). Zfs for pools is a good option, and for raid5 is the best option.

There appears to be a problem with the libvirt.img, which is kind of strange since it looks like it's new, also no idea what this is about: Apr 22 21:25:42 Storage root: initializing /etc/libvirt Apr 22 21:25:42 Storage kernel: loop3: detected capacity change from 0 to 6000 Apr 22 21:25:42 Storage kernel: EXT4-fs (loop3): mounted filesystem with ordered data mode. Quota mode: disabled. Apr 22 21:25:42 Storage kernel: ext4 filesystem being mounted at /etc/libvirt- supports timestamps until 2038 (0x7fffffff) Apr 22 21:25:42 Storage kernel: EXT4-fs (loop3): unmounting filesystem. Apr 22 21:25:42 Storage emhttpd: shcmd (1368): /etc/rc.d/rc.libvirt start Never seen libvirt trying to mount an ext4 loop device after mounting the btrfs loop device, no idea what's going on there, but if the image is new try deleting and recreating.

Yep: Apr 21 23:57:09 Serenityv2 kernel: usb 2-6: USB disconnect, device number 2 Apr 21 23:57:09 Serenityv2 kernel: xhci_hcd 0000:00:14.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state. Apr 21 23:57:09 Serenityv2 kernel: usb 2-6: new SuperSpeed USB device number 3 using xhci_hcd Apr 21 23:57:09 Serenityv2 kernel: usb-storage 2-6:1.0: USB Mass Storage device detected Apr 21 23:57:09 Serenityv2 kernel: scsi host32: usb-storage 2-6:1.0 Apr 21 23:57:10 Serenityv2 emhttpd: Unregistered Flash device error (ENOFLASH5) If there aren't any USB 2.0 ports you can try a different flash drive to see if it's any different

You can run an extended SMART test, if it takes at longer than the expected time, and that time is in the SMART report, if suggests a disk problem.

You can enable the syslog server and post that after a crash, but if it's a hardware problem, most likely there won't be anything logged.

It can be, and it's worth running, but keep in mind that memtest is only definitive if it finds errors, since you have multiple sticks you can also try running the server with just one, if the same try with a different one, that will basically rule out bad RAM.

Recommend changing the docker network to ipvlan, if you really need macvlan disable bridging for eth0, more info here: https://docs.unraid.net/unraid-os/release-notes/6.12.4/#fix-for-macvlan-call-traces

No, Unraid cannot mount ntfs, you can keep passing through the device to a VM, or format it with a supported filesystem if you want to use it in a pool.

Recommend doing that ASAP, since at least part of the problem, may have been caused by that.