JorgeB

It does, I would also recommend converting that disk to xfs once the fs is fixed, reiserfs it's not recommended for a long time.

Cache filesystem has issues, best bet is to backup all data, re-format the pool and restore the data.

No, you should do it on a Windows desktop (or mac)

SMART isn't working because you're using a raid controller, it *might* work if you select "HP cciss" on the SMART controller type (Settings -> Disk Settings)

Flash drive problems, run chkdsk on it.

Check filesystem on disk2: https://wiki.unraid.net/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui

See if this helps: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173

Please post the diagnostics: Tools -> Diagnostics

How come you have Emby running?

That won't bring the disk online, to re-enable a disable disk is the same as before: https://wiki.unraid.net/Troubleshooting#Re-enable_the_drive

Most likely.

This suggests a network issue, since the first couple of GB are cached to RAM and should be transferred a max lan speed (assuming source is capable of that).

Next time please post the complete diagnostics, it includes the syslog, SMART reports as well as other useful info. Iit's logged like an actual disk problem, but these can be intermittent, you should run an extend SMART test.

Set eth2 as eth0, you can do that by swapping them on "interface rules", reboot is need to take effect.

Regarding the disks when this is over you can run the diskspeed docker, it might help identify which ones are performing worse.

I would estimate max a couple of days, any more you'll likely get errors first. I would, IMHO it's just a matter of time until they fail again. You can, but it will slow down even more, so avoid as much as you can.

Then please run the mover now with the correct setting and post new diags.

Btrfs is very susceptible to hardware problems, especially RAM, it will quickly get corrupt with RAM errors, since you're using Ryzen take a look here, note that you're CPU is 1st gen, despite what the model name suggests.

loop2 is the docker image, that's always btrfs, and it's corrupt so you need to recreate it.

Something is not right here, pron share is set to cache="yes" in the diags, but according to the log the mover was moving data from disk1 to cache, did you changed it before grabbing diags?

As long as there are no read errors let it go on, some of your disks appear to be marginal (but OK for now), and when reading those slow sectors zones speeds can fluctuate a lot.

Make sure to check this for better pool monitoring, one of the most common reasons for those errors in a pool is one the the devices dropping offline then coming back online.

On the console type "diagnostics" then upload the zip here.

GUI is warning you that eth0 link is down: Settings for eth0: Supported ports: [ FIBRE ] Supported link modes: 1000baseT/Full 10000baseT/Full Supported pause frame use: Symmetric Receive-only Supports auto-negotiation: No Supported FEC modes: Not reported Advertised link modes: 10000baseT/Full Advertised pause frame use: No Advertised auto-negotiation: No Advertised FEC modes: Not reported Speed: Unknown! Duplex: Unknown! (255) Port: FIBRE PHYAD: 1 Transceiver: internal Auto-negotiation: off Supports Wake-on: g Wake-on: d Current message level: 0x00000000 (0) Link detected: no Lan is still working because eth2's link is up and you have a all NICs bonded. BONDNICS[0]="eth0 eth1 eth2 eth3"

It would be the same, with Unraid each array disk is a separate filesystem, same issues even if all array disks were using zfs.