JorgeB

Yes. Not sure what you mean exactly, but snapshots will have all the files from the dataset/disk from the time it was taken. You create you own script as needed, I use btrfs snapshots to backup all arrays from my servers, disk by disk, so it takes a snapshot from each disk and sends it to the backup server, I only have one share per disk, but you can have a script snapshoting multiple shares.

Please post the diagnostics for both servers.

Yes

Those diags still show issues with disks 1 and 2, if they are after checking the cables there's still a problem, see if you can fix that and post new diags after array start.

There's no driver for your NIC in that old release, update to v6.12.10 and it should work then, since there's no internet, you will need to do a manual updated.

Bonienl has been unavailable, I expect he will look at this as soon he can after that changes.

Assuming the syslog-previous cover crashes, there's nothing relevant logged, this usually points to a hardware issue, one 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.

Reboot and don't start the array, then try to import disk1 read-only, since that won't read space maps, among other things: zpool import -o readonly=on disk1 If it works, start the array, disk1 will show unmountable in the GUI, but the data should be under /mnt/disk1, if yes backup that disk and re-format

I meant run the server with just one stick, if it crashes run it with the other one, that will basically rule out RAM, memtest doesn't always catch everything.

Yes, but recommend assigning it as a pool for performance reasons. Yes, you can use the mover. Yes.

Don't forget to take care of this with Ryzen, but this should only help if it crashes when idle, not when under load. https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173

You can also test the flash drive in a different computer with legacy boot support, to make sure it's booting.

Thanks for the report, it's a known issue, should be fixed for next release: https://forums.unraid.net/topic/160470-split-level-manual-no-longer-working-after-6129/

Apr 26 14:24:41 Jonsbo kernel: zfs: `' invalid for parameter `zfs_arc_max' Apr 26 14:24:41 Jonsbo kernel: zfs: unknown parameter '6302227456' ignored Edit zfs.conf and remove the space before the value, should be: options zfs zfs_arc_max=6302227456 not options zfs zfs_arc_max= 6302227456

Get the syslog once it's stuck to se which filesystem is the problem: cp /var/log/syslog /boot/syslog.txt