March 6, 20251 yr I've been having this problem for the last couple days ever since I replaced my 2x4 GB sticks of ram with 2x8. I'm not entirely sure when this occurs, but it's less than 24 hours after booting, but more than 12. When I try to login, it doesn't list the name of my server. Submitting my login info just refreshes the page and I'm unable to enter. After restarting my computer, all of my docker images are completely reset. All of the settings are gone and I have to start over. It's very frustrating. Attached are the most recent log files I found on the flashdrive. Anyone know what's going on? dadbox-diagnostics-20250305-1806.zip dadbox-diagnostics-20250305-1819.zip
March 6, 20251 yr Community Expert 8 minutes ago, connormll said: replaced my 2x4 GB sticks of ram with 2x8. Memtest is on the boot menu.
March 8, 20251 yr Author It happened again yesterday, but this time I checked to see if my docker images were still up and they were. I was able to access everything on my server except for the Unraid control panel which I couldn't login to. I was too lazy to restart my computer this time around and just let it sit. I come back today, and I'm now able to access the Unraid control panel again. Attached is the diagnostic file I downloaded dadbox-diagnostics-20250308-1321.zip Edited March 8, 20251 yr by connormll
March 9, 20251 yr Community Expert Only see some Winbind errors logged, do you know the approx time the issue started?
March 9, 20251 yr Author 7 hours ago, JorgeB said: Only see some Winbind errors logged, do you know the approx time the issue started? Started when I got new RAM a little less than a week ago. I don't know exactly when the problem occurs. I notice the problem occurs when I get home from work (~17:00 everyday) -> reboot, problem resolved but all docker images are wiped clean -> check back in the morning before I leave for work and there's no issues (~9:00) -> comeback home to find the problem again -> repeat So, sometime between 9:00 and 17:00 everyday, or sometime between 16-24 hours after boot. But like I said this most recent time, I just waited it out and I didn't need to reboot again.
March 10, 20251 yr Community Expert One thing you can try is to boot the server in safe mode with all docker containers/VMs disabled, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one, including the docker containers.
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.