JorgeB

Disks 4 and 7 currently.

Post the approximate date and time you last experienced the issues to see if there's anything logged.

Disk was already disabled at boot, so we can't see what happened, SMART looks fine, so check/replace cables and resync parity. https://docs.unraid.net/unraid-os/using-unraid-to/manage-storage/array/replacing-disks-in-array/#re-enabling-a-disabled-disk-rebuilding-onto-itself

Yep, and if all disks mount now, check their contents; also post new diags.

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

Those errors can be intermittent; that is, the data is returned correctly on a retry; otherwise, you should get an i/o error. Devices should never return bad data, unless there's a firmware bug.

They are logged as disk failures, and SMART doesn't look good; cancel the rebuild and run an extended SMART test on both.

Disk is emulated, but it's not mounting. Unassigning the disabled disk should have no effect, but just check the filesystem.

Emulated disk 1 also has issues, I thought that one was mounting before. You also need to check fileystem on that one.

Errors come from disks 7 and 8, do they share anything in common, like a power splitter? If not, replace the cables for both.

You would need to create the boot pool with the smallest one first (or both at the same time). You can do that by booting another flash drive (after copying the current config there), then removing the boot pool and rerunning the wizard to recreate it.

Start array in normal mode now (without changing the disk assignments) and post new diags.

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).