JorgeB

Check for a support forum/discord link for the Plex container you're using, more likely to get help there:

I believe this only happens if you«re using some app/plugin that requires an updated glibc, i.e., it doesn't happen with stock Unraid.

Like the link explains you just need to go to previous apps section from CA to re-add all the apps.

Delete and recreate the docker image.

Looks like you need to install UD preclear: https://forums.unraid.net/topic/125918-log-pam-unable-to-dlopen/?do=findComment&comment=1147493

I believe updating UD and UD preclear will fix those.

There were some issues with Mellanox NICs but AFAIK all known issues were fixed on v6.10.3, for example this one, NIC is being detected, so not sure why it's not listed in the interface rules, maybe @bonienlcan't take a look to see if anything jumps out.

See if this applies to you, if yes, upgrading to v6.10 and switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enable, top right)), or see below for more info.: https://forums.unraid.net/topic/70529-650-call-traces-when-assigning-ip-address-to-docker-containers/ See also here: https://forums.unraid.net/bug-reports/stable-releases/690691-kernel-panic-due-to-netfilter-nf_nat_setup_info-docker-static-ip-macvlan-r1356/

Enable the syslog server and post that and the complete diagnostics after a crash.

Yes.

It should be obvious but formatting the disk will delete all data there, so you'll need to backup first then restore the data.

This can happen when there's a single btrfs array device, like disk2, parity will have an invalid btrfs filesystem that conflicts with the pools, this will be supported in the future but for now best solution is to format it xfs like the remaining disks, if for some reason you really want just that disk with btrfs use btrfs encrypted.

Check filesystem on disk3.

Rename network.cfg on the flash drive and reboot to see if it can get an IP from the DCHP server.

Yes, doesn't look like a device problem, just filesystem corruption.

Those errors can cause some data corruption in the rebuilt disk, if they coincide with sectors use by data, but so few errors should not be anything major, could be for example just a small glitch during a movie.

Wait for the extended test, if the disk is failing you might get more errors. Do you still have the old disk, any new data since the disk was upgraded?

It's possibly, bind the NVMe device to vfio-pci first (Tools -> System devices) then reboot and select it for the VM when creating, it will appear under other PCI devices section.

https://forums.unraid.net/topic/95309-empty-disk-using-56gb/ Parity still needs to be synced, disks might be empty but unless they are new or have been cleared they won't be all zeros. CPU is not supported by mcelog, not by Unraid, it's fine.

See if this applies to you, if yes, upgrading to v6.10 and switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enable, top right)), or see below for more info.: https://forums.unraid.net/topic/70529-650-call-traces-when-assigning-ip-address-to-docker-containers/ See also here: https://forums.unraid.net/bug-reports/stable-releases/690691-kernel-panic-due-to-netfilter-nf_nat_setup_info-docker-static-ip-macvlan-r1356/

That's a UPS option, it might not exist in yours.

Some UPS have an option to power off after some time on battery and power back on when power is restored, that's the only option.

I don't see how that is possible, let me explain what creating a blank tg3.conf does: -with Unraid v6.10.2, and only with that release, if VT-d is enabled and there is a NIC that used the tg3 driver that driver won't be loaded Unraid unless a blank tg3.conf file exists. -with any other Unraid release, including v6.10.3 that code doesn't exist, i.e., it won't make any difference having that file or not, even if you have a NIC that uses that driver. If your NIC isn't loading with VT-d enable it's a different problem, please post diags after booting witn VT-d enabled and VT-d disabled.

Second Jul 11 10:11:35 Nexus kernel: BTRFS: device fsid 653150f2-f281-4987-bb45-f3e553c14b9c devid 2 transid 534361 /dev/nvme2n1p1 scanned by udevd (1391) Jul 11 10:11:35 Nexus kernel: BTRFS: device fsid 653150f2-f281-4987-bb45-f3e553c14b9c devid 1 transid 542551 /dev/nvme1n1p1 scanned by udevd (1402) I assume you mean devid 2 (nvme2n1)? The other device will be out of sync. If yes it's always good to make sure backups are up to date, if you mounted devid2 by itself read/write best forward is to wipe the other one and then re-add to the pool.

Enable the syslog server and post that after a crash. P.S. please attach any files directly to the forum.