JorgeB

Not a great sign; I have multiple of those devices, and they don't show any errors there. Did you run an extended SMART test? If that passes, I expect they won't replace it.

Run again for both without -n, and if it asks for -L use it.

Filesystem check must be in maintenance mode. Don't change any assignments for now.

I assume the issue occurred during these timecodes? Jul 1 18:08:15 Zeke smbd[2302669]: [2026/07/01 18:08:15.594875, 0] ../../source3/smbd/smb2_read.c:265(smb2_sendfile_send_data) Jul 1 18:08:15 Zeke smbd[2302669]: smb2_sendfile_send_data: sendfile failed for file Modern Marvels/Modern Marvels-Space Stations.mp4 (Broken pipe) for client PID=2302669,CLIENT=896e1da1-74d3-11f1-87e1-001c2537013f,channel=0,remote=ipv4:192.168.0.235:52313,local=ipv4:192.168.0.80:445. Terminating Jul 1 18:30:43 Zeke smbd[2545174]: [2026/07/01 18:30:43.178852, 0] ../../source3/smbd/smb2_read.c:265(smb2_sendfile_send_data) Jul 1 18:30:43 Zeke smbd[2545174]: smb2_sendfile_send_data: sendfile failed for file Modern Marvels/Modern Marvels-Tower Bridge.mp4 (Broken pipe) for client PID=2545174,CLIENT=896e1da1-74d3-11f1-87e1-001c2537013f,channel=0,remote=ipv4:192.168.0.235:52628,local=ipv4:192.168.0.80:445. Terminating Jul 1 18:50:43 Zeke smbd[2564600]: [2026/07/01 18:50:43.306835, 0] ../../source3/smbd/smb2_read.c:265(smb2_sendfile_send_data) Jul 1 18:50:43 Zeke smbd[2564600]: smb2_sendfile_send_data: sendfile failed for file MythBusters/Mythbusters - Season 07/Mythbusters_S07E10_Curving Bullets.mp4 (Broken pipe) for client PID=2564600,CLIENT=896e1da1-74d3-11f1-87e1-001c2537013f,channel=0,remote=ipv4:192.168.0.235:52649,local=ipv4:192.168.0.80:445. Terminating Jul 1 18:51:20 Zeke smbd[2709616]: [2026/07/01 18:51:20.207806, 0] ../../source3/smbd/smb2_read.c:265(smb2_sendfile_send_data) Jul 1 18:51:20 Zeke smbd[2709616]: smb2_sendfile_send_data: sendfile failed for file Nature/Nature - Becoming Elephant The Orphans of Reteti.mp4 (Broken pipe) for client PID=2709616,CLIENT=896e1da1-74d3-11f1-87e1-001c2537013f,channel=0,remote=ipv4:192.168.0.235:52869,local=ipv4:192.168.0.80:445. Terminating If yes, this looks like a client problem. Is this the client's IP? remote=192.168.0.235 This log means the client requests a video, samba starts streaming it using sendfile(), client disconnects before the transfer finishes, samba attempts to send another chunk, kernel returns (Broken pipe), samba logs it and terminates that SMB session.

It's the same with a folder; you can delete it if you stop the Docker service. Also recommend using a Docker image instead, since Docker folders can have strange issues.

There appears to be a container constantly restarting; see if you can find which one it is by looking at their uptimes. Then reboot to clear the logs and post new diags if it still happens.

Please post the diagnostics

It should.

Yep, this is the first option you should try; there's another one if this one doesn't work, but it only suppresses the errors.

Is the missing device expected? Post the output from blkid /dev/sda and fdisk -l /dev/sda

Post the xfs_Reapir output from the emulated disk7; also run it on disk2, since the syslog is showing issues with that filesystem.

Most likely a power/connection issue, but keep monitoring for any more errors for now.

The pool is basically empty, so you could just recreate, but if you prefer to correct it, with the array running type btrfs device remove missing /mnt/data Then stop the array and reimport the pool with just that device; it should then only have the remaining device (which could also be used as an array data drive).

The pool currently has a missing device, and the GUI is not reflecting that. You should still be able to fix it and keep its data using the CLI. You can then keep that disk as a pool or move it to the array as data if you prefer; I can post more detailed instructions if you like

Do you have the time codes? It would be good to see how long the crash happens after the rebuild start, if it always immediate or just a couple of seconds; I would no longer consider it a hardware issue. If you enabled the syslog server it should have that, as long as keep it all in a single file, where there could be multiple crashes logged for comparison. My suggestion for now, to see if there's really a specific issue when trying to rebuild that disk, would be to copy all the data from the emulated disk to the actual disk, then do a new config and resync parity, and see if that doesn't crash. Can post more detailed instructions if needed.

Just to be clear, licenses cannot be transferred to an SSD, it can only be tied to a flash drive or TPM, even if using an internal boot pool.

I meant the diags posted, not all those individual files, there's no chance for me to be going through all of them. Please just post that file

Do that for half the installed plugins; retest and they are the other half if needed.

Something weird happened there to corrupt so many filesystems, likely a hardware issue. You can try the read-only option, or even -FX as a last resort, but possibly the only option is also using a file recovery app or destroy and recreate.

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.