JorgeB

Depends on the amount of installed containers and the size of the image, but as long as it doesn't keep growing it's not a problem for now.

Try booting in safe mode to rule out any plugin issues.

Constant call traces, start by running memtest, if nothing is found, and because memtest is only definitive if it finds errors, try running the server with just one stick of RAM, if the same try with a different one, that will basically rule out bad RAM, if issues persist, another thing you can try is to boot the server in safe mode with all docker containers/VMs disabled, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one.

For that you need to configure the 10GbE NIC using a different subnet:
 
 

I'm not seeing any i/o errors in the diags, there is a filesystem issue with disk2, check filesystem on that disk, run it without -n.

Check filesystem on that disk, run it without -n

You can upgrade the pool one device at a time, it will remain online during the process.
 
 
This is normal if you are using the default high water allocation method, once disk1 is over half full it will start writing to disk2.

If you still see the freeze issue and it started happening after the hardware change, it suggests the problem may be hardware related, but you can try redoing the flash drive, backup the current one first and then redo it and just restore the bare minimum, like the key, super.dat and the pools folder for the assignments, also copy the docker user templates folder, if the freeze issue is gone you can then reconfigure the server or try restoring a few config files at a time from the backup to see if you can find the culprit, if it's still there it's most likely hardware related.

Make sure you reset the stats and keep monitoring for more errors, if there are more, there's still an issue:
 
https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=700582
 
 

Try reconnecting the device, or using a different M.2 slot to see if it comes back.

Yes, but only if you do the parity sync in maintenance mode.

Try using a different flash drive with a stock install, no key needed, that will confirm if it's a board problem or not.

https://docs.unraid.net/unraid-os/manual/storage-management#rebuilding-a-drive-onto-itself

Ig this is not an option it may be linked to a different account, you should contact support with all the details.

You are using USB disks, besides not being generally recommended for other reasons, some USB bridges have issues with spin down, recommend using SATA.

Uninstall the plugin and enable turbo write manually in Disk Settings.
 
Do this test again with large files but using Windows explorer, and post a screenshot of the transfer speed graph.
 
Disk to disk transfer will always be slow, and turbo write cannot help for this.
 
 

According to iperf results the LAN is the problem, try a different cable, switch, NIC, etc.

Media share is not being exported.
 

You're right, sorry about that, must have been looking at the wrong diags.
 
Disk got disable during spin up, and there are some known issues with spin up, LSI and some Seagate disks, so would recommend trying he below or disabling spin down.
 
https://forums.unraid.net/topic/103938-69x-lsi-controllers-ironwolf-disks-disabling-summary-fix/
 
 

Jun 22 05:56:44 Tower3 emhttpd: error: put_config, 578: Read-only file system (30): fopen: /boot/config/ident.cfg.new  
Flash drive is read-only, try recreating it.

Check filesystem for that disk, run it without -n.

Yes.
 
Try the current one first, if it doesn't solve the issue, replace it.
 
Yep.

Call traces are macvlan related, so changing to ipvlan should resolved, make sure you reboot after the change, and take the opportunity to update to latest stable.

Assign both devices to a new pool, leave the fs to auto, start the array and it should mount again.

Backup the current one, recreate using the USB tool, see if boots, and if yes, restore only the complete /config folder from the backup.