From owner-freebsd-scsi@FreeBSD.ORG Sat Oct 27 17:12:19 2012 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B6D639DE for ; Sat, 27 Oct 2012 17:12:19 +0000 (UTC) (envelope-from dgilbert@interlog.com) Received: from smtp.infotech.no (smtp.infotech.no [82.134.31.41]) by mx1.freebsd.org (Postfix) with ESMTP id 3FEEF8FC0C for ; Sat, 27 Oct 2012 17:12:18 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp.infotech.no (Postfix) with ESMTP id D79F3204184; Sat, 27 Oct 2012 19:04:48 +0200 (CEST) X-Virus-Scanned: by amavisd-new-2.6.6 (20110518) (Debian) at infotech.no Received: from smtp.infotech.no ([127.0.0.1]) by localhost (smtp.infotech.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DzUOGim1gSF3; Sat, 27 Oct 2012 19:04:47 +0200 (CEST) Received: from [192.168.48.66] (unknown [199.91.209.91]) by smtp.infotech.no (Postfix) with ESMTPA id B8EF720400E; Sat, 27 Oct 2012 19:04:46 +0200 (CEST) Message-ID: <508C1425.7040909@interlog.com> Date: Sat, 27 Oct 2012 13:04:37 -0400 From: Douglas Gilbert User-Agent: Mozilla/5.0 (X11; Linux i686; rv:16.0) Gecko/20121011 Thunderbird/16.0.1 MIME-Version: 1.0 To: Stephane LAPIE Subject: Re: LSI mpt(4) driver problem : can't SMART poll, controller freezes References: <508B5EBC.8070509@darkbsd.org> In-Reply-To: <508B5EBC.8070509@darkbsd.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-scsi@freebsd.org X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: dgilbert@interlog.com List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Oct 2012 17:12:19 -0000 On 12-10-27 12:10 AM, Stephane LAPIE wrote: > Hello list, > > I have two controller cards of the following make (PCI-X controllers) : > Oct 24 09:26:00 eirei-no-za kernel: mpt0: > port 0x2000-0x20ff mem 0xdfa20000-0xdfa23fff,0xdfa00000-0xdfa0ffff irq > 24 at device 1.0 on pci6 > Oct 24 09:26:00 eirei-no-za kernel: mpt0: MPI Version=1.5.12.0 > Oct 24 09:26:00 eirei-no-za kernel: mpt0: Capabilities: ( RAID-0 RAID-1E > RAID-1 ) > Oct 24 09:26:00 eirei-no-za kernel: mpt0: 0 Active Volumes (2 Max) > Oct 24 09:26:00 eirei-no-za kernel: mpt0: 0 Hidden Drive Members (10 Max) > > Oct 24 09:26:00 eirei-no-za kernel: mpt1: > port 0x2400-0x24ff mem 0xdfa24000-0xdfa27fff,0xdfa10000-0xdfa1ffff irq > 28 at device 7.0 on pci6 > Oct 24 09:26:00 eirei-no-za kernel: mpt1: MPI Version=1.5.12.0 > Oct 24 09:26:00 eirei-no-za kernel: mpt1: Capabilities: ( RAID-0 RAID-1E > RAID-1 ) > Oct 24 09:26:00 eirei-no-za kernel: mpt1: 0 Active Volumes (2 Max) > Oct 24 09:26:00 eirei-no-za kernel: mpt1: 0 Hidden Drive Members (10 Max) > > Each of them having 8 ports used in the following fashion : > at scbus0 target 0 lun 0 (pass0,da0) > at scbus0 target 1 lun 0 (pass1,da1) > at scbus0 target 3 lun 0 (pass2,da2) > at scbus0 target 4 lun 0 (pass3,da3) > at scbus0 target 5 lun 0 (pass4,da4) > at scbus0 target 6 lun 0 (pass5,da5) > at scbus0 target 7 lun 0 (pass6,da6) > > at scbus2 target 0 lun 0 (pass7,da7) > at scbus2 target 1 lun 0 (pass8,da8) > at scbus2 target 2 lun 0 (pass9,da9) > at scbus2 target 3 lun 0 (pass10,da10) > at scbus2 target 4 lun 0 (pass11,da11) > at scbus2 target 5 lun 0 (pass12,da12) > at scbus2 target 6 lun 0 (pass13,da13) > at scbus2 target 7 lun 0 (da14,pass14) > > It should also be noted that I have to override the default SCSI timeout > delay, in order to ensure proper detection of all devices at boot by > putting the following in /boot/loader.conf : > kern.cam.scsi_delay=15000 > > I wanted to know if anyone had experienced the following problems, and > found a way around them : > > > > 1) I can't run any detailed and meaningful SMART polls on disks > belonging to these controllers. (execution logs as separate files) > > As can be seen I am running the latest available version of smartctl > from the ports : > http://www.yomi.darkbsd.org/~darksoul/eirei-no-za-broken-disk-smart-log.txt Bad link, as are the rest in this post. Which version of smartmontools are you using? Doug Gilbert > (Using the pass devices gives the same result) > > Only the "-d scsi" polling returns somewhat meaningful info whatsoever > (disk serial number etc), but even that is error-inducing, as the disk > was actually nearing death. > Here is the full SMART log recovered from running the disk from a > USB->SATA device : > http://www.yomi.darkbsd.org/~darksoul/eirei-no-za-broken-disk-smart-log2.txt > > I actually have scripts to monitor that, but it obviously relies on > smartctl being able to do its job, which it's not... > (Also, this worked perfectly fine under 8-STABLE with "-d sat"...) > > > > 2) Also, less annoying but still a show-stopper sort of for any serious > work requiring high availability : > Any disk I/O freeze ends up locking the whole controller (and the whole > ZFS pool...) until either the server crashes or the disk bails out, > whichever comes first, really. (kernel log as separate file) > > http://www.yomi.darkbsd.org/~darksoul/eirei-no-za-mpt-timeout.txt > > > Thanks for your time. >