bombz

Hello, This is an interesting idea. I do currently use CA backup for all my current dockers, and you make a good point as the backups would get quite large if including the metadata within the plex docker folder. As you stated; you are currently running 'Plex\Library\<matadata>' appdata folder folder on a separate SSD or 'pool' -- out of curiosity, is it simple to point the PLEX docker to another SSD to use that location as the metadata, perhaps a variable that is required to be added upon deploying the PLEX docker? Can you install PLEX docker to the 'default appdata location' -- while pointing the 'metadata' DIR at another SSD disk/pool? or Are you simply pointing the whole PLEX docker instance 'appdata + metadata' at a whole different SSD disk/pool in a btrfs or zfs mirror? I am really curious to this setup because it is an excellent point if/when required to restore the docker the metadata is on a completely different disk. Please feel free to include screens or PM me as I don't want this to hijack the thread out of respect. Look forward to hearing back. Thank you.

Hello, Was reviewing this post as I am soon to be migrating back to PLEX DOCKER from another OS. Are there some 'best practices' other than this transcode recommendation regarding the PLEX DOCKER deployment that are recommended? I will keep skimming this thread and attempt to collect information. Look forward to hearing back. Thanks.

Came across this thread and this is eventually exactly what I would want to implement. Going to continue research to understand how to deploy this scheduled task. Thank you.

Hello, Could you provide some further insight regarding this? Would love to try to get this deployed and operational.

+1 on this Would love to see this in CA again

Hello, Appreciate all the posts from everyone here, based on the errors attached: Oct 21 03:08:01 UnRAID emhttpd: read SMART /dev/sdf Oct 21 03:09:47 UnRAID kernel: pcieport 0000:00:01.0: AER: Multiple Corrected error received: 0000:00:01.0 Oct 21 03:09:47 UnRAID kernel: pcieport 0000:00:01.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Oct 21 03:09:47 UnRAID kernel: pcieport 0000:00:01.0: device [8086:6f02] error status/mask=00000040/00002000 Oct 21 03:09:47 UnRAID kernel: pcieport 0000:00:01.0: [ 6] BadTLP Oct 21 03:16:14 UnRAID kernel: pcieport 0000:00:01.0: AER: Multiple Corrected error received: 0000:00:01.0 Oct 21 03:16:14 UnRAID kernel: pcieport 0000:00:01.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Oct 21 03:16:14 UnRAID kernel: pcieport 0000:00:01.0: device [8086:6f02] error status/mask=00000040/00002000 Oct 21 03:16:14 UnRAID kernel: pcieport 0000:00:01.0: [ 6] BadTLP Oct 21 03:19:37 UnRAID kernel: pcieport 0000:00:01.0: AER: Multiple Corrected error received: 0000:00:01.0 Oct 21 03:19:37 UnRAID kernel: pcieport 0000:00:01.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Oct 21 03:19:37 UnRAID kernel: pcieport 0000:00:01.0: device [8086:6f02] error status/mask=00000040/00002000 Oct 21 03:19:37 UnRAID kernel: pcieport 0000:00:01.0: [ 6] BadTLP Oct 21 03:49:51 UnRAID kernel: pcieport 0000:00:01.0: AER: Multiple Corrected error received: 0000:00:01.0 Oct 21 03:49:51 UnRAID kernel: pcieport 0000:00:01.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Oct 21 03:49:51 UnRAID kernel: pcieport 0000:00:01.0: device [8086:6f02] error status/mask=00000040/00002000 Oct 21 03:49:51 UnRAID kernel: pcieport 0000:00:01.0: [ 6] BadTLP Oct 21 04:03:13 UnRAID kernel: pcieport 0000:00:01.0: AER: Multiple Corrected error received: 0000:00:01.0 Oct 21 04:03:13 UnRAID kernel: pcieport 0000:00:01.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Oct 21 04:03:13 UnRAID kernel: pcieport 0000:00:01.0: device [8086:6f02] error status/mask=00000040/00002000 Oct 21 04:03:13 UnRAID kernel: pcieport 0000:00:01.0: [ 6] BadTLP Oct 21 04:07:04 UnRAID kernel: pcieport 0000:00:01.0: AER: Multiple Corrected error received: 0000:00:01.0 Oct 21 04:07:04 UnRAID kernel: pcieport 0000:00:01.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Oct 21 04:07:04 UnRAID kernel: pcieport 0000:00:01.0: device [8086:6f02] error status/mask=00000040/00002000 Oct 21 04:07:04 UnRAID kernel: pcieport 0000:00:01.0: [ 6] BadTLP Oct 21 04:10:54 UnRAID kernel: pcieport 0000:00:01.0: AER: Multiple Corrected error received: 0000:00:01.0 Oct 21 04:10:54 UnRAID kernel: pcieport 0000:00:01.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Oct 21 04:10:54 UnRAID kernel: pcieport 0000:00:01.0: device [8086:6f02] error status/mask=00000040/00002000 Oct 21 04:10:54 UnRAID kernel: pcieport 0000:00:01.0: [ 6] BadTLP Oct 21 04:19:07 UnRAID emhttpd: read SMART /dev/sde Oct 21 04:19:07 UnRAID emhttpd: read SMART /dev/sdo Oct 21 05:04:47 UnRAID kernel: pcieport 0000:00:01.0: AER: Multiple Corrected error received: 0000:00:01.0 Oct 21 05:04:47 UnRAID kernel: pcieport 0000:00:01.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Oct 21 05:04:47 UnRAID kernel: pcieport 0000:00:01.0: device [8086:6f02] error status/mask=00000040/00002000 Added the following: Select > Main Select > Flash Scroll down > Syslinux Configuration Unraid OS kernel /bzimage append pcie_aspm=off, initrd=/bzroot pci=noaer Also referenced this post regarding pci=noaer Since reboot, there is no further errors. Appreciate the assist here everyone! Thank you!

Thanks buddy. That was an oversight for sure. I'll mark topic as resolved. Cheers, appreciate the assist here!

Hello, I was adjusting my shares today and noticed that my disk 10 is no longer seen in the included or excluded disks I can access the disk directly via explorer or SSH The disk is online in the GUI, not sure why unraid 'shares' no longer sees it I have shut down and rebooted the server with no change to this concer. Any ideas? Thanks.

Select > Docker Section in top banner in UnRaid Select > the docker you are having the concern with Select > Edit (from the docker menu) In the 'Update Container' section: Select > Advanced View (top right of the page) Scroll down to > Path: /data: * Select > Edit In the 'Edit Configuration' window: Select > Access Mode Select > Read/Write - Slave Select > Save Select > Apply Once processing has finished go to Settings (in the top banner) Select > Fix Common Problems Select > Rescan The previous error should resolve itself. Hope that helps.

Hello, THANK YOU for this post! umount /var/lib/docker Worked perfectly to unmount disk shares on 6.12.2 Was rebooting to update to 6.12.4 and this unmount looping issue occurred. Many thanks!

Hello, Would that be in a .cfg file somewhere on the flash drive? I am trying to understand how he got it to the state it is in. Could he have done something in docker, and revproxy that made this act up in such a way? Look forward to hearing back. Thank you for your assistance with this! EDIT: Found in Settings->Management Access Thanks

Hello, Attempted with https://IP:2443 Was able to successfully connect (invalid SSL cert). Trying to attempt to understand how to set things back to normal for this instance, so the port is no longer required? Any suggestions? Thanks.

Appreciate this post. I picked up the following card recently: LSI SAS 9300-16I 12GB/S HBA BUS ADAPTER CARD IT Mode 4*SFF-8643 SATA Cable I was curious of the best way to check over the card before putting into production in UnRaid, as well confirm IT MODE is actually flashed and working correctly. Is there a step by step guide to reference before using the card? Thank you.

Hello, Stumbled across your post regarding this setup, and if you were able to figure it out successfully? My setup differs a bit as I have (2X) gateways with (2X) different WAN connections. Plan: Looking to understand how to setup the UnRaid server so the following takes place: (1X) onboard NIC This NIC has a gateway on the network as well as a WAN1 connection. Would like to to use this NIC for internal communications only. I DO NOT want to use this WAN1 connection as a primary connection. Would rather keep this as a backup, fail-over WAN1 connection (1X) PCI NIC This NIC has a gateway on the network as well as a WAN2 connection. Would like to use this PCI NIC for external communications only. Is there a way to configure UnRaid to always use this PCI NIC for the WAN2 only? I most commonly know within the Windows OS you can change the NIC priority "interface matrix" order of the NICs. I am not sure if I can set this up in the this method and was seeking some clarity. Thank you.

Hello, Quick question regarding adding an additional NIC into my current UnRaid server, will attempt to give as much detail as possible. Current Setup: (1X) onboard NIC connected to the network (WAN1) New Setup: (1X) onboard NIC (WAN1) <existing nic> (1X) PCI NIC (WAN2) <new nic> Plan: Looking to understand how to setup the UnRaid server so the following takes place: (1X) onboard NIC This NIC has a gateway on the network as well as a WAN1 connection. Would like to to use this NIC for internal communications only. I DO NOT want to use this WAN1 connection as a primary connection. Would rather keep this as a backup, fail-over WAN1 connection (1X) PCI NIC This NIC has a gateway on the network as well as a WAN2 connection. Would like to use this PCI NIC for external communications only. Is there a way to tell UnRaid to always use this PCI NIC for the WAN2 only? I most commonly know within the Windows OS you can change the NIC priority "interface matrix" order of the NICs. Is there a method that this can be set within the UnRaid OS? My hopes is I worded this correctly for a broad understanding. I am also open to suggestions from the community to assist with this plan. Appreciate your time. Thank you!

Hello, Appreciate the follow-up. I did not try those ports via the webGUI IP:PORT I will do my best to attempt these suggestions, since I am remote from the system assisting a friend, I will have them setup my remote connection back to them and see if these suggestions allow me to access the webGUI. If they do, would I be required to suggest for them to always user IP:PORT to access the webGUI moving forward, or where do you think the problem resides after investigation? Thank you.

Hello, Working on a friends system remotely who said they can no longer connect to the GUI , which i confirmed. I was able to connect via SSH with the IP address, and pull diagnostics ifconfig /boot I also performed from SSH nano /boot/config/docker.cfg and change DOCKER_ENABLED="yes" to be DOCKER_ENABLED="no" To attempt to see if it was a docker port, but that didn't seem to resolve the concern Have still been unsuccessful ... trying to figure out why webGUI is not triggering. I was curious if someone could review the attached to point me in the correct direction, if the diags show anything? Thank you in advance! tower-diagnostics-20230922-1922.zip

Hello, Ah ok -- the old ones in 6.12.* do not say deprecated on my instance. I will install 'Appdata Backup' - KluthR's Repository plugin: installing: appdata.backup.plg Executing hook script: pre_plugin_checks plugin: downloading: appdata.backup.plg ... done Executing hook script: pre_plugin_checks Checking some pre-install things... Plugin files were not present. Fresh install plugin: downloading: appdata.backup-2023.06.23.tgz ... done Extracting plugin files... Checking cron. Checking cron succeeded! ---------------------------------------------------- appdata.backup has been installed. (previously known as ca.backup2) 2022-2023, Robin Kluth Version: 2023.06.23 ---------------------------------------------------- plugin: appdata.backup.plg installed Executing hook script: post_plugin_checks Thank you for clarifying the process. All looks well. Will monitor the backups moving forward and see if there are any concerns. Thanks for all your hard work, new GUI looks great!

Right. So what am I missing? I attempt to install 2.5 (update) which states it's already installed. Regardless what I select, it states it's already installed? What am I missing to perform this installation and migration?

I attempted to update to 2.5 using the action menu Output plugin: updating: ca.backup2.plg Executing hook script: pre_plugin_checks Skipping package ca.backup2-2022.12.13-x86_64-1 (already installed) ca.backup2 has been installed. Copyright 2015-2020, Andrew Zawadzki Version: 2022.12.13 plugin: ca.backup2.plg updated Executing hook script: post_plugin_checks Updating support link I see this as well, but I am confused with the process I suppose Thoughts?

Hello, I have pushed up to the latest OS. Quick question, when I attempt to search apps, I am able to find the latest backup and restore app. However, it states to update (from the actions menu) rather than install a new instance. If I proceed will it overwrite my current instance and migrate the settings? Based on what you stated, I was understanding it as a new instance would be installed, and then migrate from the old to the new?

Hello community, Reaching out as I had a question regarding the proper process to change over to the new plugin. I have been meaning to push up my global server version from 6.11.1 to the current stable branch 6.12.1 As I usually run the update assistant before pushing the server up to the latest branch, I have one 'plugin error' pertaining to 'ca.backup2.plg' Checking for plugin compatibility Issue Found: ca.backup2.plg is deprecated for ALL unRaid versions. This does not necessarily mean you will have any issues with the plugin, but there are no guarantees. It is recommended to uninstall the plugin Before I proceed, I was curious if it is best to remove this plugin as a whole, then push up to 6.12.1, and install the new plugin. or Push up to the latest server version, then remove this old plugin, and install the newer one? Also, changing over to the newer plugin, will I have to reconfigure the settings or can I pull a backup from 'ca.backup2.plg' to import them into the newer plugin. I appreciate any feedback regarding this, and thank you all in advance :-)

Ah OK. Appreciate this information. I have been checking my share where my backups populate with 2.0 (which I currently have deployed) everything seems OK, however good to know regarding the reporting that 2.0 does not inform/log. I suppose I can wait until 6.12 (stable) before updating this app. Once 6.12 stable releases, this app (2.5) will be EOL as you stated. Will there be another new thread created or forked to 'Appdata Backup/Restore v3'?

Hello, Wait till 6.12 is stable, yet update to 6.12... that's confusing. (yes I saw the first post). Was reaching out to clarify what maybe was missing. I understand 'Appdata Backup/Restore v2' is EOL, however there were concerns with V2.5 when it was picked up and maintained, so I stuck with 2.0 until 2.5 became stable. I suppose sticking to 2.0 until 6.12 is released will be the best course of action as auto-backup is currently not operational (based on the first post) in 6.11.x

Hello, I am currently still deployed on CA Backup / Restore Appdata, due to some of the concerns when the repo was forked a few months back as there were dev concerns reported (previous thread). I am curious how things are coming along as I would like to consider moving to the latest repo. Anything to be noted before moving to the latest (issues, bugs, errors, specific deployment processes)? Current version: Thank you.