JorgeB

Cache=No doesn't move any files, only yes or prefer does.

Get the log from Mint, it will show.

Run memtest, disk could be good but bad RAM can make the post read fail.

These should have worked, post a photo of the error you're getting.

How are you mounting that device? Not seeing any pool named media.

Disk dropped offline, looks more like a power/connection problem.

This.

Try clearing the browser cache and/or using a different browser, if that fails boot in safe mode.

Please post the diagnostics and the output of: ls -la /mnt/user

Sep 23 11:23:35 BIGDADDY kernel: BTRFS: device fsid b22551d5-574f-45b3-a984-7648d094271c devid 1 transid 867196 /dev/sdb1 scanned by udevd (667) Sep 23 11:23:35 BIGDADDY kernel: BTRFS: device fsid b22551d5-574f-45b3-a984-7648d094271c devid 2 transid 862906 /dev/sdd1 scanned by udevd (663) Pool was out already of sync at boot, note the different transids, this suggests one them dropped offline before, and looking at the stats they both did: Sep 23 11:24:30 BIGDADDY kernel: BTRFS info (device sdb1): bdev /dev/sdb1 errs: wr 479443, rd 6903, flush 6054, corrupt 193330, gen 810 Sep 23 11:24:30 BIGDADDY kernel: BTRFS info (device sdb1): bdev /dev/sdd1 errs: wr 21307930, rd 58098292, flush 590499, corrupt 2129794, gen 5010 Hopefully not at the same time but the pool might still be a mess, since one of the devices was wiped after removing it you first need to recover that, with the array stopped type: btrfs-select-super -s 1 /dev/sdb1 Then unassign all pool devices, start array, stop array, re-assign both pool devices, start array, post new diags.

Don't see a reason for the disk mounting ro, try asking in the UD plugin support thread.

Looks like the HBA is losing connection with all the disks at the same time, I would suspect an issue with the enclosure, could also be the HBA>enclosure cable, try adding adding one disk.

Server wasn't rebooted since last time, so cables were not replaced, did you at least check them? Though not easy to really do that with the server on, swap cables/slots between that disk and another one then see if the problem follows the disk or not.

There's some discussion about that here. https://forums.unraid.net/bug-reports/stable-releases/6100-vnc-no-longer-connects-r1902/

Should be fixed once -rc6 is released.

In a Windows computer, if you're not familiar with the command line use the GUI, right click on the disk, tools, repair disk.

You need to remove this to be able to use them in Unraid: Formatted with type 2 protection So try re-formatting them without it, more info below: https://forums.unraid.net/topic/93432-parity-disk-read-errors/?do=findComment&comment=864078 https://forums.unraid.net/topic/110835-help-with-a-sas-drive/

Run chkdsk on it first.

Which errors?

It's a known issue.

Now re-assign disk4, start array and post new diags.

Use the UD plugin to connect a USB disk/device to copy what you need.

Clear the browser cookies and try again.

Parity disk looks healthy, re-sync it and if there are issues post new diags before rebooting.

x32 is bogus, likely virtualization related, run the diskspeed docker to test total controller bandwidth.