From owner-freebsd-scsi@freebsd.org Tue Jun 7 06:35:09 2016 Return-Path: Delivered-To: freebsd-scsi@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 477A1B6D2DE for ; Tue, 7 Jun 2016 06:35:09 +0000 (UTC) (envelope-from borjam@sarenet.es) Received: from cu01176a.smtpx.saremail.com (cu01176a.smtpx.saremail.com [195.16.150.151]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 08F6612E0 for ; Tue, 7 Jun 2016 06:35:08 +0000 (UTC) (envelope-from borjam@sarenet.es) Received: from [172.16.8.36] (izaro.sarenet.es [192.148.167.11]) by proxypop03.sare.net (Postfix) with ESMTPSA id 1E7E89DE019; Tue, 7 Jun 2016 08:25:19 +0200 (CEST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: Avago LSI SAS 3008 & Intel SSD Timeouts From: Borja Marcos In-Reply-To: <986e03a7-5dc8-f5e0-5a17-4bf49459f905@mindpackstudios.com> Date: Tue, 7 Jun 2016 08:25:19 +0200 Cc: freebsd-scsi@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <2823D96D-881D-4D40-B610-FC8292FA2FC5@sarenet.es> References: <30c04d8b-80cb-c637-26dc-97caebad3acb@mindpackstudios.com> <08C01646-9AF3-4E89-A545-C051A284E039@sarenet.es> <986e03a7-5dc8-f5e0-5a17-4bf49459f905@mindpackstudios.com> To: list-news X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Jun 2016 06:35:09 -0000 > On 07 Jun 2016, at 00:19, list-news = wrote: >=20 > *# sysctl vfs.zfs.vdev.bio_delete_disable=3D1* > (a few minutes later) So trim is not causing it. >=20 > *Error:* > Jun 6 13:36:15 s18 kernel: (da6:mpr0:0:16:0): WRITE(10). CDB: 2a 00 = 30 65 13 90 00 00 10 00 > Jun 6 13:36:15 s18 kernel: (da6:mpr0:0:16:0): CAM status: SCSI Status = Error > Jun 6 13:36:15 s18 kernel: (da6:mpr0:0:16:0): SCSI status: Check = Condition > Jun 6 13:36:15 s18 kernel: (da6:mpr0:0:16:0): SCSI sense: UNIT = ATTENTION asc:29,0 (Power on, reset, or bus device reset occurred) > Jun 6 13:36:15 s18 kernel: (da6:mpr0:0:16:0): Retrying command (per = sense data) > ... >=20 > *And again 2 minutes later:* >=20 > Jun 6 13:38:43 s18 kernel: (da2:mpr0:0:12:0): WRITE(10). CDB: 2a 00 = 21 66 63 58 00 00 10 00 > Jun 6 13:38:43 s18 kernel: (da2:mpr0:0:12:0): CAM status: SCSI Status = Error > Jun 6 13:38:43 s18 kernel: (da2:mpr0:0:12:0): SCSI status: Check = Condition > Jun 6 13:38:43 s18 kernel: (da2:mpr0:0:12:0): SCSI sense: UNIT = ATTENTION asc:29,0 (Power on, reset, or bus device reset occurred) > Jun 6 13:38:43 s18 kernel: (da2:mpr0:0:12:0): Retrying command (per = sense data) I suffered this particular symptom because, it seems of a broken LSI3008 = card. Finally I replaced it with a LSI2008 (I didn=E2=80=99t have a = spare LSI3008 handy) and the errors vanished. In my case it is a NFS storage = based on ZFS and Samsung SSD disks serving several Xen=20 hosts. In my case the disks are SATA. I know that it was a defective card and not a problem with the LSI3008 = cards or driver because I have a twin system working like a charm from day zero. I would try, if possible, to swap the controller.=20 Borja.