Date: Mon, 18 Nov 2013 14:55:44 -0800 From: aurfalien <aurfalien@gmail.com> To: Polytropon <freebsd@edvax.de> Cc: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: drive blink on demand? Message-ID: <05DB1D7A-BF86-4EF0-8EC8-AF6F344557D7@gmail.com> In-Reply-To: <20131118235239.8949768e.freebsd@edvax.de> References: <959063E8-FD7A-43C1-B0D7-B241F487E4BD@gmail.com> <20131118235239.8949768e.freebsd@edvax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
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=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?05DB1D7A-BF86-4EF0-8EC8-AF6F344557D7>