FreeNAS not responding, screenshot attached

[scurrier]

On my windows computer, I went to access a drive mapped to FreeNAS and it was not responsive. Would not respond to ping either. Looked at my IPMI console view and saw what's in the attached screenshot. Text was flying by on the console, I could not read it without the screenshot.

Rebooted and things went back to normal.

Getting pretty annoyed with the random crap that my freenas setup is doing. Perhaps not updating every time a stable train update comes in is the answer.

 

[diedrichg]

Is a misconfigured Windows client statically taking 192.168.1.255? Did you purposely disable IPV6? Did you change the default settings for CIFS and/or FreeNAS network settings?

 

[scurrier]

Misconfigured client taking static IP: No, I just did some scans and nobody has it. Plus I'd know not to give anybody the broadcast address of a subnet.

Did I disable ipv6: probably, I'm afraid of its security implications

CIFS/network settings: I am using TCP_NODELAY. That's about it. I think since my install is older it is still running SMB3 which I believe is not the current default. I use LACP for networking to a Netgear GS748TP.

 

[diedrichg]

From the Googling that I did disabling IPv6 was one of the causes. Not having CIFS settings as default was my personal guess. You should consider going back to smb2 as well.

Misconfigured client taking static IP: No, I just did some scans and nobody has it. Plus I'd know not to give anybody the broadcast address of a subnet.

Did I disable ipv6: probably, I'm afraid of its security implications

CIFS/network settings: I am using TCP_NODELAY. That's about it. I think since my install is older it is still running SMB3 which I believe is not the current default. I use LACP for networking to a Netgear GS748TP.

 

[anodos]

I'd try disabling lacp. Try with single nic. See if problem recurs. Post full smb4.conf.