On Thu, Mar 20, 2014 at 12:42:55PM -0400, Joe Landman wrote: > Note: if you do use the LSI 2208, get a copy of the sas2ircu, so you > can light up devices ID LEDs correctly (we are adapting something we > wrote on Linux a while ago to run on SmartOS to help users correctly > identify which drive is which as this turns out to be non trivial for > zfs and non-HW raid).
The correct place for this to live is in libtopo. We've already done the work to wire up mpt_sas to the topo functionality, so that the disk-lights module will do the correct thing. Most likely all that would be required for this to work on your kit would be the creation of a proper topo map (see the one for Joyent-Compute-Platform-1101 in illumos). Please do not use third-party utilities for this, especially binary-only ones like LSI's. Note also that the existing code should work out of the box on any system that has expanders with ES targets that correctly provide LED control (it's rare to find ones that don't); the separate map is needed only for DA architectures. If any of that is not working correctly on your systems, we should get bugs filed and figure out what's wrong. > We've had a few nasty surprises on BIOS revisions on SMC kit, in that > BIOS tables set during POST aren't always what one might expect. Which > leads to some very interesting/painful crashes. It's critical to validate the firmware versions that you use and force your vendor to deliver only those versions, regardless of who the vendor is. As you well know, locking firmware revisions is pretty much the first and most basic aspect of vendor management one learns. :) ------------------------------------------- smartos-discuss Archives: https://www.listbox.com/member/archive/184463/=now RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00 Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb Powered by Listbox: http://www.listbox.com
