Solution larrymancer Posted March 19, 2021 Solution Share Posted March 19, 2021 About once every 24 hours my unraid server will become unresponsive to a point where the server reboot or I need to reboot it manually. This started right after I replaced the motherboard CPU and RAM. Below is the syslogs from the time it happened up until I did a restart. Any ideas as to why this is happening? Mar 18 14:59:43 Tower nmbd[4295]: retransmit_or_expire_response_records: Failed to resend packet id 25650 to IP 192.168.122.255 on subnet 192.168.122.1 Mar 18 14:59:44 Tower root: Stopping virtlogd... Mar 18 14:59:45 Tower root: Stopping virtlockd... Mar 18 14:59:46 Tower emhttpd: shcmd (180): umount /etc/libvirt Mar 18 14:59:46 Tower kernel: ccp 0000:2a:00.2: ccp enabled Mar 18 14:59:46 Tower kernel: kvm: Nested Virtualization enabled Mar 18 14:59:46 Tower kernel: SVM: kvm: Nested Paging enabled Mar 18 14:59:46 Tower kernel: SVM: Virtual VMLOAD VMSAVE supported Mar 18 14:59:46 Tower kernel: SVM: Virtual GIF supported Mar 18 14:59:47 Tower nmbd[4295]: [2021/03/18 14:59:47.159753, 0] ../../source3/libsmb/nmblib.c:922(send_udp) Mar 18 14:59:47 Tower nmbd[4295]: Packet send failed to 192.168.122.255(138) ERRNO=Network is unreachable Mar 18 14:59:50 Tower nmbd[4295]: [2021/03/18 14:59:50.670589, 0] ../../source3/libsmb/nmblib.c:922(send_udp) Mar 18 14:59:50 Tower nmbd[4295]: Packet send failed to 192.168.122.255(138) ERRNO=Network is unreachable Mar 18 14:59:52 Tower nmbd[4295]: [2021/03/18 14:59:52.672619, 0] ../../source3/libsmb/nmblib.c:922(send_udp) Mar 18 14:59:52 Tower nmbd[4295]: Packet send failed to 192.168.122.255(138) ERRNO=Network is unreachable Mar 18 14:59:54 Tower nmbd[4295]: [2021/03/18 14:59:54.443794, 0] ../../source3/libsmb/nmblib.c:922(send_udp) Mar 18 14:59:54 Tower nmbd[4295]: Packet send failed to 192.168.122.255(138) ERRNO=Network is unreachable Mar 18 14:59:55 Tower nmbd[4295]: [2021/03/18 14:59:55.199148, 0] ../../source3/libsmb/nmblib.c:922(send_udp) Mar 18 14:59:55 Tower nmbd[4295]: Packet send failed to 192.168.122.255(138) ERRNO=Network is unreachable Mar 18 14:59:55 Tower nmbd[4295]: [2021/03/18 14:59:55.199242, 0] ../../source3/libsmb/nmblib.c:922(send_udp) Mar 18 14:59:55 Tower nmbd[4295]: Packet send failed to 192.168.122.255(137) ERRNO=Network is unreachable Mar 18 14:59:55 Tower nmbd[4295]: [2021/03/18 14:59:55.199267, 0] ../../source3/nmbd/nmbd_packets.c:179(send_netbios_packet) Mar 18 14:59:55 Tower nmbd[4295]: send_netbios_packet: send_packet() to IP 192.168.122.255 port 137 failed Mar 18 14:59:55 Tower nmbd[4295]: [2021/03/18 14:59:55.199314, 0] ../../source3/nmbd/nmbd_nameregister.c:581(register_name) Mar 18 14:59:55 Tower nmbd[4295]: register_name: Failed to send packet trying to register name #001#002__MSBROWSE__#002<01> Mar 18 15:00:03 Tower nmbd[4295]: [2021/03/18 15:00:03.242142, 0] ../../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2) Mar 18 15:00:03 Tower nmbd[4295]: ***** Mar 18 15:00:03 Tower nmbd[4295]: Mar 18 15:00:03 Tower nmbd[4295]: Samba name server TOWER is now a local master browser for workgroup WORKGROUP on subnet 172.17.0.1 Mar 18 15:00:03 Tower nmbd[4295]: Mar 18 15:00:03 Tower nmbd[4295]: ***** Mar 18 15:00:03 Tower nmbd[4295]: [2021/03/18 15:00:03.242290, 0] ../../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2) Mar 18 15:00:03 Tower nmbd[4295]: ***** Mar 18 15:00:03 Tower nmbd[4295]: Mar 18 15:00:03 Tower nmbd[4295]: Samba name server TOWER is now a local master browser for workgroup WORKGROUP on subnet 192.168.1.200 Mar 18 15:00:03 Tower nmbd[4295]: Mar 18 15:00:03 Tower nmbd[4295]: ***** Mar 18 15:00:16 Tower sSMTP[4576]: Creating SSL connection to host Mar 18 15:00:16 Tower sSMTP[4576]: SSL connection using TLS_AES_256_GCM_SHA384 Mar 18 15:00:16 Tower sSMTP[4576]: Authorization failed (535 5.7.8 https://support.google.com/mail/?p=BadCredentials f9sm2068826qto.46 - gsmtp) Mar 18 15:00:45 Tower nmbd[4295]: [2021/03/18 15:00:45.397341, 0] ../../source3/libsmb/nmblib.c:922(send_udp) Mar 18 15:00:45 Tower nmbd[4295]: Packet send failed to 192.168.122.255(138) ERRNO=Network is unreachable Mar 18 15:00:50 Tower ntpd[1894]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized Mar 19 01:05:50 Tower kernel: md: sync done. time=36541sec Mar 19 01:05:50 Tower kernel: md: recovery thread: exit status: 0 Mar 19 03:40:01 Tower crond[1915]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null Mar 19 19:19:35 Tower emhttpd: Starting services... Quote Link to comment
trurl Posted March 20, 2021 Share Posted March 20, 2021 Go to Tools-Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post in this thread. Quote Link to comment
larrymancer Posted March 20, 2021 Author Share Posted March 20, 2021 Are requested I have attached the diagnostics file, and the syslog file to this post. The server went into a unresponsive state sometime last night and I had to restart the server to bring it back up. tower-diagnostics-20210320-0844.zip syslog-192.168.1.200.log Quote Link to comment
JorgeB Posted March 20, 2021 Share Posted March 20, 2021 Start here: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173 Quote Link to comment
larrymancer Posted March 21, 2021 Author Share Posted March 21, 2021 Thanks for Ideas. I tried downclocking the ram to 2133 but that did not make a difference. This Moring I updated the Bios of my motherboard to the latest version, but was not able to find the PSU settings talked about in the link. Wont know if the bios update fixes anything till tomorrow, but hopefully that was the issue. Quote Link to comment
JorgeB Posted March 22, 2021 Share Posted March 22, 2021 17 hours ago, larrymancer said: This Moring I updated the Bios of my motherboard to the latest version, but was not able to find the PSU settings talked about in the link. They should be in there somewhere, if you can't find it and it still crashes try disabling C-states. Quote Link to comment
larrymancer Posted March 23, 2021 Author Share Posted March 23, 2021 I disabled C states and unraid has been up and running for a day and half with no issues. I think that fixed it. Thank you for the help. 1 Quote Link to comment
Recommended Posts
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.