JorgeB

See here:
https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=511923
 

Set the minimum free space for the share before you hit apply, if not set it defaults to 10%, and you don't have that available.

Current shutdown timeout is not long enough, go to Settings -> Disk Settings and change the shutdown timeout to something like 150 secs, then retry.

That looks like a disk problem, if possible try a different controller or PC to confirm.

Docker image is corrupt, delete and recreate.

Cache device dropped offline:
 
Aug 23 00:07:22 FatFarmHQServer kernel: ata6: hard resetting link Aug 23 00:07:27 FatFarmHQServer kernel: ata6: COMRESET failed (errno=-16) Aug 23 00:07:27 FatFarmHQServer kernel: ata6: reset failed, giving up Aug 23 00:07:27 FatFarmHQServer kernel: ata6.00: disable device  
Since it's an MX500 try this:
https://forums.unraid.net/topic/134954-warning-crucial-mx500-ssds-world-of-pain-stay-away-from-these/?do=findComment&comment=1255816
 

Parity check is known to stall with those Dell controllers, if it's a possibility suggest using a true LSI HBA in IT mode,

You were passing through device 08:00.0 (08:00.1, 08:00.2 and 08:00.3) to the VM, before this was the GPU but now it's a SATA controller, remove these entries if you are no longer using the GPU or edit them all to 09:00.X if you still are.

That's only for the drive(s) assigned to parity, and if you know the previous assignments you can check "parity is already valid" before array start to avoid a re-sync.

Only the root user can use SSH, other users are for SMB/NFS.

Reiserfs can take a long time replaying the journal after an unclean shutdown, it can be hours per disk for large disks, so for now just wait, you should see HDD activity led blinking.

Best bet is to run xfs_repair again without -n, most times there's no data loss, but look for a lost-found folder once it's done.

Array must be stopped, if you still don't see extra slots set the number of slots to more than 3.

Unassign one of the data disks and start the array, Unraid will re-create the partition layout, if that's the only problem the emulated disk will then mount, if it does and contents look correct you can rebuild on top, then repeat for the other disks.

The errors are usually with parity, you just need to run a correcting sync, but if the drives are btrfs formatted on can run a scrub on each one to confirm, but I would bet the data is fine, except if there was any that being written at the time the power went off, those files can be incomplete.

root: mountpoint '/mnt/cache' exists and is not empty  
This mount point should not exist before the device is formatted, you can try removing it manually and re-format.

That's usually flash drive related.
 
Taat disk is not good, you need a new one, then rebuild disk11.

Unassign parity, start array, stop array, re-assign parity, start array.

Device has been failing the extended SMART test for a long time:
 
SMART Extended Self-test Log Version: 1 (1 sectors) Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed: read failure 90% 12001 21048 # 2 Short offline Completed: read failure 90% 11977 21048 # 3 Extended offline Completed: read failure 90% 11977 21048 # 4 Extended offline Completed: read failure 90% 11975 21048 # 5 Extended offline Completed: read failure 90% 11951 21040 # 6 Extended offline Completed: read failure 90% 11947 21040 # 7 Extended offline Completed: read failure 90% 11947 21048 # 8 Extended offline Completed: read failure 90% 11947 21048 # 9 Extended offline Completed: read failure 90% 11947 21048 #10 Extended offline Completed: read failure 90% 11947 21048 #11 Extended offline Completed: read failure 90% 4236 99125488 #12 Extended offline Completed: read failure 90% 4232 99125488  
It should have been replaced long ago, you can clone it with ddrescue to try and recover as much data as possible

Aug 27 03:59:16 Jurassic-Nas emhttpd: SATAFIRM_S11_PNY4720002924020600B (sdd) 512 234441648  
SATAFIRM on the device name suggests it failed, constant ATA errors on the log as well, you can try to replace/swap cables to rule that out but suspect an SSD issue.

Cache is almost fully allocated, but not fully, so not sure if it's related to that, still a good idea to balance the filesystem, then reboot and post new diags after array start.

Disk problem looks more power/connection related, but the disk SMART shows some issues, so try replacing/swapping cables (power and SAS) and if issues continue I would replace the disk.
 
There are also issues with your pool it's been dropping a device:
 
Aug 12 09:50:35 UNRAID kernel: BTRFS info (device sdb1): bdev /dev/sdb1 errs: wr 4, rd 0, flush 1, corrupt 0, gen 0 Aug 12 09:50:35 UNRAID kernel: BTRFS info (device sdb1): bdev /dev/sdg1 errs: wr 36552100, rd 60558, flush 3120, corrupt 722097, gen 0  
Run a correcting scrub and also see here for better pool monitoring.

If you are passing through any GPU to a VM sometimes booting one way or the other can work better for that, for the rest it's usually the same.

Unraid gets the temps directly from the drives.

Constant ATA errors, looks more like power/connection issue, start by replacing the cables.