December 23, 20241 yr Unraid OS: 6.12.14 (I think, can't check until I reboot) My Unraid server has become unresponsive, ping is ok: > ping 192.168.1.10 PING 192.168.1.10 (192.168.1.10) 56(84) bytes of data. 64 bytes from 192.168.1.10: icmp_seq=1 ttl=63 time=4.13 ms 64 bytes from 192.168.1.10: icmp_seq=2 ttl=63 time=24.9 ms 64 bytes from 192.168.1.10: icmp_seq=3 ttl=63 time=25.5 ms 64 bytes from 192.168.1.10: icmp_seq=4 ttl=63 time=20.1 ms 64 bytes from 192.168.1.10: icmp_seq=5 ttl=63 time=2.13 ms 64 bytes from 192.168.1.10: icmp_seq=6 ttl=63 time=28.3 ms ^C --- 192.168.1.10 ping statistics --- 6 packets transmitted, 6 received, 0% packet loss, time 5010ms rtt min/avg/max/mdev = 2.126/17.498/28.275/10.455 ms I started Wireshark and filtered for ip addr 192.168.1.10 (ip address of Unraid server). I've tried to SSH to the server, from browser attempted to access tower.local and 192.168.1.10:80. I've also attempted to access NFS shares with no avail. All should be included in the Wireshark trace. Attempting to ssh to unraid server: > ssh unraid -vvv OpenSSH_9.6p1 Ubuntu-3ubuntu13.5, OpenSSL 3.0.13 30 Jan 2024 debug1: Reading configuration data /home/NAME/.ssh/config debug1: /home/niels/.ssh/config line 20: Applying options for unraid debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/*.conf matched no files debug1: /etc/ssh/ssh_config line 21: Applying options for * debug2: resolve_canonicalize: hostname 192.168.1.10 is address debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts' -> '/home/NAME/.ssh/known_hosts' debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts2' -> '/home/NAME/.ssh/known_hosts2' debug3: channel_clear_timeouts: clearing debug3: ssh_connect_direct: entering debug1: Connecting to 192.168.1.10 [192.168.1.10] port 22. debug3: set_sock_tos: set socket 3 IP_TOS 0x10 debug1: Connection established. debug1: identity file /home/NAME/.ssh/id_ed25519 type 3 debug1: identity file /home/NAME/.ssh/id_ed25519-cert type -1 debug1: Local version string SSH-2.0-OpenSSH_9.6p1 Ubuntu-3ubuntu13.5 debug1: Remote protocol version 2.0, remote software version OpenSSH_9.8 debug1: compat_banner: match: OpenSSH_9.8 pat OpenSSH* compat 0x04000000 debug2: fd 3 setting O_NONBLOCK debug1: Authenticating to 192.168.1.10:22 as 'root' debug3: record_hostkey: found key type ED25519 in file /home/NAME/.ssh/known_hosts:18 debug3: load_hostkeys_file: loaded 1 keys from 192.168.1.10 debug1: load_hostkeys: fopen /home/NAME/.ssh/known_hosts2: No such file or directory debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts: No such file or directory debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts2: No such file or directory debug3: order_hostkeyalgs: have matching best-preference key type [email protected], using HostkeyAlgorithms verbatim debug3: send packet: type 20 debug1: SSH2_MSG_KEXINIT sent debug3: receive packet: type 20 debug1: SSH2_MSG_KEXINIT received debug2: local client KEXINIT proposal debug2: KEX algorithms: [email protected],curve25519-sha256,[email protected],ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group14-sha256,ext-info-c,[email protected] debug2: host key algorithms: [email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],ssh-ed25519,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,[email protected],[email protected],rsa-sha2-512,rsa-sha2-256 debug2: ciphers ctos: [email protected],aes128-ctr,aes192-ctr,aes256-ctr,[email protected],[email protected] debug2: ciphers stoc: [email protected],aes128-ctr,aes192-ctr,aes256-ctr,[email protected],[email protected] debug2: MACs ctos: [email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],hmac-sha2-256,hmac-sha2-512,hmac-sha1 debug2: MACs stoc: [email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],hmac-sha2-256,hmac-sha2-512,hmac-sha1 debug2: compression ctos: none,[email protected],zlib debug2: compression stoc: none,[email protected],zlib debug2: languages ctos: debug2: languages stoc: debug2: first_kex_follows 0 debug2: reserved 0 debug2: peer server KEXINIT proposal debug2: KEX algorithms: [email protected],curve25519-sha256,[email protected],ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group14-sha256,ext-info-s,[email protected] debug2: host key algorithms: rsa-sha2-512,rsa-sha2-256,ecdsa-sha2-nistp256,ssh-ed25519 debug2: ciphers ctos: [email protected],aes128-ctr,aes192-ctr,aes256-ctr,[email protected],[email protected] debug2: ciphers stoc: [email protected],aes128-ctr,aes192-ctr,aes256-ctr,[email protected],[email protected] debug2: MACs ctos: [email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],hmac-sha2-256,hmac-sha2-512,hmac-sha1 debug2: MACs stoc: [email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],hmac-sha2-256,hmac-sha2-512,hmac-sha1 debug2: compression ctos: none,[email protected] debug2: compression stoc: none,[email protected] debug2: languages ctos: debug2: languages stoc: debug2: first_kex_follows 0 debug2: reserved 0 debug3: kex_choose_conf: will use strict KEX ordering debug1: kex: algorithm: [email protected] debug1: kex: host key algorithm: ssh-ed25519 debug1: kex: server->client cipher: [email protected] MAC: <implicit> compression: none debug1: kex: client->server cipher: [email protected] MAC: <implicit> compression: none debug3: send packet: type 30 debug1: expecting SSH2_MSG_KEX_ECDH_REPLY debug3: receive packet: type 31 debug1: SSH2_MSG_KEX_ECDH_REPLY received debug1: Server host key: ssh-ed25519 SHA256:9XB9lD+KjQtAKg3pQ32/wWpK2jeBo6oIrYP7VmlC1+I debug3: record_hostkey: found key type ED25519 in file /home/NAME/.ssh/known_hosts:18 debug3: load_hostkeys_file: loaded 1 keys from 192.168.1.10 debug1: load_hostkeys: fopen /home/NAME/.ssh/known_hosts2: No such file or directory debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts: No such file or directory debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts2: No such file or directory debug1: Host '192.168.1.10' is known and matches the ED25519 host key. debug1: Found key in /home/NAME/.ssh/known_hosts:18 debug3: send packet: type 21 debug1: ssh_packet_send2_wrapped: resetting send seqnr 3 debug2: ssh_set_newkeys: mode 1 debug1: rekey out after 134217728 blocks debug1: SSH2_MSG_NEWKEYS sent debug1: Sending SSH2_MSG_EXT_INFO debug3: send packet: type 7 debug1: expecting SSH2_MSG_NEWKEYS debug3: receive packet: type 21 debug1: ssh_packet_read_poll2: resetting read seqnr 3 debug1: SSH2_MSG_NEWKEYS received debug2: ssh_set_newkeys: mode 0 debug1: rekey in after 134217728 blocks debug3: send packet: type 5 debug3: receive packet: type 7 debug1: SSH2_MSG_EXT_INFO received debug3: kex_input_ext_info: extension server-sig-algs debug1: kex_ext_info_client_parse: server-sig-algs=<ssh-ed25519,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,sk-ssh-ed25519@openssh.com,sk-ecdsa-sha2-nistp256@openssh.com,rsa-sha2-512,rsa-sha2-256> debug3: kex_input_ext_info: extension [email protected] debug1: kex_ext_info_check_ver: [email protected]=<0> debug3: kex_input_ext_info: extension [email protected] debug1: kex_ext_info_check_ver: [email protected]=<0> debug3: receive packet: type 6 debug2: service_accept: ssh-userauth debug1: SSH2_MSG_SERVICE_ACCEPT received debug3: send packet: type 50 Connection closed by 192.168.1.10 port 22 Before I reboot, is there any way I can secure/check further logs? And after the reboot, where do I find the relevant logs? Thanks! unraid-server-unresponsive-filtered.pcapng
December 24, 20241 yr Community Expert See if you can still get the diagnostics using the keyboard/monitor or IPMI.
December 25, 20241 yr Author I left the server on, as I didn't have time to troubleshoot the issue. And now it is back in business! (a modern Christmas miracle ) From Uptime Kuma, I can see that the server was unresponsive from 22nd of December 19:00 until December 24 around 14:48. I have now collected diagnostics (haven't had time to look at it). tower-diagnostics-20241225-1810.zip EDIT: I'm actually only on 6.12.13 and not 6.12.14 as I expected. Time to update I guess. Edited December 25, 20241 yr by Jorgensen
December 26, 20241 yr Community Expert Solution Diags show issues with the flash drive, it may be a good idea to replace it.
December 26, 20241 yr Author Wow, that was a lot of errors (Tower kernel: SQUASHFS error: Failed to read block)... I've just created a backup of the flash and I'll be looking for a new flash drive. I'm a bit surprised this wasn't highlighted in the Unraid GUI. Anyway, thanks a lot for your assistance. I'll close this issue as resolved.
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.