SOULV1CE

Hello and thank you for this plugin. I am setting up on fresh Unraid install 7.2.3 and cant get my Intel iGPU to show stats. I have an Nvidia Quadro P400 card also which appears to be showing everything correctly. Any suggestions on what to try to get iGPU working is appreciated! root@OMNIUS:~# timeout -k .500 .400 intel_gpu_top -J -s 250 [ { "period": { "duration": 3.031570, "unit": "ms" }, "frequency": { "requested": 0.000000, "actual": 0.000000, "unit": "MHz" }, "interrupts": { "count": 0.000000, "unit": "irq/s" }, "rc6": { "value": 99.997790, "unit": "%" }, "power": { "GPU": 0.000000, "Package": 26.777135, "unit": "W" }, "imc-bandwidth": { "reads": 1791.108437, "writes": 346.029031, "unit": "MiB/s" }, "engines": { "Render/3D": { "busy": 0.000000, "sema": 0.000000, "wait": 0.000000, "unit": "%" }, "Blitter": { "busy": 0.000000, "sema": 0.000000, "wait": 0.000000, "unit": "%" }, "Video": { "busy": 0.000000, "sema": 0.000000, "wait": 0.000000, "unit": "%" }, "VideoEnhance": { "busy": 0.000000, "sema": 0.000000, "wait": 0.000000, "unit": "%" } }, "clients": { } } { "period": { "duration": 252.752354, "unit": "ms" }, "frequency": { "requested": 0.000000, "actual": 0.000000, "unit": "MHz" }, "interrupts": { "count": 3.956442, "unit": "irq/s" }, "rc6": { "value": 99.999997, "unit": "%" }, "power": { "GPU": 0.000000, "Package": 8.127803, "unit": "W" }, "imc-bandwidth": { "reads": 496.998551, "writes": 4.883009, "unit": "MiB/s" }, "engines": { "Render/3D": { "busy": 0.000000, "sema": 0.000000, "wait": 0.000000, "unit": "%" }, "Blitter": { "busy": 0.000000, "sema": 0.000000, "wait": 0.000000, "unit": "%" }, "Video": { "busy": 0.000000, "sema": 0.000000, "wait": 0.000000, "unit": "%" }, "VideoEnhance": { "busy": 0.000000, "sema": 0.000000, "wait": 0.000000, "unit": "%" } }, "clients": { }

@strike I think in my case I am good and dont need to do that. I had appdata set before as cache primary and array secondary storage using the path mnt/user/appdata. I think due to this the path already existed in both locations. After I moved everything off the cache drive I changed to array as primary storage and no secondary storage. Once I restored the containers everything was already pointing to the correct place. Checking everything out now and it all generally looks good - just have to make a few fixes due to something happening with my custom network.

Thank you for the reply and guidance @strike . I am reinstalling the containers now. As for your question why I want them running on the array - it is a temporary measure. I am setting up a new Unraid system side by side as I have made many changes over the years on the existing one and want to have a fresh start. I needed to empty this cache drive from the current system so I can add it to the new system. Once I migrate data over there I will continue to use cache pools again.

Ran mover to try and move everything off my cache drive onto my array. Did not stop Docker service before doing so. All of my containers show stopped now and icons are gone for them. Unable to restart them as it cannot find. I also still have ~23GB of stuff still on my cache drive that did not move. When I try to run mover again, it says file exists and then eventually gets to a point where it hangs and I have to manually stop it. My current state is that I have the Docker service disabled now, have not done anything else. 2 problems I am trying to solve are: Figure out how to move the rest of the files off the cache drive onto the array safely. Fix all of my containers that broke and get them running again off the array only. Diagnostics are attached. Many thanks for the help in advance. erasmus-diagnostics-20250822-1927.zip

@itimpi Thanks. If I wanted to go the route mentioned in Step 4 first bullet point and clear the drive quickly by reformatting it, but I already did a new config, is this possible? All I have done so far is new config and have not restarted the array. Can I re-add the removed drives to their original assignments, restart the array now with 'parity is already valid' option, and then follow the steps outlined in the link? Or would even this still require rebuilding the parity because I already did new config?

I used Unbalanced plugin to move data off 4 smaller drives in my array to larger drives. I did new config and removed the 4 small drives from the array, keeping the rest of the drive assignments as-is. Does this situation make sense for me to check the option 'parity is already valid' before starting my array again? To my understanding parity would have updated as I moved the data from the small to large drives.

Is redirecting to https when inputting a URL with http a known issue for the WebUI? I saw one previous comment asking about this back in January but havent seen anything since. My example: I put in this for WebUI label: http://[IP]:[PORT:8443]/ When I click WebUI on the container it goes to https://10.0.0.100:8443/

Thanks for this! I think it might not be necessary to have to define net.unraid.docker.managed: "composeman" because I saw it already existed by default in the docker-compose.override.yml that gets created for a project. Also I just want to mention that it works fine with using environment variables to define these as well - my setup is working correctly like this with the actual values defined in a .env file: net.unraid.docker.shell: ${LABEL_SHELL} net.unraid.docker.icon: ${LABEL_ICON_CODE-SERVER} net.unraid.docker.webui: ${LABEL_WEBUI_CODE-SERVER} Setting external: false did not work for me for an already created network in Unraid - when I tried to do this I got the error: However using network_mode: "skynet" was successful.

Thanks for this comment. I made some further progress and will share to make it more Unraid friendly. To add WebUI option for the container we can toggle Advanced View and add the following to the WebUI section http://[IP]:[PORT:8090]/ The icon URL can also be updated from the Advanced View, you are right that it wont display in the native format from Github (I think it was .svg or something). Instead I just updated used the icon from this page which is saved as .png. Also I enjoyed the little QR code Easter Egg from this one https://forums.unraid.net/uploads/monthly_2023_04/gopher.thumb.png.7ca4e3809e310e5a43056ab4aa6b6080.png I added the following to the Post Arguments for my system to redirect to the correct IP address for the PocketBase Admin UI. The default URL goes to 0.0.0.0. --http 10.0.0.100:8090 Along with your mention of adding a path mapping for database persistence, I also added the container port variable in case I need to change the host port, and also the timezone and IP scan range. These can be changed within the application as well I noticed afterwards, but I would rather have them set in the container. Here is a screenshot of my setup in case this will help anyone else in their configuration:

All disks connected through Supermicro backplane to HBA connected to motherboard. I can see operating lights on HBA and it is getting power, maybe something happened to it? I think I have another HBA I can swap out to see if that is the problem. Thank you for the quick response to my post.

Shows no device for all of my drives. Diagnostics attached. Any help is appreciated thank you. omnius-diagnostics-20230526-1028.zip

I just solved a problem I was having with adding the PAPERLESS_TRASH_DIR parameter that I wanted to share. As mentioned in the Paperless documentation the default value of this parameter is "Defaults to empty (i.e. really delete documents)." Because it is empty it is never mapped to any container path - I verified this by looking in the /paperless.conf.example and src/paperless/settings.py file. So because of this you first need to create a container variable for PAPERLESS_TRASH_DIR and map it to a container path such as /usr/src/paperless/media/trash because nothing is ever defined for this. Now that we have defined the variable to the container path, we can then proceed with mapping the container path /usr/src/paperless/media/trash to a host path such as /mnt/user/data/media/documents/paperless-ngx/media/trash/. Finally after doing this when deleting a file it should be moved to the host path folder /mnt/user/data/media/documents/paperless-ngx/media/trash/ and not be permanently deleted.

I just set this up right now and got the webUI to load. After initial pull I noticed the container stopped so I went into the logs and saw the following error: I then referenced this section of the pgAdmin docs and ran the following command in my Unraid terminal to set the needed permissions for the pgadmin user: sudo chown -R 5050:5050 /mnt/user/appdata/pgadmin4 Now when I went to start up the pgadmin4 container again all was successful and the webUI launched successfully. Hope this helps! Also I just noticed that after I typed all of this out @dreadu posted the same solution before me back in June 2022 that I completely missed because scatter brain🤦‍♂️ Leaving this comment up in case others are like me who miss it as well!

Ok thank you for the explanation! I have a BPN-SAS3-846EL1 backplane using both the J49 and J50 connections to a single LSI 9300-16i HBA. I unplugged ports 2 & 3 on the HBA. So just for me to be 100% clear, there is no redundancy benefit for me to plug these back in because this is not supported in Unraid?

Yes I have dual channel transmission cables from my backplane to HBA. I shutdown, unplugged one of the cables, rebooted and now magically the VM cache pool is valid again! So it seems it was something with the dual channel that was causing the issue maybe? Is it ok to plug in the second cable again? New diags are attached. omnius-diagnostics-20230106-0926.zip