-
Upgrading from 7.2.4 to 7.2.6 or 7.3.0 fails
Thanks JorgeB, that was the issue, my USB has been in there for years and I guess I reached the write limit and could not re-enable write so I replace the drive and I am back up and running.
-
Upgrading from 7.2.4 to 7.2.6 or 7.3.0 fails
I have 2 severs and tried to upgrade both today. the 1st went fine with no issues. When trying on the second it fails with this error. Additionally, I tried upgrading to 7.2.6 and tried updating the Community Apps and Unraid Connect, both fail. Looking at my notifications I see a couple that show the Flash drive is write protected but it appears to be read/write when I look at the permissions. plugin: installing: unRAIDServer.plg Executing hook script: pre_plugin_checks plugin: downloading: unRAIDServer.plg ... done Executing hook script: pre_plugin_checks *** *** Please update the Unraid Connect plugin before upgrading Unraid! *** plugin: run failed: '/bin/bash' returned 1 Executing hook script: post_plugin_checks plugin: updating: dynamix.unraid.net.plg Executing hook script: pre_plugin_checks plugin: downloading: dynamix.unraid.net-4.34.0-x86_64-1.txz ... plugin: dynamix.unraid.net-4.34.0-x86_64-1.txz download failure: Generic error Executing hook script: post_plugin_checks crimson-diagnostics-20260516-1250.zip
-
-
OS 6.12.3: Unable to update Docker containers
I upgraded to 6.12.11 this morning and it fixed the problem.
-
OS 6.12.3: Unable to update Docker containers
Continued to troubleshoot, changed my DNS servers as per the other threads I have seen, deleted docker image and reinstalled all dockers but still can't update on this server (Crimson) unless I use recreate in portainer. My other server (Colbalt) on the same network updates fine. cobalt-diagnostics-20240706-0654.zip crimson-diagnostics-20240706-0648.zip
-
OS 6.12.3: Unable to update Docker containers
Ok Thanks
-
OS 6.12.3: Unable to update Docker containers
After updating from the 6.11 to 6.12, I'm unable to update any docker containers unless I use recreate function in Portainer. All of the dockers still function normally however, none of the dockers will download any update data even though the system states an update is ready. I tried changing my DNS to 8.8.8.8 as suggested in this thread but that didn't fix the issue. It is frustrating that I have two servers on the same network with the same settings, one updates fine but this one has several containers that won't update. I have to use Portainer recreate to update them on this server. crimson-diagnostics-20240614-0755.zip
-
OS 6.12.3: Unable to update Docker containers
It didn't work for me. It is frustrating that I have two servers on the same network with the same settings, but one updates fine but this one has several containers that won't update. I have to use Portainer recreate to update them on this server. crimson-diagnostics-20240614-0755.zip
-
NEED HELP WITH DOCKER ISSUES AND UNABLE TO STOP ARRAY
I have had some issues with improper shutdowns and the server starting parity after every shutdown, then I had a cache drive fail so I replaced it and during parity I had another fail. I have done the following: 1. Started a new config, I preserved the Array but built the cache pool with new drives. I added my process pool back with no changes. 2. I reinstalled my dockers using the previous apps reinstall. 3. I had some freezing issues so I deleted the docker image and started over again. 4. After reinstalling all again it seemed to be fine for a couple days. Today, I started having issues with dockers running slow and refusing to stop (example SAB went from download speeds in the 200-300M range to 1-2K range) , I get a server error while trying to stop the container. I stopped the docker service and tried to restart it but it shows yes but also shows it is not running, next I tried to stop the array and restart but array won't stop because cache target is busy. This server has been running pretty solid for a few years now, I have recently upgraded my internet to 2.5G fiber and changed the router to accommodate 2.5G. My backup server is running perfect after this change. I'm having a hard time finding the issue with this one so any help would be greatly appreciated. Seems like after a reboot it is more stable but the dashboard takes a long time to load (all adblockers are disabled for that site) and I can't update the dockers because I get server errors trying to stop the dockers Thanks in advance Phil crimson-diagnostics-20230301-0032.zip
-
Need help with Docker issues and unable to stop array
Seems like after a reboot it is more stable but the dashboard takes a long time to load (all adblockers are disabled for that site) and I can't update the dockers because I get server errors trying to stop the dockers
-
Need help with Docker issues and unable to stop array
I have had some issues with improper shutdowns and the server starting parity after every shutdown, then I had a cache drive fail so I replaced it and during parity I had another fail. I have done the following: 1. Started a new config, I preserved the Array but built the cache pool with new drives. I added my process pool back with no changes. 2. I reinstalled my dockers using the previous apps reinstall. 3. I had some freezing issues so I deleted the docker image and started over again. 4. After reinstalling all again it seemed to be fine for a couple days. Today, I started having issues with dockers running slow and refusing to stop (example SAB went from download speeds in the 200-300M range to 1-2K range) , I get a server error while trying to stop the container. I stopped the docker service and tried to restart it but it shows yes but also shows it is not running, next I tried to stop the array and restart but array won't stop because cache target is busy. This server has been running pretty solid for a few years now, I have recently upgraded my internet to 2.5G fiber and changed the router to accommodate 2.5G. My backup server is running perfect after this change. I'm having a hard time finding the issue with this one so any help would be greatly appreciated. Thanks in advance Phil crimson-diagnostics-20230301-0032.zip
-
Random server freezing/lagging issues
Jorge, I changed back to 1G nic for awile and I still had the same issue. Then I swatched back to the 10Gbe nic and changed the Docker custom network type -> ipvlan and it has been running pretty good for the last couple days. I will let it run like this for a few more days but I think that was the problem. Also, I just upgraded to 6.11.0 so that may have also been the fix. Thanks for the help, I'll let you know.
-
Random server freezing/lagging issues
Ok I'll try it and let you know. Thanks for the quick response. It won't detect both lans because I disabled the 1G nic in the Bios. Can I configure with the 1G and the 10G on the same network? My switch is an unmanaged switch with 2 10G and 8 1G ports.
-
Random server freezing/lagging issues
Hey guys, I could use a little help. I have been getting a lot of random issues in the last week, High CPU usage, all threads stuck 100%, Slow access to files, Plex locking up, other docker randomly freezing and I get Server Error (no code) when I try to stop or restart the docker. When I reboot the server using the reboot button it takes more than 20 min and when it comes back up it starts a Parity check due to unclean shut down. I stopped docker and ran mover, but mover is really slow also. The only warnings I get from fix common problems is my Network adapters are configured with a non-standard MTU of 9014. I have a 10Gbs nic installed and onboard nic disabled but it gives the warning for both eth0 and eth1. Only eth0 shows on network settings. I tried downgrading to 6.10.2 but it didn't help. VM seems to be fine. My diagnostics are attached but it is after restart due to frozen GUI. crimson-diagnostics-20220917-0138.zip
-
[Solved] I Changed Router now I can't Access Unraid Dashboard
Woke up today and everything is working. Strange?
-
[Solved] I Changed Router now I can't Access Unraid Dashboard
I set up a pfsense router and now I can't access Unraid Dashboard. I booted in GUI mode, changed ip address to 10.xx.xx.xx to match the router ip scheme. Restarted and now I can't get to dashboard from network or GUI Mode. Tried starting in GUI Safe mode but just get black screen with cursor blink. In normal boot and GUI mode, I can access all shares from the network using the new ip, all autostart dockers and vms are working but I have no way of accessing the Dashboard to control anything. Following another thread I pulled the USB and copied all files then deleted the config/ssh and ssl folders, rebooted and still no luck. I also tried editing the network.cfg to old ip and swapped back to the old router and still had the same issue. I can access the internet from the unraid GUI. Any assistance would be greatly appreciated. crimson-diagnostics-20220228-1600.zip