mostlydave Posted November 17, 2021 Share Posted November 17, 2021 My server boots, but parity check stops progressing at random point. I have powered off and check all connections, they seem good to me. I have attached a diagnostic before starting the array and after, and current syslog. I am unable to get a diagnostic download after the parity check hangs. Please let me know if this server can be salvaged, I'm about ready to give up on it. zelda-syslog-20211117-1339.zip zelda-diagnostics-20211116-1913.zip zelda-diagnostics-20211116-1912.zip Quote Link to comment
trurl Posted November 17, 2021 Share Posted November 17, 2021 Your syslog ends with a lot of this Nov 17 08:29:15 Zelda kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Nov 17 08:29:19 Zelda kernel: sd 13:0:0:0: Power-on or device reset occurred Nov 17 08:29:19 Zelda rc.diskinfo[8842]: SIGHUP received, forcing refresh of disks info. Nov 17 08:29:19 Zelda kernel: sd 13:0:0:0: Power-on or device reset occurred which is referring to this 03:00.0 Serial Attached SCSI controller [0107]: Broadcom / LSI SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] [1000:0072] (rev 03) You should only run a correcting parity check after a noncorrecting check shows sync errors, and you are reasonably sure there isn't some hardware problem. So you are corrupting parity due to controller issues. Quote Link to comment
mostlydave Posted November 17, 2021 Author Share Posted November 17, 2021 So I just powered off, reseated the Controller card, and the server rebooted without prompting to do a parity check: The array did start and seems ok, Should I start a noncorrecting parity check now? Quote Link to comment
trurl Posted November 17, 2021 Share Posted November 17, 2021 7 minutes ago, mostlydave said: Should I start a noncorrecting parity check now? Yes. I suspect you may have already corrupted parity, but no point in correcting it now until you see if your hardware is working well enough to get a good result. Quote Link to comment
Michael_P Posted November 17, 2021 Share Posted November 17, 2021 You should also update the firmware on the HBA, 07.15.08.00 is really old Quote Link to comment
mostlydave Posted November 18, 2021 Author Share Posted November 18, 2021 I don't have a good feeling about things so far Quote Link to comment
trurl Posted November 18, 2021 Share Posted November 18, 2021 post new diagnostics Quote Link to comment
Squid Posted November 18, 2021 Share Posted November 18, 2021 As mentioned, update your firmware. But wouldn't be a bad idea to reseat the cabling (power and sata / sas) to the drives. Quote Link to comment
mostlydave Posted November 18, 2021 Author Share Posted November 18, 2021 Here's a current Diagnostics, I'll work on the firmware zelda-diagnostics-20211117-1919.zip Quote Link to comment
trurl Posted November 18, 2021 Share Posted November 18, 2021 2 hours ago, mostlydave said: current Diagnostics Looks like the earlier ones 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.