JorgeB

Not enough info, those errors are likely about the docker image, we'd need to see the beginning of the problem.

"tower" is only linking at 100Mbits: Speed: 100Mb/s

Yes, you should use the device, it's also possible it's still using the old layout, try rebooting first.

That's not a linux partition, dd should have overwritten any existing paritition(s), though since a 2TB disk will be MBR it might be using the backup GPT, suggest you completely wipe that disk and delete all partitions, then re-run dd, also make sure you're using the correct target.

This is an old model, it works with Unraid, I tested one once, not sure if it works reliably as I didn't use it for long.

Due to a current btrfs bug you need to run the balace to single (or any other profile) twice.

Disks are showing some SMART warnings, but this type of read errors can be intermittent, run another check (non correcting), also keep an eye on these attributes, if they continue to increase there will likely be more errors soon. ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 1 Raw_Read_Error_Rate POSR-K 200 199 051 - 5 ... 200 Multi_Zone_Error_Rate ---R-- 200 200 000 - 6

Most likely sectors where the data was on disk5 correspond to good sectors on disk1, also sometimes these errors can be intermittent, but less likely in this case. Impossible to tell for sure without checksums but based on the number of errors probably not much. Since disk5 now has some corruption, rebuilding disk1 will also result in the same.

What I saw looked fine.

It won't move any open files.

There's a couple of files that already exist, also one skipped, maybe it's in use, like seeding?

Make sure mover logging is enable, run the mover and post new diags right after it stops.

Those errors are like related, but can't say what's causing them, you thing you can try is the latest beta, newer kernel works better with Ryzen.

Since there are already errors might as well stop now.

This is a symptom of a drive dropping offline, diags are after rebooting but you're using a Marvell controller and those are known to cause that and other problems, all 3 disks showing errors on the GUI are unsurprisingly connected to it.

Also start a test for disk1, it can't be software, but it can be a different hardware issue, though it's logged as an actual disk problem for both disks.

Damn, I would now redo the array without disk1 or disk2 (or both), since they are the oldest ones.

Disk2 appears to be failing, run an extended SMART test. P.S. next time please post the single diags zip file.

Despite only one cache device being assigned the pool is made of two devices, then the 2nd device was precleared while still in use by the pool, this caused all the errors, cache itself still appears to be good since it's raid1 and it corrected the errors, docker image is corrupt, likely it's using a NOCOW share and those can't be fixed, you need to remove the second device from the pool and recreate the docker image, good to run a scrub also.

Diags are after rebooting with parity already disabled, re-sync it then grab diags after it gets disable and post those.

You only mentioned the SMART errors, not the same thing. Basically just copy everything anywhere else, format and copy back, you can use this to help. If there's been no more errors and it's going at a normal speed you can wait for the check to finish.

The problems start with the flash drive: Nov 20 08:27:21 Tower kernel: xhci_hcd 0000:01:00.0: remove, state 4 Nov 20 08:27:21 Tower kernel: usb usb2: USB disconnect, device number 1 Nov 20 08:27:21 Tower kernel: xhci_hcd 0000:01:00.0: USB bus 2 deregistered Nov 20 08:27:21 Tower kernel: xhci_hcd 0000:01:00.0: remove, state 1 Nov 20 08:27:21 Tower kernel: usb usb1: USB disconnect, device number 1 Nov 20 08:27:21 Tower kernel: usb 1-1: USB disconnect, device number 2 Nov 20 08:27:21 Tower kernel: print_req_error: I/O error, dev sda, sector 2049 Nov 20 08:27:21 Tower kernel: Buffer I/O error on dev sda1, logical block 1, lost async page write Nov 20 08:27:21 Tower kernel: print_req_error: I/O error, dev sda, sector 32745 Nov 20 08:27:21 Tower kernel: Buffer I/O error on dev sda1, logical block 30697, lost async page write Nov 20 08:27:21 Tower kernel: print_req_error: I/O error, dev sda, sector 469512 Nov 20 08:27:21 Tower kernel: Buffer I/O error on dev sda1, logical block 467464, lost async page write Nov 20 08:27:21 Tower kernel: usb 1-5: USB disconnect, device number 3 Nov 20 08:27:21 Tower acpid: input device has been disconnected, fd 5 Nov 20 08:27:21 Tower acpid: input device has been disconnected, fd 6 Nov 20 08:27:21 Tower kernel: usb 1-6: USB disconnect, device number 4 Nov 20 08:27:21 Tower emhttpd: error: put_config_idx, 619: No such file or directory (2): fopen: /boot/config/shares/3ds_Max.cfg Nov 20 08:27:21 Tower emhttpd: error: put_config_idx, 619: No such file or directory (2): fopen: /boot/config/shares/appdata.cfg Nov 20 08:27:21 Tower emhttpd: error: put_config_idx, 619: No such file or directory (2): fopen: /boot/config/shares/data.cfg Nov 20 08:27:21 Tower kernel: FAT-fs (sda1): Directory bread(block 30696) failed Nov 20 08:27:21 Tower kernel: FAT-fs (sda1): Directory bread(block 30697) failed Nov 20 08:27:21 Tower kernel: FAT-fs (sda1): Directory bread(block 30698) failed Nov 20 08:27:21 Tower kernel: FAT-fs (sda1): Directory bread(block 30699) failed Nov 20 08:27:21 Tower kernel: FAT-fs (sda1): Directory bread(block 30700) failed Nov 20 08:27:21 Tower kernel: FAT-fs (sda1): Directory bread(block 30701) failed Nov 20 08:27:21 Tower kernel: FAT-fs (sda1): Directory bread(block 30702) failed Nov 20 08:27:21 Tower kernel: FAT-fs (sda1): Directory bread(block 30703) failed Nov 20 08:27:21 Tower kernel: FAT-fs (sda1): Directory bread(block 30704) failed Nov 20 08:27:21 Tower kernel: FAT-fs (sda1): Directory bread(block 30705) failed Another option is if you're passing-through the Unraid flash drive to a VM.

Not clear to me what's causing the issues by looking at the logs, one thing you can try it to boot the server in safe mode with all docker/VMs disable, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one.

There were read errors on disk15, those should be visible in the GUI, you should also have received a notification about that. Run an extended SMART test on that disk. P.S. There's also filesystem corruption on the cache pool, you should backup and re-format.

On a Windows PC.