Leaderboard

Development on UUD 1.6 is now COMPLETE! I'm finally heading to bed! When I wake up, I will gather screenshots and finish up the content and verbiage for the release posts. Still a few more hours of work, but I'll be glad to get this one out the door. I really hope you guys like it. Lots of exciting stuff for you to discover and unpack tomorrow!

Engaging documentation mode...

@SpencerJ @limetech The Ultimate UNRAID Dashboard Version 1.6 is here! This is the largest release yet 😁. Leveraging the power of the UNRAID API I bring you Array, VM, and Docker Monitoring. This new version also adds a dedicated SSD (Cache or otherwise) monitoring section complete with TBW monitoring to show SSD % of drive life used. There are a ton of other features, enhancements, bug fixes, improvements and continued refinement of the UI and color scheme. In total, UUD Version 1.6 adds 25 new Panels across 7 sections. Enjoy! 😉 New Dependencies: Dockers: UNRAID API (Install With Default Setup / Follow Current Project Install Guide) Download from Community Apps https://github.com/ElectricBrainUK/UnraidAPI New Grafana Plugins JSON API https://grafana.com/grafana/plugins/marcusolsson-json-datasource/?pg=plugins&plcmt=featured-undefined&src=grafana_footer Run Following Command in Docker: grafana-cli plugins install marcusolsson-json-datasource Dynamic Image Panel https://grafana.com/grafana/plugins/dalvany-image-panel/?pg=plugins&plcmt=featured-undefined&src=grafana_footer Run Following Command in Docker: grafana-cli plugins install dalvany-image-panel New Grafana Data Source: "UNRAID API" Dashboard Variables Please Note: This release is an example tailored to MY UNRAID Server. The intent here is that you will take this and modify it for your Setup. You have everything you require to template new panels and tailor it to your own needs. Highlights: New UNRAID API Related Panels Dynamic Header Host Name Array Status Parity Status Mover Running (True/False) Parity Check Running (True/False) Overwatch Docker Monitoring with Real Time Dynamic Images/Statuses Dockers (Running) Dockers (Stopped) VM Monitoring with Real Time Dynamic Images/Statuses VMs (Started) VMs (Stopped) Docker Dockers (All) Docker Details Virtual Machines VMs (All) VM Details Server Hardware Shows More Detail Regarding Specific Server Hardware Specifications Array Growth Array Growth (Lifetime) Shows Array Growth Over Rolling Last 10 Years (1 Data Point Per Day) SSD (Cache) Drive Health SSD Writes (Day) Shows SSD Writes For Rolling Last 24 Hours at 15 Minute Intervals Controlled By New SSD Drive Variable SSD Writes (Year) Shows SSD Writes For Rolling Last Year at 1 Day Intervals Controlled By New SSD Drive Variable SSD Lifetime Writes Measures SSD Lifetime Writes Math Based on Manufacturer Max TB Written (TBW) Specification Color Based on Thresholds (Derived From Manufacturer TBW) SSD Lifetime Reads Measures SSD Lifetime Writes Math Based on Manufacturer Max TB Written (TBW) Specification Color Based on Thresholds (Derived From Manufacturer TBW) SSD Life Used Calculates Used Drive Life Based on Lifetime Rights Divided by Manufacturer Max TBW Math Based on Manufacture Max TB Written (TBW) Specification Color Based on Thresholds (% of Manufacturer TBW) SSD Drive Temperature (Dynamic Colors Based Temp Thresholds) Plex Library Statistics Combined Growth Chart Across All Libraries The old way was just ugly and too performance intensive This is a nice one stop shop! Completely Overhauled with New Panels with Media Type Breakdowns Across Sub Libraries Changes Variable Now Used for Varken Datasource (Set at Top of Dashboard) Updated GUI Panels/Sizes/Locations/Colors/Themes Change Uptime Panel to Fit New Theme System Power Panel Changed System Power to Bar Charts Scaled the Volts to a Range Between 1V and 12V Array Growth Changed All Panels to Rolling Timelines Today So Far = Last 24 Hours This Week So Far = Last 7 Days This Month So Far = Last 30 Days This Year So Far = Last 365 Days Plex Stats Renamed to Plex Streams Plex Heatmaps Changed All Panels to Rolling Timelines Today So Far = Last 24 Hours This Week So Far = Last 7 Days This Month So Far = Last 30 Days This Year So Far = Last 365 Days Plex History Device Types Changed Chart from Pie to Donut Stream Types Changed Chart from Pie to Donut Media Types Changed Chart from Pie to Donut Media Qualities Changed Chart from Pie to Donut Changed Panels to Rolling Timelines Today So Far = Last 24 Hours This Week So Far = Last 7 Days This Month So Far = Last 30 Days This Year So Far = Last 365 Days Plex Library Growth Changed All Panels to Rolling Timelines Today So Far = Last 24 Hours This Week So Far = Last 7 Days This Month So Far = Last 30 Days This Year So Far = Last 365 Days CPU 01 Core Load Changed Labels So Cores Reflect Only the Core Number Before: Core01, Core02, ... After: 01, 02, ... This Improves Readability and Scalability on Smaller (Non 4K Displays) Array Disk Storage Used % Field: Removed Cell Background Colors and Changed Override to Basic Gauge Improved Visual Experience and Readability Array Total Storage Used % Field: Removed Cell Background Colors and Changed Override to Basic Gauge Improved Visual Experience and Readability Flash Storage Used % Field: Removed Cell Background Colors and Changed Override to Basic Gauge Improved Visual Experience and Readability Unassigned Storage Used % Field: Removed Cell Background Colors and Changed Override to Basic Gauge Improved Visual Experience and Readability Flash Storage Used % Field: Removed Cell Background Colors and Changed Override to Basic Gauge Improved Visual Experience and Readability Drive S.M.A.R.T. Health Overview Temp (C) Field: Removed Cell Background Colors and Changed Override to Colored Text Improved Visual Experience and Readability Drive S.M.A.R.T. Health Overview Temp (C) Field: Removed Cell Background Colors and Changed Override to Colored Text Improved Visual Experience and Readability UDMA CRC Errors Field: Removed Cell Background Colors and Changed Override to Colored Text Improved Visual Experience and Readability Current Pending Sectors Field: Removed Cell Background Colors and Changed Override to Colored Text Improved Visual Experience and Readability Reallocated Sectors Field: Removed Cell Background Colors and Changed Override to Colored Text Improved Visual Experience and Readability Reallocated Events Field: Removed Cell Background Colors and Changed Override to Colored Text Improved Visual Experience and Readability Offline/Uncorrectable Field: Removed Cell Background Colors and Changed Override to Colored Text Improved Visual Experience and Readability Helium Level Field: Removed Cell Background Colors and Changed Override to Colored Text Improved Visual Experience and Readability Drive S.M.A.R.T. Health Summary Min Field: Removed Cell Background Colors and Changed Override to Colored Text Improved Visual Experience and Readability Max Field: Removed Cell Background Colors and Changed Override to Colored Text Improved Visual Experience and Readability Mean Field: Removed Cell Background Colors and Changed Override to Colored Text Improved Visual Experience and Readability Total Field: Removed Cell Background Colors and Changed Override to Colored Text Improved Visual Experience and Readability UPS Stats UPS Runtime Left Removed Exclamation Point From Panel Name Changed All Panels to Rolling Timelines Today So Far = Last 24 Hours This Week So Far = Last 7 Days This Month So Far = Last 30 Days This Year So Far = Last 365 Days Removed Cell Background Colors Improved Visual Experience and Readability Fixes/Improvements All Panels are Now Driven by Datasource Variables Adjusted All Drive Path Panels to Use Regex Resolves ROOTFS Issue Some Users Were Experiencing UUD Should Now Not Care How Your Paths are Setup and Just Work Adjusted Drive Variables to Select Distinct Based on Selected Time Interval Removes Missing/Old Drives From Panels and Removes Legacy Data Prevents Old Device IDs "SD*" From Showing Up After Reboots Provided You Select a Timeframe After the Reboot Varken Geolocation Map Fixed Bug Where Geo Map Header Was Hidden Behind UI Elements Gave Panel a New Name of "Stream Origination" Map Now Automatically Centers on Current Stream (Last Geo Hash) Changes Default Zoom Level to 3 (Zoom Out By Factor of 1) Changed Geo Location Blips to Yellow to Match Plex Color Theme Added Mouse Zooming/Scrolling (Wheel) to Map General Graphs Now Start at "0" Where Applicable (Docker Ram) % Graphs Now Cap at 100% (CPU Graphs) Drive Queries Now Correctly Account For Dynamic Host Variable (Custom Query and Parenthesis Placement) UUD 1.6 Screenshots (With Personal Info Redacted): A TREMENDOUS amount of work has gone into this release. There are a ton of people who have contributed to this release whether it be bug fixes, suggestions, improvements, or new ideas. I will do an updated post to specifically call out each and every person who helped with this 1.6 build. First, though, I just want to get this out to you guys ASAP. There are a few tips and tricks that I will also release in a post soon that will detail some of the gotchas with the UNRAID API and new Grafana Plugins. I just need some time to put that together. In the meantime, please let me know how your baseline 1.6 install is going. I really hope you guys enjoy this release!!!

Okay I pushed a new version, you can reinstall the plugin from CA to get it immediately if the update doesn't show in the plugin menu right away. @jungle it should include your fix as well.

amdgpu is the right choice for you. I think the right place to post this question would be on the RadeonTOP support. The radeon kernel modules is for GPU's I think before the 2xx series, so to speak for old GPU's.

Include ZFS in the base unraid supported filesystem. Can be used with dockers for copy on write as well as snapshot support and quotas. Would also make a great cache drive filesystem since you can use Raid-Z protection on the cache pool. Also support filesystem compression... Plus it is more mature than BTRFS. Thanks, Jeff

🙌🙌🙌🙌🙌 Epic!

You need to enable Destructive Mode in UD's main settings IIRC

It's ALIIIIVE! Thank you sir Where can I donate to you?

Ha ha. Welp, it's about to happen. Uploading code now. Should be about 1-2 hours out. Screenshots are done, and I just have to get the posts written. Welcome to the UUD community.

Sigh. I forgot to remove the int cast before it gets sent to the Settings page. Pushed yet another update. Re-install or update if available and then run through the settings again making sure to apply at least once to take the new BUS ID.

You can add or remove a subdomain to trigger the renewal process. If it fails again be sure to set the staging variable to "true", this will increase the rate limiting so you don't hit the limit when testing. Set it back to false when you have it working.

Please note that this can be very diffuculty because not every card uses the same Nuvoton chip also keep in mind that many people have APU's.

I believe that is corrent indeed, for OpenVPN atleast. I've also played around with that in the past. However, I don't think this would work if you use Wireguard. And since WireGuard and OpenVPN both would need different settings (the --device /dev/net/tun or something else for WireGuard), the privileged mode is an universal 'fix'. Unless there won't be a conflict running the container with multiple --device parameters. But I wouldn't know which one WireGuard would use.

I think i figured out the problem... I ran the 'New Permissions' task in unRAID and overwrote my permissions for my docker dir.

Laut meiner Messungen sind die von Mean Well besser, aber da sprechen wir höchstens von 0,5 Watt Differenz

Ok, thanks for answering. Next time I will post over there.

Es wird auf jeden Fall der richtige CPU Treiber mit "intel_pstate" verwendet. In der Ausgabe sieht man zB auch dass die CPU Kerne runtertakten: Scheinbar fehlen die notwendigen Treiber im Linux Kernel. Dort ist kein Comet Lake und kein Rocket Lake aufgeführt: https://github.com/torvalds/linux/blob/b74b991fb8b9d642b8fea20d6245c6e19125a305/drivers/idle/intel_idle.c#L1070 Wobei ich nicht weiß, ob das nur den Status ausgibt oder tatsächlich auch Einfluss auf den Schlafzustand der Kerne hat?!

Tested and working, thanks much.

There's my likely problem, I'm not up to date on my unraid version. Thank you for the information!

Laut hier geht es Richtung Treiber: https://www.spinics.net/lists/stable/msg420136.html @mr_cg Führe mal das aus: grep . /sys/devices/system/cpu/cpu0/cpuidle/state*/name Bei mir: /sys/devices/system/cpu/cpu0/cpuidle/state0/name:POLL /sys/devices/system/cpu/cpu0/cpuidle/state1/name:C1 /sys/devices/system/cpu/cpu0/cpuidle/state2/name:C1E /sys/devices/system/cpu/cpu0/cpuidle/state3/name:C3 /sys/devices/system/cpu/cpu0/cpuidle/state4/name:C6 /sys/devices/system/cpu/cpu0/cpuidle/state5/name:C7s /sys/devices/system/cpu/cpu0/cpuidle/state6/name:C8 /sys/devices/system/cpu/cpu0/cpuidle/state7/name:C9 /sys/devices/system/cpu/cpu0/cpuidle/state8/name:C10

Okay, I think I've got the cause. It is failing to match the Intel iGPU from your Xeon with the AMD regex (which is desired behavior) but isn't continuing on to the actual R9 Fury match. Let me figure out how to fix that as I'm using preg_match_all which should continue.

thank you for the help! Worked now!

done

Have you stopped the container at the very first start once? Please look in your gamedirectory if there is a file called runtime in there, if so, please remove this file and restart the container and wait for it to finish the startup. Have you any kind of firewall or something like PiHole in front of the Server? The Minecraft server needs exclusive internet access on the very first start since it tries to download the runtime and minecraft itself.

The Cron job runs every night at about 2. You have to check the logs for why it's not renewing the certs. I think the log is named letsencrypt. Also restart the container and post the log. Be sure to redact domain and personal info.

Hey, you figured out the right spot about your Problem. Its permissions. You can grand your cifs user permission or run openhab with the right uid and guid. Mounting sftp is another alternative. Cheers Gesendet von meinem Redmi Note 8 Pro mit Tapatalk

Thanks @b3rs3rk for your contribution. Sorry to copy/past my comment but I feel the right place is here in this support thread :} - Can you recommend me the correct kernel module to enable (I know the radeontop plugin enables the amdgpu module) for my AMD Sapphire (reference design) R9 Nano GPU? - Should it be the “radeon” kernel module? Would it be a problem if I had manually enabled radeon kernel module via the officially recommended way (boot script - which is what I have already done but haven’t tried out my GPU since I setup my unraid instance) and then also install the radeontop & gpu stats plugin? **Note 1:** I did the above and the stats plugin shows N/A for all fields. Also I did select vendor in gpu stats plugin settings but unit ID list is blank. radeontop did report correct VMem (didn’t check other stats - sorry mobile terminal isn’t that nice). **Note 2:** I have since then removed my modprobe.d directory and the radeon kernel conf file. Rebooted unRAID. Still the same as reported above. Let me know what I can do to help fix it. Thanks again! (You’re our last hope for those chugging along on a radeon/AMD GPU)

Nothing other than upgrading to v6.9.x.

In diesem Artikel beschreibt der Hersteller, wie eine VM konfiguriert werden muss: https://knowledge.starface.de/pages/viewpage.action?pageId=46564497

Ja das geht. Manche Boards unterstützen auch "Bifurcation". Da kommt es dann drauf an welchen Modus. Zb x8 x8 würde dann sogar diesen Adapter erlauben: https://www.supermicro.com/en/products/accessories/addon/AOC-SLG3-2M2.php

"user " is now a reserved share name in 6.9+, that's the likely reason its not showing up.

Da mein altes Board keine M.2 Ports hat, habe ich zwei von diesen Adaptern eingebaut: Lycom DT-120 PCIe x4 M.2 Adapter Die laufen einwandfrei bei mir.

Cache is failing to balance because it's completely full, you could try stopping the array, mounting cache manually with skip_balance, delete some data to free up some space then mount normally. If you want to try that do this: Stop array then type on the console mkdir /x mount -o skip_balance /dev/sdX1 /x X=one of the cache devices, either one is fine Then still on the console or using for example midnight commander browse to /x and delete some data, when done umount /x Start array and see if it can finish balancing.

What is the error? A log output would be very helpful.

Hi there, i'm using ASRock J3455-ITX, 16GB RAM. weird, my system is solid rock stable with 6.8.3, Jellyfin-AMD-Intel-Nvidia docker + Intel GPU Top. Capable to transcode HEVC to H.264 no less than 100fps (mostly around 120fps).

That pool is in a weird state and it's showing errors in one of the devices: Mar 18 09:03:56 Bakuzan kernel: BTRFS info (device sdb1): bdev (efault) errs: wr 2, rd 0, flush 0, corrupt 2969, gen 0 See here for more info on that for the future, for now I would suggest backing up that pool and wiping the devices, then re-create.

In the display settings it's these 2 headings. To match the dashboard color I used MS snipping tool and grabbed a sample of the background color then went to this website https://html-color-codes.info/colors-from-image/ and uploaded the image. It will then generate the HTML code for the color that you enter into the "header custom background color" line. You can also find the codes for every other color on that site to create whatever font color you want.

Keeping it but otherwise classifying it as abandonware is what the concerns are about.

Suddenly stopped working for me again last Monday night. Manually running via command line and via the plugin page works fine, automated tests just aren't working. Any ideas?

Up! Can we get at least an idea of whether the support for NFSv4 is being considered and/or actively worked on? Or do I need to start looking for another storage solution to provide that feature for me? Thanks!

Hi, I realise this is an old thread but some of your comments helped me get to a solution for this, so I made an account to post it for anybody else with the same issue Steps to route 2x the same container through a single VPN container (using sonarr and binhex-qbittorrentvpn as an example): 1. Create your VPN container. Enable privoxy, create 2x port fields (for sonarr, I did 8989:8989 and 8990:8990). If there isn't one already, create an ADDITIONAL_PORTS variable field with the comma-separated list of ports to forward. i.e. '8989,8990' without quotes 2. Create a network named after this container, i.e. container:binhex-qbittorrentvpn. Can do this by commandline with `docker network create container:binhex-qbittorrentvpn` without quotes 3. Download from CA and create first container to route, e.g. sonarr. Set 'network type' to 'container:binhex-qbittorrentvpn' (or equivalent). If it has a port field remove it, and set the /config Path to a separate appdata folder 4. Download another of the same container from CA (Note: don't do what I did and recreate from the original template or you'll have issues with Rebuild-DNDC after due to matching container IDs). Do the same setup again for the second container, call it something different, and set the /config Path to a separate appdata folder from the first one. Enable advanced mode and in the WebUI field, change the port number here to be the second port number (in my case, 8990) 5. Stop the first container, and start the second one (with the non-default port). Navigate to the default port WebUI page (192.168.X.X:8989 in my case, NOT 8990) 6. Change the port in the container settings to be the secondary port you want to use. In sonarr's case, Settings -> General -> Port Number -> 8990. Save and restart the container 7. Now start the first container, and check if you can access them both via their respective ports Hope this helps someone

Information: Pour certaines raisons, parfois il peu être nécessaire de mettre en place une limitation de RAM sur un conteneur DOCKER. Pour l'exemple j'ai choisi le conte,neur PLEX, un logiciel de streaming vidéo pour ceux qui ne connaissent pas. Si vous ne mettez pas de limitation RAM à PLEX, il peu arriver si vous avez plusieurs utilisateurs qui sollicitent votre serveur en même temps, que la quantité de RAM alloué au conteneur PLEX grimpe à plusieurs Giga de RAM. Nous n'avons pas tous 32 ou 64Go installé sur notre machine. Et si la RAM viens à saturer cela peu vous empêcher d'accéder à d'autres services hébergés sur votre serveur. PS: mon UNRAID est en français, c'est la version Bêta du coup si vous avez l'interface en anglais je vous laisse adapter les menus. Mise en place de la limitation de RAM: a) Activer l'INTERFACE AVANCÉE du conteneur b) Ajout de commande permettant la limitation RAM Après avoir activé la vue interface avancé, plusieurs options apparaissent. Ce positionner sur la ligne ( paramètre supplémentaire) et entrer la commande suivante: -m 8G info: 8G = 8Go à vous d'adapter selon votre configuration matériel. Appliquer les modifications au conteneur. c) Ajout d'une limitation CPU De base vous pouvez limiter le nombre de cœurs CPU alloué à un conteneur DOCKER. Cela permet également que le serveur reste accessible pour d'autre service installé sur votre serveur. La limitation CPU, est a mon sens surtout utile pour les applications gourmande en CPU. CONCLUSION: Attention à ne pas mettre une limitation trop basse, cela pourrais empêcher un conteneur de démarrer, ou qu'il ne fonctionne pas correctement. Cela est utile également pour des conteneurs écrit en JAVA, qui en général sont assez gourmand en RAM, ou permet d'éviter qu'un conteneur ayant un problème et "s'emballe" jusqu'à saturer la RAM et rendre le serveur inopérant. FIN

....steht gleich als 1. in der Info zum Plugin...und hier:

Hey, Thx for the reply. Ideally i would prefer docker to use its own internal network ( like in bridge mode) and have it bridge out to a different nic and a static ip address. I played around with those settings yesterday but It ended the internal and external address IPs are the same. I have 8 containers that should be kept in the 172.17.0.x subnet that docker uses and I want to use a single ip address and nic for all the containers.

Resolved: For now, you have to choose "VA API" as the transcoder and NOT Intel Quick Sync Video. Totally confusing and frustrating but VA API definitely works. I confirmed it is hitting QSV with the Intel GPU Tools container.

I also have configured letsencrypt reverse proxy for subdomain nessus.subdomain.conf Note1: include /config/nginx/auth.conf points towards my Organizr setup. You might not want to use this server { listen 443 ssl; listen [::]:443 ssl; server_name nessus.*; include /config/nginx/ssl.conf; client_max_body_size 0; include /config/nginx/auth-location.conf; location / { include /config/nginx/auth.conf; include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_nessus w.x.y.z; ## Change to IP of HOST proxy_pass https://$upstream_nessus:8834; } }

Its in seconds, and its the time to wait after starting