From owner-freebsd-stable@freebsd.org Sat Nov 14 14:31:07 2015 Return-Path: Delivered-To: freebsd-stable@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 890ECA2EDC8; Sat, 14 Nov 2015 14:31:07 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from mail.in-addr.com (mail.in-addr.com [IPv6:2a01:4f8:191:61e8::2525:2525]) (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 491FB1051; Sat, 14 Nov 2015 14:31:07 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from gjp by mail.in-addr.com with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1Zxbr6-000KXg-Mk; Sat, 14 Nov 2015 14:31:04 +0000 Date: Sat, 14 Nov 2015 14:31:04 +0000 From: Gary Palmer To: Kai Gallasch Cc: Royce Williams , freebsd-scsi@freebsd.org, freebsd-stable Subject: Re: LSI SAS2008 mps driver preferred firmware version Message-ID: <20151114143104.GA41119@in-addr.com> References: <5644FF09.9090200@free.de> <56472686.5030301@free.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <56472686.5030301@free.de> X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: gpalmer@freebsd.org X-SA-Exim-Scanned: No (on mail.in-addr.com); SAEximRunCond expanded to false X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Nov 2015 14:31:07 -0000 On Sat, Nov 14, 2015 at 01:18:14PM +0100, Kai Gallasch wrote: > On 12.11.2015 23:20 Royce Williams wrote: > > Firmware should match driver, e.g.: > > > > mps0: Firmware: 19.00.00.00, Driver: 19.00.00.00-fbs > > > > > > Some of this may help -- not yet updated for 10.2, but may still be useful: > > > > http://roycebits.blogspot.com/2015/01/freebsd-lsi-sas9211-8i-hba-firmware.html > > Thanks! Lots of information about reflashing the 9211-8i. > So I upgraded the old firmare of the controller from > > mps0: Firmware: 05.00.17.00, Driver: 20.00.00.00-fbsd > to mps0: Firmware: 20.00.04.00, Driver: 20.00.00.00-fbsd > (FreeBSD 10.2) > > As I understand it the firmware 20.00.00.00 was pulled by avago and > replaced with the fixed version 20.00.04.00 > > I will give feedback if I notice any problems with this FW version. > > As a side note: Flashing the 9211-8i to the new firmware version changed > the way FreeBSD orders the disk devices on this server: > > With the old firmware it looked like this: > > root@:~ # camcontrol devlist > at scbus0 target 10 lun 0 (pass0,da0) > at scbus0 target 11 lun 0 (pass1,da1) > at scbus0 target 12 lun 0 (pass2,da2) > at scbus0 target 13 lun 0 (pass3,da3) > at scbus0 target 14 lun 0 (pass4,da4) > at scbus0 target 15 lun 0 (pass5,da5) > at scbus0 target 16 lun 0 (pass6,da6) > at scbus0 target 17 lun 0 (pass7,da7) > at scbus0 target 18 lun 0 (pass8,da8) > at scbus0 target 19 lun 0 (pass9,da9) > at scbus0 target 20 lun 0 (pass10,da10) > at scbus0 target 21 lun 0 (pass11,da11) > at scbus0 target 22 lun 0 (pass12,ses0) > at scbus7 target 0 lun 0 (pass13,ses1) > > The order is according to the order the disks are placed in the drive > bays: (da0, bay1; da1, bay2, ..) > > > With the new firmware it now looks like this: > > at scbus0 target 8 lun 0 (pass0,da0) > at scbus0 target 9 lun 0 (pass1,da1) > at scbus0 target 10 lun 0 (pass2,da2) > at scbus0 target 11 lun 0 (pass3,da3) > at scbus0 target 12 lun 0 (pass4,da4) > at scbus0 target 13 lun 0 (pass5,da5) > at scbus0 target 14 lun 0 (pass6,da6) > at scbus0 target 15 lun 0 (pass7,da7) > at scbus0 target 16 lun 0 (pass8,da8) > at scbus0 target 17 lun 0 (pass9,da9) > at scbus0 target 18 lun 0 (pass10,da10) > at scbus0 target 19 lun 0 (pass11,da11) > at scbus0 target 20 lun 0 (pass12,ses0) > at scbus7 target 0 lun 0 (pass13,ses1) > > So now the drive stuck in the last drive bay is seen as da0 and the > drive in the first drive bay as da11 > > But: In the controller BIOS the scan order of the drives did not change > at all with the new firmware! So the change is only in the way FreeBSD > sees the drives. > > My explanation for this change in drive ordering is, that my 9211-8i is > a SUN branded one (SGX-SAS6-INT-Z) and the server is a SUN server. So > maybe the original firmware contained some adaptations for this server, > that are missing in the new firmware. > > Can the way FreeBSD orders scanned SAS drives be changed? If not, no > problem, as I use partition labels for my zfs pools and the disks are > also labeled on the server as well. You can do thinks in /boot/loader.conf to hard code bus and drive assignments. e.g. hint.da.0.at="scbus0" hint.da.0.target="19" hint.da.0.unit="0" hint.da.1.at="scbus0" hint.da.1.target="18" hint.da.1.unit="0" See scsi(4) or cam(4) for more hints. You're probably better off using GPT labels though, as they will survive any future disk order changes. The fact the target numbers changed means that loader.conf changes will fix the current issue but may not work properly after any future firmware updates. Gary