Nogami

Main system 128GB, backup 16GB. Used Supermicro servers, bought before things went crazy for pricing.

Same issue here.. Having --runtime=nvidia as an extra parameter returns an "invalid parameter" error. Removing it allows the docker to start, but without hardware transcoding.

Just tried 7.3 b2 and don't see a way of selecting v580.142 for my Quadro P600 card?

Trying to figure out why running: /usr/local/sbin/sanoid --verbose --configdir=/mnt/user/system/sanoid --cron doesn't prune local snapshots according to my rules, but if I run with debug instead /usr/local/sbin/sanoid --debug --configdir=/mnt/user/system/sanoid --cron Everything works as expected and it prunes the snapshots. Any ideas?

Thanks for this, worked fine on my main system and backup to remove the mbuffer error.

I think a reasonable timeframe for supporting old versions with upgrades that only patch major vulnerabilities is fine. Maybe 2 years tops.

Think this is pretty fair. 1 year of included upgrades is pretty standard and I don’t have an issue with this as long as they never move to a “don’t pay a sub and your existing paid software expires” (adobe’s garbage model). As long as this is not the case, it’s just a 1 year support contract and not a “subscription” in the sense of Apps where you lose everything if you don’t continue to pay. Gotta nip that line of FUD in the bud. Retaining a lifetime option that’s a bit more expensive is also quite reasonable for us long term users. There must also be a way that’s less expensive than buying an entire new license to reactivate your license if you don’t keep renewing every year and want to skip a bunch of interim upgrades and just get current. Too many companies don’t value customers that helped get them there and it would pain me if limetech went that way and only chased new subs rather than treasuring existing customers who are usually the biggest advocates.

Thanks for the update, I’ve switched to the default recent master. I’ll report back if there are any issues.

Saw this in my log from last night: seems that UPS [ups] is in OL+DISCHRG state now. Is it calibrating or do you perhaps want to set 'onlinedischarge' option? Some UPS models (e.g. CyberPower UT series) emit OL+DISCHRG when offline. This is using 2.8 stable. Didn't trigger a shutdown this time, if it was the same issue. Was only in that mode for 2 seconds, then switched back on and: UPS [email protected] on line power

Thanks for all of the testing and updates here. I've had two random NUT-related shutdowns in the last month, so I'm thinking I may have something similar, however I don't have enough logging enabled to verify everything. That my system came back online without a parity check would indicate a safe shutdown (and both my main server that monitors the UPS, and my backup server which monitors through NUT both did clean shutdowns at the same time, so I'm pretty sure that's where the issue is. Also switched my config to stable 2.8.0 to see if the problem is solved. device.model Back-UPS RS 1350MS

I have a few dockers with data inside the appdata folder, however getting an error that there's nothing inside the volume and it refuses to back anything up. [18.06.2023 19:18:20][jackett][info] Stopping jackett... [18.06.2023 19:18:25][jackett][info] done! (took 5 seconds) [18.06.2023 19:18:25][jackett][debug] Backup jackett - Container Volumeinfo: Array ( [0] => /mnt/apps/jackett_downloads/:/downloads:rw [1] => /mnt/user/appdata/jackett:/config:rw ) [18.06.2023 19:18:25][jackett][debug] usorted volumes: Array ( [0] => /mnt/user/appdata/jackett [1] => /mnt/apps/jackett_downloads ) [18.06.2023 19:18:25][jackett][info] Should NOT backup external volumes, sanitizing them... [18.06.2023 19:18:25][jackett][info] jackett does not have any volume to back up! Skipping [18.06.2023 19:18:25][jackett][info] Starting jackett... (try #1) /mnt/apps/jacket_downloads is indeed empty for /mnt/user/appdata/jackett, there's 21MB of files and riirectories in there. Note that if I enable "save external volumes" for that docker it does back it up, however the data is inside the appdata folder, so it shouldn't show as an external volume, should it? Maybe related to having my appdata on a ZFS drive in 6.12? One other small question - it's creating backups with user root, group root. Shouldn't it be nobody/users when creating on shares?

Thanks, this worked here as well when my ZFS pool hung up after doing a lot of messing with converting my appdata and cache to ZFS drives for the compression.

Any chance would could get an option (or default) show datasets to be enabled?

Really enjoying this plugin so far, makes managing my ZFS pool much easier in 6.12. My only comment would be a GUI suggestion that when you make a modification to a ZFS entry (for example renaming or adding/deleting something), it should trigger an immediate refresh on the unRAID UI, rather than waiting for the next scheduled update (~30 sec).

I've had this problem for a while, and I've done some testing and found that disabling the "unassigned devices" plugin resolves it for me on one of my servers, but not the other one. Must be plugins that insert data on the main page.