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
------------------------------------------------------------
On 21/03/2012 08:23, Matt Burke wrote:> 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)> # 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?Not sure if I can help but I'll throw these thoughts at you - If I run dmesg | grep ada0 the first and last lines are - ada0 at ahcich0 bus 0 scbus0 target 0 lun 0 ada0: Previously was known as ad4 or ls -l /dev | grep ada lrw-rw-rw- 1 root wheel - 4B 6 Mar 04:19 ad4@ -> ada0 lrw-rw-rw- 1 root wheel - 6B 6 Mar 04:19 ad4p1@ -> ada0p1 ... lrw-rw-rw- 1 root wheel - 4B 6 Mar 04:19 ad8@ -> ada1 lrw-rw-rw- 1 root wheel - 6B 6 Mar 16:19 ad8p1@ -> ada1p1 ... I think man glabel may give some ideas but man libgeom would be a starting place if your looking at drivers.> 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.Sounds like this is your best bet. Find out how close he is to release and offer to test, help push to be accepted in trunk.
On 03/20/12 21:53, Matt Burke wrote:> 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.Just to follow this up, I got in contact with Areca support, who sent me their new v1.00.00.02 (2012-03-23) arcsas driver and CLI tool, which is now available on their website: http://www.areca.com.tw/support/s_freebsd/nonraid_freebsd.htm The API download has also been updated (dated 2012-03-14) to include separate SAS HBA support, and stuff built against it works correctly for me. As a result I now have management visibility (and ability to toggle drive identification) via the ARC-1320 cards. -- Sorry for the below disclaimer... 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 ------------------------------------------------------------
On 03/28/12 06:11, Fred Liu wrote:> Does ARC-1320 card need specific backplane to work with to identify > HDD's position?Shouldn't imagine so... I'm using a set of 4x four-bay Chenbro 80H10321513C0 jobbies in a 4U box for a total of 16 disks. My original post showed me lighting up an identification LED by poking values at the backplane via the ses device, but the Areca utility seems to do it by poking the drives themselves - which is a much better solution and *should* be backplane-agnostic. -- Sorry for the below disclaimer 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 ------------------------------------------------------------
On 03/28/12 12:40, Fred Liu wrote:>> Shouldn't imagine so... I'm using a set of 4x four-bay Chenbro >> 80H10321513C0 jobbies in a 4U box for a total of 16 disks. >> >> My original post showed me lighting up an identification LED by poking >> values at the backplane via the ses device, but the Areca utility seems >> to >> do it by poking the drives themselves - which is a much better solution >> and >> *should* be backplane-agnostic. > > Sounds very good! But what if the drive is thoroughly damaged?How would you identify such a drive on any other system? -- Sorry for the disclaimer... 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 ------------------------------------------------------------
> > How would you identify such a drive on any other system? >Normally, there are printed labels as the backup solution. Thanks. Fred
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
---------- ????? ---------- ???? Fred Liu <fred.fliu@gmail.com> ??? 2012?4?9? ??3:56 ??? Re: SAS Drive identification LEDs ???? Mike Pumford <mpumford@mpcdata.com> Thanks. Can you recommend what drive and enclosure can provide working SES in 9.0? Thanks. Fred ? 2012?3?30? ??5:18?Mike Pumford <mpumford@mpcdata.com> ???> 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 > > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
Yes. I understand. I have been seeking for long time to enable SES in my home server which is comprised of commodity hardwares. But I have got no luck. I will try sg3_utils if possible. Many thanks. Fred ? 2012?4?10? ??4:52?Mike Pumford <mpumford@mpcdata.com> ???> Fred Liu wrote: >> >> Thanks. Can you recommend what drive and enclosure can provide working >> SES in 9.0? >> > Sadly no. Most of my disk enclosure experience was under contract to an OEM > provider of enclosures and I never really found out who they ended up > selling the final products too. These are large rack mount stand alone > enclosures and SES support was a universal feature. > > I'd still suggest installing sg3_utils you might find your current enclosure > provides enough info. > > > 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 >