JorgeB

This is usually the easiest way, and it also allows to keep docker/VMs online, if they are using cache.

Likely loop2 is now libvirt, but at boot time it shows the docker image issues.

Problem with the onboard SATA controller, quite common with some Ryzen servers, look for a BIOS update but best bet it to use an add-on controller (or a different board).

Docker image is corrupt, delete and recreate.

Same model is working for me, from a working release please post the output of: ls -l /dev/disk/by-id/

Enable the syslog server and post that after a crash.

Thy clearing all the browser cookies.

Stop all containers and start them one by one, see if you can identify which one is causing all the noise.

I identify FUSE as the cause, any deeper dive within FUSE is above my knowledge, I'm more of a hardware guy. This should be easy to reproduce in any server if you do a transfer with small files, it's where the issue is more noticeable, e.g., map another Unraid server (or any other SMB client) to a user share and do a timed cp, I use a folder with several subfolders with about 10.000 files totaling about 10GB, I always do 3 runs and calculate the average speed, with Unraid v6.10.3 on my test server I'm getting 52.98MiB/s for this transfer, now map to the same server/device but using a disk share instead and repeat the same transfer, now I get 255.43MiB/s.

Looks more like a power/connection problem, but since the disk dropped offline there's no SMART report, check/replace cables and post new diags after array start.

I missed this part, did you test from a client PC? Assuming you have one with 10GbE and a fast device to copy from.

Difficult to say for sure, check all cables, also make sure you're not splitting any SATA power to more than two.

Yeah, you should avoid USB for array/pool devices, for many reasons.

In the oldest diags disk1 issues look more like a power/connection problem, disk ended up dropping offline. In the newest diags disk1 initially looks like a power/connection problem, but then it's logged as a disk problem, and the disk has pending sectors, so possibly problems with the connection and the disk, it might even be power problems causing the pending sectors, disk7 looks like a power/connection problem.

GUI doesn't currently support SMART tests for SAS devices, you can still run them manually.

Changed Priority to Other

Didn't notice before that drive is connected using USB, could be an issue with the USB bridge, please try with the disk connected to an onboard SATA port.

This is a strange one, do you see the same error if you try to assign it for example as disk9?

That's fine, but like mentioned that text only applies to non redundant pools.

It's still the disk with most free space in bytes, so it will go there.

Mounting read only should work for this, then it should be re-formatted to avoid future issues.

That suggests a device issue, if you're willing balance the pool to raid0 and test again.

Is this a redundant or non redundant pool? Above highlighted text is for non redundant pools only.

If the previous release you were running was stable you can go back to it in Tools -> OS Update -> Restore

Aug 21 04:21:00 NAS kernel: r8169 0000:06:00.0 eth0: Link is Down .. Aug 21 04:21:03 NAS kernel: r8169 0000:06:00.0 eth0: Link is Up - 2.5Gbps/Full - flow control rx/tx .. Aug 21 04:21:26 NAS kernel: r8169 0000:06:00.0 eth0: Link is Down .. Aug 21 04:21:29 NAS kernel: r8169 0000:06:00.0 eth0: Link is Up - 2.5Gbps/Full - flow control rx/tx .. Aug 21 04:21:30 NAS kernel: r8169 0000:06:00.0 eth0: Link is Down .. Aug 21 04:21:33 NAS kernel: r8169 0000:06:00.0 eth0: Link is Up - 2.5Gbps/Full - flow control rx/tx NIC issues, try different cables/switch, or different NIC.