JorgeB

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.

Please post the diagnostics after tryng to create the new boot pool.

Previous diags are full of spam, post new ones please without the DVD drive (after array start)

How are you running xfs_repair? If from the CLI post the command used.

Please start your own threads, enable the syslog server and post that and the diags after it happens, though the symptoms are similar, there may be different causes, and it gets complicated trying to support multiple users in the same thread.

Don't see those erros logged, there is a container running out of RAM, something related to Bambu. Type reboot in the CLI and see if it reboot after 5 minutes, if not you may need to force it.

This would be my main suspect, since it's one of the more affected models by the Intel 13/14 gen issues, lot of users with stability issues with this and similar CPUs, look for a BIOS updatye, it can sometimes help if the CPU is not too far gone.

You need to delete the extra pool cfg, please post the diagnostics to see their names.

I'm not seeing any issues logged, but it looks like the syslog is missing stuff, since it ends with Jun 19 07:35:07 NAS kernel: If it happesn again, confirm the syslog has the last lines, if not try tailing it.

Yep, only the bz* files and changes.txt are updated.

Make sure to copy the complete /config folder.

Flash drive problem, 7.3.x is more strict witht he flash drive partition layout, easiest way to fix is to backup the flash drive, recreate it with the USB tool and 7.3.1, restore only the config folder from the backup.

This is a normal behavior with the MX500, monitoring that attribute should be disabled for them.