jwmoss Posted July 3, 2022 Share Posted July 3, 2022 Issue in title. See attached for anonymized logs. tower-diagnostics-20220703-1821.zip Quote Link to comment
JorgeB Posted July 4, 2022 Share Posted July 4, 2022 If the server power downs it's likely a hardware problem, possibly temp or PSU related. Quote Link to comment
jwmoss Posted July 25, 2022 Author Share Posted July 25, 2022 Uploaded persistent logs. This wasn't during a parity check, which leads me to believe some sort of hardware failure. Not sure where to start? First line of problem: Jul 24 21:10:32 Tower kernel: microcode: microcode updated early to revision 0x28, date = 2019-11-12 **** syslog Quote Link to comment
jwmoss Posted July 25, 2022 Author Share Posted July 25, 2022 1 minute ago, jwmoss said: Uploaded persistent logs. This wasn't during a parity check, which leads me to believe some sort of hardware failure. Not sure where to start? First line of problem: Jul 24 21:10:32 Tower kernel: microcode: microcode updated early to revision 0x28, date = 2019-11-12 **** syslog 601.41 kB · 0 downloads This was 2 hours prior: Jul 24 19:46:05 Tower kernel: TCP: br0: Driver has suspect GRO implementation, TCP performance may be compromised. Quote Link to comment
JorgeB Posted July 25, 2022 Share Posted July 25, 2022 Nothing relevant logged before the crash, that also points to a hardware problem. 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.