Kilrah

Totals aren't really helpful, you need to look at which container(s) increase.

Are you sure? What is the pool filesystem and configuration since you never mentioned it? No pool setting would result in independent drives if they're in the same pool. Detail your setup precisely.

Add those. Or update the whole template where they've been added

Yup, been running with no filter since this was released, so ~23M torrents / ~140GB DB. It's stored on a compressed zfs volume on a 250GB drive and takes about 60GB, I nuked the backup folder before looking at how much the backups were taking. I'm already taking care of backups with the Appdata Backup plugin like for everything else and the backups go to another pool so this ended up bloating both since now the appdata backups included not only the DB but the built-in backups.

If Immich runs ML on unraid it doesn't matter whether it's for 1 pic or 10000, loading the models will still take the same amount of RAM. That's not visible in the posted diags.

What is reporting that? Not seeing out of memoty messages in the syslog What did you restrict? To how much? You have containers stopping/starting frequently. 8GB is low for anything using ML.

What's with the new database backup that gets enabled by default on existing installs with no heads up? Just spent an hour figuring out why all hell broke loose on my system and fixing a pool that was thrown offline due to it. My pool bitmagnet data is stored on can't just take 7 days of full DB backups on a whim.

Again UD does it. Install Unassigned Devices Plus plugin, enable Destructive mode in settings, then you can clear/format, etc...

Use smb/nfs to mount shares.

The UD suite does all that already.

Still good practice to have one support thread per template even if you're not the container author (just mention it) as these "one thread for all" always become a jumbled mess.

No, unbalanced is for transfers within the array. You use the Unassigned Devices plugin for that.

Probably. What is that drive (and all others) connected to? Mobo or adapters?

What do you mean by "sign of the new configuration"? If you mean the type of pool (mirror/raidz/stripe...) then it'll be what you'll have set it to in the pool settings prior to adding the drive.

Bit hard to say without an actual file and json editor, chuck it in an online validator and check

Are the names different? And yes you must ensure correct start order, it's alphabetical by default but can be rearranged, any container dependent on another must start afterwards. Delays can be added to make sure the container has fully started before continuing.

Share has to be something other than "appdata" or it would be merged with the other, and the data for said container must be a subfolder of that.

That's been common knowledge for years, the problem is nobody can guarantee a particular adapter will work. These things are so generic and interchangeable that even if you buy one now and it's fine someone else buying from the same listing a couple months later may get one with no GUID because the seller changed the actual product they sell, use one with a different chip etc.

"?" button will expand all help texts in all unraid pages. Clicking on a setting's text will expand just that one.

Yeah but you'd make them "conform" to the standard layout. For example I have a "pool2" pool, that has an "appdata_pool2" share on it in which the per-container appdata folders are, and then in appdata sources I have /mnt/pool2/appdata_pool2. Then every container's folder beneath that will be seen as internal. Or you could just set those folders in "Include extra files/folders" at the bottom.

No, that just means that the plugins are now managed by the Unraid org instead of the 3rd party they were under before. No change for users.

You should not have those. Like the default /mnt/user/appdata that's supposed to be the parent folder of where appdata is located. Why not have appdata in the default share? Media you sure want separate, but...

Whenever I notice there's an update basically.

Those are not plugins but containers, so wrong place... Looks like the right one hasn't been updated in half a decade, so probably don't want that.

It's not a Docker container, so not something you can just put in CA.