moose1207

The server ran steady for a couple of days, and I had a restart on the 25th . I'm attaching my syslog that covers 25-27th. Hopefully this helps narrow the issue down. syslog-previous

Syslog is showing 32 gigs. Is there a way to shrink it? or do I need to delete it and have it create a new one? Can I open it in kate or something and just grab the last few days? EDIT: I just changed it to mirror to flash drive, it was chosen to send to flash on shutdown - but I think because of the crash it wasn't getting added. I will update when it crashes again.

Over the past few days my server seems to randomly crash. I cannot log into the UI, and no reply if I ping the server. I also don't have any display out of the server and cannot SSH, requiring me to hard reset. After resetting, the server seems to operate just fine... until it randomly crashes again. I have attached diagnostics- I am not sure if it contains logs from before the shutdown, I have syslog enabled and as a side note - I just looked up the syslog share and the file appears to be 34 gigs? Could this be a problem? zeus-diagnostics-20250621-1608.zip

Yea, the options are not super intuitive. After clicking around I finally saw it list the mover actions. Is there a reason why mover ignores files that list the array as primary location? Thanks for the assist!

Nevermind! Figured it out. Had to set to use cache as primary, and move to the array. Setting save location to array doesn't move files apparently.

I suspect I'm having issues with my SATA cache SSD because I have spotted errors in the log here and there recently. I ran a short smart test and it says OK, though I did not run an extended test. Moving files on and off the drive is still working fine for now. I installed a new NVME SSD, (it's still unassigned currently) and want to set it up to be the new cache drive. I set all my shares to use the array, however mover isn't moving anything to the array. Docker and VM is disabled. Mover logs just say start, and stop. Am I missing a step? zeus-diagnostics-20250613-1403.zip

Ran memtest and it passed with no issues.

Nope. I just figured that had something to do with the OS itself. Been running Unraid for years, this is the first time I've seen this.

I saw those cache drive errors as well, I recently rebuilt my server and plan to change my cache to an nvme SSD within a week or so, so I ignored it. I'm not sure about the large docker.img What causes it to grow? I had a lot of problems with my previous server hardware- and constantly had issues with containers having faults - randomly being removed, hanging and such. Is there anything I can do to fix the file - does it even matter? Anything I can do about the swap errors? Thanks.

I woke up this morning to this error. I'm trying to be self sufficient so I dug through some of the logs and did some online searching in an attempt learn and possibly come up with a solution. The solution is that this is beyond my current capabilities lol. I did see some reoccurring errors. I found a I/O error, dev sdm - Looking through the array "Var" log I was able to locate that device by serial number and that device was listed as a historical unassigned device which I then promptly removed from UD, why is a historical device generating I/o errors? No other drive in my array appears to be using dev/sdm I'm thinking the big problem is that I am seeing get_swap_device: Bad swap file entry 3fd400979278f ### [PREVIOUS LINE REPEATED 1585193 TIMES] ### Searching for this problem didn't bring up anything helpful to me. I read that a reboot will temporarily help, but I haven't rebooted yet in case it may cause some other issue to arise. What do I need to do from here? zeus-diagnostics-20250527-1345.zip

Where do you look to find this? I would like to learn for future issues so I can fix on my own. Restarting fixed all my issues. Thanks so much!

Hoping someone can point me in the right direction. I was told by a family member they couldn't login to Audiobookshelf, I saw the container needed an update and chalked it up to maybe just needing a restart. It was running at the time, and I have been using the mobile app all morning. I updated the container and it did so without issues, but then didn't start. I noticed that If i try to start any currently stopped container I get the default execution error. All my other running containers are (or appear to be) working fine. I do have a drive failing, that I plan to replace in the next couple of days. I have attached logs. I haven't tried restarting docker or the server yet. Thanks! zeus-diagnostics-20250319-1414.zip

Changing cables seems to have fixed my issues. In an interest to learn, May I ask what you saw in the diagnostics that led you to the conclusion of the cache drive/ cables being the issue? Thanks again for your help!

OK, Thanks, I'll replace cables, restart and update.

Here they are. zeus-diagnostics-20240109-1120.zip

Hello All, I just randomly started having this issue where docker fails and displays the failed to start. I read a couple forum posts from google that recommended restarting and it should be fine. I restarted my server but when it came back on it didn't detect a clean reboot. I canceled parity check and started the array yesterday and everything seemed to be fine. I went to use an application this morning and noticed docker is failed again. I see a bunch of failed I/O in the logs but I'm a noob and don't know how to tell which device is sdb1, all devices seem to be working fine. I'm not sure where to start troubleshooting so any help is greatly appreciated. EDIT: I just noticed that I also cannot login to access my shares, I am just prompted with an infinite amount of login requests DockerFailedToStart.txt syslog

Thanks, that would make sense because the server didn't crash during the rebuild - when I had dockers disabled. I'll give this a try.

Hang happened again, Noticed around 6:30. Attaching another syslog. After looking at it the last thing going on before the forced reboot appears to be fix common problems around 3 something. I removed FCP but attaching the log here in case someone can point me in a better direction. syslog2

Hello all. TL;DR Unraid keeps hanging and becoming unresponsive - Seems to happen only when dockers are enabled - Logs Attached Issue happened around 1:45 PM Today Aug 24th. I'm not new to Unraid but I am also not an expert when it comes to fully troubleshooting issues. A few days ago I had a drive with reallocated sectors get disabled. During troubleshooting I found the drive had totally failed. I got a replacement drive and rebuilt. During rebuild I had ( and am still having apparently) an issue where around 1 to 2 hours Unraid becomes completely unresponsive - no gui, and cannot ping the server. A hard reboot was all that was possible. After reading some other posts on the forum I decided to disable all docker containers - and I was able to rebuild with no issues (approximately 23 hours) Today I turned my dockers back on and I had some issues, My CPU was showing 80% usage and the server was very slow. Main page showed no disk usage, and all dockers were showing 0% CPU usage. I ran top in terminal and saw that Tailscale, Plex and my torrent docker were showing 99% usage. Eventually the server became unresponsive and I rebooted - the usage issue disappeared but my Plex docker wasn't working - after removing it a couple times and adjusting settings I fixed that issue. (not sure if its related but I'd like to be thorough) A few minutes later I decided to fire up Plex in the living room but it wouldn't connect - Try to log into Unraid and its locked up again and I cannot ping the server. At this point I don't know what is causing the issue. Because of these issues I enabled the syslog to flash option and I will attach here. Not that I know what I was looking for but I was reading through the log and saw a bunch of entries where plugins are being installed - but I never chose to update or install anything at this time. Curious to know what is doing this. syslog

Hello everyone, I'm not sure where I should start troubleshooting. I decided today I wanted to add a VM to Unraid and the only reason is to have a RetroArch or retro gaming PC remotely available. The Unraid server is currently running on an AMD FX 8350 (8 Core, 8 Threads) with 16GB of ram and I currently do not have an ssd as a cache drive- as it recently failed, so my entire server is currently made of hdd. I have very bad performance when trying to create a VM. I tried creating a Win 7 VM and after 4 hours abandoned it while it was still at the first stage. I was successful in creating an Endeavour VM (KDE Plasma) - but only after letting the install run all night. Endevour runs sluggish and it takes about 2 to 3 seconds for response after clicking on anything. I installed Conky and never saw the system rise above 3% CPU (with 6 of 8 cores allotted) or 1.5G of Ram with 8G allotted. I tried installing Lubuntu as a test - but it seems to hang at about 13%. and has not finished installing even hours later. I tried these VM's set for "auto" drive selection and have also tried selecting a specific drive with no difference. Also Checking Unraid STATS tab - the processor has never risen above 4% regardless of install and RAM sometimes seems to be used a bit but never full potential. Also i noticed if I click on VMS tab Unraid just sits there with the thinking symbol forever and never loads the list of VM's while a VM is being is installed or updated- also with the processor and RAM not loading up.. I know my server doesn't have the best hardware performance wise but I definitely don't think its so slow it should take hours to install a lightweight Linux distro. What should I look at, are there any logs I can provide you that would help? Thanks!

I'm still learning and loving it lol. I didn't realize I can set up a unique IP address for the docker and use that for navigation/forwarding. I'll try that out. Thanks!

Got it! So unfortunately with the freebie router that comcast provides they have removed access to manage it, and now you can only do a simple forward rule Port X to Port X, and NOT Port X to Port Y. I have forwarded 443 on my router and now it seems to be working right. I think I'll just buy a proper router I can manage, and ditch the comcast supplied one. Thanks!

Attached images of what I have set up. Do I need to use cloudflare for dns auth? Is there a better solution maybe?

Unless I am mistaken, Comcast routers do not allow redirects, I created a "port forward" but I think that just essentially opens the port. My only options are to select my server and then type a port number I want opened. Those port numbers I selected were 180 and 1443. In my docker container I have set up 180 -->80 and 1443-->443

Update from my issue posted above . I restarted my router and things are working better however I am still having the issue if I go to Subdomain.Mydomain.me I am directed to my ISP router login page rather than going to my docker. Entering the duckdns.com:PORT# takes me to the docker but I'm sure this is not a secure connection. Any ideas?