Indi

This is exactly why it's confusing learning this plugin, because stop/backup/start each container makes this statement conflicting. You can't start from the top and stop from the bottom at the same time So stop/backup/start for each container is actually stopping, and starting, from the bottom up only, it does not start from top down I appreciate your patience and helping me with this, I think I got things working and splitting up the groups has helped, also knowing that start/stop is from bottom up for the specific option I have set, I'm in a much better state

It's starting to make some sense, though the one part that's unclear is the containers outside of a group, so the underlying order for all containers and the groups. For mine below, I still don't know if the VPN groups at the bottom are first to be backed up, or if it's going to start at the top when using the option "Stop/backup/start for each container". It's misunderstood for me because the start and stop are two different orders, and the very nature of stop/backup/start for each container should go line by line, but it literally could go in either direction and it's not clear which direction that is. Is it stoping/backup/starting from top down in the main list? Or because it's stopping first, is it going in reverse order from bottom up, because it says stop is that order in reverse and stopping is the first action. If it is going bottom up, then the placement of my VPN groups is wrong in the main list.

So does the "Stop will be this order in reverse" only apply when you do stop all, backup all, start all? That's why I am confused, if the start order is top to bottom, but you're using stop/backup/start for each container, if stop is the first action then it would be starting from the bottom?

So I have a 30 second delay on each on of these containers, but something still isn't right as they are all broken and down after the backup I am giving this a try to see if this works any better, basically backup the VPN containers as it's own group, then move on, but still confused on the start order. Assuming it's backwards, VPN is first to backup, then VPN2 will go next, then the rest of my containers where order doesn't matter

I am trying so hard to get this to work...but the start/stop is so confusing. I use "Stop, Backup, Start for each container". But this statement "This defines the start sequence. Stop would be this order in reverse" So if it's starting and stopping each container individually....that second statement seems contradicting. Is it backing up from Top > Down, or Down > Up?? But then using a group, it says "All Containers inside a group will be stopped by their order, backuped then started again" so, does using a group bypass the "Stop, Backup, Start for each container" option and instead it stops all, backs up all, then starts in the same order? I need my VPN containers to be up, before moving to the rest, but the ordering isn't making any sense to me and I keep running into issues with containers not working after AppData Backup runs on Mondays.

I am on Unraid 6.12.9 currently, was just moving up to 6.12.10 The below process fixed it up, things seem to be okay now and I am on 6.12.10 1. Uninstall Plugin 2. Reboot to finish upgrade to 6.12.10 3. Reinstall Plugin 4. Reboot

Went to upgrade to Unraid 6.12.10 today and got these errors, unsure what to do. Download from plugin package(s): Nvidia Driver for unRAID v6.12.10 failed! Please visit the support thread(s) before rebooting to avoid plugin issues! Nvidia Driver v470.239.06 download failed, please go to the support thread for this plugin and make a post with a screenshot from this error! I don't know why it tried to download v470.238.06, that seems wrong. I have v550.67 installed currently. The production branch is what I use, and now it says that there is no version found for this version of Unraid. Update: tried to just switch to the latest, but it's still trying to download the wrong version.

For now I moved the VPN containers to the bottom of the list in AppData Backup, so they should stop first...we will see if I can work around this. With containers that use a VPN network, anytime the VPN containers restart the containers that rely on it go through a rebuild step, this is what I assume is breaking during the process going out of order. If the VPN containers can stop/backup/start first, they should be running and ready to go when they get to the dependant containers. I will see next Monday if it helps. I feel like a simple fix for this plugin would be to add backup groups with specific start/stop orders. I could group all the VPN dependant containers together, and then AppData Backup can back these up as I specifically state. Just a thought.

I use the Appdata backup and run it weekly on Monday, however every Monday I have certain containers that don't work, primarily the ones that are behind a VPN container for the network. I've tried to fix this with the proper start order and I use the "Stop, Backup, start for each container" because it seems like it would have the least amount of conflict. Though, I think what's happening is once it gets to the Gluetun VPN container which is required for some other containers, those then break and I have to go and manually restart the containers. I might play around with stop all, backup, start instead, but has anyone had this issue and have a way around it? The start/stop order seems counter-intuitive. The order defines the start sequence...but then stopping would be that order in reverse? Why? If you're using start, backup, start for each container, why wouldn't it go down the list from top to bottom? With that methodology the Start order would be bottom to top if you're using the option for each container, if the stop order is reversed...? So the critical containers should be at the bottom, not the top?

The pentagon shape next to the container lock icon is always red for me and says the autostart order is wrong. Though I can never correct it, does clicking that icon do anything?

Will this plugin get updated to support the autostart order? I use AppData Backup and run this every Monday, but every Monday my containers don't work and I have to restart them in the correct order. If I autocorrect the start order in unraid when using this plugin, it does nothing. So the plugin cleans up the UI, but causes more work in other areas on a weekly basis for me.

Ah this is my issue, they are in a raid0 config, I wanted to test how speeds were in this config Look forward to the next version!

There is another script to modify mover tuner to exclude files and/or folders, I haven't tested this myself but plan to tonight https://gist.github.com/fritolays/da5b835080ad0a4f8a48013b7b7745d8

It's just strange, I see read/writes to all my drives in low amounts but I can't seem to find anything that's actually writing to it like this

Do these show different? I am seeing activity now and grabbed a fresh diagnostics foxdie-diagnostics-20240201-1248.zip