JorgeB

Looks OK

You must unmount before unpluging it.

RAM is overclocked, start here: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/#findComment-819173

Alwsys good to try other options, but IIRC TrueNAS is the same regarding this.

This is typically not needed, so it's not really a feature that someone has requested or is on LT's radar, you can create a feature reuqest here if you like: https://product.unraid.net/b/unraid-os-feature-requests

IIRC , Unraid will always repartition a pool device if the existing partition is not the default layout, you could create the parrion and format it ZFS outside the GUI, then just import the pool using the GUI, that would work.

Type reboot in the CLI, but if it doesn't reboot after 5 minutes you may need to force it.

Those are not the complete diagnsotics, but not seeing any obious issues on the syslog, post a screeshot showing the error you see.

Note as far as I know, only root has SSH access.

Do you see the same speed with the array started in maiantnce mode?

Jun 20 00:12:09 Tardis unassigned.devices: Mounting partition 'sdj1' at mountpoint '/mnt/disks/transport data'... This unassigned disk dropped offlione: Jun 20 11:33:51 Tardis kernel: sd 1:0:5:0: device_block, handle(0x000d) Jun 20 11:33:53 Tardis kernel: sd 1:0:5:0: device_unblock and setting to running, handle(0x000d) Jun 20 11:33:53 Tardis kernel: sd 1:0:5:0: [sdj] tag#5829 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=DRIVER_OK cmd_age=5s Jun 20 11:33:53 Tardis kernel: sd 1:0:5:0: [sdj] tag#5829 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e5 00 Jun 20 11:33:53 Tardis kernel: sd 1:0:5:0: [sdj] tag#5830 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=DRIVER_OK cmd_age=0s Jun 20 11:33:53 Tardis kernel: sd 1:0:5:0: [sdj] tag#5830 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 98 00 Jun 20 11:33:53 Tardis kernel: sd 1:0:5:0: [sdj] Synchronizing SCSI cache Jun 20 11:33:53 Tardis kernel: sd 1:0:5:0: [sdj] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK Jun 20 11:33:53 Tardis kernel: mpt2sas_cm1: mpt3sas_transport_port_remove: removed: sas_addr(0x4433221104000000) Jun 20 11:33:53 Tardis kernel: mpt2sas_cm1: removing handle(0x000d), sas_addr(0x4433221104000000)

Enable the syslog server and post that after the next crash.

Please post the diagnostics just to confirm the pool is OK

If the help is actually wrong, I would recooemd creatign a bug report https://product.unraid.net/b/unraid-os-bugs

If there was an unclean shutdown, a few sync errors are normal.

Emulated disk5 has filesystem issues, and with btrfs this may not be an easy fix, my first suggestion would be see it the actual disk can mount with the UD plugin (you need to unassign it first), also keep the old disk instact for now if you still have it.

I don't see any btrfs erros, I do see what looks like a bad NVMe device (which ends up crashing the kernel): Jun 17 23:05:06 Unraid kernel: nvme nvme1: invalid id 220 completed on queue 17 Jun 17 23:05:06 Unraid kernel: nvme1n1: I/O Cmd(0x0) @ LBA 18446744073709551615, 0 blocks, I/O Error (sct 0x0 / sc 0x13) Jun 17 23:05:06 Unraid kernel: nvme nvme1: request 0xee genctr mismatch (got 0x4 expected 0x5) The controller is returning completion entries that do not belong to the current queue generation, That usually indicates an NVMe controller firmware bug, failing NVMe SSD, PCIe communication corruption, etc

If the device has data that you want to keep you need to migrate it first

Can't really help with that, but did you try ChatGPT or similar? They can sometimes help with things like that.

Don't see any obvious issues logged, you can try recreating the docker image, not sure it will help, but it won't hurt: https://docs.unraid.net/unraid-os/troubleshooting/common-issues/docker-troubleshooting/#re-creating-the-docker-image-file Then: https://docs.unraid.net/unraid-os/troubleshooting/common-issues/docker-troubleshooting/#reinstalling-docker-applications Also see below if you have any custom docker networks: https://docs.unraid.net/unraid-os/troubleshooting/common-issues/docker-troubleshooting/#restoring-docker-custom-networks

Make sure it's labeld UNRAID, all caps.

Please use the existing support thread for the plugin you are using

I see multipal apps segfaulting, this typically is a hardware issue, RAM or CPU, in this case I would lean more to the CPU, there are some users on their 3rd and 4th CPUs.

It's easier to do it in Windows for example

When using the CLI you must use the correct md device, but if the result above was from the GUI, the filesystem appears to be damaged beyond repair, best bet is to use a file recovery app like UFS explorer, the free trial should show if it can recover the data.