thanks, i got it. unfortunately, the solaris x86 executable doesn't seem to run under openindiana. Here is the result:
root@nas:/tank/windows/dswartz# file sas2ircu sas2ircu: ELF 32-bit LSB executable 80386 Version 1, dynamically linked, stripped root@nas:/tank/windows/dswartz# ./sas2ircu Killed Maybe I am dense, but I am not sure I see the point of having kernel messages identifying a specific HW item that is impossible (or at the very least extremely difficult and/or non-intuitive) to chase back to the specific device that is having issues. Ugh, not how I wanted to start Monday :( -----Original Message----- From: Jim Klimov [mailto:jimkli...@cos.ru] Sent: Monday, June 11, 2012 9:20 AM To: Discussion list for OpenIndiana Cc: Dan Swartzendruber Subject: Re: [OpenIndiana-discuss] mapping target number to disk? 2012-06-11 17:10, Dan Swartzendruber ?????: > > How do I map 'target 9' to a drive? Google was not remotely helpful - the > only thread I found recommended downloading lsiutil (which I can't find > anywhere). I installed sasinfo, which prints a lot of info, but nothing > obviously useful to me. Any help appreciated... There were some references in zfs-discuss list last month, I think the URL should be like this (I did not check myself): ===== http://www.lsi.com/channel/products/storagecomponents/Pages/LSISAS9211-8i.as px select * SUPPORT & DOWNLOADS download SAS2IRCU_P13 ===== HTH, //Jim Klimov _______________________________________________ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
