JorgeB

You will need to zero the log, it's the only option to try and fix the filesystem, and most often it is not a problem.

Post the output from btrfs fi show

You can rename *.plg in /boot/config/plugins to *.bak, then reboot and retest. If the same, try the other half, then keep drilling down.

It's worth a try, but in my experience, if it doesn't mount read-only, most times this requires a pool destroy and restore. If you don't have backups, I recommend cloning the disk with dd before proceeding so that you also have the option to use a file recovery app like UFS Explorer. For a single disk zfs pool, the standard cheaper version may be able to recover the data, and the free trial should show if it can recover.

Both show this, mening zfs cannpt write to them, try a read-only import zpool import -o readonly=on -d /dev/md1p1 disk1 zpool import -o readonly=on -d /dev/md11p1 disk11

That looks like a bad flash drive, you can try recreating it first, if the issues persist, best to replace it.

Not seeing anything that would explain crashes, though the syslog is being spammed with USB manager messages, making it much more difficult to analyze; see if you can quiet that. Regarding the hardware, and since it's a Ryzen CPU, make sure this has been taken care of: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/#findComment-819173

It's still logging the same errors; suggest using a bigger hammer: try redoing the flash drive, backup the current one first and then recreate it using the USB tool 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 (\config\plugins\dockerMan\templates-user), if all works 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.

Swap both cables with a different disk, re-enable the disk, and see if there are any more errors: https://docs.unraid.net/unraid-os/using-unraid-to/manage-storage/array/replacing-disks-in-array/#re-enabling-a-disabled-disk-rebuilding-onto-itself

The driver is missing, but as far as I can find, there's no Linux in-tree kernel driver, only an out-of-tree driver, so I'm afraid you would need to wait for the driver to be added to the kernel upstream.

This should not make any difference, but you can try starting the array in maintenance mode and importing using the pool using the md device, if it still fails, and most likely will, post the output from tail -n 50 /proc/spl/kstat/zfs/dbgmsg

This error is not on the diagnostics posted, but it means the Unraid driver is crashing, and it's almost always a hardware issue, most often bad RAM or a bad CPU.

If you can log in from the CLI using a monitor/monitor see if you can get the diags, if not, post a photo of where the boot stops.

This is an actual issue that should be resolved; post new diags after you get some errors.

Looks good, rebuild finished without any errors or warnings logged.

If it doesn't post, it won't be in the logs, it's also not an Unraid issue.

You can, but it's not required to run the SMART test.

There's nothing relevant logged; it suggests more of a hardware issue, Post the diagnostics mostly to see the hardware used.

You can still run

There are constant Samba errors being logged: Jun 29 18:35:46 hightower nmbd[2503]: [2026/06/29 18:35:46.378765, 0] ../../source3/lib/interface.c:716(load_interfaces) Jun 29 18:35:46 hightower nmbd[2503]: WARNING: no network interfaces found Jun 29 18:35:46 hightower nmbd[2503]: [2026/06/29 18:35:46.629355, 0] ../../source3/lib/interface.c:716(load_interfaces) Jun 29 18:35:46 hightower nmbd[2503]: WARNING: no network interfaces found Don't see what's causing them. My first suggestion would be to rename /config/network.cfg on the flash drive to network.bak then reboot, this will revert the LAN settings to default DHCP, then post new diags after array start.

If it's not FUSE there's some other bottleneck or issue; it's certainly not an Unraid limitation. I can get line speed with 25GbE (writing to an exclusive share, though FUSE it drops to around 1.8GB/s with this server)

It's logged as a disk error, but SMART looks OK. Recommend running another parity check or an extended SMART test.

Best bet is to look for the support thread for that container

So it's not the same issue; I recommend starting your own thread to avoid confusion. Also, please post there the basic hardware you are using.

You can disable the Docker and/or VM services for a few hours or a day, and check the SMART stats before and after, it that stops the increase, then start enabling them one by one and retest.