Squid

Are those the correct diagnostics? They're from Nov 13th

No issues. Sab is however pretty much inconsistent all the time due to it being in written in Python instead of C like NZBGet

https://wiki.unraid.net/Manual/Changing_The_Flash_Device Any issues, https://unraid.net/contact with a copy and paste (no screenshots) of what appears within Tools - Registration

There doesn't appear to be any obvious corruption on that file. Did you try hitting "rescan" within FCP?

Sorry. Dolby Vision. I equate the two in my head. But DV is what your issue actually is. (If you play the video on your PC say with MPC-HC you'll see that the videos all have a purple tint to them if your monitor doesn't support DV (which it most likely doesn't)) Plex seems to not particularly care anymore about managing to properly render DV videos on non DV equipment, and there's a long list of complaints on their forum regarding this, especially because about a year ago it did work. Usually (I suppose), DV would be identified in the filename of whatever media you're pirating so it may be possible to tell Radarr to skip those releases and try another one, but the real issue here is Plex and you'd be best talking on the forum and join the chorus there regarding this.

There's no correct answer to that. It boils down to what port do you want to use to access it. The WebUI will figure it all out.

To run two instances of any given app, from Apps (Settings) enable allow install of second instance. Then from Installed Apps, under actions a new option will appear saying "Install Second Instance" On the template, everything will be adjusted accordingly but you will still need to change the port mappings appropriately to not conflict.

The existing instance will continue to run and another instance will also be created. No checks are done on the scheduled runs. To avoid this, you would have to put in appropriate controls into the script to check for this situation.

Don't download HDR movies unless you have an HDR 4K TV

You really should upgrade to 6.11.x But, you'd need to show a screenshot of your settings

no

Docker Folders plugin installed?

Your cache drive has been remounted as Read-Only due to corruption / IO errors Best to wait for @JorgeB to advise

You can also run docker inspect {nameOfContainer}

Those options go into Post Parameters (Advanced View) in the template

Do a rescan with FCP. That folder (users) was there when it last ran....

Strange... Ultimately, what you'd want to do is with the service disabled, delete the docker image / folder Then you'd reinstall everything you had via Apps, Previous Apps

Set the UMASK (or permissions) in the download client's settings appropriately (probably UMASK would be 0)

You run it from the command prompt.

Try a different port. If that fails, then replace the flash drive. You'll also have to reboot

Nov 20 17:59:33 nas CA Backup/Restore: Backup / Restore Completed Why not instead restore the backup you had previously made before the SSD swap? It always works Probably about 100x faster than using UnBalance to move stuff around and at least 1000x faster than doing the same thing with mover? Having you tried recreating the docker image yet?

General rule. Any random card will pass through. The difficulties come mainly via the motherboard choice, and how it's set up for IOMMU groups etc and whether if you need it the ACS override settings will work for you... When in doubt, you're always better off with full size motherboards instead of mini ATX as they at least give you more options for configurations / playing around.

Only reason for a drive to spin back up is that a read is currently happening for it. If the parity also spins back up at the same time, then a write is happening to that data drive. In terms of why, the first guess is that your docker image file (or folder) is sitting on a data disk. Alternatively, your appdata share is on a data drive. Additionally, if you're running NextCloud / Owncloud then due to their own designs, any disk which is a member of its media shares will always stay spinning.

Probably post parameters

Top of my head, the mce is because of the microcode update being issued to the CPU and is probably no issue Nov 19 16:35:03 Punisher kernel: microcode: CPU0: patch_level=0x08701021 Nov 19 16:35:03 Punisher kernel: microcode: CPU1: patch_level=0x08701021 Nov 19 16:35:03 Punisher kernel: microcode: CPU2: patch_level=0x08701021 Nov 19 16:35:03 Punisher kernel: microcode: CPU3: patch_level=0x08701021 Nov 19 16:35:03 Punisher kernel: microcode: CPU4: patch_level=0x08701021 Nov 19 16:35:03 Punisher kernel: microcode: CPU5: patch_level=0x08701021 Nov 19 16:35:03 Punisher kernel: microcode: CPU6: patch_level=0x08701021 Nov 19 16:35:03 Punisher kernel: microcode: CPU7: patch_level=0x08701021 Nov 19 16:35:03 Punisher kernel: microcode: CPU8: patch_level=0x08701021 Nov 19 16:35:03 Punisher kernel: microcode: CPU9: patch_level=0x08701021 Nov 19 16:35:03 Punisher kernel: microcode: CPU10: patch_level=0x08701021 Nov 19 16:35:03 Punisher kernel: microcode: CPU11: patch_level=0x08701021 Nov 19 16:35:03 Punisher kernel: microcode: Microcode Update Driver: v2.2. Nov 19 16:35:03 Punisher kernel: IPI shorthand broadcast: enabled Nov 19 16:35:03 Punisher kernel: sched_clock: Marking stable (11946833916, 343487151)->(12438976477, -148655410) Nov 19 16:35:03 Punisher kernel: mce: [Hardware Error]: Machine check events logged Nov 19 16:35:03 Punisher kernel: registered taskstats version 1 Nov 19 16:35:03 Punisher kernel: mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 27: faa000000000080b Nov 19 16:35:03 Punisher kernel: mce: [Hardware Error]: TSC 0 MISC d012000800000000 SYND 5d000000 IPID 1002e00000500 Nov 19 16:35:03 Punisher kernel: mce: [Hardware Error]: PROCESSOR 2:870f10 TIME 1668897207 SOCKET 0 APIC 0 microcode 8701021