JorgeB

Re-start the array, pool should mount now, if it doesn't post new diags.

Make sure the pool is exported and then see below for how to remove swap and make partition #2>#1
 
https://forums.unraid.net/topic/153274-how-to-non-irreversibly-migrate-from-truenas-core-with-zfs-to-unraid/?do=findComment&comment=1369139
 
After that go to Tools - New Config and reset the array, then assign sdb to a pool, not to the array, you also need to assign at least one data array device, you can assign the other disk or an old flash drive for example, start the array and the pool should import.
 
 

Unraid creates all zfs pools with utf8only=on, I see two options that you could use to solve that:
 
- have rsync convert to utf8 during the transfer, you would need to know the old charset in use, if it was for example ISO-8859-1, you just need add to the rsync command
 
rsync -av --iconv=ISO-8859-1,utf-8 /source /dest  
- other option would be to reformat the pool/disk without enabling utf8only=on

Looks like a power/connection problem with disk1, check/replace cables and post new diags after array start.

Check filesystem on disk3, run it without -n, and if it asks for it, use -L

Look for the container support thread/Discord:
 

Please use the existing plugin support thread:
 

Unfortunately there's nothing relevant logged, this can be 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.

v6.13 already contains a fix for that, but note that it will require re-formatting the filesystem.

Type reboot in the CLI, if it doesn't reboot after 5 minutes you will need to force it, then see if it comes back normally.

By default it will create a mirror.

It's logged as a disk error, even if SMART looks good, run another extended test, but even if it passes, if there are any more errors I would consider replacing it.

@Frank1940Since there's some interesting and still relevant info in that thread I've created a copy here:
 
 

Stop the array, click on the pool and set "Enable user share assignment" to Yes.

Emulated disk1 is mounting, if contents look correct you can rebuild on top and sync parity at the same time:
 
https://docs.unraid.net/unraid-os/manual/storage-management#rebuilding-a-drive-onto-itself

It's not logged as a disk problem and SMART looks fine, most likely a power/connection issue.

Device was busy, reboot and try to format again, that should do it.

You can do a new config: Tools - New config - Preserve all
 
Then assign disk3 and check "parity is already valid" before array start, still a good idea to run a parity check after, and if you started the array without disk3 there will be some sync errors.

The filesystem should be fixed now, reboot to clear the logs.
 
Don't recommend using -L unless xfs_repair asks for it.

You can use this:
https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=511923
 

That suggests the updated was not the problem, it may have just been a coincidence, with all those different apps segfaulting I would start by running memtest.

If the SMART test passed the disk is OK for now, you can click on the thumbs down to acknowledge the current errors, it will then only change if more appear.
 
 
 

The XML is missing from the diags, but looks like the SATA controller (and a USB controller) are bound to the opensense VM, so Unraid lost connection with all disks when it tried to start..

The NIC is detecting a link change/drop:
 
 
Try a different NIC if possible.

Check filesystem on the unmountable disks, run it without -n