JorgeB

Please post the diagnostics.

https://forums.unraid.net/topic/117773-network-interface-rules-duplicate-mac-address-assignments/?do=findComment&comment=1130230

You'll probably need to wait for a new release that includes an updated version of mcelog.

Changed Status to Closed Changed Priority to Other

Diags are just after rebooting, so there's not much to see, if you want to try updating again enable the syslog server and post that if it crashes again.

Changed Status to Closed Changed Priority to Other

If it still boots of course.

That's from mcelog, not Unraid, it's not problem.

Changed Priority to Other

If it's a Dell server see here: https://forums.unraid.net/topic/119502-bzimage-checksum-error/?do=findComment&comment=1108354

Syslog starts over after every reboot, so not much to see, enable the syslog server and post that after the next crash.

Yep.

Prefail is just the type os some SMART attributes, also disk4 looks healthy, most likely not a disk problem.

Try changing the docker custom network type to ipvlan, advanced view must be enable on the docker settings page.

Yep. If you suspect an issue with the GPU on v6.10 you can also try blocking the driver from loading by adding modprobe.blacklist=amdgpu to the append line of syslinuc.cfg

Other thing you could try is doing a new config and just assign about half of current array drives, see if there's a difference, if it's the CPU that is somehow limiting it should be noticebly faster, or sync the entire array with single parity also to compare.

It's very strange, doesn't make sense CPU being at 100% while syncing at 16MB/s, don't really now what else to try, you can run diskspeed docker just to make sure all disks are performing normal.

These errors appear to come from one of the NVMe devices: 42:00.0 Non-Volatile memory controller [0108]: Samsung Electronics Co Ltd NVMe SSD Controller PM9A1/PM9A3/980PRO [144d:a80a] Subsystem: Samsung Electronics Co Ltd NVMe SSD Controller PM9A1/PM9A3/980PRO [144d:a801] Kernel driver in use: nvme Kernel modules: nvme If there's a different slot you can use try, if not you should be able to suppress the errors, to at least stop filling the log up. As for the parity check it's using a lot of CPU, parity check is single threaded, and it's showing 100% CPU, which would mean it's being limited by that, but it doesn't make much sense with the CPU you have... Did you notice slower performance with anything else?

Cache filesystem is going read-only: May 23 10:31:46 Tower kernel: BTRFS info (device sde1): forced readonly Best way forward to make sure it's fixed is to backup anything else important on cache and re-format it, then restore the data and re-create the docker image.

Also not clear it could be fixed, since from what I understand it's a Dell issue, related to how they use virtualization that conflicts with Linux.

Change /mnt/user0/ to /mnt/user/, user0 doesn't include contents from any pool.

Please post the diagnostics.

No, as long as the board doesn't have some compatibility issue with them.

Not for now, but I'll post an update in the announcements thread when there's new info, while this isn't an Unraid issue I know that LT is looking at it.

Looks like a hardware problem, do you have some hardware you could swap around to test, like different PSU, board, etc?