From owner-freebsd-questions@FreeBSD.ORG Mon Nov 18 22:55:48 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E446175C for ; Mon, 18 Nov 2013 22:55:48 +0000 (UTC) Received: from mail-pb0-x236.google.com (mail-pb0-x236.google.com [IPv6:2607:f8b0:400e:c01::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id BF30E2E25 for ; Mon, 18 Nov 2013 22:55:48 +0000 (UTC) Received: by mail-pb0-f54.google.com with SMTP id un15so964259pbc.41 for ; Mon, 18 Nov 2013 14:55:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=bEoDQXARcMFWFKYK2KuF7wPA90R7n3CTESsrtBrkuq4=; b=m1PyRryfB1MomfPUK8oCmXUMjQHzWYFpM/6KFOQ6YNjjNfY8SiCVprd3a0ym+36qk0 ZuJZNBDBX9vpzfnnOOBxDjeopC8XxmII18rPRacTuPA150ztH+zJ6hDHji1efRSq+qKw AyJDOHXvs3ZfjPCma9Aaxcp/FBkjIqEza+K932kA5PD351mxWFtL0x719OIspAIkqEu3 0eAiydZLtThBgELwSfBvXeFYi5a7W1wHimn/NaqkaJVJurHJFtH5MiUUA2vLyVaU8nbT kn/LAOzSOFha30CXpkFC7X8FSy+GtOzPFSjYKCXojtuks4a5Yr0HZdrZzMzWlP71whtV JR3A== X-Received: by 10.68.66.33 with SMTP id c1mr15775512pbt.73.1384815347595; Mon, 18 Nov 2013 14:55:47 -0800 (PST) Received: from briankrusicw.logan.tv ([64.17.255.138]) by mx.google.com with ESMTPSA id fk4sm29385584pab.23.2013.11.18.14.55.46 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 18 Nov 2013 14:55:46 -0800 (PST) Subject: Re: drive blink on demand? Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=us-ascii From: aurfalien In-Reply-To: <20131118235239.8949768e.freebsd@edvax.de> Date: Mon, 18 Nov 2013 14:55:44 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: <05DB1D7A-BF86-4EF0-8EC8-AF6F344557D7@gmail.com> References: <959063E8-FD7A-43C1-B0D7-B241F487E4BD@gmail.com> <20131118235239.8949768e.freebsd@edvax.de> To: Polytropon X-Mailer: Apple Mail (2.1085) Cc: FreeBSD Questions X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Nov 2013 22:55:49 -0000 On Nov 18, 2013, at 2:52 PM, Polytropon wrote: > On Mon, 18 Nov 2013 14:09:25 -0800, aurfalien wrote: >> Hi, >>=20 >> I've 42 disks across 4 JBODs using LSI HBAs. >>=20 >> I've been doing dd if=3D/dev/disk... of=3D/dev/null and watching >> what rapidly blinks to identify drives. >>=20 >> However is there a better or at least non janky way to do this? >=20 > I've been using a very stupid way: >=20 > Usually disks are located in trays. Give each tray a number > or a letter and a color, depending on if you're organizing > them in RAID configurations, such as stripes and mirrors. > Apply labels to the disks according to their code and > function, e. g. red1, red2, red3, blue1, blue2, blue3; > for a striped mirror (or mirrored stripe similarly) with > spare disks: green1a, green2a, green3a, blue1a, blue2b, > blue2b, blue3b (the disks) and red1, red2, red3 (spares). > This makes it easy to identify disks per location. So > whenever the disk labeled yellow4a causes trouble, you > immediately know where to apply a hammer. :-) >=20 > Maybe this is an inspiration for a solution, in worst case > as a "how not to do it" if it abolutely fails to meet your > requirements. :-) Thanks dude, was thinking of this as well. I was messing with the LSI sas2ircu tools. Seems aight, sorta = convoluted until I get the hang of it of course.. - aurf=