(Solved) Unraid keeps temporarily locking up. New install

[Awperator]

Hi, I've searched the forum/discord and haven't found a solution to the issue I'm having. Existing fixes dont seem to help.

Problem statement: When using the GUI, unraid locks up completely for a few seconds on simple tasks. I could click the browse icon to get the syslog file from the flash, and the taskbar on my browser will say "connecting", and then a few seconds later, I'll have a window that says that it could not connect, the server took too long to respond.

I've run memtest86 UEFI (not the one that comes with Unraid, I cant boot into it). Memory passes fine. I've run multiple of the default test with 4 passes. No errors. 

I've tried taking out a stick of memory and running on 1 instead of 2. No change.

I've tried different browsers. When i'm in a 'stuck' state, no other browser can connect. I cant ssh in, and any open SSH sessions (e.g. if i'm rsyncing in a tmux window) will be frozen as well and not be updating. 

I've enabled a syslog server and I'll attach it here. I couldnt see anything unusual.

I use PFSENSE as a router that handles DHCP and a pihole that handles DNS. On PFSENSE, DNS resolver is disabled and DNS forwarder is enabled. On the pihole, I have DNSSEC enabled.

 

On the hardware side (besides the info given in the diagnostics zip), I do have shucked drives. I had to do the kapton 3.3V trick on all of the data drives in the array. The parity drive did not need the kapton 3.3V trick.

 

Any help is appreciated. Please let me know if you need more data.

 

syslog thewalrus-diagnostics-20220723-1204.zip

Edited July 23, 2022 by Awperator

[Awperator]

Some more information - I'e booted to GUI mode in Unraid, and it seems to be much snappier, no hangups so far. Leads me to think that there could be something going on with the network if Unraid is very responsive when requesting from localhost instead of requesting from an IP in my network.
Any ideas on what could be the cause?

Basic network details:

PFSENSE router, no VLANS. In DNS forwarder, the settings for DHCP registration, static dhcp, and prefer dhcp are unchecked. DNS resolver is not enabled.

On pihole, under DNS advanced settings, the first 2 options (Never forward non-FQDN A and AAAA queries, Never forward reverse lookups for private IP ranges) are unchecked, but use DNSSEC is checked.
On the browser side, I use ublock origin, but that is disabled for local addresses. This entry:

/^https?://192.168.1.*/

is in my trusted sites.

 

Appreciate the community and any help given!

 

[Awperator]

Ok some more troubleshooting:

Local login with GUI mode is perfect. No issues whatsoever at all.

WEB access and SSH access from 2 different macbooks on the same network have issues. The web access has been described above (timing out). With SSH, I have periodic lag, where I press a key and no response in the terminal, or I sometimes get completely disconnected and have to log back in again.

Since this is happening on 2 different computers (on the same network), I think it could be a couple of things:

1. Either something is wrong with my network settings
   1. I doubt this because I have a synology and raspberry pi that I SSH into regularly and do not experience these issues
   2. 2 different macbooks had the same issue. Does not seem like a localized issue on one computer. 
2. Something is wrong with the NIC or network settings on the unraid computer
   1. I think this is more likely....

I have disabled bonding in network settings (as I only have one NIC)... Havent changed anything else. We'll see if this helps. 

If anyone has gone through something like this, please let me know!

 

Appreciate the community, cheers!

[JorgeB]

Nothing obvious, try connecting directly to a router just for testing.

[Awperator]

Can't believe this... It was my router/access point. I guess it couldnt handle wifi + lan traffic?
My network topology: Fiber -> WAN -> LAN -> WNDR4500 in bridge mode as a Wireless AP
On the wireless AP, I had a synology, unraid box, eufy, and raspberry pi wired in. Various wireless devices.

 

I added a dumb switch to connect all the devices formerly wired into the AP, and also connected the AP so that wireless devices would still work. Issue went away. Glad the issue is resolved!!