> On May 5, 2017, at 11:32 PM, Artyom Zhandarovsky <bardi...@gmail.com> wrote: > > Hi to every one. > > I have found a way to use latst SAS3IRCU_P14.zip in OmiOS. > If to look a little bit closer into internals of the old sas3ircu you will > see the following: > > ===== cut ==== > 00000254BA: FE FF 2F 00 64 69 5F 69 │ 6E 69 74 28 29 20 66 61 юя/ di_init() > fa > 00000254CA: 69 6C 65 64 0A 00 6D 70 │ 74 5F 73 61 73 00 2F 64 iled◙ mpt_sas > /d > > ===== cut ==== > > if you look into newest versions > > ===== cut ==== > 00000253D5: 6F 74 2F 00 64 69 5F 69 │ 6E 69 74 28 29 20 66 61 ot/ di_init() > fa > 00000253E5: 69 6C 65 64 0A 00 6C 73 │ 63 00 6D 70 74 5F 73 61 iled◙ lsc > mpt_sa > 00000253F5: 73 00 2F 64 65 76 69 63 │ 65 73 25 73 3A 64 65 76 s > /devices%s:dev > ===== cut ==== > > yes it looks into lsc driver, but it also new about mpt_sas, but for some > reason it does not work. > > So why just not to make some "hiew" )) and place mpt_sas in front of lsc > > ========= cut ============== > 00000251C0: 6D 70 2F 72 6F 6F 74 2F │ 00 64 69 5F 69 6E 69 74 mp/root/ > di_init > 00000251D0: 28 29 20 66 61 69 6C 65 │ 64 0A 00 6D 70 74 5F 73 () failed◙ > mpt_s > 00000251E0: 61 73 00 6C 73 63 00 2F │ 64 65 76 69 63 65 73 25 as lsc > /devices% > 00000251F0: 73 3A 64 65 76 63 74 6C │ 00 53 41 53 32 30 30 34 s:devctl > SAS2004 > ========= cut ============== > but do not use "space" between those writings cause it will write 20, and we > need 00. > > Now run it > > ============== cut =================== > root@kxxx-xxx:/export/home/admin# ./sas3ircu 0 display > Avago Technologies SAS3 IR Configuration Utility. > Version 14.00.00.00 (2016.07.21) > Copyright (c) 2009-2016 Avago Technologies. All rights reserved. > Read configuration has been initiated for controller 0 > ------------------------------------------------------------------------ > Controller information > ------------------------------------------------------------------------ > Controller type : SAS3008 > BIOS version : 0.00.00.00 > Firmware version : 14.00.00.00 > Channel description : 1 Serial Attached SCSI > Initiator ID : 0 > Maximum physical devices : 1023 > Concurrent commands supported : 10176 > Slot : Unknown > Segment : 0 > Bus : 13 > Device : 0 > Function : 0 > RAID Support : No > ------------------------------------------------------------------------ > IR Volume information > ------------------------------------------------------------------------ > ------------------------------------------------------------------------ > Physical device information > ------------------------------------------------------------------------ > Initiator at ID #0 > > Device is a Hard disk > Enclosure # : 2 > Slot # : 0 > SAS Address : 5000cca-2-3c0b-d88e > State : Ready (RDY) > Size (in MB)/(in sectors) : 5723166/1465130645 > Manufacturer : HGST > Model Number : HUH728060AL4204 > Firmware Revision : C7J0 > Serial No : 2RG6HYSX > Unit Serial No(VPD) : 2RG6HYSX > GUID : 5000cca23c0bd88c > Protocol : SAS > Drive Type : SAS_HDD > > Device is a Sequential access device > Enclosure # : 2 > Slot # : 0 > SAS Address : 5003048-0-0181-dafd > State : Standby (SBY) > Manufacturer : LSI CORP > Model Number : SAS2X28 > Firmware Revision : 0717 > Serial No : x36557230 > Unit Serial No(VPD) : N/A > GUID : N/A > Protocol : SAS > Drive Type : SAS_HDD > > Device is a Hard disk > Enclosure # : 2 > Slot # : 1 > SAS Address : 5000cca-2-3c0b-d48e > State : Ready (RDY) > Size (in MB)/(in sectors) : 5723166/1465130645 > Manufacturer : HGST > Model Number : HUH728060AL4204 > Firmware Revision : C7J0 > Serial No : 2RG6HPHX > Unit Serial No(VPD) : 2RG6HPHX > GUID : 5000cca23c0bd48c > Protocol : SAS > Drive Type : SAS_HDD > > Device is a Hard disk > Enclosure # : 2 > Slot # : 2 > SAS Address : 5000cca-2-3c0b-dfc2 > State : Ready (RDY) > Size (in MB)/(in sectors) : 5723166/1465130645 > Manufacturer : HGST > Model Number : HUH728060AL4204 > Firmware Revision : C7J0 > Serial No : 2RG6JEMX > Unit Serial No(VPD) : 2RG6JEMX > GUID : 5000cca23c0bdfc0 > Protocol : SAS > Drive Type : SAS_HDD > > Device is a Hard disk > Enclosure # : 2 > Slot # : 3 > SAS Address : 5000cca-2-3c0b-ea96 > State : Ready (RDY) > Size (in MB)/(in sectors) : 5723166/1465130645 > Manufacturer : HGST > Model Number : HUH728060AL4204 > Firmware Revision : C7J0 > Serial No : 2RG6K4ZX > Unit Serial No(VPD) : 2RG6K4ZX > GUID : 5000cca23c0bea94 > Protocol : SAS > Drive Type : SAS_HDD > > ============== cut ============== > > > > > The same way you can modify the sas3flash, but it incorrectly determines the > firmware version, seems to be the problem of old mpt_sas driver > > ============== cut ============== > > Firmware Product ID : 0x3860 > Firmware Version : 127.100.219.120 > NVDATA Vendor : Undetermined > NVDATA Product ID : Undetermined > BIOS Version : N/A > UEFI BSD Version : N/A > FCODE Version : N/A > Board Name : SAS9300-16e > Board Assembly : H3-25520-01E > Board Tracer Number : SP64606278 > ============== cut ============== > > > If OmiOS would include lsc driver, i think we all will be happy. Cause i > tried to import it from 11.3 Solaris.. > Yes it starts to load up, but tries to call non existent functions in kernel > and fails.
Instead of using binaries meant for another, different OS (Oracle Solaris) to get LSI MPT HBA information and to upload firmware to the HBA, it would likely be better if the community worked on a native command-line utility to do the former, and a plugin for fwflash(1M) to do the latter. IMO, trying to use Oracle Solaris binaries on any illumos system is not something I would consider to be a reliable proposition in the long term. Instead of trying to chase any changes there, I would prefer to invent my own. /dale
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
