Mlatx

Hi All, I’ve been using whoogle through reverse proxy for a while now. Over the last several months, it randomly freezes, and I have to restart the docker. Has anyone else had this issue? There are no errors in the logs. I wonder if a reinstall would help.

Hi All, It was the processor. Replacement came today, and all is booted up.

I had to download and run memtest from memtest86.com because I needed a UEFI boot. Unraid's memtest, based on that, needs legacy CSM enabled. I needed my monitor and let it run 2 cycles. No issues were found. I updated the bios and still have boot problems. I tried each ram stick individually, and the problems persist. I doubt 2 ram sticks would go bad at the same time. It's either the motherboard or CPU. This is not going to be fun. I figure I'll start with the motherboard as CPU's have a lower failure rate. New mobo arrives tomorrow.

Update so far. I was trying to use a linux live cd to pull the last 6.12.x backup I had. All the live distros I've tried lock up after a few minutes. I installed the 6.11.5 backup to a flash drive. It got stuck at the bzfirmware checksum. So I put it into another usb port. It move passed the error but then got stuck on a plugin coral-driver/packages/5.19.17/._Coral... md5 error. I tried a another usb with this version and was able to boot in after a couple of attempts. The array didn't start because the license wasn't valid on the new disk. The UI eventually locked up, and I had to restart it. I figured the other usb slot might work for getting 6.12.3 working. I got past the checksum but then through an error "eth0" not detected. It went through the process of booting but did not assign IP addresses. Out of 3 USB's, I had all types of issues. Random restarts. Lockups at different points. I'm lost at this point. I'm going to run a memory test. Is it possible the motherboard is bad? Here are 2 pictures I took. One was interested because it was saying something about lack of communication between processors. This is the generic named photo. The other was after the UI froze when I got in. Any other suggestions?

That didn't work. Something in the configuration got corrupted in the downgrade. I can either find the backup on the disk (not optimal), or I have a backup of the last 6.11 I can go back to. If I did that, would it affect my dockers in anyway?

I copied the stock config files to the old usb. It got stuck in the same place. I copied my configuration files to the new usb, and now it gets stuck at bzmodules checksum Ugh. I'm going to try installing 6.12.4 and copy my files over and see if that works. At least this way I can get to my backup and restore it.

That's a good idea. Although if that is the case, this is going to suck to fix, meaning I'll have to find the backup on the drive.

The new usb worked. I'm assuming I put the config folder back on and all should work.

Here is what I did. 1. Copy the current USB contents somewhere 2. Wipe the usb with a fresh 6.12.3 installation 3. Replace the config folder with the one I copied I still can't boot. I'm getting stuck at the bzfirmware checksum. How can I get around this?

The past few days I've been having issues with unraid becoming unresponsive after nightly docker updates. I went to downgrade to 6.12.3, and now it won't boot. I have a backup, but it's on the server. The software I use to copy from the server from my mac has not copied for a while now unfortunately. Rather than remove the drives to find the correct one, how can I get back into unraid? I would hope the easiest way would be to download 6.12.4 and replace the files on the flash drive that may have been corrupted leaving the system configuration intact.

I'm having the same issue the last couple of days. I have syslog server running, and there are no visible errors. It runs fine during the day. When the dockers update at midnight, the UI is unavailable as well as all docker apps. Today, I downgraded to 6.12.3, and now it won't boot up. I believe I have a backup from when I moved to 6.12 or really hope I do. I had no issues with 6.12.3. Here are my syslog events since it became unresponsive. Sep 21 00:00:01 server Docker Auto Update: Community Applications Docker Autoupdate running Sep 21 00:00:01 server Docker Auto Update: Checking for available updates Sep 21 00:00:36 server Docker Auto Update: Found update for AdGuard-Home. Not set to autoupdate Sep 21 00:00:36 server Docker Auto Update: Stopping postgresql14 Sep 21 00:00:36 server kernel: veth5f54955: renamed from eth0 Sep 21 00:00:36 server Docker Auto Update: Stopping sabnzbd Sep 21 00:00:41 server Docker Auto Update: Installing Updates for postgresql14 adminer sabnzbd Sep 21 00:00:51 server Docker Auto Update: Restarting postgresql14 Sep 21 00:00:52 server kernel: eth0: renamed from veth0d401ff Sep 21 00:00:52 server Docker Auto Update: Restarting sabnzbd Sep 21 00:00:52 server sSMTP[10781]: Creating SSL connection to host Sep 21 00:00:52 server sSMTP[10781]: SSL connection using TLS_AES_256_GCM_SHA384 Sep 21 00:00:55 server sSMTP[10781]: Sent mail for "my email" (221 2.0.0 Service closing transmission channel) uid=0 username=root outbytes=661 Sep 21 00:00:55 server Docker Auto Update: Community Applications Docker Autoupdate finished Sep 21 00:01:34 server root: /etc/libvirt: 920 MiB (964665344 bytes) trimmed on /dev/loop3 Sep 21 00:01:34 server root: /var/lib/docker: 34.7 GiB (37309169664 bytes) trimmed on /dev/loop2 Sep 21 00:01:34 server root: /mnt/cache: 1.6 TiB (1781115658240 bytes) trimmed on /dev/sdc1

I think have fixed the issue. I’ve assigned a static IP to unraid since I’ve had the system, over 5 years. There were no issues until the past week. I don’t know what changed. I went from static to dynamic IP assigned by pfsense. All networking issues have been fixed since last night.

You are a life saver. I'm having networking issues and figured I'd try upgrading the bios. I forgot to enable IOMMU, and unraid booted fine. After enabling it, it would not boot. I made this change, and I can boot back in. Thank you.

I'm still having out of memory issues. Here is the latest log if anyone can find any issues. server-diagnostics-20230604-1726.zip

Looking at the syslog server results, I see these lines before it went down again. Jun 4 14:18:54 server kernel: eth0: renamed from veth8a18a6f Jun 4 14:19:41 server kernel: veth6e45a3d: renamed from eth0 Jun 4 14:20:24 server kernel: vethfa89d03: renamed from eth0 Jun 4 14:20:25 server kernel: eth0: renamed from vethf117695 Jun 4 14:22:33 server kernel: veth107ce0c: renamed from eth0 Jun 4 14:22:34 server kernel: eth0: renamed from vetha05b5fd I changed ethernet cables and saw no change. I'm going to update the bios and try again.