Indi

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

I am noticing the last week or so, that my two parity drives are in a constant read/write activity and normally, I never see them perform any activity outside of Parity writes or checks. Looking over my shares, I can't seem to find anything that's array only except my backups share, but that only runs on Mondays foxdie-diagnostics-20240201-1044.zip

This cache drive is ZFS (3 m.2 in raid0) with only a single dataset, the folders are a few levels down from the root share

When mover is done moving files, it's leaving the directory/folder on the cache drive, so I have hundreds and hundreds of empty folders leftover on the cache How can I get mover tuner to remove folders after it's moved the file?

My NVME drives are grey, how can I enabled these to test speeds?

Ahhh thank you! This was driving me crazy lol I couldn't figure out how to get into an existing folder view to edit things. I didn't think to click on the folder name which was my issue

How am I supposed to add containers to existing folders?....this doesn't seem possible at all. I can only create new folders.

I am new to using this plugin, I thought I understood reading the initial post on this thread on how to use it, but I am confused. I chose the default when clearing some new drives, which was one cycle. I didn't see in the details that one "cycle" is actually 5 steps? Step 1: Pre-read verification - Took 26 hours Step 2: Zeroing the disk - Took 28 hours Step 3: Write preclear sig Step 4: Verify preclear sig Step 5: (Where I am now) Post-Read in progress? 1% done. Overall, I expect this to all be done in approximately 80 hours. This seems way more extensive than if I had unraid perform it, I am not complaining though as I just stress tested the hell out of these new drives I got. Question: Is there a cycle that won't take 4 days to complete on 20TB drives? Or is this the fastest option for this plugin