MowMdown

The typical unraid user will not generally benefit from moving away from the traditional unraid array to a zpool setup. The only downside to not doing a zpool is losing out on the data integrity and verification features. Media playback does not benefit from speed of zfs data striping. Media storage does not benefit from the compression on zfs disks. For anything that is wrote once and read many times will not benefit from being stored on a zpool, with the exception I listed previously.

As for your cache pools using mirrored pools is the smart move due to cache not having it's own parity system in place in the event of a failed disk.

I personally would keep the unraid array and just combining your two 1TB SSDs into a single zfs mirror otherwise you get zero benefits from having single devices zfs zpools as you currently have.

Im in the camp of "if you don't know why you need it, you probably don't need it."

Another downside of going zfs is unraid does not present any GUI accessible options for disk recovery for zfs zpools. Everything you will need to fix/repair degraded zpools is done through command line. Are you prepared to deal with this in the event of a disk failure?

The largest downsides are all your disks must work in tandem which means no individual spin down of disks and also if you lose more disks than parity (raidz level) you lose the ENTIRE zpool worth of data.

Aug 6 16:52:37 Venus kernel: mce: [Hardware Error]: Machine check events logged Aug 6 16:52:37 Venus kernel: [Hardware Error]: Deferred error, no action required. Aug 6 16:52:37 Venus kernel: [Hardware Error]: CPU:1 (19:21:0) MC23_STATUS[-|-|-|-|-|-|Deferred|-|-]: 0x9090909090909090 Aug 6 16:52:37 Venus kernel: [Hardware Error]: IPID: 0x0000000000000000 Aug 6 16:52:37 Venus kernel: [Hardware Error]: Bank 23 is reserved. Aug 6 16:52:37 Venus kernel: [Hardware Error]: cache level: RESV, tx: INSNNo further action is required at this time, just monitor your server for future MCE errors.

The container path for thumbnails has to be /photos/thumbs for it to work.

Does the GPU show up on the Nvidia Driver Plugin page? If not, you're likely out of luck.

As for emby, did you set NVIDIA_VISIBLE_DEVICES = all

You should actually leave the fields blank that you don't intend to use. You ideally want to use "Time On Battery" only and have unraid shut down after X amount of time when on battery. Leaving everything else blank

Well im still not quite sure what the actual issue is but I do know docker.img being on an HDD isn't helping and will keep disks awake and I see in your syslog the disk constantly spinning up.

Click the thumbs down icon on the dashboard to acknowledge it.

We solved the issue in discord, basically immich creates subfolders under it's preconfigued "photos" path. Those folders have to exist in their location regardless if you set their location to another share entirely.

For example, these folders cannot be deleted(left photo) otherwise the link is broken even though these folders have been set to a different location (right photo):


The OP seems to have mover deleting the empty folders (left photo) when mover is ran which results in a broken link.

Click on the pool name and see if a scrub is running 

Appdata backup plugin would be a good first start. You can write a backup script or use one of the many dockers that can backup stuff.

You named the variables correctly but I don't think you actually created the variables, click edit and post the screenshot of the edit page for the two
See how the orange text is blank next to "Container Variable"

 
Should look like this (repeat this for the driver capabilities variable as well):
 


 
I think you missed the "key" portion the name portion is irrelevant (the name is just so you can identify it in the template)
 
It would have shown up in this list:
 

 
Like so
 
docker run -d --name='plex' --net='media-net' --pids-limit 2048 -e TZ="America/New_York" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Tower" -e HOST_CONTAINERNAME="plex" -e 'VERSION'='LATEST' -e 'NVIDIA_VISIBLE_DEVICES'='all' (this is missing from yours) -e 'NVIDIA_DRIVER_CAPABILTIES'='all' (this is also missing) -e 'PUID'='99' -e 'PGID'='100' -e '100'='100'  

The biggest thing to look at is the AMPs on the 12V rail of the PSU sticker regarding HDD counts.
 
Figure out the startup amps of the HDDs and assume they will all start up at the same time (they will at array start)

Here's an example, 45.5A is max amperage for disk startup on ALL disks, so if each disk needed 5A to start up for example, this PSU would only be able to handle 8-9 disks max starting up at the same time. Some PSUs have split 12V rails meaning if you have too many disks on a single 12V rail, no bueno.
 

I’ve had one MCE on my Ryzen based system recently on a 7beta however if it’s reoccurring you probably should evaluate your hardware.
 
unfortunately with AMD it’s not possible to read the MCE log.
 
 
 

Having a cache pool mirror never hurts in case one of the drives dies you can keep running until you can replace it, it wont bring your server down.

1. Passing a test isn't enough IMO, you need to look at the values and assess whether or not you have pending sectors, etc. The things that indicate the drive is dying.
2. If the cables are replaced and UDMA CRC errors are still occurring, it could be a bad controller.
3. The data should not be corrupt as the drive is essentially retrying to send the data until it does so successfully.
4. Check the controller and cables again.
 
UDMA CRC issues are a cable/controller communication issue. Should not have any affect on the health of the drive. Maybe check the drive's physical sata connector too?

You need to delete the codec folder and restart plex
 

You can install tmux manager plugin and use mc (midnight commander) in the terminal or you can use the unbalanced plugin or you can use Krusader docker container
 
note: if you do not use tmux and you’re running an operation in terminal, if you close the terminal window the process is killed. Tmux allows it to run essentially in the background even if you close the terminal window.

Click on the cache drive and see what the minimum free space is set to.

If you use GluetunVPN docker you do not need the qbittorrent-vpn. You would just use the standard qbittorrent docker.
 
You essentially are going to route qbit through gluetun 

I also forgot to tell you to hit the "Clear Stats" button at the bottom of the MAIN tab, this will zero out the reads/write numbers so you can see easier identify which disks have writes increasing from 0.

MegaRAID cards are not recommended, see quote from the linked post: 
 
 

Seems like a pretty solid plan. You don’t have to preclear SSDs. The purpose of preclear is to stress a mechanical drive and zero it out. 

File system overhead, totally normal.

1. Install the Intel GPU Top plugin.
 
2. Add this to the "extra parameters" field for the docker(s) you want to add the GPU to:
--device=/dev/dri  
That's it. Also just need to be on Unraid 7.
 

Hold up, what exactly are you trying to do? You are supposed to add Hydra to Sonarr/Radarr not the other way around.
 
For example, when you’re in Hydra, click config at the top, then click the big button that says “Configure NZBHydra in…”  then you click SonarrV3, add the API from sonarr and it will configure NZBhydra as an indexer inside sonarr. Repeat this for each “arr” app you’re using.
 
also when you’re configuring the URL you use the IP of your unraid machine. So if your unraid machine is “192.168.1.55” your URL is “http://192.168.1.55:5076” because 5076 is hydras port.

attached is an example