daithi

Damn I think this is what happened to me. I've checked old backups and the ones that threw an error this week never had a tar.gz in the backup location. I just never noticed because I never got a notification (which I did after you made the change).

I think the same thing has happened to you as what I posted on Thursday. I haven't had a chance to do much digging, but I had a quick scan and some of my failed containers are at /mnt/cache/appdata whereas some of my successful containers are at /mnt/user/appdata. I need to clean them up before Wednesday night (next scheduled backup) and see if that makes a difference.

Last night I got an error on 4 of my containers (about 1/4). Have never seen this error before: [21.02.2024 23:31:24][ℹ️][recyclarr] Stopping recyclarr... done! (took 0 seconds) [21.02.2024 23:31:24][ℹ️][recyclarr] Should NOT backup external volumes, sanitizing them... [21.02.2024 23:31:24][⚠️][recyclarr] recyclarr does not have any volume to back up! Skipping. Please consider ignoring this container. [21.02.2024 23:31:25][ℹ️][recyclarr] Starting recyclarr... (try #1) done! ... [21.02.2024 23:41:26][ℹ️][Dozzle] No stopping needed for Dozzle: Not started! [21.02.2024 23:41:26][ℹ️][Dozzle] Should NOT backup external volumes, sanitizing them... [21.02.2024 23:41:26][⚠️][Dozzle] Dozzle does not have any volume to back up! Skipping. Please consider ignoring this container. [21.02.2024 23:41:27][ℹ️][Dozzle] Installing planned update for Dozzle... [21.02.2024 23:41:31][ℹ️][Dozzle] Starting Dozzle is being ignored, because it was not started before (or should not be started). ... [21.02.2024 23:42:23][ℹ️][jellyfin] Stopping jellyfin... done! (took 4 seconds) [21.02.2024 23:42:27][ℹ️][jellyfin] Should NOT backup external volumes, sanitizing them... [21.02.2024 23:42:27][⚠️][jellyfin] jellyfin does not have any volume to back up! Skipping. Please consider ignoring this container. [21.02.2024 23:42:27][ℹ️][jellyfin] Installing planned update for jellyfin... [21.02.2024 23:42:42][ℹ️][jellyfin] Starting jellyfin... (try #1) done! ... [21.02.2024 23:42:44][ℹ️][netdata] Stopping netdata... done! (took 2 seconds) [21.02.2024 23:42:46][ℹ️][netdata] Should NOT backup external volumes, sanitizing them... [21.02.2024 23:42:46][⚠️][netdata] netdata does not have any volume to back up! Skipping. Please consider ignoring this container. [21.02.2024 23:42:46][ℹ️][netdata] Installing planned update for netdata... [21.02.2024 23:42:57][ℹ️][netdata] Starting netdata... (try #1) done! All my other containers backed up fine without error. (Dozzle is not running, I haven't got around to fixing it since they changed the user format in the container)

Unless certain parts of the OS can be decoupled from the rest, I can't see how security updates would be pushed to people who's "Upgrade License" has expired. LT aren't going to maintain every single point release so they can push a bugfix to every Tom on 6.12.6, Dick on 6.12.8 and Harry on 7.0.1 We've seen Google do this with Android, where your Play Services or WebView can be updated through the Play Store without the Hardware OEM pushing a OS update. That has taken them years (and you could argue it's still a work in progress). And as for community developed plugins... I think it's a little unreasonable to expect volunteers to keep old versions alive. Nobody is making plugins for Photoshop 5 or Fruity Loops 12 either.

All due respect but are you willingly just ignoring the actual issues people are talking about? "I don't understand the rootcause", "The code excerpt seems quite unconclusive", "I don't see any proofs or even hints of that" The code that has been dug up literally says: "Pay your annual fee to continue receiving OS updates.": "Pay your annual fee to continue receiving OS updates.", "Your license key's OS update eligibility has expired. Please renew your license key to enable updates released after your expiration date.": "Get a Lifetime Key": "Get a Lifetime Key", "Key ineligible for future releases": "Key ineligible for future releases", People are worried that Limetech, like many other tech businesses, are going to try and pull the rug out from under them. There's a line in there that says "Get a Lifetime Key" and that has me hopeful that maybe it's all being blown out of proportion, but they need to communicate this better. What if they try and pull some bullshit like "your lifetime was for the lifetime of 6.x, now you need a "new lifetime" for 7.x? Yes 6.x has been around for a long, long time (2015 I believe). But who's to say that 7.x will last that long? What if I buy a "new lifetime" for 7.x in 2024 and then 8.x arrives in 2025? Being a holiday in the States and half of Canada, I'm not expecting any official input today. So this is probably going to stew and get even more toxic before they weigh in on anything.

I'll check it out thanks I don't think it will come at a lower price, and I'm fine with that. They would be maintaining 2 release channels it's not exactly a cost cutting opportunity.

Would love an LTS channel for Unraid. Many people are sticking with 6.11.5 or even 6.9.x releases for stability. A lot of the newer features are "nice to haves" not "must haves" for me but I wanted to update to a newer release for security patches etc. I stayed on 6.11.5 until this weekend. I know the macvlan debacle isn't entirely an Unraid problem (have seen the kernel bug report submitted by LT), but it would have been good for a lot of users if there was a 6.11.5 LTS with security updates/patches as it's almost 12 months old now. Some user facing UI improvements I would like: Native docker organization Docker Folder is dead. I'm just about to try out FolderView which looks like it will work for my needs, but it seems like the startup order management is a bit hacky. Docker is one of the main Unraid features advertised/drawing people in and this aspect is a bit lacking. Resource management/monitoring UI. Dashboard gives me a 5min graph of CPU usage but only RAM at that instant. Would like Unraid to provide a way to see my CPU/RAM usage over a longer time (hour, day, week).

Seems like the testdasi image doesn't work, I changed the repo to kylek and it worked straight away.

Thanks. Lots of housekeeping now that I'm finally brave enough to leave 6.11.5

Oh I should have '/mnt/cache/appdata/' in front of each line, that's a dumb mistake. Does it include subfolders in that format? For example if I use the GUI to add the '/Plex Media Server/Media/' folder, then the Plugin adds two lines to that text field: /mnt/cache/appdata/plex/Library/Application Support/Plex Media Server/Media/ /mnt/cache/appdata/plex/Library/Application Support/Plex Media Server/Media/localhost/ Are both lines needed or can I get rid of the second/localhost one?

Does this make sense for excluded folders for Plex?

Did you figure out what happened/how to fix it?

The same nvme drive also caches for my media array. Sabnazbd downloads to it before the mover puts it on a spinning disk. Would I need separate drives to use the Exclusive Share feature?

I've read there are maybe some performance benefits to running appdata from */mnt/cache/appdata* and bypassing the FUSE overhead. I didn't realise this when I set up my server and all my dockers are running from */mnt/user/appdata* with appdata set to cache:prefer. Cache drive is 90% free so I'm not worried about running out of space. I'm a little paranoid I'm going to break something. Plan: 1. Stop the Docker Service 2. Change *Default appdata storage location* to */mnt/cache/appdata*. Should I also change Docker Directory to something else? (eg. */mnt/cache/system/docker/docker*) 3. One by one go through the containers changing the appdata field to */mnt/cache/appdata/'container_name'* 4. Run Mover again (just to make sure) 5. Start the Docker Service Am I missing anything there? I also notice the System share has a libvirt file although I don't have any VMs. If I were to spin one up in the future, should I do something similar for that?

Thanks, seems to have updated without a hitch