October 16, 2025Oct 16 Recently, from what I can see at random I suddenly can not access the Web GUI. The last couple of months this has happened about once a week.I have to do shut off /turn on the computer to get the GUI back.I have attached my diagnostics but I don't know if they are any use, as I just had a bzfirmware error on reboot so the server is now rebuilding parity. I can see a bunch of CSUM errors in the log as of now, but I am lost as to wether this is a problem in itself or if it could be related.I also share an overview of my dockers:Any help is greatly appreciated. tower-diagnostics-20251016-2129.zip
October 17, 2025Oct 17 Community Expert Enable the syslog server and post that after it happens next time.
October 19, 2025Oct 19 Community Expert Docker image is corrupt; delete and recreate it, then reboot and post new diags after array start.https://docs.unraid.net/unraid-os/troubleshooting/common-issues/docker-troubleshooting/#re-creating-the-docker-image-fileThen:https://docs.unraid.net/unraid-os/troubleshooting/common-issues/docker-troubleshooting/#reinstalling-docker-applicationsAlso see below if you have any custom docker networks:https://docs.unraid.net/unraid-os/troubleshooting/common-issues/docker-troubleshooting/#restoring-docker-custom-networks
October 19, 2025Oct 19 Author Ok i have rebuilt dockers/docker.img. But parity is also rebuilding. Is it safe to reboot while parity is running or should I wait?
October 19, 2025Oct 19 Community Expert 21 minutes ago, tormi said:Is it safe to reboot while parity is running or should I wait?Normally rebooting would cause this to restart from the beginning (unless you have the Parity Check Tuning plugin installed and you have set it to continue from point reached).
October 19, 2025Oct 19 Author Here is new syslog. Looks better now. I stoppedsyslog-Tower.log the parity sync midway. Should I run a new one?
October 22, 2025Oct 22 Author syslog-Tower.rarI have been away for a few days. This is the same syslog as last time but in rar format. I can see my server is not accessible yet again...
October 22, 2025Oct 22 Community Expert Syslog are just docker image erros, if the Docker image has been recreated, start a new log and post that one after the crash.
October 24, 2025Oct 24 Author syslog-Tower.rarThe problem persists. I have been away for a few days, but when I returned I could not access the server again.I have not done anything else the last couple of months than to install an extra instance of wordpress, but for the last couple of crashes I am not even running those containers, as I was worried about a port conflict.
October 25, 2025Oct 25 Community Expert You didn't start a new log as asked, but for a couple of days, the only thing logged are messages like this. This wasn't being logged before, so possibly something changed.Oct 19 21:07:48 Tower kernel: usb 1-14: input irq status -75 receivedOct 19 21:07:48 Tower kernel: usb 1-14: input irq status -75 receivedOct 19 21:07:48 Tower kernel: usb 1-14: input irq status -75 received...Oct 20 02:06:02 Tower kernel: usb 1-14: input irq status -75 receivedOct 20 02:06:02 Tower kernel: usb 1-14: input irq status -75 receivedOct 20 02:06:02 Tower kernel: usb 1-14: input irq status -75 receivedThen there's nothing logged from this last line, until the server was rebooted on the 24th:Oct 24 23:09:14 Tower rc.rsyslogd: Syslog server daemon... Started.
October 25, 2025Oct 25 Author Hmmm...I thought the syslog would continue. Should I mirror the syslog to USB, I read somewhere that that could screw up the flash disk aswell...? Will this give you more data?Anyways I restarted the syslog server I guess that is what you meant about starting a new log.
October 26, 2025Oct 26 Community Expert 16 hours ago, tormi said:I read somewhere that that could screw up the flash disk aswell...? Will this give you more data?Should be the same.
October 27, 2025Oct 27 Author Another day, another crash. Syslog attached.syslog-Tower (271025).rarEverytime the parity check also starts... So my server is either dead or running a parity checks these days. And to my knowledge, I have done nothing specific that should cause this. My initial thought was some problems with the dockers and they hogging the network card, but I have not been running any dockers for a while now so... Edited October 27, 2025Oct 27 by tormi
October 27, 2025Oct 27 Community Expert Oct 27 01:50:02 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 1064, gen 0Btrfs is detecting lots of data corruption; this is typically bad RAM, recommend starting by running memtest.
October 27, 2025Oct 27 Author Holy F........I had this freaking thing 1 year ago, but not the same errors though. Thanks though. Will do it! Update: So far the two first memsticks are failing massively.... How can this happen? It is only a year ago since I changed 2 of the sticks and tested all of the. Server has just been running for 6 of the last 12 months maximum... Edited October 27, 2025Oct 27 by tormi
October 27, 2025Oct 27 Author It certainly looks better now as far as I can see.Already packed my 2 errored ram and returning them. They were installed in January 2025, had no errors at that time. Does this make sense that they are already broken?I am getting worried Unraid is eating ram? :) syslog-Tower (5).log
October 28, 2025Oct 28 Community Expert Any hardware can go wrong at any time, and failing RAM is certainly not caused by the OS
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.