syslog error help

[Rob_Dingen]

Hi

 

I have some error lines in the syslog is this a big problem?

MB X8SIL-F

SASLP-MV8

6x Hitachi 2TB 5k3000

1x WD EARS 2TB

PRO 5.10b

Below are the lines colored red in unMenu

Jul 29 20:38:11 Towermetin kernel: ata5: sas eh calling libata port error handler (Errors)

Jul 29 20:38:11 Towermetin kernel: ata5: sas eh calling libata port error handler (Errors)

Jul 29 20:38:11 Towermetin kernel: ata6: sas eh calling libata port error handler (Errors)

Jul 29 20:38:11 Towermetin kernel: ata5: sas eh calling libata port error handler (Errors)

Jul 29 20:38:11 Towermetin kernel: ata6: sas eh calling libata port error handler (Errors)

Jul 29 20:38:11 Towermetin kernel: ata7: sas eh calling libata port error handler (Errors)

Compleet syslog attached

 

Rob

 

syslog-2011-07-29.txt

[Joe L.]

Hi

 

I have some error lines in the syslog is this a big problem?

MB X8SIL-F

SASLP-MV8

6x Hitachi 2TB 5k3000

1x WD EARS 2TB

PRO 5.10b

Below are the lines colored red in unMenu

Jul 29 20:38:11 Towermetin kernel: ata5: sas eh calling libata port error handler (Errors)

Jul 29 20:38:11 Towermetin kernel: ata5: sas eh calling libata port error handler (Errors)

Jul 29 20:38:11 Towermetin kernel: ata6: sas eh calling libata port error handler (Errors)

Jul 29 20:38:11 Towermetin kernel: ata5: sas eh calling libata port error handler (Errors)

Jul 29 20:38:11 Towermetin kernel: ata6: sas eh calling libata port error handler (Errors)

Jul 29 20:38:11 Towermetin kernel: ata7: sas eh calling libata port error handler (Errors)

Compleet syslog attached

 

Rob

 

 

The lines are "red" only because they have the word error somewhere within them.  They would be red if they said

No Errors detected...

Just letting you know, the color coding is only based on a few pattern matching rules.

[Rob_Dingen]

Thanks Joe

 

Running parity check now at 50% and no errors yet.

 

Rob