[OpenIndiana-discuss] LSI 9211-8i kernel error message

[Brogyányi József]

Hi

I found the bug. I'd like to write what was the problem. My server is 
Dell PowerEdge T20. It has 2 PCIe big slots.
One is 2.0 other is 3.0. This card is working both slots. I thought that 
it's working only one slot.
So it's working in blue SLOT1. It close to CPU.
The black SLOT4 close to the bottom of case.
Now it hasn't got any kernel or smart 199 error. I  think the black slot 
is driven by C226 and blue is driven by CPU.
I'm very happy now.
Brogyi

2014.11.07. 15:38 keltezéssel, Scott LeFevre írta:
> On Fri, 2014-11-07 at 14:57 +0100, Brogyányi József wrote:
>> 2014.11.07. 14:51 keltezéssel, Scott LeFevre írta:
>>> sudo sasinfo hba-port -vly
>> Scott thank you very much but what does it mean this text?
>>
>> HBA Name: SUNW-mpt_sas-0
>>     HBA Port Name: /dev/cfg/c9
>>       Type: SAS Device
>>       State: online
>>       Local SAS Address: 500605b002c88570
>>       Attached SAS Address: 50014ee003cc90e6
>>       Number of Phys: 1
>>       Phy Information:
>>         Identifier: 2
>>           State:  enabled
>>           HardwareLinkRate(Min/Max): 1.5Gbit/6Gbit
>>           ProgrammedLinkRate(Min/Max): 1.5Gbit/6Gbit
>>           NegotiatedLinkRate: 6Gbit
>>           Link Error Statistics:
>>               Invalid Dword: 0
>>               Running Disparity Error: 0
>>               Loss of Dword Sync: 0
>>               Reset Problem: 0
>>     HBA Port Name: /dev/cfg/c10
>>       Type: SAS Device
>>       State: online
>>       Local SAS Address: 500605b002c88570
>>       Attached SAS Address: 50014ee003ccd190
>>       Number of Phys: 1
>>       Phy Information:
>>         Identifier: 3
>>           State:  enabled
>>           HardwareLinkRate(Min/Max): 1.5Gbit/6Gbit
>>           ProgrammedLinkRate(Min/Max): 1.5Gbit/6Gbit
>>           NegotiatedLinkRate: 6Gbit
>>           Link Error Statistics:
>>               Invalid Dword: 0
>>               Running Disparity Error: 0
>>               Loss of Dword Sync: 0
>>               Reset Problem: 0
>>     HBA Port Name: /dev/cfg/c11
>>       Type: SAS Device
>>       State: online
>>       Local SAS Address: 500605b002c88570
>>       Attached SAS Address: 50014ee25f963534
>>       Number of Phys: 1
>>       Phy Information:
>>         Identifier: 6
>>           State:  enabled
>>           HardwareLinkRate(Min/Max): 1.5Gbit/6Gbit
>>           ProgrammedLinkRate(Min/Max): 1.5Gbit/6Gbit
>>           NegotiatedLinkRate: 6Gbit
>>           Link Error Statistics:
>>               Invalid Dword: 0
>>               Running Disparity Error: 0
>>               Loss of Dword Sync: 0
>>               Reset Problem: 0
>>     HBA Port Name: /dev/cfg/c13
>>       Type: SAS Device
>>       State: online
>>       Local SAS Address: 500605b002c88570
>>       Attached SAS Address: 50014ee20a40fba8
>>       Number of Phys: 1
>>       Phy Information:
>>         Identifier: 4
>>           State:  enabled
>>           HardwareLinkRate(Min/Max): 1.5Gbit/6Gbit
>>           ProgrammedLinkRate(Min/Max): 1.5Gbit/6Gbit
>>           NegotiatedLinkRate: 6Gbit
>>           Link Error Statistics:
>>               Invalid Dword: 0
>>               Running Disparity Error: 0
>>               Loss of Dword Sync: 0
>>               Reset Problem: 0
>>
> This output likely rules out your cabling and possibly your power supply
> as being an issue.  All the link rates negotiated at 6Gbit and there are
> no error, sync, or reset issues reported presumably by the hba which is
> good.
>
> I've seen issues similar to your caused by the power supply being under
> powered or low quality.
>
> I'd recommend looking at smartmontools and what you get out of
> smartctl -d scsi -x /dev/....
>
> Look for Non-media error count and if its increasing with each message.
>
> At the end of the output there's typically a SAS SSP section that lists
> other link related counters that the drive is tracking.  I just looked
> at one of my systems and the hba doesn't show any link issues (via
> sasinfo) but the drive has registered several Invalid DWORD count,
> Running disparity error count, and Loss of DWORD synchronization events.
> This system isn't producing any disk or hba error messages so this may
> be common or typical.
>
>