mptbase Code={Abort}
Quoted 4 lines
Could you let me know when he replies, please? I would like know whether it is something serious or can be ignored.
Certainly. I think this is certainly impacting performance badly, judging by the LED's on each drive - each time an error occurs, it can take up to 10 seconds for them toi settle back to a stable pattern of activity.
Quoted 2 lines
I have noticed that turning off NCQ significantly reduces amount of the errors.
I have already tried this and found that the errors were slightly more frequent, but I had updated the HBA BIOS and firmware before I set the queues to 1, so I'm not sure which change had an effect.
Regards,
Richard
Quoted 2 lines · Richard Scobie
I have already tried this and found that the errors were slightly more frequent, but I had updated the HBA BIOS and firmware before I set the queues to 1, so I'm not sure which change had an effect.
In my case, setting it reduced amount of errors from ~100 to ~30 during full raid rebuild. But anyway -- it is still 30 to more.
I have made an updated of the BIOS and firmware as a first thing after I have connected controllers so I cannot compare results with the old BIOS unfortunately.
Regards,
Sebastian
Re: mptbase Code={Abort} (LSI SAS1068 PCI-X Fusion-MPT)
Hi All,
The problem still exists. With NCQ turned off as well as with NCQ turned on.
# dmesg |grep 'Code={Abort}, SubCode(0x3000)'
mptbase: ioc0: LogInfo(0x31123000): Originator={PL}, Code={Abort}, SubCode(0x3000)
mptbase: ioc0: LogInfo(0x31123000): Originator={PL}, Code={Abort}, SubCode(0x3000)
mptbase: ioc0: LogInfo(0x31123000): Originator={PL}, Code={Abort}, SubCode(0x3000)
(...)# dmesg |grep 'Code={Abort}, SubCode(0x3000)' |wc -l
377Does anyone know, what that messages mean?
Regards,
Sebastian