Gragorg

Look like something is filling your docker image. If you hit the "container size" button on docker tab is there anything obvious? Also turn on the advanced view switch on the docker tab and see if you have any orphans at the bottom of the screen.

Did you login to https://www.plex.tv/ or your local ip webgui for your server?

If you login to plex.tv website can you select a movie? If so Hit the "..." and select "get info". In the bottom left corner of the window hit "View XML". Take a look in the address bar of your browser and the the token should be at the end. You can copy this for your docker template.

You should post your diagnostics. It sounds like you put the 3 drives in the array. Typically SSDs are not recommended for the array as there is no TRIM support. If this is the case I would put the 2TB in the array and use the SSD in a pool for testing.

Yes you can remove the trial key and reboot. I would make a copy of it just in case something goes south.

Is your docker image showing full on the dashboard? Also post your diagnostics.

You can do the parity swap procedure.

Currently my parity is by far my largest drive and I agree it should skip the portion after the largest data drive. However there is no way to skip. Would be a good new feature thou.

Here is the list of approved controllers. JMB585 and Asmedia are both on the approved list. Just be sure they do not use port multipliers. So a JMB585 should be a 5 port card and an Asmedia ASM 1166 is a 6 port. Both chipsets should work well.

So when I did my parity check this month I had an issue with a drive connection resetting so it took longer than normal. When i completed the parity check it send a notification (telegram) that said it took "1 day, 9 hr, 4 min, 14 sec". In reality it took "1 day, 17 hr, 29 min, 10 sec" and I can see that clearly in the history. Yesterday I went to address the drive that was resetting connection but since I had a warm spare already in my machine I just used it to rebuild. The rebuild notification reported "1 day, 17 hr, 29 min, 10 sec" was the completion time. In reality it took "8 hr, 20 min, 35 sec" as it is clearly listed in the history. It seems to be sending the previous time. Is this a known bug?

The requirement for an array device is going to be removed in a future release. The ZFS zpool has higher performance but drives do not spin down. The array allows you mix and match hard drive sizes and expand one drive at a time when needed. It also spins down unused drives to save power but performance is limited to the performance of a single drive as data is not striped. If you lose one drive your data is covered in both cases (array and raidz). If you lose two drives the raidz pool you would lose your data while the array would only lose the two failed disks and all remaining data would be intact. You can add a second parity to the array to have a two disk fault tolerance.

Update went smoothly. Thanks for all your hard work.

I would run an extended smart test on the disk. CRC errors are usually a connection issue. However if the Realocated sector count and Reported uncorrect increase it could be a disk problem and I would change the disk. I believe CRC errors are already corrected.

This seems to be the case for me I am using macvlan with bridging disabled. What really threw my for a loop is my netgear RAXE 500 actually sees both them for the same ip while my old router did not.

Take a peak in your config folder on your usb is pro.key file present there? I assume you followed the email instructions from unraid and rebooted to take effect?