Boomháuer

This did indeed fix the non-numeric value issue. I have updated my post to reflect this. Thank you for the quick response.

FIXED: This was fixed with the 2023.04.15 release. Love the plugin, running the latest version 2023.04.04 on unRAID v6.10.2, but I'm getting an error message now: Everything seems to be working fine for me but I did search for the error here and this has happened before and was fixed with an update to the plugin. That thread is located here and was fixed with Update 2019.02.18b: Commit #53 - MINOR ISSUE: Found the actual line, checks for disksize value before calculating human readable size. Any ideas? UPDATE 1: All of the drives are active now and the error message went away, not sure if that helps debug the issue or not. Please reference the second image. UPDATE 2: Figured that it was a good time to upgrade to unRAID to v6.11.5, while all drives were spinning after rebooting the system the error message went away. As soon as I spun four disks down the same exact error message popped up again.

Changed Status to Solved

@JorgeBthank you for the suggestion. I was able to use option 1) Mount filesystem read only (safe to use) and copy the files off of the cache drive except for one Ubuntu VM. You saved me a bunch of time and I appreciate it greatly. Now to shut the server down and install the new cache drive.

Well, I may have found my problem. My cache drive is saying that it's unmountable and that's where my appdata and VMs were hanging out. SMART says that the drive is fine, am I screwed at this point? I do have a backup of the appdata folder from about three weeks ago so it's not the end of the world I guess but if I could get the cache working again that would be preferable. Thanks

As far as I know I was using the standard appdata folder, unfortunately I already tried to revert back to 6.8.3 but I will post logs in a bug report. Thanks.

Awesome, just upgraded from 6.8.3 to 6.9.0 and now I have no Docker Containers or VMs... EDIT: Just went back to 6.8.3 and they are still missing... super not happy now.

@falconexe thank you for the offer but I got busy with a few work things and am now just getting back to responding, I apologize for the delay. I'm at work now but at least able to check messages Per your request I've attached my query below, let me know what you think.

That's not it either. I edited the Current Streams to say the following: default Tautulli WHERE type = current_stream_stats AND server = 1 OR server = 2 This changed the current streams from 1 to 0 I left the Current Transcode Streams alone with the following and it's reporting correctly: default Tautulli WHERE type = current_stream_stats AND server = 1 This is reporting correctly as 1 stream Transcoding

When I try to combine them using the server = "1" AND server = "2" I get N/A instead of a number. However, I can select server = "1" or I can select server = "2" and get the appropriate number of streams. I'll work on this some more and let you know what I come up with if I find anything.

That's awesome, I'll give it a shot and let you know how it works. EDIT: Works like a charm!

@falconexe to just talk this through I'd need to create a Varken-2 datasource the same way I created the original Varken datasource and in that Varken-2 datasource I would need to reference in the configuration the Tautulli-2 instance that I need to get the second set of data from. Should I also split out the multiple Radarr and Sonarr instances while I'm at it, although since it's looking at different data and the libraries are not named the same this might not be an issue, but I figured I'd ask before I created Varken-2. Do I just go into the original Varken and remove the Tautulli-2 instance and then restart the Docker Containers to get rid of it and enable the Varken-2 datasource? I'm a little fuzzy on the datasource variable but I get the idea so I'll cross that bridge when I come to it and I'm comfortable with editing the panels in the dashboard. I do have to ask one question about the original Varken configuration. Maybe you don't know the answer to this but I thought I'd float it out there anyway and that's what is the purpose of being able to configure multiple Tautullis in Varken if we can't differentiate between the two? Do you know if this is a limitation of Grafana or how Varken is presenting the data? Just curious. Thank you for your help and the awesome UUD.

I've successfully installed and configured the UUD using the excellent The ULTIMATE UnRAID Dashboard! video series by Nate Harris however I do have a question about reporting information. I've tried searching the the answer to this but I've not had good luck so I'm just going to ask. I have two Tautulli instances, tautulli-1 and tautulli-2 configured in Varken, reporting on two different Plex servers. My question is how to I distinguish between the two servers while reporting information? As an example Current Streams, Current Transcode Streams, etc are reporting the current streams from one Tautulli server but not the other. How do I select which Tautulli instance the information is coming from? As far as I know Varken is setup correctly and I can pull certain information from each but I can't figure out the Streams issue.

Updating UD and rebooting my server fixed the problem with the symbolic links. Thanks again for your help.

@dlandon, I had already done that and the symbolic links were still there. Just to be sure I made sure that Unassigned Devices had legacy mode turned off and I unmounted and remounted the shares. The symbolic links are still showing up. Maybe the unRAID 6.9.0 upgrade will come out soon and I can reboot the server then and see if that fixes the problem. Thanks again for your help.

Okay, I decided to not fight the system as it were and went in and updated everything to /mnt/remotes/shareName and now everything seems to be working fine with two exceptions. I still have five symbolic links in /mnt/disks and I misentered /mnt/remote instead of /mntremotes with an S in a couple of places and now have a couple of symbolic links there too. Is there a way to get rid of these? I have an app I run in a Docker Container called taskcafe which had it's own taskcafe network listed under network instead of br0 or bridge. I can't remember how I got that initially setup, I haven't gone looking for the solution yet but if you happen to know off the top of your head that would be great. Regardless, thank you all for your help. Linux is not my native OS and when things go sideways on me I can only go so far before way out in the weeds.

Okay, going along on this theme I decided to rename one of the Unassigned Devices Mount Point names. I changed DROBO5N2_Music to DROBO_Music. Krusader still showed it as a file and wouldn't do anything but pop up the dialogue box on what app to open it with however in the Terminal command line I was able to navigate to /mnt/disks and do a directory. I could still see the DROBO5N2_Music which should have gone away I would have though and I also saw the new DROBO_Music@ with an "@" at the end of it. However, I was still able to /mnt/disks/DROBO_Music, get a directory and see everything like I should. So it's looking like the Unassigned Devices data has gotten corrupt maybe and I don't know where to go clear that out so that I can recreate these shares?

@trurl, so I went in and checked and turned on Legacy Mount Point Compatibility although I don't ever remember having to do that before but it did give me different results from what I was seeing before so progress I guess? Now all 10 SMB Shares that show up in Unassigned Devices are showing up in Krusader BUT half of them are showing up as directories and half of them are showing up as files. The ones that are showing up as directories are still empty and the ones that are files ask me what I want to use to open them when I click on them. I've enclosed a PIC of what I'm seeing below.

@trurl, thank you for the reply however per my post I'm already using Unassigned Devices and like I said everything was working fine before the server lost power. I also just went back to make sure that the paths were set to RW/Slave on all of the appropriate Containers and they are. Any other ideas of what I could look at?

(SOLVED) The issues was fixed by changing my Docker Container mount points from /mnt/disks/xxxx to /mnt/remotes/xxxx. HELP! Power outage early this morning and the unRAID server didn't shutdown gracefully even with a UPS... which is a separate issue. I've been working on this off and on all day but I can't get it working correctly. The issue at hand is complicated but here goes. Unassigned Devices has 10 mounted SMB Shares, they have worked wonderfully for 250+ days of uptime until this morning. I can click on any of the Mount Points in Unassigned Devices and see all of the files that I expect to see. However, when I go into a Docker Container, even though the path is there it doesn't see any files. So for instance if I go into Krusader it's only seeing eight of the 10 shares and if I go into one of those shares it's not showing all of the directories that are supposed to be there and and inside of the directories that are there they are empty. If I access them from my Windows 10 PC all of the files and directories are there as expected. To try and fix this I have done the following: - Stopped and Restarted the Array - Rebooted the unRAID Server - Recreated the shares under Unassigned Devices - Removed and reinstalled Unassigned Devices - Removed and reinstalled Krusader - Deleted the whole Docker images and reinstalled all of the Containers... two of which I can't get reconfigured because I can't remember how to setup a different network name Needless to say none of these things worked. Any help or ideas would be GREATLY appreciated as I'm at the end of my rope with this. unraid-diagnostics-20210108-1842.zip