From owner-freebsd-scsi@freebsd.org Wed Nov 18 16:54:20 2015 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 55711A32A46; Wed, 18 Nov 2015 16:54:20 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (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 0B47B1D9F; Wed, 18 Nov 2015 16:54:20 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1Zz5zs-000Ahq-TV; Wed, 18 Nov 2015 19:54:16 +0300 Date: Wed, 18 Nov 2015 19:54:16 +0300 From: Slawa Olhovchenkov To: Freddie Cash Cc: freebsd-stable , freebsd-scsi@freebsd.org Subject: Re: LSI SAS2008 mps driver preferred firmware version Message-ID: <20151118165416.GS31314@zxy.spb.ru> References: <56472686.5030301@free.de> <20151114143104.GA41119@in-addr.com> <7710CBCC-E68F-4454-9E29-E50ED1C6B511@sarenet.es> <20151116205734.GM48728@zxy.spb.ru> <20151118102502.GO48728@zxy.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Nov 2015 16:54:20 -0000 On Wed, Nov 18, 2015 at 08:15:15AM -0800, Freddie Cash wrote: > On Wed, Nov 18, 2015 at 2:25 AM, Slawa Olhovchenkov wrote: > > > On Mon, Nov 16, 2015 at 01:19:55PM -0800, Freddie Cash wrote: > > > > > On Mon, Nov 16, 2015 at 12:57 PM, Slawa Olhovchenkov > > wrote: > > > ​Did the original disk get labelled automatically? No, you had to do > > that > > > when you first started using it. So, why would you expect a > > > replaced disk > > > > Initial labeling is problem too. > > For new chassis with 36 identical disk (already installed) -- what is > > simple way to labeling disks? > > > > ​That's the easy part. Boot with all the drives pulled out a bit, so they > aren't connected/detected. > > Insert first disk, wait for it to be detected and get a /dev node, then > partition/label it. Repeat for each disk. Takes about 5 minutes to label > a 45-bay JBOD chassis. Hmm, from me to server more then 1700km, how I can do this? > No different than how you would get the serial number off each disk before > inserting them into the chassis, so you'd know for sure which slot they're > in. This is do by manufacturer. Or in DC after service ordering. I am don't assemble servers, in general. And I am don't see servers and don't know how they look. > "Replace disk in bay with blinked led" > > > > Author: bapt > > Date: Sat Sep 5 00:06:01 2015 > > > > ​And, how did you manage to do that before Sep 5, 2015?​ Deteched disk don't blink activity LED. > Usaly serial number can be read w/o pull disk (for SuperMicro cases > > this is true, remote hand replaced disk by S/N for me w/o pull every disk). > > > > ​How? We have all SuperMicro storage chassis (SC2xx, SC8xx, and JBODs) and > server chassis in our data centre here. None of them allow you to read the > serial number off the physical disk without pulling the disk out > completely.​ You'd have to manually label each bay with the serial number > before inserting the disk into the chassis ... which is no different from > labelling the device in the OS. Except it's much faster to find a 3D > co-ordinate (enc0a6) than to scan every bay looking for a specific serial > number. For SC847A this do for me in NL DC (as I understand -- through holes at an angle). > But, to each their own. :) Everyone has their "perfect" system that works > for them. :D > > -- > Freddie Cash > fjwcash@gmail.com