mbc0

Ok, Woke this morning to see it has happened again and it appears it is triggered by cabackup (probably just where it is stopping and starting dockers) I have Sophos XG Home running on a 3rd Unraid Server with a 4 port NIC which is setup to these ip ranges (This has been my setup for years) 192.168.0.* - Local LAN 192.168.1.* - Local WiFi 192.168.8.* - 5G Router I am able to use & ping all these ranges from all devices and all 3 unraid servers until this error occurs. When this issue occurs I am unable to ping the outside world and any other ip addresses that are 192.168.1.* & 192.168.8.* as the destination is unreachable ONLY 192.168.0.* will continue to work. I can even still ping 192.168.0.10 which is my Sophos installation for DSL Broadband but still have no internet access. When this error occurs, all other Unraid servers & devices can see each other and have zero problems. I currently have the issue as I type this and have stopped all containers but left the docker service running and the problem still exists. As soon as I disable the docker service the networks are available again and I can ping everything as expected! I cannot see anything to help me in the diags, really would appreciate some help here 🙂 Thank you

Last night I removed my 10gbe card from the server and now just using the on-board 100mb just in case it is causing these problems, I cannot see anything useful in the diags unfortunately, hoping someone might see something when they get a chance 🙂

Hi, I am having this weird situation every few days where my dockers and unraid lose internet connection and some dockers are losing connections (Agent DVR loses contact with 4 of my 6 cameras) Plex loses connection to the internet etc. Unraid console is unable to ping most of my lan or the internet. I have noticed that all 21 disks are spun up all the time when this happens, the auto spin down stops working. If I stop my docker service I am then able to ping the internet and the cameras that were unavailable whilst the docker service was running and then start the docker service and everything is back up and running as normal. I have attached my diags and could really do with some guidance please! unraid1-diagnostics-20230608-2122.zip unraid1-diagnostics-20230608-2122.zip

I hope it gets updated, I use it every day!

Thanks buddy, I appreciate it!

@Squid I can confirm just by stopping and starting the array everything is now working rather than a full reboot. I imagine that if I had stopped and started the docker engine I would have had the same result? I have been putting up with this for a good 6 months+ but thought I would ask about it today, any ideas?

@Squid Leaving Sab running I can restart Radarr, Sonarr, Lidarr and still none of them can connect to Sab, the only way I have found to get them communicating again is to reboot the server for a 2nd time.

If I restart Radarr and Sabnzbd I still have the communication problem, the only way I have found to resolve is to reboot again.

I am having problems on "first" boot where my docker contairs cannot talk to each other (i.e. radarr to sabnzbd) Test was aborted due to an error: Unable to connect to SABnzbd, Error: ConnectFailure (No route to host): 'http://192.168.0.53:8080/api?mode=get_config&apikey=**intentionally deleted**&output=json' This happens EVERY time I reboot the server until I reboot again and then everything is great until I need to reboot again. Can anyone please help? unraid1-diagnostics-20230303-0913.zip

The problem of being unable to SSH arose at the same time as the motherboard/cpu swap as well

The problem arose after changing the unraid motherboard/cpu so maybe I just made an assumption? Can you please confirm if my screenshots look ok though? Thank you

Hi JorgeB, it is connected to my router with internet access. I have just woken this morning to find that the \\unraid1 now works? it was left on overnight so maybe something resolved? Thank you!

Also, I am no longer able to ssh into the server

Hi, Can someone please look over my network setup since replacing my motherboard/cpu I cannot access it like I used to eth0 is 10gbe eth1 is onboard I used to just have eth0 10gbe connected for years and it worked fine but since replacing motherboard/network this is no longer the case. I have deleted the network.cfg file so unraid can create a new one but still this would not work I have managed to get it "working" by enabling eth1 and plugging in a LAN cable to my switch, although this "works" and I can confirm the 10gbe is also working as I can copy at 900mbp/s to the server from my desktop My Windows mounts no longer work e.g. \\unraid1\Backups but \\192.168.0.33\Backups works fine. All info in the routing table is automatic, I have not entered anything in there! unraid1-diagnostics-20230228-2357.zip

Sorry to ask but do I need a comma?

Thank you, Do you know if it is the same as the Power Saving Settings n Tips n Tweaks? Enable Intel Turbo/AMD Performance Boost? No Normal CPU Scaling Governor: Power Save Power Saving CPU Scaling Governor: Power Save

Hi, I have just installed an NVIDIA P4000 and am getting these errors (loads in the log) I have swapped slots with my HBA card but still getting them, can anyone advise please? Feb 28 17:34:01 UNRAID1 kernel: pcieport 0000:00:01.1: AER: Corrected error received: 0000:00:00.0 Feb 28 17:34:01 UNRAID1 kernel: pcieport 0000:00:01.1: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Feb 28 17:34:01 UNRAID1 kernel: pcieport 0000:00:01.1: device [1022:1453] error status/mask=00000040/00006000 Feb 28 17:34:01 UNRAID1 kernel: pcieport 0000:00:01.1: [ 6] BadTLP BIOS:American Megatrends Inc. Version F13a. Dated: 11/30/2021 CPU:AMD Ryzen Threadripper 2950X 16-Core @ 3500 MHz HVM:Enabled IOMMU:Enabled Cache:1536 KiB, 8 MB, 32 MB Memory:64 GiB DDR4 (max. installable capacity 512 GiB) Network:bond0: fault-tolerance (active-backup), mtu 1500 Kernel:Linux 5.19.17-Unraid x86_64 OpenSSL:1.1.1s unraid1-diagnostics-20230228-1731.zip

Thank you so much for your help, the problem was traced to an unreadable file & folder on my cache drive, I had to format it to get rid! Backup now working as expected! 🙂

I already have this setup, sorry, I was not clear but that is what I meant by no useful information in the log at all. I am using the existing PSU from my previous threadripper setup, all I have changed is motherboard & cpu I have the Dynamix System Temperature plugin installed and normally around 26C CPU, highest I have seen is 40C when being hammered. I can see no more I can do with this setup, maybe an intermittant issue with the motherboard? since installation I have had RAM related issues, corrupt NVME cache drive, lost all dockers & VM's (all seperate occasions) but when running, everything is perfect for 1-3 days. I will transplant the threadripper back in and setup another server using this suspect motherboard/cpu config to see what happens, unless you can think of anything else I can try. The only reason(s) for doing all this were to save energy costs.

Hi, I have had nothing but problems with this new motherboard/cpu config M/B:ASRock Z790 Pro RS/D4 Version BIOS:American Megatrends International, LLC. Version 4.01. Dated: 01/06/2023 CPU:13th Gen Intel® Core™ i5-13600K @ 3465 MHz When the server locks up, there is still power, the network card is flashing but I cannot access the server even directly with a monitor plugged in or SSL etc, nothing. I am now using a 3rd set of 4 DIMMS since problems began so would safely say it's not the RAM Temps are never above 40C so confident of not being a temperature related issue. I have attached DIAGS since powering off/on at 18:12 tonight I have logs written to a share but there is nothing of any use written in the log and no errors. The BIOS has been reset to standard, no power limits, no overclock, everything totally standard. Where can I go from here to find the problem please? I think I am going to have to swap back to my threadripper for reliability and put this motherboard/cpu config into a test bench. unraid1-diagnostics-20230226-1820.zip

Hi, just wondering if anyone can confirm please?

Been using shrmn/gsdock for years without issue, I did not realise there was another repo?

I ran the 4 sticks I took out in memtest for over 24 hours in another board with no issues and as all 8 sticks have been running without issue in my previous config I am confident there is no physical issue with the RAM (All Corsair Vengeance) I have not overclocked but did choose a power saving option (The reason for changing from a Threadripper) in the BIOS of which I cannot remember but I am going to change that back to standard just to eliminate what the problem could be. I have also enabled power saving in tips and tweaks as this is what brought me under the 150w I was looking for, do you think that could have any influence on this problem?

This is worrying! I replaced all 4 sticks of RAM the other day so they chances of it actually being the RAM are slim to none I would have thought. It is a brand new motherboard and CPU, my old motherboard had 8 slots for RAM and never missed a beat I have now had these errors on both sets of 4 so I am making the assumption that it is not the RAM causing the issue so maybe the motherboard? (Asrock z790 pro rs/d4) I am on the latest BIOS, are there any steps I can take to try and get on top of this issue?

Unable to stop the server currently 😞 Feb 21 11:22:18 UNRAID1 emhttpd: shcmd (2491271): umount /mnt/cache Feb 21 11:22:18 UNRAID1 root: umount: /mnt/cache: target is busy. Feb 21 11:22:18 UNRAID1 emhttpd: shcmd (2491271): exit status: 32 Feb 21 11:22:18 UNRAID1 emhttpd: Retry unmounting disk share(s)... Feb 21 11:22:23 UNRAID1 emhttpd: Unmounting disks... Feb 21 11:22:23 UNRAID1 emhttpd: shcmd (2491272): umount /mnt/cache Feb 21 11:22:23 UNRAID1 root: umount: /mnt/cache: target is busy. Feb 21 11:22:23 UNRAID1 emhttpd: shcmd (2491272): exit status: 32 Feb 21 11:22:23 UNRAID1 emhttpd: Retry unmounting disk share(s)... Feb 21 11:22:28 UNRAID1 emhttpd: Unmounting disks... Feb 21 11:22:28 UNRAID1 emhttpd: shcmd (2491273): umount /mnt/cache Feb 21 11:22:28 UNRAID1 root: umount: /mnt/cache: target is busy. Feb 21 11:22:28 UNRAID1 emhttpd: shcmd (2491273): exit status: 32 Feb 21 11:22:28 UNRAID1 emhttpd: Retry unmounting disk share(s)...