huntrm

Thanks Scooter. Worked perfectly on V7.2.3. I did the following: 1) Installed Theme-Park Docker Image - changed it to ports 91 and 92 2) In my case, I went with: root_source_folder="/mnt/user/appdata/theme-park/www/css/" 3) And instead of plex.css for unraid, I swapped it for aquamarine.css: custom_css_line='<link type="text/css" rel="stylesheet" href="/webGui/styles/theme-park/css/base/unraid/aquamarine.css"/>'

Thank for the help. Removed port 80 and then re-added port 8154 mapped to port 80 and it started up fine. Only issue is that when you click on the docker icon to open up the web UI, it puts me at port 8080 which is another docker app.

I'll throw my vote in for this one. I also could use this one for my server. Thank you.

I don't use any of the options that are available after installing the theme. I simply scroll to the bottom of the configuration for the plugin and turn on Custom Styling (advanced) and then I copy/paste this in the box for the Aquamarine theme. You can try that then swap out maybe to the plex.css look. I'm running 7.1 of Unraid. table.dashboard { background: var(--transparency-dark-15); border: 1px solid var(--transparency-light-25); } table.dashboard thead.stopgap { display: none; } table.dashboard tr > td.next { border-top: 1px solid var(--transparency-light-25); color: var(--text-hover); } table.dashboard tbody { border: 1px solid var(--transparency-light-15); } </style> <link type="text/css" rel="Stylesheet" href="https://theme-park.dev/css/base/unraid/aquamarine.css" />

Well this was some work, but I was able to get V1.7 of this dashboard on 7.0.1 of Unraid working going through the thread and hacking my way through it with all the containers and configuring grafana with the various data sources. For those that try this, here are some tips for you in the order that I deployed my implementation of this dashboard: Grafana docker install: I used the official latest version, didn't make any changes except I'm using port 3003 as I'm running Homepage on 3000. Bridge mode from the instructions. InfluxDB (V1.8) docker: Used the official V1.8 version from the app store. Made no changes to the docker install. Bridge mode also, kept it at port 8086, didn't use the "alpine" version that I saw in a few places. I tried 2.x version and didn't have any luck and 1.8 works fine. Telegraf docker (this was challenging): I selected the official version also from the app store. I created a directory prior called "telegraf" first in my /mnt/user/appdata directory and I used this abbreviated version for the telegraf.conf file: https://github.com/skaterpunk/UUD/blob/main/telegraf.conf. The 10,000 line conf file that has been referenced (and is archived on the wayback machine) a few times in this thread was just too overwhelming for my skills and patience. The only thing I changed was the influxDB location and enabling the UPS for my power supply (which is working in Unraid). After uploading the .conf file into the appdata/telegraf directory, I made the following changes to the docker container before deploying it: Changed the repository to: telegraf:alpine Host mode (already enabled but important to point this out) Host path 7 points to the conf file: /mnt/user/appdata/telegraf/telegraf.conf Turn on advanced mode on upper right hand corner, then add: Extra Parameters: --entrypoint=/bin/sh Post Arguments: -c "apk add --no-cache sed && sed -i 's/su-exec telegraf/su-exec root/' /entrypoint.sh && apk update && apk upgrade && apk add smartmontools curl python3 py3-pip docker && python3 -m venv /venv && source /venv/bin/activate && pip install requests && exec /entrypoint.sh telegraf" It should begin to populate your InfluxDB. You can install a docker container called Chronograf to connect your InfluxDB and see if there's data inside that DB as V1.8 doesn't have a web UI (versus 2.x). Varken docker for Media Library/Plex Stats Varken hasn't been updated in a few years but it's still able to interface and collect stats from Tautulli and the Arrr stack of apps. For deploying it, do the following: Create a directory called varken in your appdata (e.g., /mnt/user/appdata/varken Download the sample varken.ini file and edit it for your environment. I used this example here: https://github.com/HStep20/Ultimate-Unraid-Dashboard-Guide/blob/master/appdata/GUS-varken/varken.ini I only have one instance of Sonarr so changed that to 1 and not 1,2 (same with radarr). I set ombi to false as I don't use it. For the Maxmind License, I registered at https://maxmind.com and got a free license. I copied and pasted that license into the config and uncommented that line. I finally configured InfluxDB, Tautulli, Sonarr, Radarr with their various IP addresses and API keys. I have a Ubiquiti instance, but it won't work since it requires authentication to complete the login. Copy this varken.ini into your varken directory. Deploy varken with bridge mode (preset already), correct the timezone, and make sure the config directory is correct. It will then interface with your InfluxDB. Unraid API Go to app store, search for "unraid API" and select unraid-simple-monitoring-api docker image. The port 24940 should work for you. Deploy it as-is, no changes needed. Configuring Grafana Log into grafana instance. You need to add three data sources: First, select InfluxDB - connect it to your influxDB IP address. To configure it, called it "telegrafDB" or whatever you want. HTTP URL=Your influxDB url: http://10.0.1.5:8086 (example for me) Database=telegraf HTTP method=post Save/Test Repeat these steps for Varken, name it "varkenDB" or whatever you want. Change the database to varken and HTTP method=post. Save and Test and you should be connected. For the third data source, the Unraid API, it took me some time and persistence. Here's what worked: Install new data source, which is Infinity (it supports JSON connections). Configure infinity to connect to your unraid api instance: Name=UNRAID API (I used what the author used for this dashboard, so not sure if it really matters). No Auth Base URL=http://10.0.1.5:24940/api/getServers (in my case), yours will vary (you can test it also) Enable Health Check. Set health check url to: http://10.0.1.5:24940/api/getServers (in my case) Save and Test and you should be set. All three data sources are now connected to Grafana. Download the V1.7 JSON for this dashboard and Create New Dashboard, Import JSON, select the V1.7 JSON. It will install and load. Finally, select your Host (unraid server), Telegraf Datasource: telegrafdb, Varken Datasource: varkendb, and then Unraid API Datasource: UNRAID API. Select your proper parity drive(s), Array Drive(s), Cache Drive (I don't use one), SSD Drive, and Flash Boot Drive. Stats should populate and you can then add/remove tiles for the dashboard. My only issue so far is that I'm missing the following in my dashboard: Stream Origination Tile Map - No data is showing up from Varken and the Mapping License that I have. Not sure if that will take time or I'm doing something wrong. Some Temperature and Fan Speeed Tiles aren't working. Not so worried that much about this. Hope this helps any newbs like me who are wishing to deploy this one on V7.0.1. Thanks.

Not following. This is for the plugin, which should start and connect to Pihole, correct? To begin gathering stats from it? What docker container are you referring to that I should enable Host Access? I'm running pihole independently on it's own VM on a separate piece of hardware from the unraid server - not as a docker container on the unraid server. I did see this instruction which doesn't apply in my case: Please note that if you run your PiHole in a Docker container in a Custom network like br0 you have to enable the option "Enable host access" in your Docker settings, otherwise the plugin can't connect to your PiHole instance)

Nothing. Same issue where it just won't start. Not sure if maybe the plugin is limited to only working with a pihole that's deployed on Unraid (shouldn't be). Or, if something broke in some releases with Pihole and/or Unraid. Again, I can ping the pihole instance easily from the Unraid server.

1) On the pihole at 10.0.1.18/admin, I log in with my simple password. I navigate to Settings, Web interface / API. 2) Turn on expert to display the API selection under Advanced Settings. 3) Click on Configure App Password. 4) Password is generated and I copy/paste that password (very long one with special characters and such). 5) Click on Replace App Password and I get an acknowledgement from Pihole. 6) Pihole tells me that I have to log back in and it then takes me to the login screen. 7) With that app password, I paste it in to test it and it works, taking me to the pihole dashboard. In Unraid with the Pihole Prometheus Pi-Hole Exporter, I have 10.0.1.18 and then port 80. I paste in that same app password that worked for logging in, click Change & Start. Nothing works with this approach. Running Pihole Core 6.0.5. Not sure what I'm doing wrong but the plugin just won't start up. I am able to ping 10.0.1.18 easily from the Unraid server, so connectivity shouldn't be an issue. I've also tried to mix up the IP address in the plugin, such as 10.0.1.18/admin/login.php or 10.0.1.18/admin/.

I just started playing with this today, and I'm unable to connect my pihole. Clearly their changes to their API has broken things.

So that I'm following, Theme Engine in 7.0.1 today isn't fully working or has issues, correct? This will be fixed in 7.1? Every 2-3 days, I'm losing my theme and I simply copy the custom CSS, remove the plugin, reinstall it, and then paste in the custom CSS. It gets back to working each time with this method.

I had a situation recently where my nextcloud instance stopped working with nginx proxy mgr and with tailscale. Tailscale for some reason just stopped starting up, preventing me from accessing nextcloud. I did some digging on this and did the following, which may not have solved it and instead just created a new IP to which I then changed it to the old IP for my docker instance. 1) In the tailscale docker container, change TS_STATE_DIR: = /state to TS_STATE_DIR: = /var/lib/tailscale/ 2) Tailscale will then start back up. 3) Go into your tailscale console and find the old instance and copy that IP address. Go into your new instance of that tailscale container that it's assigned to and replace the IP with the old one. Worked for me but not sure if it's the right thing to do here.

Thanks for the guidance on how to restore everything. It was very easy.

I watched it and didn't understand what youre trying to point out. If I move the SAS 10TB drive to the inner slot of 2 or 3 versus being on the outside of 1 or 4 for the backplane, everything works. Is that addressed in the video?

I'll wrap up this thread by saying that a new cable and card didn't solve the issue. It has to be a backplane and a SAS harddrive compatability issue to which I'll explain. The case is laid out as drives 1-4 on the top row and then 5-8 on the bottom row. If I drop in a 2TB SAS drive that I have into drive bay 4, it spins up with no errors and the preclear begins. If I take the problematic 10TB SAS drive and put it in that same bay 4 or even on bay 8 (both are on the far right of the case), 1024 errors happen immediately. However, if I take that same 10TB drive and put it in bay 5 (under bay 1), the preclear works fine. Looks like some sort of compatability issue that I don't feel like working on any further. It's just a bit bizarre. I didn't try to remove any security on that drive (it does have a code/serial on the top) and at first, I suspected this is the culprit but I'm unable to get a utility loaded into Unraid to solve this issue (and I don't want to deal with spinning up a linux boot drive and work from there since the drive is working in another drive bay. And to add more mystery to this one, after the 10TB SAS drive was precleared and BTRFS formatted in drive bay 5, I moved it to drive bay 4 (the problematic bay) and the array spun up with no issues/errors. I kicked off a SMART extended scan and after several hours, the famous 1024 errors popped up. I'm gonna now move that drive away from bay 4 and down to a bay 5,6,7 and re-run the SMART scan.

Done, I put Unraid in safe mode with gui, and tried the above. I still got the 1,024 read errors immediately after spinning up the disk.

Latest as of 9/12: It doesn't appear to be a card issue. The LSI card is throwing 1024 errors as before. So now let's buy a new cable to see if that is the issue. Just ordered an Oracle SAS cable SFF-8087 to SFF-8643 from the Art of the Server to see if that is the issue.

To add a little more mystery, I switched the backplane cables to the card to see what would happen. Results are: - Cable1 (where the drives are) to Port 1 on the card, I got 128 write errors - Swapped the cables so that Cable 2 would connect to Port 1 on the card, I got 1024 write errors Odd... Now I'm going to move all four drives to the lower portion of the backplane to see what happens. EDIT: Got the 1024 write errors by moving the four drives to the lower part of the backplane. Still unsure if it's a backplane, cable or card issue. New card will arrive next week and will help to rule things out. Following, I'll then order new cables and continue to work on this one. I'm really hoping its not the backplane. I'll end up living with the issue if so.

I did and same results even after I pulled the card out and reseated it. It has to be something with the hardware, and I'm guessing it's the card even though it has been working perfectly with the two SATA drives and the one SAS drive. I'm rulling out the cables since they are connecting the card to the backplane. My next step is that I've ordered an LSI card from The Art of the Server on his ebay site and I'm going to give that card a try. Maybe it has the latest firmware, better compatibility, etc. If anyone has any other suggestions, please let me know. In the meantime, I'll be waiting on this card and will give it a try.

This one is a head scratcher for me. I could use some advice on how to proceed. Hardware: Silverstone RM21-308 Case with included backplane Backplane connects to an Supermicro SAS/SATA add-on card: https://www.supermicro.com/products/accessories/addon/AOC-S3008L-L8e.php Three drives in ONE of the backplane lanes/cable are two SATA WD Reds (2x18TBs) and one SAS HGST/WD drive (10TB) CPU/Motherboard is an Intel i5-14500 and ASRock Z790M-ITX. When I add a fourth similar 10TB SAS drive in the same lane/cable for the card/backplane, Unraid will throw a few hundred write errors and it then begins a parity check (the clearing stops). HOWEVER, when I move that same exact drive to the second unused lane with no drives on it, it runs fine with the clearing process and no errors are thrown. I've had no issues at all with the drives or Unraid. Any ideas on how to proceed? BIOS updates? Firmware updates on the card (is that possible and how)? Known issue with these cards? Thank you!

Thanks for the response. So to get some clarification on your build, your SSDs are in the write cache mode, correct? What type of network are you running? 1G or 2.5G or 10G? I'm trying to just see if I'm missing something in my approach - I'm considering putting in dual SSD in mirrored mode as well for some reason, but I'm not fully sure if it's worth it. I can always put in a second NVME for write cache (but I'm not running a parity drive) - in doing so, it will help local writing from the apps/VMs to the machine, but I can achieve that with SSDs and maintain some sort of maintenance. But, right now with my 1G network, accessing the server remotely and such won't get me much advantage - however, if I'm using it locally doing all sorts of stuff, the dual SSDs for write cache might be worth it (but I'm not running parity - yet....). Anyway, thanks for reading and I plan on putting the hardware together this weekend. Will spin up Unraid at some point then, start playing with it to see if I should layer in the dual SSDs and stick with the one NVMe.

Thanks for this post, 1471. I'm heading down the same path with the Asrock, but plan on keeping it simple on the storage running Unraid. I'm planning on using a single 2TB NVME (docker, VMs, and Plex) then 2 x 18TB drives to start off with no parity. Everything is automated to offload weekly to a Synology NAS for backup, then I do offsite with Backblaze with the Synology. So, parity/redundancy/availability isn't so important to me and also, it's my understanding that if I'm running a 1G network, the write cache isn't that beneficial for me (using the NVMEs). Can you please share why the dual NVMEs (I'm assuming for write cache) in your setup and the SSDs? I'm trying to think my build out a bit further and wondering if I'm missing anything or failing to understand such builds as yours.