Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 6 Jun 2010 04:49:01 +0200
From:      =?iso-8859-1?Q?St=E5le?= Kristoffersen <staale@kristoffersen.ws>
To:        Artem Belevich <fbsdlist@src.cx>
Cc:        freebsd-scsi@freebsd.org, Matthew Jacob <mj@feral.com>
Subject:   Re: mpt request timed out
Message-ID:  <20100606024901.GC53735@putsch.kolbu.ws>
In-Reply-To: <AANLkTikRlH9DHdVMKSYImSaE1kxLuqCKiUN992dtvQlm@mail.gmail.com>
References:  <20100606014516.GA53735@putsch.kolbu.ws> <AANLkTim2DGamjA3kV6jDcjyXNhhkL6j6aCfT__V7ZFpQ@mail.gmail.com> <4C0B077F.1020409@feral.com> <AANLkTikRlH9DHdVMKSYImSaE1kxLuqCKiUN992dtvQlm@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On 2010-06-05 at 19:37, Artem Belevich wrote:
> On Sat, Jun 5, 2010 at 7:27 PM, Matthew Jacob <mj@feral.com> wrote:
> > On 6/5/2010 7:25 PM, Artem Belevich wrote:
> >> I used to have "UNIT ATTENTION asc:29,0" errors on mpt when it was
> > I'm sorry, but this is useless and totally not relevant. Unit Attention in
> > this case just notes that a reset occurred.d
> 
> Agreed. That particular message didn't help me at all in
> troubleshooting the problem.
> I've stumbled on correlating SMART data more or less by accident.
> 
> >> In my case those errors were correlating pretty well with disks' SMART
> >> UDMA_CRC_Error_Count.
> >
> > That is much more useful.
> 
> After firmware change both mpt and SMART errors disappeared.

I'm already running the latest IT firmware, and I don't have any
CRC-errors:
# for i in {0..20}; do smartctl -a da$i > da$i;done
da0:199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
da1:199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
da10:199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
da11:199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
da12:199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
da13:199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
da14:199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
da15:199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
da16:199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
da17:199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
da18:199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
da19:199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
da2:199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
da20:199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
da3:199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
da4:199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
da5:199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
da6:199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
da7:199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
da8:199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
da9:199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0

-- 
Ståle Kristoffersen



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100606024901.GC53735>