Shesakillatwo

I also experienced this issue with "binhex-krusader" several times on two different Unraid Servers. I had noted that it appeared that the "Extracting" and/or "Pull Complete" messages on a larger component fails to complete then the update jumps to the end of the update process over any remaining components. It is not always the same component where it fails. I also noted this issue today on my MariaDB Docker update which I ran a second time and it completed successfully. This feels kinda like a timeout issue or other failure to move to the Extracting or completion phase when updates are occuring. Any thoughts would be greatly appreciated. I defintiely do not want my MariaDB Docker corrupted due to a failure to complete a Docker Update.

I experienced this issue the other day as well. So I did nothing for a few days and tried the update again last night and it worked. Ii appeared to me that when this issue occurs that one of the larger components/files does not actually reach the "Pull Complete" stage after which I still have the indicator that an update is available. I have also seen this before.... Could it be an Unraid Timeout issue???

I have a Motherboard with built in ethernet. I am receiving a message through Fix Common Problems "Realtek R8168 NIC found" and "The default Realtek NIC driver is known to have issues, consider installing the driver plugin from Community Applications if you are having stability issues or trouble with networking. Search for: r8168 in Community Applications, install the plugin and reboot your server." I looked up on line and this Motherboard spec sheet says it has a "Realtek® 8111H Gigabit LAN Controller". This looks to be supported by the "RTL8168(B)/RTL8111(B) PCI Drivers" app if I am reading this correctly. I see this error but I am not experiencing and specifc issues with Stability that I have noticed. I have though noticed that if I copy several (5 to 10 for example) large video files to my media array after about 2 files copying at a speed of 100 GB, the whole process slows down to about 15GB to 30GB for the duration. THings do finish without error but the process takes a long time. I am not extremely techy at the command line and it feels like everytime I do something like this I end up with unintended negative outcomes. THese are often a challenge for me to correct. So, before I embark on adding this app/driver is this liely to correct the slowdown I see when copying multiple large files?? And are there any other concerns or should I simply ignore the error the comes into "Fix Common Problems" on this? Any thoughts would be greatly appreciated.....

So can I just go into the isos and system share settings and change them from what they are now to Array---->Cache without doing anything else? Then just wait till mover runs and then go under Settings->Global Share settings and enable the option for Exclusive Shares??? Sorry, somewhat of a newbie and do not want to cause other issues....

I have two unraid servers and while troubleshooting a different issue I noticed that the mover settings for the two servers are not quite the same for these two directories, isos and system. This seemed odd to me since they are both basically system folders. I am not having any problems or failures on this, but am a bit confused why things might be different and what the best setup is. I realize I have the option of choosing these settings regardless of what the defaults might be when building these servers but I am curious what the recommendations on these might be as they are system shares/folders. I do have cache pools on both servers and I do have two parity drives on each server. For the isos folder/share both of my unraid servers are set to Cache----->Array and both have cache as the primary storage. For the system folder/share one of my unraid servers is set to Cache----->Array and the other is set to Array---->Cache. Both again have cache as the primary storage. So, is there a best setup for best performance for this, and if I need to adjust any of these settings is that just a simple switch in the setup for these shares or do I have to do some other work?

Every time I update some of my docker containers I get the "Docker high image disk utilization" message. Over time this seems to be increasing and now has reached 80% with recent Docker updates. If I look at the container size from the Docker page/tab I see this: Name Container Writable Log onlyofficedocumentserver 3.60 GB 353 MB 476 kB binhex-krusader 2.68 GB 0 B 36.1 MB freepbx 2.07 GB 32.0 MB 36.1 kB nextcloud 1.12 GB 239 MB 7 kB guacamole 781 MB 45.9 MB 16.0 kB swag 636 MB 154 MB 16.6 kB plex 340 MB 21.5 kB 3.70 kB mariadb 306 MB 23.4 kB 5.45 kB adminer 250 MB 0 B 36.1 MB vaultwarden 214 MB 0 B 17.8 kB heimdall 182 MB 51.5 MB 6.12 kB nginx 147 MB 25.2 kB 5.90 kB Total size 12.3 GB 875 MB 72.7 MB If I then look at the Settings page I see this: Docker volume info btrfs filesystem show: Label: none uuid: "ID Removed" Total devices 1 FS bytes used 20.21GiB devid 1 size 30.00GiB used 25.52GiB path /dev/loop2 btrfs scrub status: UUID: "ID Removed" no stats available Total to scrub: 20.63GiB Rate: 0.00B/s Error summary: no errors found SInce total to Scrub is 20.63 GiB, should I do this and will is reduce the size? I looked but could not find details on the Scrub button. Also, if this is not a solution, thoughts on what might be the issue here?

I so much wanted this Docker to work but I had nothing but issues with it. I switched to running BI in a VM (had to buy a Windows 10 License for about $29 USD) and have had virtually no issues since. Maybe 2 years now? I also upgraded the VM to windows 11 since it was an option and through that it has continued to work very well. I also recall that when I made the change the Unraid CPU Usage was not really any higher with the VM than with the Docker so no real downside from my perspective..... Just an FYI.....

OK, thanks so much. I must have misinterpreted some things I read on Drive sizes. I knew you could not have data drive space larger than the Parity drive space but I thought I read if I put a physical drive in for data that is larger than the Parity drive the data drive would only use the amount up to the Parity drive limit. Thanks for clarifying that this is not possible or correct!

I have two 6TB Data Drives in my Server and all my data Drives are 4TB. I want to increase the size of several of my Data Drives from 4 TB to at least 6TB. However, when looking on line it appears that 8TB Drives are at about the same price point as the 6TB drives these days. I know and can put the 8TB data drives in place of the current 4TB drives but if I leave the current 6TB parity drives in place for now the new 8TB drive will only use 6TB. Now to my question: If I do this now to address my immediate need, and add larger parity drives later, will adding 8TB or 10TB Parity drives later immediately allow access to the remaining 2TB of space on the 8TB Data Drives I add today or will I need to do some other tweaks or adjusting to get the additional space for use?

Thanks so much for the quick reply. I am glad to hear that if using the device mapping it does not matter what port my coordinators are plugged into. That puts that concern to rest! On the question of "Did you set them to auto connect in the mappings at VM start", I am pretty sure I did but when tinkering at the time I was first setting this up maybe I made a mistake? I will see how it goes for now and let you know if I see any additional issues. Probably user error..... BTW, this is an Awesome Plugin. Before I found it I was really struggling with how I was gonna make this work for my three Home Assistant coordinators so this was a gold find for me. Thanks!

I just updated some of my USB Coordinator sticks for my Home Assistant VM running on unraid. I needed to install this plugin (which is amazing) because all three of my new coordinators were being identified as the same hardware which was causing issues with the Standard USB Pasthrough and as a result my Home Assistant would not start and displayed an execution error. After fumbling a bit I got this set up using Port mappings and it worked well. However it seemed if I rebooted the VM, not all the USB devices reconnected properly. I was able to reconnect them from the USB Manager GUI but I would prefer not to have to remember to do this everytime I reboot? So I updated my setting and mapped these coordinators as Devices which also worked. Have not rebooted and will not unless I have some issues or need updates. I was though curious if others had similar experiences and which version (port or device) you are using to map to Home Assistant? Lastly, with my coordinators mapped as devices versus ports, if I unplug a coordinator and move it to a different USB Port will it still be recognized and connect properly? I kinda assumed if I used the port method and connected to a different port when re-plugging the cordinator it might not be recognized. Thanks!

I am experiencing an issue where my USB sticks ( I have a Sonoff, Nortek, and a 433 radio) appear to randomly loose connection with Home Assistant. How did you reset the boot order mentioned above, and what order did you use?

I am installing Authelia today and had one issue that required me to run mysql_upgrade -u root -p against my existing MariaDB to get past an error in the log. I no longer see any log errors on start up but this is all I see in the Logs: time="2023-01-16T12:42:52-05:00" level=info msg="Authelia v4.37.5 is starting" time="2023-01-16T12:42:52-05:00" level=info msg="Log severity set to info" time="2023-01-16T12:42:52-05:00" level=info msg="Storage schema is being checked for updates" time="2023-01-16T12:42:52-05:00" level=info msg="Storage schema is already up to date" time="2023-01-16T13:02:56-05:00" level=info msg="Initializing server for non-TLS connections on '[::]:9098' path '/'" I did have to change the port I use from 9091 to 9098 as the 9091 port is alread in use on my network. I do not see an IP prior to the :9098 like in the install video but I and not sure why??? I am also unable to log into the app. Any help would be appreciated. Thanks!

I have purchased a Domain and setup the Cloudflared Tunnel. I am using SWAG as the Reverse Proxy. I have edited the app.subdomain.conf files for several things and I have some end points accessible from the outside world and some are not. This is what I am trying to fix. I have two Unraid Servers and the Cloudflared Docker is installed on my "dataserver". I have a few other Dockers and two VM's which I want to be able to access through the tunnel. I cannot access the VM's or the one Adguard Docker on this machine I want to despite having tried many things. I am however able to access my backup Adguard instance (which is running on a Raspberry Pi) fine through the Cloudflared tunnel. I have configured both the main and backup Cloudflare tunnels the same except for their specific IPs so I do not understand why one works and the other does not. I do have separate subdomain.conf files for each. I was also hoping to access the "VM Console(VNC)" for one of the two VM's on this unraid Server but I cannot figure out how to configure this??? I can also not access a VM on the Second Unraid Server. Again, I do not know how to configure to get to the "VM Console(VNC)" on that VM. Any help on this would be appreciated. I can access my main router from the outside the network fine through router.my_domain.com and that works. I can also access some dockers on my second unraid server "mediaserver" including plex, nextcloud, guacamole and vaultwarden but I cannot access others like my freepbx docker.

Did some more digging based on the results from the command you suggested. Found a similar post so I deleted the My Servers plugin and reinstalled it and all appears to be working now..... Thanks so much!

Lets start here cause of the differences. I ran this command on both Servers. "unraid-api report -v" The results on the bad Server are shown here: root@MediaServer:~# unraid-api report -v bash: unraid-api: command not found root@MediaServer:~# The good server retruned this information: <-----UNRAID-API-REPORT-----> SERVER_NAME: DataServer ENVIRONMENT: production UNRAID_VERSION: 6.10.2 UNRAID_API_VERSION: 2.47.1 (running) NODE_VERSION: v14.15.3 API_KEY: valid MY_SERVERS: authenticated MY_SERVERS_USERNAME: xxxxxxxxxxx RELAY: connected MOTHERSHIP: ok ONLINE_SERVERS: DataServer[owner="xxxxxxxxxxx"] OFFLINE_SERVERS: MediaServer[owner="xxxxxxxxxxx"] ALLOWED_ORIGINS: http://localhost, http://IPV4ADDRESS, https://IPV4ADDRESS, http://dataserver, https://dataserver, http://dataserver.local, https://dataserver.local, https://IPV4ADDRESS.HASH.myunraid.net, https://IPV4ADDRESS.HASH.myunraid.net:WANPORT HAS_CRASH_LOGS: no </----UNRAID-API-REPORT----->

I have two servers. One of these always shows offline in My Serversbut it looks connected? Have tried a few things but this does not ever seem to correct. Was this way in 6.9.2 and is still this way in 6.10.2. Has the latest My Servers Plugin installed. Any suggestions?

Thanks for the response. I purchased this power supply to use: https://www.amazon.com/dp/B09BNBWSWJ?ref=ppx_yo2ov_dt_b_product_details&th=1 And an extra pair of Sata Cables: https://www.amazon.com/dp/B09BN49K96?psc=1&ref=ppx_yo2ov_dt_b_product_details How I identified the Problem is on the Connectors that attach to the Power Supply there are 5 wires on each, but of the six locations wire can be attached on those connectors they are diifferent between the two cables I ordered seperately and the Sata Cables that came with the power supply. Not sure just one pin is wrong or several (thay are all Black) but the connector plugs are different. When I removed these cables and conneted with Splitter Sata cables I could get new drives to be recognized. I also put the original drives in another Unraid server I have and none of the four were recognized..... I also found the Tools - New Config a few hours after I posted and I am rebuilding parity now. Hopefully all will work! Thanks again!

I moved my all my drives to a new system two days ago and have been pulling my hair out because 4 of my 8 Data Drives were not coming up. To make a long story short, the Power cable connector on the New Power supply I bought was wired incorrectly on one of the Pins and it appears to have fried the last 4 drives from my array. Both Parity Drives, the 4 Cache Drives, and the First 4 drives in my array are all good. with the loss of the last 4 drives in my array, I would like to know if there is any way to reserect the Server with everything that was on the first 4 data drives drives and simply add 4 new drives the last drives and restore data??? My dockers, apps, etc are all on Cache or the first four drives. Let me know please!

After playing with it for a few months I went with a Windows VM instead. Has been working great since I made that move. I was also concerned as it does not appear to have any ongoing support or updates.

I have an unraid Server with two 6TB Parity Drives. I also have two 2TB Drives that I want to replace and upgrade to 4 TB. Can I power the system off and replace both at the same time so I can avoid two Individual Parity Rebuilds?

So I am using an old Asus Motherboard with an Intel® Core™ i7-3770K CPU @ 3.50GHz that I had laying around. I upped it to 32 GB of Ram. I currently have 12 1080P cameras connected to the system. I set up the Blue Iris vm using 6 of the 8 cores ( 1/5 2/6 3/7 ) leaving the 0/4 Cores for other things. I did also try it on only 4 cores but decided to leave it at 6 because when I run the GUI to do updates to Blue Iris I felt the CPU Utilization went a bit higher than I wanted. I am not yet using Deepstack and not sure I will. I was mainly trying to duplicate my old Stand alone Blue Iris Box with hopefully better performance. While I don't remember specifics I would say the performance is similar if not a bit better than the stand alone. Below is a plot of the two weeks or so since I mad the change. Average CPU for the Server sits around 35%-40% with only the Windows Service Running and goes up to about 55%-60% with the Gui open. So far no spikes or restart issue and none of the 100% CPU issues. The fact that it has been Rock Solid Stable is one of the main reasons I moved away from the Docker. Downside is I had to buy a windows 10 Key but that was only $29 USD. Worth the trade off.....

So I took the leap and set up Blue Iris with a Window 10 VM on the Same unraid Server I was running the Blue Iris Docker. I stopped the Docker and have not yet deleted it. I was also able to copy my config with the .reg file to the new VM and only had to make a few changes! I was very surprised and happy with the outcome. First, I run the BI Service on the VM so the Gui is not always running. I start the Gui when I need to make changes but leave it off otherwise. I access the cameras and normal things from my Mobile app. I found running just the Service I actually had about 5-10% bettter CPU Utilization on Server when compared to the Docker. If I start the GUI on the VM it goes about 10+% higher than the docker but again, I only run the GUI to make changes and adjustments. This said, If things continue to be stable and I have no issues over the next week or two it is my intention to delete the Docker and stay with the VM. I will ost a message after I have tested a while and made that decision.

I have never set up an Unraid VM before but am definitely open to trying it. Our of curiosity if you happen to know, how is the CPU usage on the VM when compared to the Docker? my Docker runs at about 40% CPU utilization unless the Gui is open in which case it seems to go up 8-10%. Just curious how it compares if you had actually run the Docker Version.

So after a few weeks I have some observations and questions. It appears that some times when I start this docker blue Iris appears to be starting but never full does start up and the CPU sits at 100% till I stop the docker. Once stopped if I restart it it starts up fine most of the time. In addition I upgraded from 16GB of RAM to 32GB. The docker now seems to use about 8-10% less CPU. I do though still see the Docker occasionally climb in memory use till it falls over as shown above. Some times it does this a few hours after starting the Docker and sometimes it does after a few days. This has not improved updating BlueIris. So based on your comment above I was curious if this could be a Wine issue rather than a Blue Iris issue. I know nothing about wine so if this is possibly the case any idea how to troubleshoot this? It does seem odd no one else has reported this issue???