July 3, 20224 yr Issue in title. See attached for anonymized logs. tower-diagnostics-20220703-1821.zip
July 4, 20224 yr Community Expert If the server power downs it's likely a hardware problem, possibly temp or PSU related.
July 25, 20223 yr Author 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
July 25, 20223 yr Author 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.
July 25, 20223 yr Community Expert Nothing relevant logged before the crash, that also points to a hardware problem.
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.