Date: Fri, 30 Mar 2012 10:18:31 +0100 From: Mike Pumford <mpumford@mpcdata.com> To: <freebsd-stable@freebsd.org> Subject: Re: SAS Drive identification LEDs Message-ID: <4F757A67.5080302@mpcdata.com> In-Reply-To: <CALi05Xz%2BAJvbmgwh4Jn7jHi6D_TWfnxW5QdU1j7MZYnicotEoQ@mail.gmail.com> References: <4F68FC3E.2090401@icritical.com> <4F71FEAE.3090506@icritical.com> <A5A6EA4AE9DCC44F8E7FCB4D6317B1D201C61C774418@SH-MAIL.ISSI.COM> <4F72C588.2000204@icritical.com> <A5A6EA4AE9DCC44F8E7FCB4D6317B1D201C61C7744B1@SH-MAIL.ISSI.COM> <4F7309E2.4000502@icritical.com> <CALi05Xz%2BAJvbmgwh4Jn7jHi6D_TWfnxW5QdU1j7MZYnicotEoQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Fred Liu wrote: >> >> How would you identify such a drive on any other system? >> > > Normally, there are printed labels as the backup solution. > You can identify SAS drives in an enclosure if the drive and enclosure provide the information needed. If you issue an INQUIRY EVPD read of page 0x83 on the drive it should give you the WWN and target SAS addresses of the drive. You should then be able to tie this up with the array element in the enclosure by matching it up with data in the SES diagnostic page 0xA from the enclosure. sg3_utils provides command line tools that can perform these queries. Mike -- Mike Pumford, Senior Software Engineer MPC Data Limited e-mail: mpumford@mpcdata.com web: www.mpcdata.com tel: +44 (0) 1225 710600 fax: +44 (0) 1225 710601 ddi: +44 (0) 1225 710635
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F757A67.5080302>