Ulf Thomas Johansen Posted December 13, 2023 Share Posted December 13, 2023 Hi. System has been running stable for many months now, and over the last two weeks I've had two lock ups. As I am running headless I cannot see any core messages on the screen, but after last lock-up I mirrored syslog to the usb drive. I do fear a hardware issue and would appreciate any help in nailing it down. Regards //Thomas algarheim-diagnostics-20231213-1938.zip Quote Link to comment
JorgeB Posted December 13, 2023 Share Posted December 13, 2023 Nothing relevant logged in the previous syslog that I can see, but it ended in a way that suggest it could have been full: Dec 13 10:51:39 Algarheim kernel: mdcmd (317): set md_write_method 1 Dec 13 10:51:39 Algarheim kernel: Post new diags after the next crash, also if possible stop the SSH spam in the log, even if just temporarily, it may fill it up before the crash. 1 Quote Link to comment
Ulf Thomas Johansen Posted December 13, 2023 Author Share Posted December 13, 2023 Thanks. I have changed the ssh config (some remnants of an old debug session I presume) - and will patiently await the next failure. Is there anyway to extend the log? Quote Link to comment
JorgeB Posted December 13, 2023 Share Posted December 13, 2023 Not that I know of. Quote Link to comment
Ulf Thomas Johansen Posted December 13, 2023 Author Share Posted December 13, 2023 Thanks. Quote Link to comment
Ulf Thomas Johansen Posted December 13, 2023 Author Share Posted December 13, 2023 Well that didn't take long: These are the last lines of the syslog: Dec 13 20:06:11 Algarheim emhttpd: spinning down /dev/sdi Dec 13 20:12:59 Algarheim kernel: docker0: port 1(vethd91a85e) entered disabled state Dec 13 20:12:59 Algarheim kernel: veth8207b51: renamed from eth0 Dec 13 20:12:59 Algarheim kernel: docker0: port 1(vethd91a85e) entered disabled state Dec 13 20:12:59 Algarheim kernel: device vethd91a85e left promiscuous mode Dec 13 20:12:59 Algarheim kernel: docker0: port 1(vethd91a85e) entered disabled state Dec 13 20:12:59 Algarheim kernel: docker0: port 1(vethee0e3aa) entered blocking state Dec 13 20:12:59 Algarheim kernel: docker0: port 1(vethee0e3aa) entered disabled state Dec 13 20:12:59 Algarheim kernel: device vethee0e3aa entered promiscuous mode Dec 13 20:12:59 Algarheim kernel: docker0: port 1(vethee0e3aa) entered blocking state Dec 13 20:12:59 Algarheim kernel: docker0: port 1(vethee0e3aa) entered forwarding state Dec 13 20:12:59 Algarheim kernel: eth0: renamed from veth52ba7c3 Dec 13 20:12:59 Algarheim kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethee0e3aa: link becomes ready Quote Link to comment
JorgeB Posted December 14, 2023 Share Posted December 14, 2023 Unfortunately there's nothing relevant logged, this usually points to a hardware issue, one thing you can try is to boot the server in safe mode with all docker/VMs disabled, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one. 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.