Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 15 Jun 2002 16:42:02 -0600
From:      Scott Long <scott_long@btc.adaptec.com>
To:        Patrick Thomas <root@utility.clubscholarship.com>
Cc:        freebsd-scsi@freebsd.org
Subject:   Re: aac problems showing up in dmesg
Message-ID:  <20020615224202.GA33523@hollin.btc.adaptec.com>
In-Reply-To: <20020615152404.D68572-100000@utility.clubscholarship.com>
References:  <20020615152404.D68572-100000@utility.clubscholarship.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Jun 15, 2002 at 03:25:58PM -0700, Patrick Thomas wrote:
> 
> Hello,
> 
> I am seeing the following messages in my dmesg:
> 
> aac0: **Monitor** ID(0:00:0) Timeout detected on cmd[0x2a]
> aac0: **Monitor** ID(0:00:0) Timeout detected on cmd[0x2a]
> aac0: **Monitor** SCSI Channel[0]: Timeout Detected On 81 Command(s)
> aac0: **Monitor** ID(0:00:0); Aborted Command [command:0x2a]
> aac0: **Monitor** ID(0:00:0); Error Event [command:0x2a]
> aac0: **Monitor** ID(0:00:0); Medium Error, Block Range 43539103 :
> 43539198
> aac0: **Monitor** ID(0:00:0); Random Positioning Error
> 
> 
> The bulk of the messages, however, are simply:
> 
> aac0: **Monitor** ID(0:00:0) Timeout detected on cmd[0x2a]
> aac0: **Monitor** ID(0:00:0) Timeout detected on cmd[0x2a]
> aac0: **Monitor** ID(0:00:0) Timeout detected on cmd[0x2a]
> aac0: **Monitor** ID(0:00:0) Timeout detected on cmd[0x2a]
> aac0: **Monitor** ID(0:00:0) Timeout detected on cmd[0x2a]
> aac0: **Monitor** ID(0:00:0) Timeout detected on cmd[0x2a]
> aac0: **Monitor** ID(0:00:0) Timeout detected on cmd[0x2a]
> aac0: **Monitor** ID(0:00:0) Timeout detected on cmd[0x2a]
> aac0: **Monitor** ID(0:00:0) Timeout detected on cmd[0x2a]
> 
> 
> Two questions:
> 
> 1) what exactly does this mean, in english :)
> 
> 2) what should I do about it ?
> 
> thanks,
> 
> PT


Those messages are coming directly from the processor on the card and
indicate some sort of problem with drive 0 on channel 0.  It could be
caused by bad cables and/or termination, or it might be that the
drive is starting to fail.  

Scott

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-scsi" in the body of the message




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