From owner-freebsd-scsi@FreeBSD.ORG Fri Dec 9 20:00:37 2005 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3C40716A41F for ; Fri, 9 Dec 2005 20:00:37 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 67C9843D64 for ; Fri, 9 Dec 2005 20:00:31 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.14] (imini.samsco.home [192.168.254.14]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id jB9K0UaP073205; Fri, 9 Dec 2005 13:00:30 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <4399E25E.5010701@samsco.org> Date: Fri, 09 Dec 2005 13:00:30 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.7) Gecko/20050416 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Brad Miele References: <20051209141608.W3172@localhost> In-Reply-To: <20051209141608.W3172@localhost> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: freebsd-scsi@freebsd.org Subject: Re: isp errors with QLogic 2312 / DL380 / MSA 1500 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Dec 2005 20:00:37 -0000 Brad Miele wrote: > Hello, > > I have recently moved from individual HP MS30 SCSI shelves to the HP MSA > 1500 SAN with two MS30 SCSI shelves and two MS20 SATA shelves. > > I am seeing the following in messages: > > Dec 9 13:42:16 bwayipn04 kernel: isp0: command timed out for 0.125.4 > Dec 9 13:49:58 bwayipn04 last message repeated 4 times > Dec 9 13:55:48 bwayipn04 last message repeated 2 times > Dec 9 13:59:44 bwayipn04 kernel: (da3:isp0:0:125:4): READ(10). CDB: 28 > 0 6a 54 85 bf 0 0 80 0 > Dec 9 13:59:44 bwayipn04 kernel: (da3:isp0:0:125:4): CAM Status: SCSI > Status Error > Dec 9 13:59:44 bwayipn04 kernel: (da3:isp0:0:125:4): SCSI Status: Check > Condition > Dec 9 13:59:44 bwayipn04 kernel: (da3:isp0:0:125:4): UNIT ATTENTION > asc:29,0 > Dec 9 13:59:44 bwayipn04 kernel: (da3:isp0:0:125:4): Power on, reset, > or bus device reset occurred > Dec 9 13:59:44 bwayipn04 kernel: (da3:isp0:0:125:4): Retrying Command > (per Sense Data) > Dec 9 13:59:45 bwayipn04 kernel: (da1:isp0:0:125:2): WRITE(10). CDB: 2a > 0 88 7a 71 9f 0 0 20 0 > Dec 9 13:59:45 bwayipn04 kernel: (da1:isp0:0:125:2): CAM Status: SCSI > Status Error > Dec 9 13:59:45 bwayipn04 kernel: (da1:isp0:0:125:2): SCSI Status: Check > Condition > Dec 9 13:59:45 bwayipn04 kernel: (da1:isp0:0:125:2): UNIT ATTENTION > asc:29,0 > Dec 9 13:59:45 bwayipn04 kernel: (da1:isp0:0:125:2): Power on, reset, > or bus device reset occurred > Dec 9 13:59:45 bwayipn04 kernel: (da1:isp0:0:125:2): Retrying Command > (per Sense Data) > Dec 9 14:00:24 bwayipn04 kernel: (da2:isp0:0:125:3): READ(10). CDB: 28 > 0 1 21 13 ff 0 0 20 0 > Dec 9 14:00:24 bwayipn04 kernel: (da2:isp0:0:125:3): CAM Status: SCSI > Status Error > Dec 9 14:00:24 bwayipn04 kernel: (da2:isp0:0:125:3): SCSI Status: Check > Condition > Dec 9 14:00:24 bwayipn04 kernel: (da2:isp0:0:125:3): UNIT ATTENTION > asc:29,0 > Dec 9 14:00:24 bwayipn04 kernel: (da2:isp0:0:125:3): Power on, reset, > or bus device reset occurred > Dec 9 14:00:24 bwayipn04 kernel: (da2:isp0:0:125:3): Retrying Command > (per Sense Data) > Dec 9 14:08:00 bwayipn04 kernel: isp0: command timed out for 0.125.4 > Dec 9 14:08:00 bwayipn04 kernel: isp0: command timed out for 0.125.4 > > the time out errors occur more often, and while the device recovers (it > seems), it does stop i/o while it works itself out. This is my first > venture into the fiber waters, and coming off of really solid > performance with the scsi shelves i am a bit worried. can anyone offer > any pointers on where to start looking here? > > regards, > > Brad This can mean that you have a bad power supply, or that the drive is having significant problems, or that an unexpected bus reset happened. The latter is the least likely. Scott