Minor (but confusing) error in Alert instructions on how to update LSI adapter firmware
The bottom of Section 21 of the online manual gives this command to update the LSI adapter firmware and bios:
sas2flash -f firmwareimagename -v biosname -c controllernumber
The "-v" option is incorrect and should be "-b" which I found in the sas2flash manual.
I tried "-v" and it gives an invalid command error while trying "-b" works.
This appears to be a keyboard typo since v and b are adjacent.
Also, I'm not sure this is worth opening another ticket (I leave this up to you), but the version of sas2flash in FreeNAS 9.3 is P14 (run sas2flash -ver) whereas the FreeNAS recommended LSI firmware for 9.3 is P16. There is a P16 installer for FreeBSD on the LSI web site which is a P16 version of sas2flash. It is probably a good idea to use the same revision of sas2flash that matches the firmware being installed. In reality, it's probably not critical, since sas2flash probably doesn't care what's in the firmware or bios image files, but it could contain some logic related to what bios or firmware version(s) it can load over previous versions, etc., which might prevent "bricking" the HBA in some circumstances.
FYI, my release is FreeNAS-9.3-STABLE-201501212031 which was not a choice in the Seen in drop down box.
#10 Updated by Dru Lavigne over 5 years ago
I commit doc changes to master and the stuff that is automatically built for doc.freenas.org shows my edits. If you are not doing the same thing in your automated SU builds, the SU's that were built after I sent you the tarballs are not getting updated. We agreed early in the new year that I wouldn't switch the docs from master until it came time to tag 10 and branch the docs.
#11 Updated by Jordan Hubbard over 5 years ago
Hmmm. OK, I must have missed something in that communication. I think right now we're going to have to do a forklift merge from master into 9.3-STABLE and then periodically sync it up from master before I roll SUs, because it's just not an easy thing to check just the documentation out of master. Every SU I've built for the last month or so has been done with the 9.3-STABLE doc tree. I'll figure out how to do this - no worries.