scooterbaga

I'm having an odd behavior where the Status/Log section is empty and says "backup is not running" when the scheduled job runs. It appears to be functioning as expected otherwise. The dockers stop, the backup files appears in the folder and continue to update, then the dockers fire back up, etc. Just no status during the process. It also seems as if the email notifications are delayed. The ones that used to fire at the beginning and during the process now all fire at the end when the backup finishes. When I first noticed it happening, I tried to run a manual backup which did nothing. (I'm assuming because it was already running.) Then wound up restarting the server and from there a manual run seemed to work as expected. Was hoping it was something simple I'm missing or a known issue before I posted logs. unraid: 6.12.10 and plugin version: 2024.03.17

Apologies for more issues to the pile... Hadn't occurred to me until I added the VNC_PW key, but this docker is going to reset the OS/OBS settings on a rebuild. Is that going to happen with every update as well? Anyone have any suggestions there? I know you can backup OBS settings. Aside from manually saving off directories, is there an easier way? Should we incorporate Syncthing into the OS, or something so we can "backup" these settings?

I think I figured this out. The docker settings are ignoring my custom VNC port value. I was able to use TightVNC after changing to the default 5901 value.

Had to delete and reinstall to get it working. Where's the option to change the vnc password in the setup? I'm unable to access the VNC from a 3rd party client? I'm using TightVNC Viewer just "closes gracefully" when I make the attempt. Couple other things. Might want to consider putting an OBS shortcut on the desktop. You may also want to update the info in the thread's first post. Thanks for your time/effort. Nice to finally be able to use this.

WebUI didn't work for me on last version, and it seemed like other comments said "wait for an update". After updating to the latest, I see this: Any help would be great. Let me know if I can provide more info. Thanks.

Hello, Looks like the NVIDIA_VISIBLE_DEVICES default value is "YOUR-GPU-IP". Should that be "YOUR-GPU-ID"? Had me trying to figure out which IP address to put there.

I use exFAT for compatibility. I use this drive on Mac, Windows, and Unraid. I'm unaware of a better/easier method without installing/maintaining additional software if there is one. Did you catch my edit regarding the drive seeming to be fine? I think attempting to read/write from the disk with the partial plugin damaged the filesystem. (Could still easily/purely be a drive issue though.)

Hello, Had some very bizarre behavior when trying to use Unassigned Devices after the creation of the Plus addon. My 4TB exFAT drive mounted and was usable in Krusader without the addon, but I was having issues. If I'm understanding what the addon does, I'm surprised the drive even mounted in the first place. I'm guessing the "base" plugin updated automatically, and fix common problems hadn't caught it yet to mention the addon? I was able to browse the exFAT drive in Krusader and start a Move process. However, it would get about 50GB in and freeze up. After a couple cancels and retries, Krusader crashed and I had to just reboot. Then the exFAT disks would no longer mount and I starting digging into UD to reinstall it, then noticed the addon. I was on 6.5.3, installed the addon, and was still unable to mount. (Very likely due to it not occurring to me to reboot after installing the addon.) Anyway, after misreading the minimum requirements for the addon, I upgraded to 6.8.0. All anecdotal at this point, and those logs are long gone. Just thought I'd mention how this presented for me in case it comes up for anyone else. There's also every chance that I'm just bad at unraid and a complete fringe case... and/or that drive is coincidentally failing. e.g. Disk sdp is the before mentioned 4TB drive. Not sure if it's the plugins not liking the format or the drive failing at this point. As the topic isn't lighting up with the issue, I'm guessing I'm fighting two things at once here and the plugins are fine. I'll have to look at the disk more in the morning. As for the non-disk failure issue... Perhaps, if it's possible and/or worth the effort, consider having the base plugin throw a warning sign for disks that require the addon? Thanks for your time/effort here and on the plugins. edit: After looking at and repairing the filesystem on the drive, it appears to be fine. I believe my initial Move process using the partial UD plugin may have borked the file system on the drive during the delete part of the Move. Just guessing, but I thought it was worth mentioning.

Did anyone figure this out? Sorting by date is a mess.