michealangelo Posted July 26 Share Posted July 26 (edited) recently moved and my server has been acting up and I just can't pin down exactly what it is. last lines I see in the log before each crash: Jul 25 17:50:31 Tower kernel: mdcmd (37): nocheck cancel Jul 25 17:50:31 Tower kernel: md: recovery thread: exit status: -4 Jul 25 08:55:48 Tower network: reload service: nginx Jul 25 09:05:00 Tower root: Fix Common Problems Version 2024.05.04 Jul 25 09:05:01 Tower root: Fix Common Problems: Warning: Docker Application MKVToolNix has an update available for it Jul 25 09:05:07 Tower root: Fix Common Problems: Error: Macvlan and Bridging found Jul 24 06:50:00 Tower root: Fix Common Problems Version 2024.05.04 Jul 24 06:50:02 Tower root: Fix Common Problems: Warning: Docker Application MKVToolNix has an update available for it Jul 24 06:50:05 Tower root: Fix Common Problems: Error: Machine Check Events detected on your server Jul 24 06:50:05 Tower root: mcelog: ERROR: AMD Processor family 23: mcelog does not support this processor. Please use the edac_mce_amd module instead. Jul 24 06:50:05 Tower root: CPU is unsupported Jul 24 06:50:08 Tower root: Fix Common Problems: Error: Macvlan and Bridging found Jul 24 11:55:43 Tower kernel: usb 1-9: reset high-speed USB device number 2 using xhci_hcd Jul 24 11:55:44 Tower kernel: sd 0:0:0:0: [sda] 62656641 512-byte logical blocks: (32.1 GB/29.9 GiB) Jul 25 03:04:50 Tower root: /var/lib/docker: 7.3 GiB (7890485248 bytes) trimmed on /dev/loop2 Jul 25 03:04:50 Tower root: /mnt/cache: 854 GiB (917023154176 bytes) trimmed on /dev/sdb1 Jul 23 19:36:56 Tower kernel: usb 1-9: reset high-speed USB device number 2 using xhci_hcd Jul 23 19:36:56 Tower kernel: sd 0:0:0:0: [sda] 62656641 512-byte logical blocks: (32.1 GB/29.9 GiB) unassigned.devices and 'Fix Common Problems' have been removed but server still ends up crashing. any help would be greatly appreciated Edited July 26 by michealangelo Quote Link to comment
michealangelo Posted July 26 Author Share Posted July 26 here's the full log syslog-4.log Quote Link to comment
itimpi Posted July 26 Share Posted July 26 30 minutes ago, michealangelo said: Jul 24 06:50:08 Tower root: Fix Common Problems: Error: Macvlan and Bridging found What release of Unraid Are you using? If not on the 6.12.11 (or a 7.0.0 beta) then you could be getting macvlan related crashes. Quote Link to comment
michealangelo Posted July 26 Author Share Posted July 26 3 hours ago, itimpi said: What release of Unraid Are you using? If not on the 6.12.11 (or a 7.0.0 beta) then you could be getting macvlan related crashes. updated to 6.12.11 4-5 days ago and that seemed to help but it crashed again eventually Quote Link to comment
JorgeB Posted July 26 Share Posted July 26 Unfortunately there's nothing relevant logged, this can be a hardware issue, one thing you can try is to boot the server in safe mode with all docker containers/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. Quote Link to comment
michealangelo Posted July 26 Author Share Posted July 26 16 minutes ago, JorgeB said: Unfortunately there's nothing relevant logged, this can be a hardware issue, one thing you can try is to boot the server in safe mode with all docker containers/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. thanks for the input. I've been coming to the same conclusion but what doesn't make sense to me is it has never crashed during the parity check and this particular server had an uptime in the hundreds of days up until a couple months ago Quote Link to comment
JorgeB Posted July 27 Share Posted July 27 Parity check increases load/power usage, any marginal hardware could now show the problem. Quote Link to comment
michealangelo Posted July 29 Author Share Posted July 29 server is still crashing any help would be greatly appreciated syslog2.txt Quote Link to comment
JorgeB Posted July 29 Share Posted July 29 Still the same: On 7/26/2024 at 6:57 PM, JorgeB said: Unfortunately there's nothing relevant logged Quote Link to comment
michealangelo Posted July 29 Author Share Posted July 29 Just now, JorgeB said: Still the same: yes that is why I am asking the community Quote Link to comment
michealangelo Posted July 29 Author Share Posted July 29 On 7/27/2024 at 3:55 AM, JorgeB said: Parity check increases load/power usage, any marginal hardware could now show the problem. this just makes no sense to me... server is functional under load but crashes during idle? seems so incredibly unlikely Quote Link to comment
Solution JorgeB Posted July 29 Solution Share Posted July 29 40 minutes ago, michealangelo said: server is functional under load but crashes during idle? I understood it was the opposite, you didn't post the diags so don't know what CPU you are using, but that is a known issue with Ryzen CPUs, if that is the case see here: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173 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.