JorgeB

That's not how it works:
 
https://docs.unraid.net/unraid-os/manual/docker-management/#re-create-the-docker-image-file
Also see below if you have any custom docker networks:
https://docs.unraid.net/unraid-os/manual/docker-management/#docker-custom-networks

That looks like a bad drive, it's not even giving a complete SMART report, but try another cable and SATA port just to be certain.

That suggests one of them is only connected at 100Mbits, check link speeds on both sides.

Check filesystem on disk6, run it without -n

Jun  3 06:29:32 MeJoMediaHome root: cannot import 'mejomediahomemovies' as 'mejomediahomemovies': I/O error Jun  3 06:29:32 MeJoMediaHome root: #011Recovery is possible, but will result in some data loss. Jun  3 06:29:32 MeJoMediaHome root: #011Returning the pool to its state as of Sun Jun  2 08:21:09 2024 Jun  3 06:29:32 MeJoMediaHome root: #011should correct the problem.  Approximately 6 seconds of data Jun  3 06:29:32 MeJoMediaHome root: #011must be discarded, irreversibly.  Recovery can be attempted Jun  3 06:29:32 MeJoMediaHome root: #011by executing 'zpool import -F mejomediahomemovies'.  A scrub of the pool Jun  3 06:29:32 MeJoMediaHome root: #011is strongly recommended after recovery.  
If you are OK with the 6 sec loss, and probably there's no other option, type on the console:
 
zpool import -F mejomediahomemovies  
then and assuming tit works type:
 
zpoo export mejomediahomemovies  
Finally re-start the array and the pool should now import, if yes run a scrub.
 
 
 
 

Yes, try a different cable and switch port.

Assuming you want some redundancy I would created two raidz1 vdevs, if you can use 14 or 16 devices, if you really want 15 then three raidz1 vdevs, or maybe just a single raidz2 vdev with all 15, depending on what the pool is going to be used for.
 
 

May 22 03:28:00 NAS kernel: macvlan_broadcast+0x10a/0x150 [macvlan] May 22 03:28:00 NAS kernel: ? _raw_spin_unlock+0x14/0x29 May 22 03:28:00 NAS kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan]  
Macvlan call traces will usually end up crashing the server, switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right)), then reboot.

Doesn't look like a disk problem.

Docker image is corrupt, delete and recreate.
https://docs.unraid.net/unraid-os/manual/docker-management/#re-create-the-docker-image-file
Also see below if you have any custom docker networks:
https://docs.unraid.net/unraid-os/manual/docker-management/#docker-custom-networks

You just need to create or or more shares and export them over SMB, both Windows and Mac can use them.
 
https://docs.unraid.net/unraid-os/manual/shares/user-shares/

That suggests the corruption is on metadata, in that case would recommend backing what you can from the pool, reformatting and restoring the data.

One of the notifications is from the Parity Check Tuning plugin, the stock browser parity related notifications are known to sometimes give the previous result, recommend checking the main page, the last parity check results there will be correct.

It's still detecting an xfs filesystem on disk2, post the output of:
 
xfs_repair -v /dev/md2p1  

Not really destabilized, but after the that the GUI commands won't work, so you need to reboot.

Try testdisk.

Try booting the flashg drive in another PC to confirm it's booting, if it is, it may be some compatibility issue with the kernel.

Let it complete at least one pass, also note that memtest is only definite if it finds errors, but if it doesn't after a pass you can try recreating the fileystem, or try zfs, if issues persist there could still be an underlying hardware problem.

Start by running memtest.

You will need to delete/restore the corrupt files listed in the syslog, then run another scrub to confirm 0 errors, but I would recommend memtest first.

Is "Use SSH" enabled in Settings -> Management Access?

You would need to assign all the pool devices in the GUI, but this is not supported, only one partition per device is supported.

In my experience true bitrot is extremely rare, but zfs and btrfs in the array can only detect bitrot, but not repair it, but you would still know which files need to be
replaced.
 
https://docs.unraid.net/unraid-os/manual/storage-management/#converting-to-a-new-file-system-type
 
Parity adds redundancy, it's never a backup, dual parity with two drives seems overkill to me, much better to use that drive as an external backup.
 
It's a valid option, each one has advantages and disadvantages, you can choose according to your priorities, to expand a zfs pool, and until raidz expansion is supported in a year or so, you would need to replace all the disks with larger ones, or add a new vdev with the same number of disks.
 
 
 
 

Backup the current one first and then redo it and just restore the bare minimum, like the key, super.dat and the pools folder for the assignments, also copy the docker user templates folder, if all works you can then reconfigure the server or try restoring a few config files at a time from the backup to see if you can find the culprit.

Before checking filesystem replace the cables on disk6, since there are constant ATA errors, and probably what caused the issues, then run xfs_repair.