Intermittent Shutdowns


1 post in this topic Last Reply

Recommended Posts

After about 2 years of running good I am experiencing random shutdowns. At first I thought it was my PSU because I was using an old EVGA bronze from like 15 years ago... Replaced that with a new one and the issue is still continuing. I ran memtest for well over 24 hours and that passed with no issues as well. The system is also connected to an UPS and it has been tested with full poweroutages thanks to construction so I think I can rule that out for the most part. My next step, unless you guys can find something in the logs pointing towards an issue, was going to be setting up a vm and stress testing the cpus. I think that might not really test them properly if I remember how hypervisors assign cpu usage. They were installed recently, but have been function fine for about 6 months. Who knows what kind of lottery I rolled with used server parts, though.

 

Attached diagnostics from after reboot.

I also started keeping a syslog record with the syslog server feature since this started happening.

This is what the log looked like in the hours before the shutdown:
 

Quote

Jul 21 06:12:12 MediaVault kernel: mdcmd (219): set md_write_method 0
Jul 21 06:12:12 MediaVault kernel:
Jul 21 06:17:12 MediaVault kernel: mdcmd (220): set md_write_method 1
Jul 21 06:17:12 MediaVault kernel:
Jul 21 06:32:12 MediaVault kernel: mdcmd (221): set md_write_method 0
Jul 21 06:32:12 MediaVault kernel:
Jul 21 06:37:12 MediaVault kernel: mdcmd (222): set md_write_method 1
Jul 21 06:37:12 MediaVault kernel:
Jul 21 06:47:12 MediaVault kernel: mdcmd (223): set md_write_method 0
Jul 21 06:47:12 MediaVault kernel:
Jul 21 06:52:12 MediaVault kernel: mdcmd (224): set md_write_method 1
Jul 21 06:52:12 MediaVault kernel:
Jul 21 07:07:12 MediaVault kernel: mdcmd (225): set md_write_method 0
Jul 21 07:07:12 MediaVault kernel:
Jul 21 07:12:12 MediaVault kernel: mdcmd (226): set md_write_method 1
Jul 21 07:12:12 MediaVault kernel:
Jul 21 07:22:12 MediaVault kernel: mdcmd (227): set md_write_method 0
Jul 21 07:22:12 MediaVault kernel:
Jul 21 07:27:12 MediaVault kernel: mdcmd (228): set md_write_method 1
Jul 21 07:27:12 MediaVault kernel:
Jul 21 07:37:12 MediaVault kernel: mdcmd (229): set md_write_method 0
Jul 21 07:37:12 MediaVault kernel:
Jul 21 07:42:12 MediaVault kernel: mdcmd (230): set md_write_method 1
Jul 21 07:42:12 MediaVault kernel:
Jul 21 07:52:12 MediaVault kernel: mdcmd (231): set md_write_method 0
Jul 21 07:52:12 MediaVault kernel:
Jul 21 07:57:12 MediaVault kernel: mdcmd (232): set md_write_method 1
Jul 21 07:57:12 MediaVault kernel:
Jul 21 12:07:14 MediaVault kernel: mdcmd (233): set md_write_method 0
Jul 21 12:07:14 MediaVault kernel:
Jul 21 12:12:14 MediaVault kernel: mdcmd (234): set md_write_method 1
Jul 21 12:12:14 MediaVault kernel:
Jul 21 13:22:14 MediaVault kernel: mdcmd (235): set md_write_method 0
Jul 21 13:22:14 MediaVault kernel:
Jul 21 13:27:14 MediaVault kernel: mdcmd (236): set md_write_method 1
Jul 21 13:27:14 MediaVault kernel:
Jul 21 14:22:14 MediaVault kernel: mdcmd (237): set md_write_method 0
Jul 21 14:22:14 MediaVault kernel:
Jul 21 14:27:14 MediaVault kernel: mdcmd (238): set md_write_method 1
Jul 21 14:27:14 MediaVault kernel:
Jul 21 17:07:15 MediaVault kernel: mdcmd (239): set md_write_method 0
Jul 21 17:07:15 MediaVault kernel:
Jul 21 17:17:15 MediaVault kernel: mdcmd (240): set md_write_method 1
Jul 21 17:17:15 MediaVault kernel:
Jul 21 17:42:15 MediaVault kernel: mdcmd (241): set md_write_method 0
Jul 21 17:42:15 MediaVault kernel:
Jul 21 17:47:15 MediaVault kernel: mdcmd (242): set md_write_method 1
Jul 21 17:47:15 MediaVault kernel:
Jul 21 18:12:16 MediaVault kernel: mdcmd (243): set md_write_method 0
Jul 21 18:12:16 MediaVault kernel:
Jul 21 18:17:16 MediaVault kernel: mdcmd (244): set md_write_method 1
Jul 21 18:17:16 MediaVault kernel:
Jul 21 19:12:19 MediaVault kernel: docker0: port 8(veth3332aa4) entered blocking state
Jul 21 19:12:19 MediaVault kernel: docker0: port 8(veth3332aa4) entered disabled state
Jul 21 19:12:19 MediaVault kernel: device veth3332aa4 entered promiscuous mode
Jul 21 19:12:19 MediaVault kernel: IPv6: ADDRCONF(NETDEV_UP): veth3332aa4: link is not ready
Jul 21 19:12:19 MediaVault kernel: docker0: port 8(veth3332aa4) entered blocking state
Jul 21 19:12:19 MediaVault kernel: docker0: port 8(veth3332aa4) entered forwarding state
Jul 21 19:12:19 MediaVault kernel: docker0: port 8(veth3332aa4) entered disabled state
Jul 21 19:12:20 MediaVault kernel: eth0: renamed from veth5965a01
Jul 21 19:12:20 MediaVault kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth3332aa4: link becomes ready
Jul 21 19:12:20 MediaVault kernel: docker0: port 8(veth3332aa4) entered blocking state
Jul 21 19:12:20 MediaVault kernel: docker0: port 8(veth3332aa4) entered forwarding state

 

mediavault-diagnostics-20200721-2131.zip

Edited by Civrock
Link to post

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.