Scuro

That was it. Thanks @JorgeB I'm surprised there isn't any kind of precheck when upgrading to throw warnings about that. I didn't see any mention in the release notes.

sparedata

Anyone else with this plugin try to update to 7.3? My encrypted btrfs pool disappears and the disks show up as unassigned devices. Downgrading back to 7.2.6 restores pool. Wasn't sure if there was a conflict with this plugin.

Does anyone else have problems with the librenms container not shutting down? I've gotten everything working correctly and I'm even using the librenms dispatch. Polling, validation, everything is green and working, except when I try to stop the container. Logs show the container seeing the shutdown requests but it just doesn't shut down. This is only an issue with librenms/librenms:latest. All other docker containers are good. 2025/03/10 09:44:17 [notice] 626#626: signal 15 (SIGTERM) received from 617, exiting [10-Mar-2025 09:44:17] NOTICE: Terminating ... 2025/03/10 09:44:17 [notice] 657#657: exiting 2025/03/10 09:44:17 [notice] 658#658: exiting 2025/03/10 09:44:17 [notice] 659#659: exiting 2025/03/10 09:44:17 [notice] 725#725: exiting 2025/03/10 09:44:17 [notice] 676#676: exiting 2025/03/10 09:44:17 [notice] 662#662: exiting 2025/03/10 09:44:17 [notice] 814#814: exiting 2025/03/10 09:44:17 [notice] 664#664: exiting 2025/03/10 09:44:17 [notice] 700#700: exiting 2025/03/10 09:44:17 [notice] 757#757: exiting 2025/03/10 09:44:17 [notice] 787#787: exiting 2025/03/10 09:44:17 [notice] 844#844: exiting 2025/03/10 09:44:17 [notice] 890#890: exiting 2025/03/10 09:44:17 [notice] 919#919: exiting 2025/03/10 09:44:17 [notice] 953#953: exiting 2025/03/10 09:44:17 [notice] 987#987: exiting 2025/03/10 09:44:17 [notice] 657#657: exit 2025/03/10 09:44:17 [notice] 658#658: exit [10-Mar-2025 09:44:17] NOTICE: exiting, bye-bye! 2025/03/10 09:44:17 [notice] 814#814: exit 2025/03/10 09:44:17 [notice] 787#787: exit 2025/03/10 09:44:17 [notice] 659#659: exit 2025/03/10 09:44:17 [notice] 725#725: exit 2025/03/10 09:44:17 [notice] 676#676: exit 2025/03/10 09:44:17 [notice] 953#953: exit 2025/03/10 09:44:17 [notice] 664#664: exit 2025/03/10 09:44:17 [notice] 700#700: exit 2025/03/10 09:44:17 [notice] 919#919: exit 2025/03/10 09:44:17 [notice] 844#844: exit 2025/03/10 09:44:17 [notice] 757#757: exit 2025/03/10 09:44:17 [notice] 662#662: exit 2025/03/10 09:44:17 [notice] 890#890: exit 2025/03/10 09:44:17 [notice] 987#987: exit 2025/03/10 09:44:17 [notice] 626#626: signal 17 (SIGCHLD) received from 664 2025/03/10 09:44:17 [notice] 626#626: worker process 664 exited with code 0 2025/03/10 09:44:17 [notice] 626#626: worker process 757 exited with code 0 2025/03/10 09:44:17 [notice] 626#626: worker process 787 exited with code 0 2025/03/10 09:44:17 [notice] 626#626: worker process 919 exited with code 0 2025/03/10 09:44:17 [notice] 626#626: signal 29 (SIGIO) received 2025/03/10 09:44:17 [notice] 626#626: signal 17 (SIGCHLD) received from 919 2025/03/10 09:44:17 [notice] 626#626: signal 17 (SIGCHLD) received from 814 2025/03/10 09:44:17 [notice] 626#626: worker process 814 exited with code 0 2025/03/10 09:44:17 [notice] 626#626: worker process 657 exited with code 0 2025/03/10 09:44:17 [notice] 626#626: signal 29 (SIGIO) received 2025/03/10 09:44:17 [notice] 626#626: signal 17 (SIGCHLD) received from 657 2025/03/10 09:44:17 [notice] 626#626: signal 17 (SIGCHLD) received from 658 2025/03/10 09:44:17 [notice] 626#626: worker process 658 exited with code 0 2025/03/10 09:44:17 [notice] 626#626: signal 29 (SIGIO) received 2025/03/10 09:44:17 [notice] 626#626: signal 17 (SIGCHLD) received from 725 2025/03/10 09:44:17 [notice] 626#626: worker process 725 exited with code 0 2025/03/10 09:44:17 [notice] 626#626: worker process 953 exited with code 0 2025/03/10 09:44:17 [notice] 626#626: signal 29 (SIGIO) received 2025/03/10 09:44:17 [notice] 626#626: signal 17 (SIGCHLD) received from 953 2025/03/10 09:44:17 [notice] 626#626: signal 17 (SIGCHLD) received from 700 2025/03/10 09:44:17 [notice] 626#626: worker process 700 exited with code 0 2025/03/10 09:44:17 [notice] 626#626: worker process 662 exited with code 0 2025/03/10 09:44:17 [notice] 626#626: signal 29 (SIGIO) received 2025/03/10 09:44:17 [notice] 626#626: signal 17 (SIGCHLD) received from 662 2025/03/10 09:44:17 [notice] 626#626: signal 17 (SIGCHLD) received from 844 2025/03/10 09:44:17 [notice] 626#626: worker process 844 exited with code 0 2025/03/10 09:44:17 [notice] 626#626: signal 29 (SIGIO) received 2025/03/10 09:44:17 [notice] 626#626: signal 17 (SIGCHLD) received from 890 2025/03/10 09:44:17 [notice] 626#626: worker process 890 exited with code 0 2025/03/10 09:44:17 [notice] 626#626: signal 29 (SIGIO) received 2025/03/10 09:44:17 [notice] 626#626: signal 17 (SIGCHLD) received from 987 2025/03/10 09:44:17 [notice] 626#626: worker process 987 exited with code 0 2025/03/10 09:44:17 [notice] 626#626: signal 29 (SIGIO) received 2025/03/10 09:44:17 [notice] 626#626: signal 17 (SIGCHLD) received from 676 2025/03/10 09:44:17 [notice] 626#626: worker process 676 exited with code 0 2025/03/10 09:44:17 [notice] 626#626: signal 29 (SIGIO) received 2025/03/10 09:44:17 [notice] 626#626: signal 17 (SIGCHLD) received from 659 2025/03/10 09:44:17 [notice] 626#626: worker process 659 exited with code 0 2025/03/10 09:44:17 [notice] 626#626: exit crond: USER librenms pid 1314 cmd php /opt/librenms/artisan schedule:run --no-ansi --no-interaction > /dev/null 2>&1 crond: USER librenms pid 1317 cmd php /opt/librenms/artisan schedule:run --no-ansi --no-interaction > /dev/null 2>&1 crond: USER librenms pid 1320 cmd php /opt/librenms/artisan schedule:run --no-ansi --no-interaction > /dev/null 2>&1 crond: USER librenms pid 1323 cmd php /opt/librenms/artisan schedule:run --no-ansi --no-interaction > /dev/null 2>&1 crond: USER librenms pid 1326 cmd php /opt/librenms/artisan schedule:run --no-ansi --no-interaction > /dev/null 2>&1 crond: USER librenms pid 1329 cmd php /opt/librenms/artisan schedule:run --no-ansi --no-interaction > /dev/null 2>&1 crond: USER librenms pid 1332 cmd php /opt/librenms/artisan schedule:run --no-ansi --no-interaction > /dev/null 2>&1 crond: USER librenms pid 1335 cmd php /opt/librenms/artisan schedule:run --no-ansi --no-interaction > /dev/null 2>&1 crond: USER librenms pid 1338 cmd php /opt/librenms/artisan schedule:run --no-ansi --no-interaction > /dev/null 2>&1 crond: USER librenms pid 1341 cmd php /opt/librenms/artisan schedule:run --no-ansi --no-interaction > /dev/null 2>&1 crond: USER librenms pid 1344 cmd php /opt/librenms/artisan schedule:run --no-ansi --no-interaction > /dev/null 2>&1 crond: USER librenms pid 1347 cmd php /opt/librenms/artisan schedule:run --no-ansi --no-interaction > /dev/null 2>&1 crond: USER librenms pid 1350 cmd php /opt/librenms/artisan schedule:run --no-ansi --no-interaction > /dev/null 2>&1 crond: USER librenms pid 1353 cmd php /opt/librenms/artisan schedule:run --no-ansi --no-interaction > /dev/null 2>&1 crond: USER librenms pid 1356 cmd php /opt/librenms/artisan schedule:run --no-ansi --no-interaction > /dev/null 2>&1

Nope, your work is appreciated. Just making sure I have the update procedures correct.

When our tailscale dashboard shows our unraid tailscale client as out of date, we are reliant on the maintainers of this repository to update their code in order to update the unraid client, correct?

Please expand upon the new clone feature and make an export feature where you can export the VM + XML to any location you want for backup.

Looks like ZFS is also supported if I make separate pools.

Okay so I guess they can't be mirrored if I want to use the full space.

I have two differently sized SSDs. One is a m.2 4TB, the other a sata 2TB. I set these to be a mirrored cache. I want to use the leftover 2 TB on the m.2 for VMs. The gui doesn't seem to have any support for this but it should be possible via command line. I am however unfamiliar with the process as well as I'm unsure what the best method is for unraid to mount on boot. Is it as simple as just making an entry in Syslinux configuration?