JorgeB

Errors for disk 6 look a little strange, before doing anything else lets see if it can still be emulated: stop the array unassign disk6 start array and post new diags.

Please post the diagnostics, you can grab then on the console, they will be downloaded to the flash drive.

Re-reading my reply I wasn't as clear as I should have been, by no I meant, no, don't do that, wait, but good news if the old disk has the data, you might post current diags so we can check SMART.

Docker image is corrupt, delete and re-create.

I told you not to do that.

You should really update Unraid, you're running an ancient release, much more difficult to look at the diags. Both parity and disk1 are failing, so some data loss might be inevitable, suggest cloning disk1 to a new disk with ddrescue to try and recover as much data as possible and add a new parity drive, alternatively use a new disk1 and parity to rebuild the array than see what you can copy from old disk1 using the UD plugin to mount it.

The ATA errors are from disk3, looks like a power/connection problem.

Constant ATA errors on disk3, check/replace cables and try again.

No, what disk do you want to rebuild? Single parity correct?

Please post the diagnostics.

I assume this was disk4? Model Family: Seagate IronWolf Device Model: ST10000VN0008-2PJ103 Serial Number: ZS5033S2 If yes also looks healthy, a few CRC errors, likely due to a bad cable. You can rebuild using new disks, but IMHO not the best option, data on disks 2 and 4 will be mostly on the lost+found folder, you'll then soend a lot of time copying the data from the original disks, I would first confirm actual disks 2 and 4 are mounting and contents look correct, you can use the UD plugin for that, if yes do a new config with the original disks and rebuild parity.

First you should post diags or SMART report with/for disk4.

I would suggest re-creating the flash drive, or just trying with a new trial one just to see if it boots and if that is the problem.

Not really, data is still stripped with raid4, just there's a dedicated disk for parity.

Why? That's what dual parity is for.

Please start a new thread in the general support forum and don't forget to include the diagnostics.

That suggests it dropped offline, try another USB port, ideally USB 2.0.

There are some known issues with V6.10.x, older Nvidia GPUs and pass-trough, VM might fail to boot or boot but give a code 43 error for the Nvidia driver, please try booting without the GPU (use VNC) just to check if the problem is the NVMe device or the GPU.

Btrfs is detecting data corruption in all your pools, you should run memtest.

Something else was also reading from it.

Please post the output of: blkid

FYI apparently there's a modded driver based on the Realtek out of tree driver that works (not tested by me):

Some good info about permissions issues after updating to v6.10 here: https://forums.unraid.net/topic/123901-plex-issues-upon-upgrade-to-6101/?do=findComment&comment=1138715

Are you using SATA ou SAS devices? Note that for SATA max cable length from controller to device is 1m, you can expand that by using a SAS expander, cable can be up to 10m from controller to expander and assuming SATA devices one adicional meter from expander to devices.

Unraid is not RAID, each disk is a separate filesystem, so no files can be larger than a single disk/pool.