July 27, 20241 yr Woke up and went to log into unraid but nothing was loading well and at some point it said no flash drive. I removed the flash drive and used chkdsk on windows both /f and /r which found no errors. After putting the usb back into the server I could no longer access the GUI or any dockers using the ip address, but I could still play plex files. Hooked up a monitor and keyboard to server to try and shut down but the "powerdown" command had some error that I forgot to note. Also tried unplugging the UPS so that auto shutdown would start but that didn't work. Finally I hit the power button which seems to have triggered the UPS timeout shutdown. This is a new MB install and first unraid boot was on the morning of July 26, after running a day of memtest86. In the log it seems like the error started around 2am July 27th but i could be wrong. Thanks for helping! syslog-192.168.1.69.log Edited July 27, 20241 yr by Nick2Smith
July 27, 20241 yr Community Expert Before the flash drive you were already having issues, possible a docker fork bomb: https://forums.unraid.net/bug-reports/stable-releases/61210-cannot-fork-resource-temporarily-unavailable-r3020/?tab=comments#comment-28397 But the flash also dropped, so possibly to different issues.
July 27, 20241 yr Author Thanks for the reply! Interesting, how do I check if that was the issue? Sorry I'm a noob. as mentioned in the topic you linked, do you think the flash dropping was due to a docker fork bomb or is there reason to believe it was some other thing? Noticed this using htop, any idea what it is? Edited July 27, 20241 yr by Nick2Smith
July 27, 20241 yr Community Expert The initial issues may have been that, but then the flash really dropped, there are USB errors, so possibly two issues.
July 28, 20241 yr Author Opened log and saw all those errors again. Changing the USB. Any idea how to check for the docker fork bomb?
July 28, 20241 yr Community Expert Post new diags if issues persist, you can the add an extra parameter to all containers if that is suspected,
July 28, 20241 yr Author Shinobi seemed to be making a lot of PID so I stopped that and changed the USB. That seemed to have fixed those two issues, but now I have other errors in the logs. For future reference to check PIDs by docker use "docker stats" syslog-192.168.1.69.log
July 29, 20241 yr Community Expert See if this helps: https://forums.unraid.net/topic/86114-nginx-running-out-of-shared-memory/?do=findComment&comment=1417205
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.