> Eheh !!!
> Don't Curb Your enthusiasm Man !!
> You picked up the wrong binary, you have to download the:
>
> Slicer3-3.6.3-2011-03-09-solaris8.tar.gz
>
Solaris 8? Are we serious? This is an EOLed product!!!
Better provide Solaris 7 binaries :-)
A.S.
--
Apostolos Syro
Try that ! and let me know .
Paolo
Il 10/3/11 9:10 AM, Apostolos Syropoulos ha scritto:
Eheh !!!
Don't Curb Your enthusiasm Man !!
You picked up the wrong binary, you have to download the:
Slicer3-3.6.3-2011-03-09-solaris8.tar.gz
Solaris 8? Are we serious? This is an EOLed product!!!
Better
Hi
I have an OpenIndiana server connected to a 12 drive JBOD chassis
through SAS, and I am trying to figure out the best way to find out
which physical drive in the chassis resolves to each of the drive
names visible from the operating system.
These are the drives I can see in OpenIndiana related
Jeppe Toustrup wrote:
> The only way I have found which I can find the order of the drives in
> the JBOD along with the above names, without pulling out each drive
> and see which one becomes unavailable, is within /etc/path_to_inst,
> where I find the following lines:
Have you tried "cfgadm -lv"?
Binary compatibility, man... :)
On Mon, Oct 3, 2011 at 03:10, Apostolos Syropoulos
wrote:
>> Eheh !!!
>> Don't Curb Your enthusiasm Man !!
>> You picked up the wrong binary, you have to download the:
>>
>> Slicer3-3.6.3-2011-03-09-solaris8.tar.gz
>>
>
>
> Solaris 8? Are we serious? This is an EOL
On Mon, Oct 3, 2011 at 16:00, James Carlson wrote:
> Have you tried "cfgadm -lv"?
Yes, "cfgadm -lv" does not list the drives connected through SAS, but
"cfgadm -lav" does. The output does however not make me much wiser
than the output I can get from path_to_inst (only lines related to SAS
drives
Jeppe Toustrup wrote:
> On Mon, Oct 3, 2011 at 16:00, James Carlson wrote:
>> Have you tried "cfgadm -lv"?
>
> Yes, "cfgadm -lv" does not list the drives connected through SAS, but
> "cfgadm -lav" does. The output does however not make me much wiser
> than the output I can get from path_to_inst (
So I was reading the earlier thread about this. I have an IBM m1015
(rebadged LSI card) flashed to IT firmware. It presents the devices as
WWN. Here's the problem: I have some shell scripts that want to do
smartctl to get temperature, health, etc... Looking at zpool status, I
see this:
On Mon, Oct 3, 2011 at 17:39, Dan Swartzendruber wrote:
> Note that only the last one seems to be a real device. The first two seem
> to be stale from previous changes. I am also not sure I believe the 2nd to
> last char ('d') is part of the WWN, since it is lower case and everything
> else is u
On Mon, Oct 3, 2011 at 17:39, Dan Swartzendruber wrote:
> Based on my reading, the OUI for a WWN is 8 bytes - the 0014EE is Western
> Digital (this is correct), followed by 5 bytes (10 hex chars) of individual
> drive ID.
The Wikipedia page for WWN[1] tells the following:
"New addressing schema:
On 10/03/11 08:52, Jeppe Toustrup wrote:
The trailing "d0" is from the Solaris specifications of designating a
hard drive. Hard drive names are written as "cXtXdX", which X replaced
by numbers (0-9 or hex). The lowercase letters are short for
Controller, Tray and Drive (or Disk?), respectively.
Does anyone have VirtualBox successfully running with OpenIndiana 151a?
The note below is a note I had sent to the VirtualBox mailing list. Members
there helped me troubleshoot this issue for about a
week before I decided the issue is probably more related to OpenIndiana than
VirtualBox.
What
May I ask what kind of SAS HBA you're using?
- Rich
On Mon, Oct 3, 2011 at 10:25 AM, James Carlson wrote:
> Jeppe Toustrup wrote:
>> On Mon, Oct 3, 2011 at 16:00, James Carlson wrote:
>>> Have you tried "cfgadm -lv"?
>>
>> Yes, "cfgadm -lv" does not list the drives connected through SAS, but
>>
On 10/ 3/11 05:35 PM, Jerry Kemp wrote:
Does anyone have VirtualBox successfully running with OpenIndiana 151a?
The note below is a note I had sent to the VirtualBox mailing list. Members
there helped me troubleshoot this issue for about a
week before I decided the issue is probably more rela
Very strange... anyone else seen this? oi 151a
(nautilus:26931): Unique-DBus-WARNING **: Error while sending message:
Did not receive a reply. Possible causes include: the remote application
did not send a reply, the message bus security policy blocked the reply,
the reply timeout expired, or
I use the LSI sas2ircu util and fmtopo to identify and flip on the
'identify' light on my disk chassis.
I wrote a script, it is very rough and would require some tuning for your
config, but it might solve your problem if your hardware is compatible.
Compatible means, LSI controller and disk she
On Mon, Oct 3, 2011 at 18:57, Rich wrote:
> May I ask what kind of SAS HBA you're using?
>
> - Rich
>
Sure, it's a LSI SAS 9201-16e:
http://www.lsi.com/products/storagecomponents/Pages/LSISAS9201-16e.aspx
--
Venlig hilsen / Kind regards
Jeppe Toustrup (aka. Tenzer)
_
Excellent. I can actually open the GUI after starting this. I was unable to
previously.
Also, once the script is broken, the original Callee RC error returns.
Here is the script output.
***
Oracle VM VirtualBox XPCOM Server Version 4.1.2
(C) 2008-20
On 10/ 3/11 07:09 PM, Jerry Kemp wrote:
Excellent. I can actually open the GUI after starting this. I was unable to
previously.
Also, once the script is broken, the original Callee RC error returns.
Here is the script output.
***
Oracle VM Virtua
Again, thank you for your reply.
May I ask how you knew about the LD_NODIRECT thing?
Jerry
On 10/ 3/11 01:20 PM, oi-disc...@gftm.eu wrote:
>
> You could either background the script or export LD_NODIRECT=1 and then call
> VBoxSVC with the --daemon flag (iirc)
>
* Jerry Kemp [2011-10-03 18:35]:
> Does anyone have VirtualBox successfully running with OpenIndiana 151a?
>
> The note below is a note I had sent to the VirtualBox mailing list. Members
> there helped me troubleshoot this issue for about a
> week before I decided the issue is probably more rel
On Mon, Oct 3, 2011 at 19:16, Jason Matthews wrote:
> I wrote a script, it is very rough and would require some tuning for your
> config, but it might solve your problem if your hardware is compatible.
>
> Compatible means, LSI controller and disk shelf that is SES2 compliant,
> supports page code
I stumbled upon a nice script and link to a utility for just such an occasion:
http://the-key.enix.org/~krystal/diskmap.py
http://www.supermicro.com/support/faqs/data_lib/FAQ_9633_SAS2IRCU_Phase_5.0-5.00.00.00.zip
Example output:
root@nerv:~/scripts# ./diskmap.py
Diskmap - nerv> disks
0:01:01
On Mon, Oct 3, 2011 at 20:55, Russell Hansen wrote:
> I stumbled upon a nice script and link to a utility for just such an
> occasion...
That looks very promising, thank you for sharing! I'll have to give
that a try tomorrow.
--
Venlig hilsen / Kind regards
Jeppe Toustrup (aka. Tenzer)
___
What did you stumble upon? Maybe its better than mine? ;-)
-Original Message-
From: Jeppe Toustrup [mailto:openindi...@tenzer.dk]
Sent: Monday, October 03, 2011 12:10 PM
To: Discussion list for OpenIndiana
Subject: Re: [OpenIndiana-discuss] Best way to map SAS
drivestophysicalpositions
But wait, there's more!
http://skysrv.pha.jhu.edu/~rercola/SAS2IRCU_10.00.00.00.zip
- Rich
On Mon, Oct 3, 2011 at 3:09 PM, Jeppe Toustrup wrote:
> On Mon, Oct 3, 2011 at 20:55, Russell Hansen wrote:
>> I stumbled upon a nice script and link to a utility for just such an
>> occasion...
>
> Tha
Hi,
Yes I've VirtualBox running on Build 151a now, but had initially also
problems with VBoxSVC.
See http://wiki.openindiana.org/oi/Spec+Files+Extra+Repository and search
for VirtualBox.
There is a problem with newer gcc.
HTH
Ewald
Am 03.10.2011 18:35 schrieb "Jerry Kemp" :
>
> Does anyone have V
27 matches
Mail list logo
