Date: Tue, 20 Mar 2012 21:53:02 +0000 From: Matt Burke <mattblists@icritical.com> To: freebsd-stable@freebsd.org Subject: SAS Drive identification LEDs Message-ID: <4F68FC3E.2090401@icritical.com>
next in thread | raw e-mail | index | archive | help
Under 9.0-RELEASE I'm having trouble figuring out how to light up the drive identification/fault lights on my enclosure (SAS disks on Chenbro 80H10321513C0 backplanes attached to Areca ARC-1320 HBAs) Building+installing the tools in /usr/share/examples/ses gives me the following ability: # getencstat -V /dev/ses0 /dev/ses0: Enclosure Status <OK> Element 0x0: Array device OK (Status=ok (bytes=0x01 0x00 0x00 0x00)) Element 0x1: Array device OK (Status=ok (bytes=0x01 0x00 0x00 0x00)) Element 0x2: Array device OK (Status=ok (bytes=0x01 0x00 0x00 0x00)) Element 0x3: Array device OK (Status=ok (bytes=0x01 0x00 0x00 0x00)) Element 0x4: Array device, Status=unknown status code 8 (bytes=0x08 0x00 0x00 0x00) Element 0x5: Array device, Status=unknown status code 8 (bytes=0x08 0x00 0x00 0x00) Element 0x6: Array device, Status=unknown status code 8 (bytes=0x08 0x00 0x00 0x00) Element 0x7: Array device, Status=unknown status code 8 (bytes=0x08 0x00 0x00 0x00) Element 0x8: Array device OK (Status=ok (bytes=0x01 0x00 0x00 0x00)) Element 0x9: Array device OK (Status=ok (bytes=0x01 0x00 0x00 0x00)) Element 0xa: Array device OK (Status=ok (bytes=0x01 0x00 0x00 0x00)) Element 0xb: Array device OK (Status=ok (bytes=0x01 0x00 0x00 0x00)) Element 0xc: Array device, Status=unknown status code 8 (bytes=0x08 0x00 0x00 0x00) Element 0xd: Array device, Status=unknown status code 8 (bytes=0x08 0x00 0x00 0x00) Element 0xe: Array device, Status=unknown status code 8 (bytes=0x08 0x00 0x00 0x00) Element 0xf: Array device, Status=unknown status code 8 (bytes=0x08 0x00 0x00 0x00) Element 0x10: Enclosure OK (Status=ok (bytes=0x01 0x00 0x00 0x00)) Element 0x11: SAS Expander OK (Status=ok (bytes=0x01 0x00 0x00 0x00)) Element 0x12: SAS Connector, Status=unknown status code 8 (bytes=0x08 0x00 0x00 0x00) Element 0x13: SAS Connector OK (Status=ok (bytes=0x01 0x3f 0x00 0x00)) Element 0x14: SAS Connector OK (Status=ok (bytes=0x01 0x02 0x00 0x00)) Element 0x15: SAS Connector, Status=unknown status code 8 (bytes=0x08 0x00 0x00 0x00) # setobjstat /dev/ses0 0xb 0x80 0x00 0x02 0x00 < light on drive bay 8 starts flashing > # setobjstat /dev/ses0 0xb 0x80 0x00 0x00 0x00 < light on drive bay 8 stops flashing > Which is great, but how can I work out how /dev/daNN maps to /dev/sesN element 0xNN? I've read mav@'s 2011 PDF on Enclosure Management (http://people.freebsd.org/~mav/Enclosure_Management_en.pdf) which shows a work-in-progress driver and getencstat which does what I need, but it looks like the project's not been committed yet. I've also tried playing around with Areca's SDK, however FreeBSDSCSIInterface()->init(i) causes the closed source driver to panic the kernel. AFAICT that class appears to be closed source too, so that's a dead end too. Is there any current way of mapping LED toggling with drive/serial numbers, or some sort of Areca HBA utility like mfiutil, or is it down to sticky labels on the front of the drive caddies? Thanks -- Sorry for the below... The information contained in this message is confidential and is intended for the addressee only. If you have received this message in error or there are any problems please notify the originator immediately. The unauthorised use, disclosure, copying or alteration of this message is strictly forbidden. Critical Software Ltd. reserves the right to monitor and record e-mail messages sent to and from this address for the purposes of investigating or detecting any unauthorised use of its system and ensuring its effective operation. Critical Software Ltd. registered in England, 04909220. Registered Office: IC2, Keele Science Park, Keele, Staffordshire, ST5 5NH. ------------------------------------------------------------ This message has been scanned for security threats by iCritical. For further information, please visit www.icritical.com ------------------------------------------------------------
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F68FC3E.2090401>