From gea at napp-it.org  Fri Mar  1 09:45:04 2013
From: gea at napp-it.org (Gea)
Date: Fri, 01 Mar 2013 15:45:04 +0100
Subject: [OmniOS-discuss] Preconfigured distributable OmniOS NAS with
	mirrorred USB sticks
In-Reply-To: <99055A16-8618-4321-818C-A5DAF992CA8B@hfg-gmuend.de>
References: <2EDC7C4A-0CC1-4E39-AE49-4ACB67F78542@hfg-gmuend.de>
	<CACLsApvYWUCUaSGOsho7CyxpyCgMhGsoY2pqqtrV+sbfq9Ec1Q@mail.gmail.com>
	<5127E503.5090609@Logan.com>
	<99055A16-8618-4321-818C-A5DAF992CA8B@hfg-gmuend.de>
Message-ID: <5130BEF0.9030808@napp-it.org>

"napp-it to go":
Preconfigured OmniOS based ZFS server distribution on USB

I have uploaded first betas of my preconfigured and ready to use napp-it 
USB ZFS server distributions with OmniOS
(newest bloody,  ZFS Version 5000 and LZ4 compress), CIFS, NFS , AFP, 
iSCSI Comstar and Xampp.

-> Download
-> Clone it  (use attached Software to a 16 GB USB Stick)
-> Boot it - Management via Web-UI


Supported hardware (my personal top 4 for a ZFS server)
- USB Image, ready to use, HP Microserver (SoHo, Backup und Mediaserver)
- USB Image, ready to use, Supermicro X9SCL/1155 (max 32GB RAM, 2-4 
Core, 17W Xeon, Medium size, All-In-One)
- USB Image, ready to use, Supermicro X9SRL/Single 2011 (max 256GB RAM, 
2-6 Core, Premium Server, All-In-One)
- USB Image, ready to use, Supermicro X9DRL/Dual 2011 (max 256GB RAM, 
4-12 Core, High End Server, All-In-One)


download: http://napp-it.org/manuals/to-go_en.html


>
>
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss


-- 
Gea

-------------------------
napp-it.org
-------------------------

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20130301/f95d2de9/attachment.html>

From esproul at omniti.com  Mon Mar  4 12:08:07 2013
From: esproul at omniti.com (Eric Sproul)
Date: Mon, 4 Mar 2013 12:08:07 -0500
Subject: [OmniOS-discuss] Updated release: r151004r
Message-ID: <CA+QY2RQhOXWxhhx_DpxtLiG+1U7fAE+QA85h9P2ZAuCb4dStxQ@mail.gmail.com>

Weekly release r151004r contains two security fixes for sudo:
 * http://www.sudo.ws/sudo/alerts/epoch_ticket.html (CVE-2013-1775)
 * http://www.sudo.ws/sudo/alerts/tty_tickets.html (CVE-2013-1776)

It also bumps pci.ids to the most recent snapshot.

In order to update sudo, you also need an updated omnios-userland
incorporation that relaxes the version restriction on sudo.  A 'pkg
update' with no options should get you all updates.

To preview the available updates, run 'pkg update -nv'.

http://omnios.omniti.com/wiki.php/ReleaseNotes#r151004r

From gate03 at landcroft.co.uk  Mon Mar 11 06:41:17 2013
From: gate03 at landcroft.co.uk (Michael Mounteney)
Date: Mon, 11 Mar 2013 21:41:17 +1100
Subject: [OmniOS-discuss] updating all zones
Message-ID: <20130311214117.3ac926ab@dickless.landy.net>

In the global zone I just did:

     # pkg update

then zlogin to each child zone and

     # pkg update

there as well.  They complained:

pkg: Unable to clone the current boot environment.

I rebooted into the new BE then repeated the pkg update in the child
zone with the same result.  I then tried to follow the instructions in

http://www.thushanfernando.com/index.php/2010/01/14/upgrading-non-global-opensolaris-zone-to-latest-be/

but:

root at world:~# zoneadm -z diener boot
zone 'diener': Unable to unmount the zone's root ZFS dataset
(/zone/diener/root). zone 'diener': 
zone 'diener': Is there a global zone process inside the zone root?
zone 'diener': 
zone 'diener': The current zone boot environment will remain mounted.

Just to make it even more fun, it seems there are multiple problems
with services not starting in at least one zone and I've had to revert
to the previous BE.

This is with bloody_20121228, pkg update to 20130208 (omnios-1) (which
has been working fine since pkg update on about 10 Feb.) so the pkg
update with the problems is omnios-2.

What have I done wrong ?  Something to do with pkg update in child
zones I'm sure.

Michael.

From a.shvayakov at yahoo.com  Mon Mar 11 10:47:06 2013
From: a.shvayakov at yahoo.com (Shvayakov A.)
Date: Mon, 11 Mar 2013 17:47:06 +0300
Subject: [OmniOS-discuss] ZFS Logical Unit stuck in the offlining state with
	COMSTAR
Message-ID: <513DEE6A.2010806@yahoo.com>

Hi,

I got a problem - ZFS Logical Unit stuck in the offlining state  with COMSTAR

Conditions to reproduce the problem:

You should to create Logical Unit with COMSTAR

stmfadm create-lu /dev/zvol/rdsk/GIGO/zvol200g
stmfadm add-view 600144F054A281000000513DB9770005

Then I mounted this device on the initiator and began to upload data with dd
During copying, I removed the LU

Intense data upload is a prerequisite for the reproducing of problem

stmfadm delete-lu -k 600144F054A281000000513DB9770005

Logical Unit  stuck in the offlining state

stmfadm list-lu -v
LU Name: 600144F054A281000000513DB9770005

     Operational Status: Offlining
     Provider Name     : sbd
     Alias             : /dev/zvol/rdsk/GIGO/zvol200g
     View Entry Count  : 0
     Data File         : /dev/zvol/rdsk/GIGO/zvol200g
     Meta File         : not set
     Size              : 214748364800
     Block Size        : 512
     Management URL    : not set
     Vendor ID         : SUN
     Product ID        : COMSTAR
     Serial Num        : not set
     Write Protect     : Disabled
     Writeback Cache   : Enabled
     Access State      : Active

As a consequence, it cannot be unloaded from the COMSTAR framework

stmfadm delete-lu 600144F054A281000000513DB9770005
stmfadm: resource busy

Hence the GIGO pool cannot be exported:

zpool export GIGO
cannot export 'GIGO': pool is busy

Resulting in the RSF-1 cluster aborting failover

Now only  reboot...

This bug is present in OpenIndiana too. I tested it.
Support RSF-1 says that this problem is fixed in the Nexentastor
What do you know about it?
Can you fix this bug in OmniOS?

Best regards,
Alexander Shvayakov


From sergey57 at gmail.com  Mon Mar 11 12:51:11 2013
From: sergey57 at gmail.com (sergey ivanov)
Date: Mon, 11 Mar 2013 12:51:11 -0400
Subject: [OmniOS-discuss] updating all zones
In-Reply-To: <20130311214117.3ac926ab@dickless.landy.net>
References: <20130311214117.3ac926ab@dickless.landy.net>
Message-ID: <CAAv=BDFVVnRywZuqBqEc6i78S=s-RWh=jSzKR0iUr8B7QdxK6Q@mail.gmail.com>

Hi Michael,
I had similar problem, after upgrading global zone and rebooting,  upgrades
in non-global zones failed. Non-global zones had lost their delegated zfs
datasets, and was not able to see even zfs they used as root filesystem. I
resolved the problem by halting zones, and then upgrading from global zone
with "-R" for image directory root. I would also be glad to see
recommendations and best practices for upgrading OmniOS with zones.


On Mon, Mar 11, 2013 at 6:41 AM, Michael Mounteney
<gate03 at landcroft.co.uk>wrote:

> In the global zone I just did:
>
>      # pkg update
>
> then zlogin to each child zone and
>
>      # pkg update
>
> there as well.  They complained:
>
> pkg: Unable to clone the current boot environment.
>
> I rebooted into the new BE then repeated the pkg update in the child
> zone with the same result.  I then tried to follow the instructions in
>
>
> http://www.thushanfernando.com/index.php/2010/01/14/upgrading-non-global-opensolaris-zone-to-latest-be/
>
> but:
>
> root at world:~# zoneadm -z diener boot
> zone 'diener': Unable to unmount the zone's root ZFS dataset
> (/zone/diener/root). zone 'diener':
> zone 'diener': Is there a global zone process inside the zone root?
> zone 'diener':
> zone 'diener': The current zone boot environment will remain mounted.
>
> Just to make it even more fun, it seems there are multiple problems
> with services not starting in at least one zone and I've had to revert
> to the previous BE.
>
> This is with bloody_20121228, pkg update to 20130208 (omnios-1) (which
> has been working fine since pkg update on about 10 Feb.) so the pkg
> update with the problems is omnios-2.
>
> What have I done wrong ?  Something to do with pkg update in child
> zones I'm sure.
>
> Michael.
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss
>

-- 
  Regards,
  Sergey Ivanov.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20130311/adfa9903/attachment.html>

From a.shvayakov at yahoo.com  Wed Mar 13 08:31:23 2013
From: a.shvayakov at yahoo.com (Shvayakov A.)
Date: Wed, 13 Mar 2013 15:31:23 +0300
Subject: [OmniOS-discuss] ZFS Logical Unit stuck in the offlining state
 with COMSTAR
In-Reply-To: <513DEE6A.2010806@yahoo.com>
References: <513DEE6A.2010806@yahoo.com>
Message-ID: <5140719B.1030501@yahoo.com>

I made upgrade the OmniOS to bloody version.
pkg://omnios/storage/stmf at 0.5.11,5.11-0.151005:20130311T155835Z
The problem still persist

From johan.kragsterman at capvert.se  Wed Mar 13 08:55:21 2013
From: johan.kragsterman at capvert.se (Johan Kragsterman)
Date: Wed, 13 Mar 2013 13:55:21 +0100
Subject: [OmniOS-discuss] ZFS Logical Unit stuck in the offlining state
 with COMSTAR
In-Reply-To: <5140719B.1030501@yahoo.com>
References: <5140719B.1030501@yahoo.com>,
	<513DEE6A.2010806@yahoo.com>
Message-ID: <OFACE8906D.46BB6584-ONC1257B2D.0046FC62-C1257B2D.0046FC68@inse.com>

-----omnios-discuss-bounces at lists.omniti.com skrev: -----
Till: omnios-discuss at lists.omniti.com
Fr?n: "Shvayakov A." 
S?nt av: omnios-discuss-bounces at lists.omniti.com
Datum: 2013.03.13 13:32
?rende: Re: [OmniOS-discuss] ZFS Logical Unit stuck in the offlining state with COMSTAR

"I made upgrade the OmniOS to bloody version.
pkg://omnios/storage/stmf at 0.5.11,5.11-0.151005:20130311T155835Z
The problem still persist"



I've seen all your messages in different mailing lists, and I am also interested in knowing what goes on with this.

Did you get confirmed from Nexenta that they solved the problem? Do you know they solved it?

I can hear silence from the lists, and that worries me....

I'd like to hear a comment from people from Nexanta...?

But perhaps it is better on the illumos devel list to ask for Nexenta comment?

Rgrds Johan

_______________________________________________
OmniOS-discuss mailing list
OmniOS-discuss at lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss




From geoffn at gnaa.net  Wed Mar 13 15:37:24 2013
From: geoffn at gnaa.net (Geoff Nordli)
Date: Wed, 13 Mar 2013 12:37:24 -0700
Subject: [OmniOS-discuss] zookeeper client disconnecting
Message-ID: <5140D574.7060400@gnaa.net>

Just wondering if anyone is  successfully using zookeeper with omnios?

The client seems to be frequently disconnecting from the zookeeper service.

thanks,

Geoff

From geoffn at gnaa.net  Wed Mar 13 16:06:07 2013
From: geoffn at gnaa.net (Geoff Nordli)
Date: Wed, 13 Mar 2013 13:06:07 -0700
Subject: [OmniOS-discuss] zookeeper client disconnecting
In-Reply-To: <5140D574.7060400@gnaa.net>
References: <5140D574.7060400@gnaa.net>
Message-ID: <5140DC2F.1020603@gnaa.net>


On 13-03-13 12:37 PM, Geoff Nordli wrote:
> Just wondering if anyone is  successfully using zookeeper with omnios?
>
> The client seems to be frequently disconnecting from the zookeeper 
> service.
>
> thanks,
>
> Geoff


Sorry, this wasn't very descriptive.

Omnios is running as a client.

The ZK server is running on Linux (Ubuntu).  server zk_version 
3.4.4-1386507, built on 09/17/2012 08:33 GMT

There are other clients running running on Linux and BSD which are not 
experience disconnect issues.


thanks,

Geoff

From jesus at omniti.com  Wed Mar 13 16:38:39 2013
From: jesus at omniti.com (Theo Schlossnagle)
Date: Wed, 13 Mar 2013 16:38:39 -0400
Subject: [OmniOS-discuss] zookeeper client disconnecting
In-Reply-To: <5140DC2F.1020603@gnaa.net>
References: <5140D574.7060400@gnaa.net>
	<5140DC2F.1020603@gnaa.net>
Message-ID: <CACLsAptEi0Q6OWSS6RN4kWa__x_artBY+RV8hyoTBs2tTYhQ-g@mail.gmail.com>

All Java? I'd start by trussing the client and tcpdumping during a
disconnection.

It's hard to imaging that this is an OmniOS or Illumos problem specifically
as that's just simple IP stuff.

On Wed, Mar 13, 2013 at 4:06 PM, Geoff Nordli <geoffn at gnaa.net> wrote:

>
> On 13-03-13 12:37 PM, Geoff Nordli wrote:
>
>> Just wondering if anyone is  successfully using zookeeper with omnios?
>>
>> The client seems to be frequently disconnecting from the zookeeper
>> service.
>>
>> thanks,
>>
>> Geoff
>>
>
>
> Sorry, this wasn't very descriptive.
>
> Omnios is running as a client.
>
> The ZK server is running on Linux (Ubuntu).  server zk_version
> 3.4.4-1386507, built on 09/17/2012 08:33 GMT
>
> There are other clients running running on Linux and BSD which are not
> experience disconnect issues.
>
>
>
> thanks,
>
> Geoff
> ______________________________**_________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.**com <OmniOS-discuss at lists.omniti.com>
> http://lists.omniti.com/**mailman/listinfo/omnios-**discuss<http://lists.omniti.com/mailman/listinfo/omnios-discuss>
>



-- 

Theo Schlossnagle

http://omniti.com/is/theo-schlossnagle
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20130313/538cedf1/attachment.html>

From peter at psych.columbia.edu  Fri Mar 15 23:20:50 2013
From: peter at psych.columbia.edu (Peter Tripp)
Date: Fri, 15 Mar 2013 23:20:50 -0400
Subject: [OmniOS-discuss] Mapping LSI SAS Target numbers to disk SAS WWNs
	(Log Info 0x31120303)
Message-ID: <3E73F8B5-BD2F-471A-B57D-D3D397C8956A@psych.columbia.edu>

No questions...just information for how to translate a Target ID to a SAS WWN on LSI MPT2 SAS2 controllers under Illumos/Solaris.  My apologies for cross posting or if this is old hat, but I've been running an LSI SAS2 controller with SATA disks and had my logs fill up with repeated cryptic entries, but never found a troubleshooting strategy until tonight. Under load (scrub) the following will repeatedly show up: 

scsi: [ID 365881 kern.info] /pci at 0,0/pci15ad,7a0 at 15/pci1000,3030 at 0 (mpt_sas0):
	Log info 0x31120311 received for target 20.
	scsi_status=0x0, ioc_status=0x804b, scsi_state=0xc
scsi: [ID 243001 kern.warning] WARNING: /pci at 0,0/pci15ad,7a0 at 15/pci1000,3030 at 0 (mpt_sas0):
	mptsas_handle_event_sync: IOCStatus=0x8000, IOCLogInfo=0x31120303

I assumed this was due to a disk failing or a cabling problem (my LSI SAS 9200-16e SAS_2116 has directly cabled WD RE4 SATA disks) but which disk is Target 20? I took the time to label my drive caddies with their WWN to ease trouble shooting, but was never able to figure out how to translate Target ID into a SAS WWN so I narrow down my troubleshooting to a single device....until now.

Run lsituil.i386 as root
(LSIUtil Kit 1.63.zip\Solaris\lsiutil.i386 from http://www.juhonkoti.net/media/LSIUTIL-1.63.zip )
* Select your MPT device
* e (Enable expert mode in menus)
* 20 (Diagnostics)
* 1 (Inquiry Test)
* 0 (Bus 0)
* XX (Target number from above, Target 20 for me)
* 0 (Lun 0)
* 83 or 80 (SAS WWN and Disk Serial Number respectively)
Output:

VPD Page:  [00-FF or RETURN for normal Inquiry] 83
 B___T___L  Page
 0  20   0   83
16 bytes of Inquiry Data returned
0000 : 00 83 00 0c 01 03 00 08 50 01 4e e2 b1 65 f5 d7            P N  e  

VPD Page:  [00-FF or RETURN for normal Inquiry] 80
 B___T___L  Page
 0  20   0   80
24 bytes of Inquiry Data returned
0000 : 00 80 00 14 20 20 20 20 20 57 44 2d 57 4d 41 59             WD-WMAY
0010 : 30 34 33 32 38 34 38 39                            04328489

The second half of the hex string from 83h is your WWN (50014ee2b165f5d7 above), and ASCII from 80h (WMAY04328489 above) the serial number.  With that info one can check the cabling path or replace the disk or whatever.  This should work with other LSI SAS2 2008/2118 controllers like the 9200-8e, 9211-8i, etc. Might even work with older SAS1 cards (1068, etc) since lsiutil should also support them. 

Just thought others might find it useful! Have a great night!

-Pete

Source:
https://www.meteo.unican.es/trac/meteo/blog/SolarisSATADeviceName

References:
http://www.juhonkoti.net/2012/01/02/supermicro-jbod-sc847e16-rjbo-enclosure-with-solaris-openindiana
http://openindiana.org/pipermail/openindiana-discuss/2012-June/008363.html
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20130315/e4035d46/attachment.html>

From esproul at omniti.com  Sat Mar 16 09:56:34 2013
From: esproul at omniti.com (Eric Sproul)
Date: Sat, 16 Mar 2013 09:56:34 -0400
Subject: [OmniOS-discuss] Mapping LSI SAS Target numbers to disk SAS
 WWNs (Log Info 0x31120303)
In-Reply-To: <3E73F8B5-BD2F-471A-B57D-D3D397C8956A@psych.columbia.edu>
References: <3E73F8B5-BD2F-471A-B57D-D3D397C8956A@psych.columbia.edu>
Message-ID: <CA+QY2RTV-yX6q=Rm3B1LCsVAeiO87NDWVH1TgohGd0Q9tdJsHA@mail.gmail.com>

Thanks Peter, that's very helpful!

On Fri, Mar 15, 2013 at 11:20 PM, Peter Tripp <peter at psych.columbia.edu> wrote:
> No questions...just information for how to translate a Target ID to a SAS
> WWN on LSI MPT2 SAS2 controllers under Illumos/Solaris.  My apologies for
> cross posting or if this is old hat, but I've been running an LSI SAS2
> controller with SATA disks and had my logs fill up with repeated cryptic
> entries, but never found a troubleshooting strategy until tonight. Under
> load (scrub) the following will repeatedly show up:
>
> scsi: [ID 365881 kern.info] /pci at 0,0/pci15ad,7a0 at 15/pci1000,3030 at 0
> (mpt_sas0):
> Log info 0x31120311 received for target 20.
> scsi_status=0x0, ioc_status=0x804b, scsi_state=0xc
> scsi: [ID 243001 kern.warning] WARNING:
> /pci at 0,0/pci15ad,7a0 at 15/pci1000,3030 at 0 (mpt_sas0):
> mptsas_handle_event_sync: IOCStatus=0x8000, IOCLogInfo=0x31120303
>
> I assumed this was due to a disk failing or a cabling problem (my LSI SAS
> 9200-16e SAS_2116 has directly cabled WD RE4 SATA disks) but which disk is
> Target 20? I took the time to label my drive caddies with their WWN to ease
> trouble shooting, but was never able to figure out how to translate Target
> ID into a SAS WWN so I narrow down my troubleshooting to a single
> device....until now.
>
> Run lsituil.i386 as root
> (LSIUtil Kit 1.63.zip\Solaris\lsiutil.i386 from
> http://www.juhonkoti.net/media/LSIUTIL-1.63.zip )
> * Select your MPT device
> * e (Enable expert mode in menus)
> * 20 (Diagnostics)
> * 1 (Inquiry Test)
> * 0 (Bus 0)
> * XX (Target number from above, Target 20 for me)
> * 0 (Lun 0)
> * 83 or 80 (SAS WWN and Disk Serial Number respectively)
> Output:
>
> VPD Page:  [00-FF or RETURN for normal Inquiry] 83
>  B___T___L  Page
>  0  20   0   83
> 16 bytes of Inquiry Data returned
> 0000 : 00 83 00 0c 01 03 00 08 50 01 4e e2 b1 65 f5 d7            P N  e
>
> VPD Page:  [00-FF or RETURN for normal Inquiry] 80
>  B___T___L  Page
>  0  20   0   80
> 24 bytes of Inquiry Data returned
> 0000 : 00 80 00 14 20 20 20 20 20 57 44 2d 57 4d 41 59             WD-WMAY
> 0010 : 30 34 33 32 38 34 38 39                            04328489
>
> The second half of the hex string from 83h is your WWN (50014ee2b165f5d7
> above), and ASCII from 80h (WMAY04328489 above) the serial number.  With
> that info one can check the cabling path or replace the disk or whatever.
> This should work with other LSI SAS2 2008/2118 controllers like the 9200-8e,
> 9211-8i, etc. Might even work with older SAS1 cards (1068, etc) since
> lsiutil should also support them.
>
> Just thought others might find it useful! Have a great night!
>
> -Pete
>
> Source:
> https://www.meteo.unican.es/trac/meteo/blog/SolarisSATADeviceName
>
> References:
> http://www.juhonkoti.net/2012/01/02/supermicro-jbod-sc847e16-rjbo-enclosure-with-solaris-openindiana
> http://openindiana.org/pipermail/openindiana-discuss/2012-June/008363.html
>
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss
>

From Rob at Logan.com  Sat Mar 16 10:50:04 2013
From: Rob at Logan.com (Rob Logan)
Date: Sat, 16 Mar 2013 10:50:04 -0400
Subject: [OmniOS-discuss] [SPAM] Mapping LSI SAS Target numbers to disk
	SAS WWNs (Log Info 0x31120303)
In-Reply-To: <3E73F8B5-BD2F-471A-B57D-D3D397C8956A@psych.columbia.edu>
References: <3E73F8B5-BD2F-471A-B57D-D3D397C8956A@psych.columbia.edu>
Message-ID: <3BB2F743-B379-4572-876E-DA97F05D4ED7@Logan.com>

> 
> Run lsituil.i386 as root
> (LSIUtil Kit 1.63.zip\Solaris\lsiutil.i386 from http://www.juhonkoti.net/media/LSIUTIL-1.63.zip )
> * Select your MPT device
> * e (Enable expert mode in menus)
> * 20 (Diagnostics)
> * 1 (Inquiry Test)
> * 0 (Bus 0)
> * XX (Target number from above, Target 20 for me)
> * 0 (Lun 0)
> * 83 or 80 (SAS WWN and Disk Serial Number respectively)

cool! another closed tool is hd 

http://docs.oracle.com/cd/E19432-01/820-1120-22/chapter2.html
http://rob.com/lancair/2013.03/hd.bz2

# ./hd
                                                                         
Device    Serial        Vendor   Model             Rev  Temperature     
------    ------        ------   -----             ---- -----------     
c0t0d0p0      9VP6JXKT  ATA      ST31000528AS      CC3E 36 C (96 F)
c1t0d0p0  550129060AGN  ATA      INTEL SSDSC2CW06  400i 255 C (491 F)
c1t1d0p0  55016H060AGN  ATA      INTEL SSDSC2CW06  400i 255 C (491 F)
c1t2d0p0      Z1N36V7B  ATA      ST1000NM0011      SN03 36 C (96 F)
c1t3d0p0      Z1N35VKL  ATA      ST1000NM0011      SN03 38 C (100 F)
c1t4d0p0      Z1N36WXN  ATA      ST1000NM0011      SN03 32 C (89 F)
c1t5d0p0      Z1N36W93  ATA      ST1000NM0011      SN03 32 C (89 F)

c0t0d0p0 is on 
01:00.0 SCSI storage controller: LSI Logic / Symbios Logic SAS1064ET PCI-Express Fusion-MPT SAS (rev 08)
while the others are on
00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family SATA AHCI Controller (rev 05)

			Rob


From johan.kragsterman at capvert.se  Mon Mar 18 05:54:47 2013
From: johan.kragsterman at capvert.se (Johan Kragsterman)
Date: Mon, 18 Mar 2013 10:54:47 +0100
Subject: [OmniOS-discuss] zones: can I add a vhba to zone?
Message-ID: <OFB8CFDB06.6347714D-ONC1257B32.00367444-C1257B32.00367449@inse.com>

Hi!

I've been searching the net for info, but not much came up, really...

What I like is, first, to attach a vhba to the zone, and I believe it would be something like: 

"zonecfg:zone1> add device"
"zonecfg:zone1:device> set match=/devices/...."

But some posts I seen suggests that it should be: "zonecfg:zone1:device> set match=/dev/"..., not ..../devices/...?

Allright, if I can get this vhba into the zone, can I change the driver with:

 "# update_drv -d -i 'pciex1077,2432' qlc" ?

And then get the target driver instead?

"update_drv -a -i 'pciex1077,2432' qlt"

And finally enable the comstar service, to start serving LU's for the Fc fabric?

Rgrds Johan



From johan.kragsterman at capvert.se  Mon Mar 18 06:15:08 2013
From: johan.kragsterman at capvert.se (Johan Kragsterman)
Date: Mon, 18 Mar 2013 11:15:08 +0100
Subject: [OmniOS-discuss] Ang:  zones: can I add a vhba to zone?
In-Reply-To: <OFB8CFDB06.6347714D-ONC1257B32.00367444-C1257B32.00367449@inse.com>
References: <OFB8CFDB06.6347714D-ONC1257B32.00367444-C1257B32.00367449@inse.com>
Message-ID: <OFF06DC88A.7EF0DEF0-ONC1257B32.00385182-C1257B32.00385189@inse.com>

-----omnios-discuss-bounces at lists.omniti.com skrev: -----
Till: omnios-discuss at lists.omniti.com
Fr?n: Johan Kragsterman 
S?nt av: omnios-discuss-bounces at lists.omniti.com
Datum: 2013.03.18 10:56
?rende: [OmniOS-discuss] zones: can I add a vhba to zone?

"Hi!

I've been searching the net for info, but not much came up, really...

What I like is, first, to attach a vhba to the zone, and I believe it would be something like:

"zonecfg:zone1> add device"
"zonecfg:zone1:device> set match=/devices/...."

But some posts I seen suggests that it should be: "zonecfg:zone1:device> set match=/dev/"..., not ..../devices/...?

Allright, if I can get this vhba into the zone, can I change the driver with:

?"# update_drv -d -i 'pciex1077,2432' qlc" ?

And then get the target driver instead?

"update_drv -a -i 'pciex1077,2432' qlt"

And finally enable the comstar service, to start serving LU's for the Fc fabric?

Rgrds Johan"





Or, perhaps, when I been thinking a little bit more about it, is the driver inhereted from the physical hba? So that the driver attached to the phys hba is also used for the vhba?

Rgrds Johan

_______________________________________________
OmniOS-discuss mailing list
OmniOS-discuss at lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss




From fabio at fabiorabelo.wiki.br  Mon Mar 18 13:40:16 2013
From: fabio at fabiorabelo.wiki.br (=?UTF-8?Q?F=C3=A1bio_Rabelo?=)
Date: Mon, 18 Mar 2013 14:40:16 -0300
Subject: [OmniOS-discuss] D-Link FGE-528T
Message-ID: <CAEekY64waHUpJMr06A_=oeto6CdV=2ds0ot_o9svFq6w1P7d_Q@mail.gmail.com>

Hi to all ...

This is my first post, from Brasil, so please forgive my bad English ...

I am installing OmniOS to serve as Storage to a vitalization project .

The hardware are Supermicro single Opteron .

I intend to bind both embedded network port to talk with a dedicated
switcher with the nodes ...

So I need another network card top use to manage the OminOS .

To that task I get a D-Link DGE-528T ( based on Realtek 8169S ) .

But OmniOS do not recognise this card !


There are a way to workaround it ??


Or I will need to get another card ?


I just have PCI slots available in this system, all PCIe slots are
fulfilled with SATA cards ...


Thanks in advance to any help


F?bio Rabelo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20130318/e8ca9869/attachment.html>

From jdg117 at elvis.arl.psu.edu  Mon Mar 18 13:48:31 2013
From: jdg117 at elvis.arl.psu.edu (John D Groenveld)
Date: Mon, 18 Mar 2013 13:48:31 -0400
Subject: [OmniOS-discuss] D-Link FGE-528T
In-Reply-To: Your message of "Mon, 18 Mar 2013 14:40:16 -0300."
	<CAEekY64waHUpJMr06A_=oeto6CdV=2ds0ot_o9svFq6w1P7d_Q@mail.gmail.com> 
References: <CAEekY64waHUpJMr06A_=oeto6CdV=2ds0ot_o9svFq6w1P7d_Q@mail.gmail.com>
Message-ID: <201303181748.r2IHmVSf014819@elvis.arl.psu.edu>

In message <CAEekY64waHUpJMr06A_=oeto6CdV=2ds0ot_o9svFq6w1P7d_Q at mail.gmail.com>
, =?UTF-8?Q?F=C3=A1bio_Rabelo?= writes:
>To that task I get a D-Link DGE-528T ( based on Realtek 8169S ) .
>
>But OmniOS do not recognise this card !

Try Masayuki Murayama's gani driver:
<URL:http://homepage2.nifty.com/mrym3/taiyodo/eng/index.html>

John
groenveld at acm.org


From esproul at omniti.com  Mon Mar 18 15:32:34 2013
From: esproul at omniti.com (Eric Sproul)
Date: Mon, 18 Mar 2013 15:32:34 -0400
Subject: [OmniOS-discuss] Surge 2013 CFP now open
Message-ID: <CA+QY2RRML-y7ZAe0oK+TqzSEt0-K1ie57A5Y7-zWKB2Qj4hUsw@mail.gmail.com>

The Surge 2013 CFP is officially open.  For details or to submit a
proposal, see http://surge.omniti.com/2013

Note that the CFP deadline is 2013-05-01 23:59 *EDT* (the timezone
wasn't originally published, but may be by the time you read this)

From kent at watsen.net  Tue Mar 19 13:45:42 2013
From: kent at watsen.net (Kent Watsen)
Date: Tue, 19 Mar 2013 13:45:42 -0400
Subject: [OmniOS-discuss] trouble compiling OmniOS
In-Reply-To: <CA+QY2RR6YU=1m67k6VsRTsw+bi5w-YWsAG-GWixWOJHoyHtskQ@mail.gmail.com>
References: <51277BBE.6030108@watsen.net>
	<CACLsApsoJmkdv4nOpYdkckKYoN_F+GPWF1G5st0+d6D2ZWSTcQ@mail.gmail.com>
	<51279CD9.8080508@watsen.net>
	<CA+QY2RRVpcGYM+Q0XHrSRko=YVUH1GFPRKMUWD12LTVBRFALEg@mail.gmail.com>
	<512818CF.3030406@watsen.net>
	<CACLsApv4JeK_SoXZWf6gGyU5Fi43b=swXpO=RmCb4zqx3L6FGg@mail.gmail.com>
	<512835EA.2080608@watsen.net>
	<CACLsAptmvseSSa-gOUdmPXxdbErcuCaFdwMX77iG6P-9oYwM7Q@mail.gmail.com>
	<5128C693.6040107@watsen.net>
	<CA+QY2RTVOin4WRe96-WVV=AO0Pg7GN=o6S2TH9ynhnAaM2ufzw@mail.gmail.com>
	<512A35AF.90101@watsen.net>
	<CA+QY2RS3OhZfOXO4WFKmOa7NN_LwBLjD0WixZmCf+PBrtu+deA@mail.gmail.com>
	<512A4C6C.5010305@watsen.net>
	<CA+QY2RS0gADCSFOrcrtQUv_mjnXb94Nhgq5HKxx4C3h0E4Uj7g@mail.gmail.com>
	<512F1125.1070405@watsen.net>
	<CA+QY2RR6YU=1m67k6VsRTsw+bi5w-YWsAG-GWixWOJHoyHtskQ@mail.gmail.com>
Message-ID: <5148A446.50100@watsen.net>

An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20130319/56b0bed5/attachment-0001.html>

From jesus at omniti.com  Tue Mar 19 14:28:28 2013
From: jesus at omniti.com (Theo Schlossnagle)
Date: Tue, 19 Mar 2013 14:28:28 -0400
Subject: [OmniOS-discuss] trouble compiling OmniOS
In-Reply-To: <5148A446.50100@watsen.net>
References: <51277BBE.6030108@watsen.net>
	<CACLsApsoJmkdv4nOpYdkckKYoN_F+GPWF1G5st0+d6D2ZWSTcQ@mail.gmail.com>
	<51279CD9.8080508@watsen.net>
	<CA+QY2RRVpcGYM+Q0XHrSRko=YVUH1GFPRKMUWD12LTVBRFALEg@mail.gmail.com>
	<512818CF.3030406@watsen.net>
	<CACLsApv4JeK_SoXZWf6gGyU5Fi43b=swXpO=RmCb4zqx3L6FGg@mail.gmail.com>
	<512835EA.2080608@watsen.net>
	<CACLsAptmvseSSa-gOUdmPXxdbErcuCaFdwMX77iG6P-9oYwM7Q@mail.gmail.com>
	<5128C693.6040107@watsen.net>
	<CA+QY2RTVOin4WRe96-WVV=AO0Pg7GN=o6S2TH9ynhnAaM2ufzw@mail.gmail.com>
	<512A35AF.90101@watsen.net>
	<CA+QY2RS3OhZfOXO4WFKmOa7NN_LwBLjD0WixZmCf+PBrtu+deA@mail.gmail.com>
	<512A4C6C.5010305@watsen.net>
	<CA+QY2RS0gADCSFOrcrtQUv_mjnXb94Nhgq5HKxx4C3h0E4Uj7g@mail.gmail.com>
	<512F1125.1070405@watsen.net>
	<CA+QY2RR6YU=1m67k6VsRTsw+bi5w-YWsAG-GWixWOJHoyHtskQ@mail.gmail.com>
	<5148A446.50100@watsen.net>
Message-ID: <CACLsApvtY18_+gYshDDiNnYfoc_4OGULNOHO2Qs-V=3TA3fR_g@mail.gmail.com>

 Super detailed bug report. Thanks for that.

Clearly there is an issue building the perl stuff.

Can you look in the nightly log to see if there are more details regarding
the commands that are being run that generate those errors?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20130319/b2ac85cb/attachment.html>

From jesus at omniti.com  Tue Mar 19 17:34:36 2013
From: jesus at omniti.com (Theo Schlossnagle)
Date: Tue, 19 Mar 2013 17:34:36 -0400
Subject: [OmniOS-discuss] trouble compiling OmniOS
In-Reply-To: <CACLsApvtY18_+gYshDDiNnYfoc_4OGULNOHO2Qs-V=3TA3fR_g@mail.gmail.com>
References: <51277BBE.6030108@watsen.net>
	<CACLsApsoJmkdv4nOpYdkckKYoN_F+GPWF1G5st0+d6D2ZWSTcQ@mail.gmail.com>
	<51279CD9.8080508@watsen.net>
	<CA+QY2RRVpcGYM+Q0XHrSRko=YVUH1GFPRKMUWD12LTVBRFALEg@mail.gmail.com>
	<512818CF.3030406@watsen.net>
	<CACLsApv4JeK_SoXZWf6gGyU5Fi43b=swXpO=RmCb4zqx3L6FGg@mail.gmail.com>
	<512835EA.2080608@watsen.net>
	<CACLsAptmvseSSa-gOUdmPXxdbErcuCaFdwMX77iG6P-9oYwM7Q@mail.gmail.com>
	<5128C693.6040107@watsen.net>
	<CA+QY2RTVOin4WRe96-WVV=AO0Pg7GN=o6S2TH9ynhnAaM2ufzw@mail.gmail.com>
	<512A35AF.90101@watsen.net>
	<CA+QY2RS3OhZfOXO4WFKmOa7NN_LwBLjD0WixZmCf+PBrtu+deA@mail.gmail.com>
	<512A4C6C.5010305@watsen.net>
	<CA+QY2RS0gADCSFOrcrtQUv_mjnXb94Nhgq5HKxx4C3h0E4Uj7g@mail.gmail.com>
	<512F1125.1070405@watsen.net>
	<CA+QY2RR6YU=1m67k6VsRTsw+bi5w-YWsAG-GWixWOJHoyHtskQ@mail.gmail.com>
	<5148A446.50100@watsen.net>
	<CACLsApvtY18_+gYshDDiNnYfoc_4OGULNOHO2Qs-V=3TA3fR_g@mail.gmail.com>
Message-ID: <CACLsApvp9Yu4FSH9RnwH8MxFsv7wvcHy8QQXJ31vFzMDnQgDMw@mail.gmail.com>

It looks like you are building tip of illumos-omnios which requires bloody.
 If you want to build on 151004, you need to use that branch of our tree.
 The perl version has changed.

Make sure that branch of illumos-omnios is cloned into
/code/omnios-151004/illumos-omnios

And that the omnios-build system you are using is a clone of the r151004
branch as well.

I would say that if you are intending to do anything with the
illumos-kernel, it would likely be helpful to run bloody and not stable.
 All development happens on bloody -- stable is only maintained.

On Tue, Mar 19, 2013 at 2:28 PM, Theo Schlossnagle <jesus at omniti.com> wrote:

> Super detailed bug report. Thanks for that.
>
> Clearly there is an issue building the perl stuff.
>
> Can you look in the nightly log to see if there are more details regarding
> the commands that are being run that generate those errors?
>



-- 

Theo Schlossnagle

http://omniti.com/is/theo-schlossnagle
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20130319/291a2119/attachment.html>

From kent at watsen.net  Tue Mar 19 23:20:09 2013
From: kent at watsen.net (Kent Watsen)
Date: Tue, 19 Mar 2013 23:20:09 -0400
Subject: [OmniOS-discuss] trouble compiling OmniOS
In-Reply-To: <CACLsApvp9Yu4FSH9RnwH8MxFsv7wvcHy8QQXJ31vFzMDnQgDMw@mail.gmail.com>
References: <51277BBE.6030108@watsen.net>
	<CACLsApsoJmkdv4nOpYdkckKYoN_F+GPWF1G5st0+d6D2ZWSTcQ@mail.gmail.com>
	<51279CD9.8080508@watsen.net>
	<CA+QY2RRVpcGYM+Q0XHrSRko=YVUH1GFPRKMUWD12LTVBRFALEg@mail.gmail.com>
	<512818CF.3030406@watsen.net>
	<CACLsApv4JeK_SoXZWf6gGyU5Fi43b=swXpO=RmCb4zqx3L6FGg@mail.gmail.com>
	<512835EA.2080608@watsen.net>
	<CACLsAptmvseSSa-gOUdmPXxdbErcuCaFdwMX77iG6P-9oYwM7Q@mail.gmail.com>
	<5128C693.6040107@watsen.net>
	<CA+QY2RTVOin4WRe96-WVV=AO0Pg7GN=o6S2TH9ynhnAaM2ufzw@mail.gmail.com>
	<512A35AF.90101@watsen.net>
	<CA+QY2RS3OhZfOXO4WFKmOa7NN_LwBLjD0WixZmCf+PBrtu+deA@mail.gmail.com>
	<512A4C6C.5010305@watsen.net>
	<CA+QY2RS0gADCSFOrcrtQUv_mjnXb94Nhgq5HKxx4C3h0E4Uj7g@mail.gmail.com>
	<512F1125.1070405@watsen.net>
	<CA+QY2RR6YU=1m67k6VsRTsw+bi5w-YWsAG-GWixWOJHoyHtskQ@mail.gmail.com>
	<5148A446.50100@watsen.net>
	<CACLsApvtY18_+gYshDDiNnYfoc_4OGULNOHO2Qs-V=3TA3fR_g@mail.gmail.com>
	<CACLsApvp9Yu4FSH9RnwH8MxFsv7wvcHy8QQXJ31vFzMDnQgDMw@mail.gmail.com>
Message-ID: <51492AE9.3080803@watsen.net>

An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20130319/5354a9c6/attachment.html>

From kent at watsen.net  Wed Mar 20 10:06:48 2013
From: kent at watsen.net (Kent Watsen)
Date: Wed, 20 Mar 2013 10:06:48 -0400
Subject: [OmniOS-discuss] trouble compiling OmniOS
In-Reply-To: <51492AE9.3080803@watsen.net>
References: <51277BBE.6030108@watsen.net>
	<CACLsApsoJmkdv4nOpYdkckKYoN_F+GPWF1G5st0+d6D2ZWSTcQ@mail.gmail.com>
	<51279CD9.8080508@watsen.net>
	<CA+QY2RRVpcGYM+Q0XHrSRko=YVUH1GFPRKMUWD12LTVBRFALEg@mail.gmail.com>
	<512818CF.3030406@watsen.net>
	<CACLsApv4JeK_SoXZWf6gGyU5Fi43b=swXpO=RmCb4zqx3L6FGg@mail.gmail.com>
	<512835EA.2080608@watsen.net>
	<CACLsAptmvseSSa-gOUdmPXxdbErcuCaFdwMX77iG6P-9oYwM7Q@mail.gmail.com>
	<5128C693.6040107@watsen.net>
	<CA+QY2RTVOin4WRe96-WVV=AO0Pg7GN=o6S2TH9ynhnAaM2ufzw@mail.gmail.com>
	<512A35AF.90101@watsen.net>
	<CA+QY2RS3OhZfOXO4WFKmOa7NN_LwBLjD0WixZmCf+PBrtu+deA@mail.gmail.com>
	<512A4C6C.5010305@watsen.net>
	<CA+QY2RS0gADCSFOrcrtQUv_mjnXb94Nhgq5HKxx4C3h0E4Uj7g@mail.gmail.com>
	<512F1125.1070405@watsen.net>
	<CA+QY2RR6YU=1m67k6VsRTsw+bi5w-YWsAG-GWixWOJHoyHtskQ@mail.gmail.com>
	<5148A446.50100@watsen.net>
	<CACLsApvtY18_+gYshDDiNnYfoc_4OGULNOHO2Qs-V=3TA3fR_g@mail.gmail.com>
	<CACLsApvp9Yu4FSH9RnwH8MxFsv7wvcHy8QQXJ31vFzMDnQgDMw@mail.gmail.com>
	<51492AE9.3080803@wats en.net>
Message-ID: <5149C278.8030105@watsen.net>

An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20130320/bdde685e/attachment.html>

From jesus at omniti.com  Wed Mar 20 10:16:24 2013
From: jesus at omniti.com (Theo Schlossnagle)
Date: Wed, 20 Mar 2013 10:16:24 -0400
Subject: [OmniOS-discuss] trouble compiling OmniOS
In-Reply-To: <5149C278.8030105@watsen.net>
References: <51277BBE.6030108@watsen.net>
	<CACLsApsoJmkdv4nOpYdkckKYoN_F+GPWF1G5st0+d6D2ZWSTcQ@mail.gmail.com>
	<51279CD9.8080508@watsen.net>
	<CA+QY2RRVpcGYM+Q0XHrSRko=YVUH1GFPRKMUWD12LTVBRFALEg@mail.gmail.com>
	<512818CF.3030406@watsen.net>
	<CACLsApv4JeK_SoXZWf6gGyU5Fi43b=swXpO=RmCb4zqx3L6FGg@mail.gmail.com>
	<512835EA.2080608@watsen.net>
	<CACLsAptmvseSSa-gOUdmPXxdbErcuCaFdwMX77iG6P-9oYwM7Q@mail.gmail.com>
	<5128C693.6040107@watsen.net>
	<CA+QY2RTVOin4WRe96-WVV=AO0Pg7GN=o6S2TH9ynhnAaM2ufzw@mail.gmail.com>
	<512A35AF.90101@watsen.net>
	<CA+QY2RS3OhZfOXO4WFKmOa7NN_LwBLjD0WixZmCf+PBrtu+deA@mail.gmail.com>
	<512A4C6C.5010305@watsen.net>
	<CA+QY2RS0gADCSFOrcrtQUv_mjnXb94Nhgq5HKxx4C3h0E4Uj7g@mail.gmail.com>
	<512F1125.1070405@watsen.net>
	<CA+QY2RR6YU=1m67k6VsRTsw+bi5w-YWsAG-GWixWOJHoyHtskQ@mail.gmail.com>
	<5148A446.50100@watsen.net>
	<CACLsApvtY18_+gYshDDiNnYfoc_4OGULNOHO2Qs-V=3TA3fR_g@mail.gmail.com>
	<CACLsApvp9Yu4FSH9RnwH8MxFsv7wvcHy8QQXJ31vFzMDnQgDMw@mail.gmail.com>
	<51492AE9.3080803@watsen.net> <5149C278.8030105@watsen.net>
Message-ID: <CACLsApu-KD+-zdTqv9RyuNipUF3wXZ43SeyVS7-8QwRfUt0dTQ@mail.gmail.com>

On Wed, Mar 20, 2013 at 10:06 AM, Kent Watsen <kent at watsen.net> wrote:

> But one thing I can't figure out is how to set the "PROTO_AREA" variable.
> The original Makefile has:
>
> PROTO_AREA =   $(PWD)/../../../proto
>
> and uses it on the following lines:
>
> *$ grep PROTO_AREA Makefile *
> PROTO_AREA =    $(PWD)/../../../proto
> CC =        $(PROTO_AREA)/usr/bin/gcc    (I explicitly set the CC
> variable above)
> LD =        $(PROTO_AREA)/usr/bin/ld
>     -isystem $(PROTO_AREA)/usr/include \
>     -isystem $(PROTO_AREA)/usr/include \
>     -L$(PROTO_AREA)/lib \
>     -L$(PROTO_AREA)/usr/lib
>     -L$(PROTO_AREA)/lib \
>     -L$(PROTO_AREA)/usr/lib \
>
>
> Searching /code for "proto" directories, I find:
>
> *$ find /code -type d -name proto*
> /code/omnios-151004/illumos-omnios/usr/src/tools/proto
> /code/omnios-151004/illumos-omnios/usr/src/cmd/sgs/proto
> /code/omnios-151004/illumos-omnios/proto
>
> But none of /usr/include, /lib, /usr/lib, or /usr/bin/ld exist under any
> of these "proto" directories
>
> Any advice how to set this PROTO_AREA variable?
>
/code/omnios-151005/illumos-omnios/proto/root_i386 is my proto root... but
it might vary if you are building a debug kernel.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20130320/21915dd0/attachment.html>

From esproul at omniti.com  Thu Mar 21 15:10:58 2013
From: esproul at omniti.com (Eric Sproul)
Date: Thu, 21 Mar 2013 15:10:58 -0400
Subject: [OmniOS-discuss] Updated release: r151004t
Message-ID: <CA+QY2RTykbCf606qCjTGR-5QM8SvSFDKzFjnvcGyN4HJ1_fZ8w@mail.gmail.com>

Weekly release r151004t delivers a security fix for KVM.  Updating
does not require a reboot, though that is the simplest way to get the
new driver module loaded.  See the release notes for instructions on
manually unloading and reloading the KVM driver.

http://omnios.omniti.com/wiki.php/ReleaseNotes#r151004t

From geoffn at gnaa.net  Fri Mar 22 14:04:23 2013
From: geoffn at gnaa.net (Geoff Nordli)
Date: Fri, 22 Mar 2013 11:04:23 -0700
Subject: [OmniOS-discuss] zookeeper client disconnecting
In-Reply-To: <CACLsAptEi0Q6OWSS6RN4kWa__x_artBY+RV8hyoTBs2tTYhQ-g@mail.gmail.com>
References: <5140D574.7060400@gnaa.net> <5140DC2F.1020603@gnaa.net>
	<CACLsAptEi0Q6OWSS6RN4kWa__x_artBY+RV8hyoTBs2tTYhQ-g@mail.gmail.com>
Message-ID: <514C9D27.7000805@gnaa.net>

On 13-03-13 01:38 PM, Theo Schlossnagle wrote:
> All Java? I'd start by trussing the client and tcpdumping during a 
> disconnection.
>
> It's hard to imaging that this is an OmniOS or Illumos problem 
> specifically as that's just simple IP stuff.
>
> On Wed, Mar 13, 2013 at 4:06 PM, Geoff Nordli <geoffn at gnaa.net 
> <mailto:geoffn at gnaa.net>> wrote:
>
>
>     On 13-03-13 12:37 PM, Geoff Nordli wrote:
>
>         Just wondering if anyone is  successfully using zookeeper with
>         omnios?
>
>         The client seems to be frequently disconnecting from the
>         zookeeper service.
>
>         thanks,
>
>         Geoff
>
>
>
>     Sorry, this wasn't very descriptive.
>
>     Omnios is running as a client.
>
>     The ZK server is running on Linux (Ubuntu).  server zk_version
>     3.4.4-1386507, built on 09/17/2012 08:33 GMT
>
>     There are other clients running running on Linux and BS
>
>     D which are not experience disconnect issues.
>
>

Thanks Theo.

It is running inside a VirtualBox VM (just for testing).  We found by 
adding another proc it seems to have fixed the issue.

Happy Friday!

Geoff

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20130322/43335c6b/attachment.html>

From ramquick at gmail.com  Sat Mar 23 04:00:19 2013
From: ramquick at gmail.com (Ram Chander)
Date: Sat, 23 Mar 2013 13:30:19 +0530
Subject: [OmniOS-discuss] Drives goes offline in Zpool
Message-ID: <CAMRGQbPhNvbq2YnpWuPoNResPibxOCZbLMwVjFJQvOxWgsf4jQ@mail.gmail.com>

Hi,

I have Dell md1200 connected to two heads ( Dell R710 ). The heads have
Perc H800 card and drives are configured in Raid0 ( Virtual Disk) in the
RAID controller.

One of the drives had crashed and is replaced by a spare. Resilvering was
triggered but fails to complete due to drives going offline.  I have to
reboot the head ( R710) and drives comes online. This happened  repeatedly
when resilver was 4% done, and again was rebooted ,  again hung at 27%
done, etc.

The issues happens with both Solaris11.1/ Omnios.
Its a 100Tb  pool with 69Tb used. I have critical data and cant afford loss
of data.
Can I recover the data anyway ( atleast partially ) ?

I had verified there is no hardware issue with H800 and also upgraded the
firmware for H800. The issue happens with both the heads.

Current OS: Solaris 11.1

Mar 22 21:47:55 solaris scsi: [ID 107833 kern.warning] WARNING: /pci at 0
,0/pci8086,340e at 7/pci1028,1f15 at 0/sd at 12,0 (sd26):
Mar 22 21:47:55 solaris    Command failed to complete...Device is gone
Mar 22 21:47:55 solaris scsi: [ID 107833 kern.warning] WARNING: /pci at 0
,0/pci8086,340e at 7/pci1028,1f15 at 0/sd at c,0 (sd20):
Mar 22 21:47:55 solaris    Command failed to complete...Device is gone
Mar 22 21:47:55 solaris scsi: [ID 107833 kern.warning] WARNING: /pci at 0
,0/pci8086,340e at 7/pci1028,1f15 at 0/sd at 18,0 (sd32):
Mar 22 21:47:55 solaris    Command failed to complete...Device is gone
Mar 22 21:47:55 solaris scsi: [ID 107833 kern.warning] WARNING: /pci at 0
,0/pci8086,340e at 7/pci1028,1f15 at 0/sd at 1c,0 (sd36):
Mar 22 21:47:55 solaris    Command failed to complete...Device is gone
Mar 22 21:47:55 solaris scsi: [ID 107833 kern.warning] WARNING: /pci at 0
,0/pci8086,340e at 7/pci1028,1f15 at 0/sd at 1b,0 (sd35):
Mar 22 21:47:55 solaris    Command failed to complete...Device is gone
Mar 22 21:47:55 solaris scsi: [ID 107833 kern.warning] WARNING: /pci at 0
,0/pci8086,340e at 7/pci1028,1f15 at 0/sd at 1e,0 (sd38):
Mar 22 21:47:55 solaris    Command failed to complete...Device is gone
Mar 22 21:47:55 solaris scsi: [ID 107833 kern.warning] WARNING: /pci at 0
,0/pci8086,340e at 7/pci1028,1f15 at 0/sd at 19,0 (sd33):
Mar 22 21:47:55 solaris    Command failed to complete...Device is gone
Mar 22 21:47:55 solaris scsi: [ID 107833 kern.warning] WARNING: /pci at 0
,0/pci8086,340e at 7/pci1028,1f15 at 0/sd at 1d,0 (sd37):
Mar 22 21:47:55 solaris    Command failed to complete...Device is gone
Mar 22 21:47:55 solaris scsi: [ID 107833 kern.warning] WARNING: /pci at 0
,0/pci8086,340e at 7/pci1028,1f15 at 0/sd at 27,0 (sd47):
Mar 22 21:47:55 solaris    Command failed to complete...Device is gone
Mar 22 21:47:55 solaris scsi: [ID 107833 kern.warning] WARNING: /pci at 0
,0/pci8086,340e at 7/pci1028,1f15 at 0/sd at 26,0 (sd46):
Mar 22 21:47:55 solaris    Command failed to complete...Device is gone

# zpool status -v

  pool: test
 state: DEGRADED
status: One or more devices is currently being resilvered.  The pool will
        continue to function in a degraded state.
action: Wait for the resilver to complete.
  scan: resilver in progress since Wed Mar 20 19:13:40 2013
    27.4T scanned out of 69.6T at 183M/s, 67h11m to go
    2.43T resilvered, 39.32% done
config:

        NAME                        STATE     READ WRITE CKSUM
        test                      DEGRADED     0     0     0
          raidz1-0                  DEGRADED     0     0     0
            c8t0d0                  ONLINE       0     0     0
            c8t1d0                  DEGRADED     0     0     0
            c8t2d0                  DEGRADED     0     0     0
            c8t3d0                  ONLINE       0     0     0
            spare-4                 DEGRADED     0     0     0
              12459181442598970150  UNAVAIL      0     0     0
              c8t45d0               DEGRADED     0     0     0
(resilvering)
          raidz1-1                  ONLINE       0     0     0
            c8t5d0                  ONLINE       0     0     0
            c8t6d0                  ONLINE       0     0     0
            c8t7d0                  ONLINE       0     0     0
            c8t8d0                  ONLINE       0     0     0
            c8t9d0                  ONLINE       0     0     0
          raidz1-3                  DEGRADED     0     0     0
            c8t12d0                 ONLINE       0     0     0
            c8t13d0                 ONLINE       0     0     0
            c8t14d0                 ONLINE       0     0     0
            c8t15d0                 DEGRADED     0     0     0
            c8t16d0                 ONLINE       0     0     0
            c8t17d0                 ONLINE       0     0     0
            c8t18d0                 ONLINE       0     0     0
            c8t19d0                 ONLINE       0     0     0
            c8t20d0                 DEGRADED     0     0     0
            c8t21d0                 DEGRADED     0     0     0
            spare-10                DEGRADED     0     0     0
              c8t22d0               DEGRADED     0     0     0
              c8t47d0               DEGRADED     0     0     0
(resilvering)
            c8t23d0                 ONLINE       0     0     0
          raidz1-4                  DEGRADED     0     0     0
            c8t24d0                 DEGRADED     0     0     0
            c8t25d0                 ONLINE       0     0     0
            c8t26d0                 ONLINE       0     0     0
            c8t27d0                 ONLINE       0     0     0
            c8t28d0                 ONLINE       0     0     0
            c8t29d0                 DEGRADED     0     0     0
            c8t30d0                 ONLINE       0     0     0
          raidz1-5                  DEGRADED     0     0     0
            spare-0                 DEGRADED     0     0     5
              c8t31d0               DEGRADED     0     0     0
              c8t46d0               DEGRADED     0     0     0
(resilvering)
            c8t32d0                 ONLINE       0     0     0
            c8t33d0                 ONLINE       0     0     0
            c8t34d0                 ONLINE       0     0     0
            c8t35d0                 DEGRADED     0     0     0
            c8t36d0                 DEGRADED     0     0     0
            c8t37d0                 ONLINE       0     0     0
          raidz1-6                  DEGRADED     0     0     0
            c8t38d0                 DEGRADED     0     0     0
            c8t39d0                 ONLINE       0     0     0
            c8t40d0                 DEGRADED     0     0     0
            c8t41d0                 DEGRADED     0     0     0
            c8t42d0                 ONLINE       0     0     0
            c8t43d0                 ONLINE       0     0     0
            c8t44d0                 ONLINE       0     0     0
        spares
          c8t45d0                   INUSE
          c8t46d0                   INUSE
          c8t47d0                   INUSE

device details:

       c8t1d0                    DEGRADED        scrub/resilver needed
        status: ZFS detected errors on this device.
                The device is missing some data that is recoverable.

        c8t2d0                    DEGRADED        scrub/resilver needed
        status: ZFS detected errors on this device.
                The device is missing some data that is recoverable.

        12459181442598970150      UNAVAIL         was /dev/dsk/c2t4d0s0
        status: ZFS detected errors on this device.
                The device was missing.

        c8t45d0                   DEGRADED        scrub/resilver needed
        status: ZFS detected errors on this device.
                The device is missing some data that is recoverable.

        c8t15d0                   DEGRADED        scrub/resilver needed
        status: ZFS detected errors on this device.
                The device is missing some data that is recoverable.

        c8t20d0                   DEGRADED        scrub/resilver needed
        status: ZFS detected errors on this device.
                The device is missing some data that is recoverable.

        c8t21d0                   DEGRADED        scrub/resilver needed
        status: ZFS detected errors on this device.
                The device is missing some data that is recoverable.

        c8t22d0                   DEGRADED        scrub/resilver needed
        status: ZFS detected errors on this device.
                The device is missing some data that is recoverable.

             The device is missing some data that is recoverable.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20130323/2da4a38e/attachment.html>

From kaspar.schiess at absurd.li  Sat Mar 23 15:41:07 2013
From: kaspar.schiess at absurd.li (Kaspar Schiess)
Date: Sat, 23 Mar 2013 20:41:07 +0100
Subject: [OmniOS-discuss] System in a strange place
Message-ID: <394064AE-9CB4-46C5-AEF4-86C63B68E698@absurd.li>

Hello,

One of my test systems running OmniOS is in a strange place - I hope to 
resurrect it from there. Last Sunday, I've updated it to the latest 
version of stable OmniOS and shut it down. Then after maintenance, I 
tried starting it again, hoping that it would come up.

It did not cleanly. If I boot into ILO, I can see that the system 
displays a root login prompt, but doesn't let me use the keyboard to log 
in.

I've since booted to an OmniOS iso and verified the state of the root 
pool (fine) and whether there were any unusual messages at boot (none). 
Seems that the system boots and then just hangs there, reacting neither 
to ssh nor to a console login (doesn't even echo keys back). Sometimes 
though I can type a few chars .. to have it lock up afterwards, in the 
space of 10-30 seconds.

I've tried verbose booting; no real useful information there - it lists 
all drivers and then locks up. I've also tried '-kd' - I get the mdb 
prompt, but can't type there (locked system).

Any help would be appreciated. What should I try?

best regards,
kaspar

From kaspar.schiess at absurd.li  Sun Mar 24 11:44:06 2013
From: kaspar.schiess at absurd.li (Kaspar Schiess)
Date: Sun, 24 Mar 2013 16:44:06 +0100
Subject: [OmniOS-discuss] System in a strange place
Message-ID: <124D3332-DACD-4206-BA17-08D824AAD382@absurd.li>

Hello,

One of my test systems running OmniOS is in a strange place - I hope to 
resurrect it from there. Last Sunday, I've updated it to the latest 
version of stable OmniOS and shut it down. Then after maintenance, I 
tried starting it again, hoping that it would come up.

It did not cleanly. If I boot into ILO, I can see that the system 
displays a root login prompt, but doesn't let me use the keyboard to log 
in.

I've since booted to an OmniOS iso and verified the state of the root 
pool (fine) and whether there were any unusual messages at boot (none). 
Seems that the system boots and then just hangs there, reacting neither 
to ssh nor to a console login (doesn't even echo keys back). Sometimes 
though I can type a few chars .. to have it lock up afterwards, in the 
space of 10-30 seconds.

I've tried verbose booting; no real useful information there - it lists 
all drivers and then locks up. I've also tried '-kd' - I get the mdb 
prompt, but can't type there (locked system).

Any help would be appreciated. What should I try?

best regards,
kaspar

From henson at acm.org  Sun Mar 24 15:10:56 2013
From: henson at acm.org (Paul B. Henson)
Date: Sun, 24 Mar 2013 12:10:56 -0700
Subject: [OmniOS-discuss] System in a strange place
In-Reply-To: <124D3332-DACD-4206-BA17-08D824AAD382@absurd.li>
References: <124D3332-DACD-4206-BA17-08D824AAD382@absurd.li>
Message-ID: <20130324191056.GQ30773@bender.unx.csupomona.edu>

On Sun, Mar 24, 2013 at 04:44:06PM +0100, Kaspar Schiess wrote:

> One of my test systems running OmniOS is in a strange place - I hope to 
> resurrect it from there. Last Sunday, I've updated it to the latest 
> version of stable OmniOS and shut it down. Then after maintenance, I 
> tried starting it again, hoping that it would come up.
> 
> It did not cleanly. If I boot into ILO, I can see that the system 
> displays a root login prompt, but doesn't let me use the keyboard to log 
> in.

You didn't perchance perform the update into an alternative boot
environment? If you did, you should be able to use grub to select the
previous pre-update boot environment to boot into to see if the updates
caused your problem. If you didn't update into a separate BE, this is an
example of why you should 8-/.

You could potentially use pkg off a boot cd to try and back out the
updates, but exactly how to do that I'm not sure of...


From kohlerr at ics.uci.edu  Mon Mar 25 01:38:19 2013
From: kohlerr at ics.uci.edu (Ryan Kohler)
Date: Sun, 24 Mar 2013 22:38:19 -0700
Subject: [OmniOS-discuss] System in a strange place
In-Reply-To: <124D3332-DACD-4206-BA17-08D824AAD382@absurd.li>
References: <124D3332-DACD-4206-BA17-08D824AAD382@absurd.li>
Message-ID: <514FE2CB.60804@ics.uci.edu>



On 3/24/2013 8:44 AM, Kaspar Schiess wrote:
> Hello,
>
> One of my test systems running OmniOS is in a strange place - I hope to
> resurrect it from there. Last Sunday, I've updated it to the latest version of
> stable OmniOS and shut it down. Then after maintenance, I tried starting it
> again, hoping that it would come up.
>
> It did not cleanly. If I boot into ILO, I can see that the system displays a
> root login prompt, but doesn't let me use the keyboard to log in.
>
> I've since booted to an OmniOS iso and verified the state of the root pool
> (fine) and whether there were any unusual messages at boot (none). Seems that
> the system boots and then just hangs there, reacting neither to ssh nor to a
> console login (doesn't even echo keys back). Sometimes though I can type a few
> chars .. to have it lock up afterwards, in the space of 10-30 seconds.
>
> I've tried verbose booting; no real useful information there - it lists all
> drivers and then locks up. I've also tried '-kd' - I get the mdb prompt, but
> can't type there (locked system).
>
> Any help would be appreciated. What should I try?
>
> best regards,
> kaspar
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss

If you have physical access to the server, can you try a ps/2 keyboard and see 
if it accepts keyboard input?

I ran into something similar on CentOS using a non standard kernel where it 
did not support usb devices. In that case, the kvm in the ilom emulates a usb 
keyboard and I couldn't type anything on the console. I had to physically go 
to the server and plug in a ps/2 keyboard so that I could work on it.

Ryan

From jmsrinivas at yahoo.com  Mon Mar 25 13:45:15 2013
From: jmsrinivas at yahoo.com (srinivas jonn)
Date: Tue, 26 Mar 2013 01:45:15 +0800 (SGT)
Subject: [OmniOS-discuss] HCL: support Intel patsburg - C6xx - Sandy Bridge
Message-ID: <1364233515.78945.YahooMailNeo@web190805.mail.sg3.yahoo.com>



quick question on support for Intel sandy bridge chipsets:

does anyone have success with running latest omniOS on Intel patsburg - ie C6xx chipset?

success has been reported against Intel C2xx - Cougar Point.

Nexenta fully supports these, and Oracle Solaris 11 too

but there is no mention in the official Illumos HCL

the "device driver utility" on OI 151-A7 reported several unknown system devices on Xeon E5-26xx server

mostly the CPU QPI modules were reported "unknown" - does this mean any known limitations?

thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20130326/8594b2c2/attachment.html>

From gmason at msu.edu  Mon Mar 25 13:53:54 2013
From: gmason at msu.edu (Greg Mason)
Date: Mon, 25 Mar 2013 13:53:54 -0400
Subject: [OmniOS-discuss] HCL: support Intel patsburg - C6xx - Sandy
	Bridge
In-Reply-To: <1364233515.78945.YahooMailNeo@web190805.mail.sg3.yahoo.com>
References: <1364233515.78945.YahooMailNeo@web190805.mail.sg3.yahoo.com>
Message-ID: <ED98A51C-4120-4B89-A0CF-1286492A04E5@msu.edu>

I've been running some Sandy Bridge, Intel C602-based systems in production for a few months now. No issues, but I also am also only using LSI SAS2008-based HBAs, I'm not using the SATA or SAS ports provided by the chipset.

Greg Mason
HPC Systems Administrator
Michigan State University
High Performance Computing Center

web: www.hpcc.msu.edu
email: gmason at msu.edu
aim: gmason at msu.edu
phone: (517) 353-8666

On Mar 25, 2013, at 1:45 PM, srinivas jonn <jmsrinivas at yahoo.com> wrote:

> 
> quick question on support for Intel sandy bridge chipsets:
> 
> does anyone have success with running latest omniOS on Intel patsburg - ie C6xx chipset?
> 
> success has been reported against Intel C2xx - Cougar Point.
> 
> Nexenta fully supports these, and Oracle Solaris 11 too
> 
> but there is no mention in the official Illumos HCL
> 
> the "device driver utility" on OI 151-A7 reported several unknown system devices on Xeon E5-26xx server
> 
> mostly the CPU QPI modules were reported "unknown" - does this mean any known limitations?
> 
> thank you.
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20130325/b6f73544/attachment.html>

From henson at acm.org  Mon Mar 25 14:28:46 2013
From: henson at acm.org (Paul B. Henson)
Date: Mon, 25 Mar 2013 11:28:46 -0700
Subject: [OmniOS-discuss] HCL: support Intel patsburg - C6xx - Sandy
	Bridge
In-Reply-To: <1364233515.78945.YahooMailNeo@web190805.mail.sg3.yahoo.com>
References: <1364233515.78945.YahooMailNeo@web190805.mail.sg3.yahoo.com>
Message-ID: <5150975E.6000701@acm.org>

On 3/25/2013 10:45 AM, srinivas jonn wrote:

> does anyone have success with running latest omniOS on Intel patsburg -
> ie C6xx chipset?

Joyent recommends the supermicro X9DRD-7LN4F-JBOD motherboard as one 
they currently use in production, which has an C602J chipset as well as 
8 SAS ports from an LSI 2308 chipset in IT mode. I'm assuming they 
evaluated compatibility fairly thoroughly :). The AHCI SATA ports should 
work fine, although from what I understand the SCU SATA ports are not 
yet supported.


From esproul at omniti.com  Mon Mar 25 14:58:51 2013
From: esproul at omniti.com (Eric Sproul)
Date: Mon, 25 Mar 2013 14:58:51 -0400
Subject: [OmniOS-discuss] HCL: support Intel patsburg - C6xx - Sandy
	Bridge
In-Reply-To: <5150975E.6000701@acm.org>
References: <1364233515.78945.YahooMailNeo@web190805.mail.sg3.yahoo.com>
	<5150975E.6000701@acm.org>
Message-ID: <CA+QY2RT=0Ftx+kqkwnF4CGj3ibheqZc1QinsssC81V3yXEo6NQ@mail.gmail.com>

On Mon, Mar 25, 2013 at 2:28 PM, Paul B. Henson <henson at acm.org> wrote:
> Joyent recommends the supermicro X9DRD-7LN4F-JBOD motherboard as one they
> currently use in production, which has an C602J chipset as well as 8 SAS
> ports from an LSI 2308 chipset in IT mode. I'm assuming they evaluated
> compatibility fairly thoroughly :). The AHCI SATA ports should work fine,
> although from what I understand the SCU SATA ports are not yet supported.

That's correct, neither SCU SAS nor SCU SATA are supported.  PCH/ICH
SATA attach as AHCI and work just fine, as do board-level integrations
like LSI SAS.

On the network side, low-end Patsburg boards from Supermicro and Intel
come with the 82579LM/82574L combo for dual-1G NICs, and both are
supported by e1000g(7).  Higher-spec boards typically include a dual
I350, which is supported by igb(7).

Eric

From henson at acm.org  Mon Mar 25 15:12:06 2013
From: henson at acm.org (Paul B. Henson)
Date: Mon, 25 Mar 2013 12:12:06 -0700
Subject: [OmniOS-discuss] Supermicro X9SRI-F NMI
Message-ID: <5150A186.7040102@acm.org>

I'm building a storage server using a supermicro X9SRI-F motherboard, 
and I'm trying to set it up to panic on an NMI so in the (hopefully 
unlikely) case the server goes out to lunch at some point, I will be 
able to generate a crash dump and some diagnostics. Right now the box is 
running a test install of omnios bloody.

The board has IPMI capability, and I'm running 'ipmitool -I lanplus -H 
host chassis power diag', which should generate an NMI.

However, instead of a log message indicating an NMI has been received (I 
don't have the /etc/system setting in yet to actually panic), the box 
wedges hard and becomes completely unresponsive.

The board also has an NMI header, although the chassis I have it in does 
not have a button to connect to it. I have not yet tried generating the 
NMI by shorting the jumper as opposed to via IPMI, so I'm not sure if 
that will do something differently.

I've never actually tried this under OpenSolaris/illumos, but am 
assuming it should work more or less the same as under Solaris 10? Has 
anybody tested NMI functionality with a recent illumos and could give me 
at least a starting point that it should be working :)?

Thanks much?

From fabio at fabiorabelo.wiki.br  Mon Mar 25 15:15:18 2013
From: fabio at fabiorabelo.wiki.br (=?UTF-8?Q?F=C3=A1bio_Rabelo?=)
Date: Mon, 25 Mar 2013 16:15:18 -0300
Subject: [OmniOS-discuss] Highpoint 640 or 640L
Message-ID: <CAEekY64Rs4i91AciS1wRb8y5y_tBpuwaqf5g628aBeYHJfEgrA@mail.gmail.com>

Hi to all

Someone knows if Marvel based SATA cards works ?

http://www.highpoint-tech.com/USA_new/series_rr600-overview.htm

Highpoint rocketraid 640L : based on Marvel 88se9235

Highpoint rocketraid 640  : based on masrvel 88se9128

This cards are not for boot the system, just for zfs storage .

I will put napp-it over Omni ...


Thanks in advance


F?bio Rabelo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20130325/e6cb39d9/attachment.html>

From henson at acm.org  Mon Mar 25 15:17:24 2013
From: henson at acm.org (Paul B. Henson)
Date: Mon, 25 Mar 2013 12:17:24 -0700
Subject: [OmniOS-discuss] changing rpool zfs properties prior to install
Message-ID: <5150A2C4.70706@acm.org>

Currently AFAIK there is no way to muck with the rpool during an omnios 
install. It's easy enough to attach another disk after the fact if you 
want a mirrored rpool, but I was thinking of trying out compression on 
my rpool, and turning that on after everything's already copied doesn't 
do much good :).

Is there anyway to use the break out to the shell option in the 
installer to go create the rpool manually, and then have the installer 
use it rather than create its own? Or any other method by which you 
could customize zfs properties on your rpool prior to the OS actually 
being installed?

Thanks?

From henson at acm.org  Mon Mar 25 15:30:12 2013
From: henson at acm.org (Paul B. Henson)
Date: Mon, 25 Mar 2013 12:30:12 -0700
Subject: [OmniOS-discuss] Irregularly scheduled SSD survey :)
Message-ID: <5150A5C4.10106@acm.org>

It seems like it's been a while since there's been an SSD discussion; 
I'm in the market for a few and was wondering if anybody had any new 
favorites, or updated information about any previous candidates.

I'm looking to get two of say 200G or larger, to create an rpool mirror 
across the first partition of each and have the second partition of each 
an independent L2ARC. Ideally I'd like to find a third small one with 
power failure protection to be a slog; if that doesn't work out I might 
carve out a third partition on each of the two big ones to create a slog 
mirror. Definitely not preferable, but it's a home server, so trade-offs 
might need to be made <sigh>.

Thanks in advance for any feedback.

From esproul at omniti.com  Mon Mar 25 15:34:30 2013
From: esproul at omniti.com (Eric Sproul)
Date: Mon, 25 Mar 2013 15:34:30 -0400
Subject: [OmniOS-discuss] Highpoint 640 or 640L
In-Reply-To: <CAEekY64Rs4i91AciS1wRb8y5y_tBpuwaqf5g628aBeYHJfEgrA@mail.gmail.com>
References: <CAEekY64Rs4i91AciS1wRb8y5y_tBpuwaqf5g628aBeYHJfEgrA@mail.gmail.com>
Message-ID: <CA+QY2RQ2DJNwefJJJ9298F8HXLXz7PPigZW3madMyYRBPgUkdg@mail.gmail.com>

On Mon, Mar 25, 2013 at 3:15 PM, F?bio Rabelo <fabio at fabiorabelo.wiki.br> wrote:
> Hi to all
>
> Someone knows if Marvel based SATA cards works ?
>
> http://www.highpoint-tech.com/USA_new/series_rr600-overview.htm
>
> Highpoint rocketraid 640L : based on Marvel 88se9235
>
> Highpoint rocketraid 640  : based on masrvel 88se9128

I don't believe any Marvell 9xxx SATA chips have ever been supported
in Solaris or any derivative.  An inexpensive alternative would be
something based on SiliconImage 3124.

Eric

From esproul at omniti.com  Mon Mar 25 15:41:07 2013
From: esproul at omniti.com (Eric Sproul)
Date: Mon, 25 Mar 2013 15:41:07 -0400
Subject: [OmniOS-discuss] changing rpool zfs properties prior to install
In-Reply-To: <5150A2C4.70706@acm.org>
References: <5150A2C4.70706@acm.org>
Message-ID: <CA+QY2RR2fPZ5B7vHVGv-A-br3=ha4KETPVLN+nB667A8pF2kRw@mail.gmail.com>

On Mon, Mar 25, 2013 at 3:17 PM, Paul B. Henson <henson at acm.org> wrote:
> Is there anyway to use the break out to the shell option in the installer to
> go create the rpool manually, and then have the installer use it rather than
> create its own? Or any other method by which you could customize zfs
> properties on your rpool prior to the OS actually being installed?

Paul,
A network install using Kayak is the best way to get what you want.
The ISO installer is the most barely-functional version we could
tolerate shipping, because we see network installs being the preferred
method of getting bits on disk.

Kayak sets compression=on by default for rpool, and can set up a
mirror for you, given a suitable list of devices in the client config:
http://omnios.omniti.com/wiki.php/Installation#Fromthenetwork

Eric

From esproul at omniti.com  Mon Mar 25 15:45:04 2013
From: esproul at omniti.com (Eric Sproul)
Date: Mon, 25 Mar 2013 15:45:04 -0400
Subject: [OmniOS-discuss] Supermicro X9SRI-F NMI
In-Reply-To: <5150A186.7040102@acm.org>
References: <5150A186.7040102@acm.org>
Message-ID: <CA+QY2RR4w6dTJvyRWt_1FaDQeFVzphZBTtz7DUVP=9dKG85qQA@mail.gmail.com>

On Mon, Mar 25, 2013 at 3:12 PM, Paul B. Henson <henson at acm.org> wrote:
> I've never actually tried this under OpenSolaris/illumos, but am assuming it
> should work more or less the same as under Solaris 10? Has anybody tested
> NMI functionality with a recent illumos and could give me at least a
> starting point that it should be working :)?

Last year when I was testing KVM on a Sandy Bridge box, I was hitting
https://github.com/joyent/illumos-kvm/issues/1 and trying to
troubleshoot via NMI.  I had the X9SRA board, which is similar to
yours.  I didn't have IPMI or a chassis button, so I was attempting to
short the appropriate pins.  I recall that I saw an NMI message on the
console, but the system did not panic.

I would go with the assumption that it will work as it did for Solaris
10, until proven otherwise. :)

Eric

From fabio at fabiorabelo.wiki.br  Mon Mar 25 15:54:28 2013
From: fabio at fabiorabelo.wiki.br (=?UTF-8?Q?F=C3=A1bio_Rabelo?=)
Date: Mon, 25 Mar 2013 16:54:28 -0300
Subject: [OmniOS-discuss] Highpoint 640 or 640L
In-Reply-To: <CA+QY2RQ2DJNwefJJJ9298F8HXLXz7PPigZW3madMyYRBPgUkdg@mail.gmail.com>
References: <CAEekY64Rs4i91AciS1wRb8y5y_tBpuwaqf5g628aBeYHJfEgrA@mail.gmail.com>
	<CA+QY2RQ2DJNwefJJJ9298F8HXLXz7PPigZW3madMyYRBPgUkdg@mail.gmail.com>
Message-ID: <CAEekY66F49a7TZQtp5WS0gf+1V+1KW2rktR3WFbvbWYykfRiug@mail.gmail.com>

2013/3/25 Eric Sproul <esproul at omniti.com>

> On Mon, Mar 25, 2013 at 3:15 PM, F?bio Rabelo <fabio at fabiorabelo.wiki.br>
> wrote:
> > Hi to all
> >
> > Someone knows if Marvel based SATA cards works ?
> >
> > http://www.highpoint-tech.com/USA_new/series_rr600-overview.htm
> >
> > Highpoint rocketraid 640L : based on Marvel 88se9235
> >
> > Highpoint rocketraid 640  : based on masrvel 88se9128
>
> I don't believe any Marvell 9xxx SATA chips have ever been supported
> in Solaris or any derivative.  An inexpensive alternative would be
> something based on SiliconImage 3124


This SI chip are SATA ll only !

My hard disks are Western Digital 4 TB sata 3 !

Are there any better option ?


F?bio Rabelo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20130325/a49bfa7b/attachment.html>

From esproul at omniti.com  Mon Mar 25 16:05:02 2013
From: esproul at omniti.com (Eric Sproul)
Date: Mon, 25 Mar 2013 16:05:02 -0400
Subject: [OmniOS-discuss] Highpoint 640 or 640L
In-Reply-To: <CAEekY66F49a7TZQtp5WS0gf+1V+1KW2rktR3WFbvbWYykfRiug@mail.gmail.com>
References: <CAEekY64Rs4i91AciS1wRb8y5y_tBpuwaqf5g628aBeYHJfEgrA@mail.gmail.com>
	<CA+QY2RQ2DJNwefJJJ9298F8HXLXz7PPigZW3madMyYRBPgUkdg@mail.gmail.com>
	<CAEekY66F49a7TZQtp5WS0gf+1V+1KW2rktR3WFbvbWYykfRiug@mail.gmail.com>
Message-ID: <CA+QY2RSyLjGFgheWfVi=A9rxXManD8akAZNqFnew5urvvzOYfg@mail.gmail.com>

Use a motherboard that has SATA-III onboard, such as recent Intel Sany
Bridge and Ivy Bridge boards.  Explore http://illumos.org/hcl/ for
SATA-III parts.

The other alternative is not to worry about SATA-III.  A spinning hard
drive can't saturate a SATA-II port as it is.

Eric

On Mon, Mar 25, 2013 at 3:54 PM, F?bio Rabelo <fabio at fabiorabelo.wiki.br> wrote:
> 2013/3/25 Eric Sproul <esproul at omniti.com>
>>
>> On Mon, Mar 25, 2013 at 3:15 PM, F?bio Rabelo <fabio at fabiorabelo.wiki.br>
>> wrote:
>> > Hi to all
>> >
>> > Someone knows if Marvel based SATA cards works ?
>> >
>> > http://www.highpoint-tech.com/USA_new/series_rr600-overview.htm
>> >
>> > Highpoint rocketraid 640L : based on Marvel 88se9235
>> >
>> > Highpoint rocketraid 640  : based on masrvel 88se9128
>>
>> I don't believe any Marvell 9xxx SATA chips have ever been supported
>> in Solaris or any derivative.  An inexpensive alternative would be
>> something based on SiliconImage 3124
>
>
> This SI chip are SATA ll only !
>
> My hard disks are Western Digital 4 TB sata 3 !
>
> Are there any better option ?
>
>
> F?bio Rabelo

From henson at acm.org  Mon Mar 25 16:58:02 2013
From: henson at acm.org (Paul B. Henson)
Date: Mon, 25 Mar 2013 13:58:02 -0700
Subject: [OmniOS-discuss] changing rpool zfs properties prior to install
In-Reply-To: <CA+QY2RR2fPZ5B7vHVGv-A-br3=ha4KETPVLN+nB667A8pF2kRw@mail.gmail.com>
References: <5150A2C4.70706@acm.org>
	<CA+QY2RR2fPZ5B7vHVGv-A-br3=ha4KETPVLN+nB667A8pF2kRw@mail.gmail.com>
Message-ID: <5150BA5A.2070802@acm.org>

On 3/25/2013 12:41 PM, Eric Sproul wrote:

> A network install using Kayak is the best way to get what you want.
> The ISO installer is the most barely-functional version we could
> tolerate shipping, because we see network installs being the preferred
> method of getting bits on disk.
>
> Kayak sets compression=on by default for rpool, and can set up a
> mirror for you, given a suitable list of devices in the client config:
> http://omnios.omniti.com/wiki.php/Installation#Fromthenetwork

I'm all over network installs for even medium-sized deployments :), but 
for the single box I'm building at the moment at home it's perhaps a 
touch more overhead than one would like ;). I see there's a page on the 
wiki talking about feeding the kayak client from a non-omnios server, 
maybe I'll take a shot at using some of my existing infrastructure at 
home to get that going. You don't happen to have a bloody equivalent to 
http://omnios.omniti.com/media/r151004.zfs.bz2 posted somewhere?

The other (slightly (meh,  considerably) more kludgy, but perhaps less 
effort required for a one off) option might be to pop into the shell 
after booting the ISO before starting the install and fiddling something 
(replace the zfs binary with a script that the detects rpool creation 
and tweaks it, start a script in the background looking for the rpool to 
show up and tweaking it when it does, ?).

Thanks much for the info.

From henson at acm.org  Mon Mar 25 17:01:34 2013
From: henson at acm.org (Paul B. Henson)
Date: Mon, 25 Mar 2013 14:01:34 -0700
Subject: [OmniOS-discuss] Supermicro X9SRI-F NMI
In-Reply-To: <CA+QY2RR4w6dTJvyRWt_1FaDQeFVzphZBTtz7DUVP=9dKG85qQA@mail.gmail.com>
References: <5150A186.7040102@acm.org>
	<CA+QY2RR4w6dTJvyRWt_1FaDQeFVzphZBTtz7DUVP=9dKG85qQA@mail.gmail.com>
Message-ID: <5150BB2E.8010702@acm.org>

On 3/25/2013 12:45 PM, Eric Sproul wrote:

> Last year when I was testing KVM on a Sandy Bridge box, I was hitting
> https://github.com/joyent/illumos-kvm/issues/1 and trying to
> troubleshoot via NMI.  I had the X9SRA board, which is similar to
> yours.  I didn't have IPMI or a chassis button, so I was attempting to
> short the appropriate pins.  I recall that I saw an NMI message on the
> console, but the system did not panic.

By default it only logs a message that it received an NMI, you need to 
add "set pcplusmp:apic_panic_on_nmi=1" to /etc/system and reboot before 
it will actually panic on one.

Thanks for the data point; I guess I'll go ahead and pop open the box 
and try shorting the jumpers directly to see if that behaves any 
differently. It will be disappointing if the ipmi interface isn't able 
to generate the same NMI functionality as the physical button, both from 
the lack of ability to do it remotely and that I'll need to get some 
physical button and wire it through a PCI slot blank or something 8-/.


From henson at acm.org  Mon Mar 25 17:04:53 2013
From: henson at acm.org (Paul B. Henson)
Date: Mon, 25 Mar 2013 14:04:53 -0700
Subject: [OmniOS-discuss] Highpoint 640 or 640L
In-Reply-To: <CA+QY2RSyLjGFgheWfVi=A9rxXManD8akAZNqFnew5urvvzOYfg@mail.gmail.com>
References: <CAEekY64Rs4i91AciS1wRb8y5y_tBpuwaqf5g628aBeYHJfEgrA@mail.gmail.com>
	<CA+QY2RQ2DJNwefJJJ9298F8HXLXz7PPigZW3madMyYRBPgUkdg@mail.gmail.com>
	<CAEekY66F49a7TZQtp5WS0gf+1V+1KW2rktR3WFbvbWYykfRiug@mail.gmail.com>
	<CA+QY2RSyLjGFgheWfVi=A9rxXManD8akAZNqFnew5urvvzOYfg@mail.gmail.com>
Message-ID: <5150BBF5.9000409@acm.org>

On 3/25/2013 1:05 PM, Eric Sproul wrote:

> The other alternative is not to worry about SATA-III.  A spinning hard
> drive can't saturate a SATA-II port as it is.

Yeah, that :).

The only reason SATA-III spinning rust exists is for marketing purposes 
and because eventually it will be cheaper to use SATA-III for everything 
rather than continuing to make separate SATA-II interfaces for hard 
disks. Unless you're planning to hook up an SSD (or one of the hybrid 
hard drives with a built-in SSD cache) there's really nothing gained 
from SATA-III.

> On Mon, Mar 25, 2013 at 3:54 PM, F?bio Rabelo <fabio at fabiorabelo.wiki.br> wrote:
>> This SI chip are SATA ll only !
>>
>> My hard disks are Western Digital 4 TB sata 3 !
>>
>> Are there any better option ?


From esproul at omniti.com  Mon Mar 25 17:57:14 2013
From: esproul at omniti.com (Eric Sproul)
Date: Mon, 25 Mar 2013 17:57:14 -0400
Subject: [OmniOS-discuss] Supermicro X9SRI-F NMI
In-Reply-To: <5150BB2E.8010702@acm.org>
References: <5150A186.7040102@acm.org>
	<CA+QY2RR4w6dTJvyRWt_1FaDQeFVzphZBTtz7DUVP=9dKG85qQA@mail.gmail.com>
	<5150BB2E.8010702@acm.org>
Message-ID: <CA+QY2RR-Vukh4YZiibUJ_po0SnCXTDfH=T4t7dLsDixK5ojkGw@mail.gmail.com>

On Mon, Mar 25, 2013 at 5:01 PM, Paul B. Henson <henson at acm.org> wrote:
> By default it only logs a message that it received an NMI, you need to add
> "set pcplusmp:apic_panic_on_nmi=1" to /etc/system and reboot before it will
> actually panic on one.

I should have been more explicit-- I did have that set, but I never
did find out why it wouldn't panic.  It might be that on Sandy Bridge
it's "apix" and not "apic" so maybe we should be setting
"apix_panic_on_nmi" instead.  I'm not even sure that tunable is
namespaced that way...

From kent at watsen.net  Mon Mar 25 19:56:58 2013
From: kent at watsen.net (Kent Watsen)
Date: Mon, 25 Mar 2013 19:56:58 -0400
Subject: [OmniOS-discuss] Can't reinstall OmniOS on CF drive
Message-ID: <5150E44A.5010101@watsen.net>


I have a machine whose root disk is a 8GB CF.  I installed OmniOS on 
this drive a few weeks ago, but it won't let me do it  again now (see 
install_log below).   The one crazy thing I see is that it's trying to 
create a volume with a size of "3230.54765606m" - which seems like a 
peculiar fraction to be passing into `zfs create`

How could it be that I could install 'stable' on this drive before and 
now, using the exact same OmniOS install CD, it won't let me? Any ideas 
how to clear or circumvent the issue?

Thanks,
Kent


2013-03-25 16:16:56,393   InstallationLogger INFO       **** START ****
PROGRESS REPORT: progress percent:0 Preparing for Installation
PROGRESS REPORT: progress percent:100 TargetDiscovery completed.
2013-03-25 16:17:30,672   InstallationLogger INFO       Going to perform 
final validation of desired target
2013-03-25 16:17:30,697   InstallationLogger.sysconfig INFO Opening 
keyboard device: /dev/kbd
2013-03-25 16:17:30,698   InstallationLogger.sysconfig INFO Detected 
following current keyboard layout: US-English
2013-03-25 16:17:30,698   InstallationLogger.sysconfig INFO console 
type: Physical Console
2013-03-25 16:17:40,684   InstallationLogger.sysconfig INFO Configuring 
NIC as: none
2013-03-25 12:17:00,022   InstallationLogger INFO       Installation 
Device Size: 7.58gbMB
2013-03-25 12:17:00,022   InstallationLogger INFO       Minimum required 
size: 2.12gb
2013-03-25 12:17:00,022   InstallationLogger INFO       Recommended 
size: 4.12gb
2013-03-25 12:17:00,023   InstallationLogger INFO       Swap type: ZVOL
2013-03-25 12:17:00,024   InstallationLogger INFO       Swap size: 3.15gb
2013-03-25 12:17:00,024   InstallationLogger INFO       Dump type: ZVOL
2013-03-25 12:17:00,024   InstallationLogger INFO       Dump size: 807.00mb
PROGRESS REPORT: progress percent:0 Preparing for Installation
PROGRESS REPORT: progress percent:100 PrepareTransfer completed.
PROGRESS REPORT: progress percent:0 Preparing for Installation
PROGRESS REPORT: progress percent:0 Preparing for Installation
PROGRESS REPORT: progress percent:0 Preparing for Installation
PROGRESS REPORT: progress percent:1 Preparing for Installation
PROGRESS REPORT: progress percent:1 Preparing for Installation
PROGRESS REPORT: progress percent:1 Preparing for Installation
PROGRESS REPORT: progress percent:2 Preparing for Installation
PROGRESS REPORT: progress percent:2 Preparing for Installation
PROGRESS REPORT: progress percent:2 Preparing for Installation
PROGRESS REPORT: progress percent:3 Preparing for Installation
PROGRESS REPORT: progress percent:3 Preparing for Installation
PROGRESS REPORT: progress percent:3 Preparing for Installation
PROGRESS REPORT: progress percent:4 Preparing for Installation
PROGRESS REPORT: progress percent:4 Preparing for Installation
PROGRESS REPORT: progress percent:4 Preparing for Installation
PROGRESS REPORT: progress percent:5 VarSharedDataset completed.
2013-03-25 12:17:07,955   InstallationLogger ERROR      cannot create 
'rpool/swap': volume size must be a multiple of volume block size
2013-03-25 12:17:07,956   InstallationLogger ERROR      Error occurred 
during execution of 'TargetInitialization' checkpoint.
Traceback (most recent call last):
   File 
"/usr/lib/python2.6/vendor-packages/solaris_install/engine/__init__.py", 
line 828, in _execute_checkpoints
     checkpoint.execute(dry_run)
   File 
"/usr/lib/python2.6/vendor-packages/solaris_install/target/instantiation.py", 
line 410, in execute
     self.create_swap()
   File 
"/usr/lib/python2.6/vendor-packages/solaris_install/target/instantiation.py", 
line 205, in create_swap
     swap.create(self.dry_run)
   File 
"/usr/lib/python2.6/vendor-packages/solaris_install/target/logical.py", 
line 723, in create
     logger=ILN, env={"LC_ALL": "C"})
   File 
"/usr/lib/python2.6/vendor-packages/solaris_install/__init__.py", line 
331, in check_call
     raise CalledProcessError(popen.returncode, args, popen)
CalledProcessError: Command '['/usr/sbin/zfs', 'create', '-p', '-V', 
'3230.54765606m', 'rpool/swap']' returned unexpected exit status 1
2013-03-25 12:17:07,970   InstallationLogger ERROR      Checkpoint 
TargetInitialization failed
2013-03-25 12:17:07,970   InstallationLogger ERROR      Command 
'['/usr/sbin/zfs', 'create', '-p', '-V', '3230.54765606m', 
'rpool/swap']' returned unexpected exit status 1
2013-03-25 12:17:08,213   InstallationLogger ERROR      Install FAILED.
Traceback (most recent call last):
   File 
"/usr/lib/python2.6/vendor-packages/solaris_install/text_install/ti_install.py", 
line 336, in perform_ti_install
     do_ti_install(install_data, screen, update_status_func)
   File 
"/usr/lib/python2.6/vendor-packages/solaris_install/text_install/ti_install.py", 
line 270, in do_ti_install
     raise ti_utils.InstallationError("Failed executing checkpoints")
InstallationError: Failed executing checkpoints
2013-03-25 12:17:16,549   InstallationLogger INFO       User quit the 
installer.
2013-03-25 12:17:16,549   InstallationLogger INFO       **** END ****


From henson at acm.org  Tue Mar 26 16:45:58 2013
From: henson at acm.org (Paul B. Henson)
Date: Tue, 26 Mar 2013 13:45:58 -0700
Subject: [OmniOS-discuss] Supermicro X9SRI-F NMI
In-Reply-To: <CA+QY2RR-Vukh4YZiibUJ_po0SnCXTDfH=T4t7dLsDixK5ojkGw@mail.gmail.com>
References: <5150A186.7040102@acm.org>
	<CA+QY2RR4w6dTJvyRWt_1FaDQeFVzphZBTtz7DUVP=9dKG85qQA@mail.gmail.com>
	<5150BB2E.8010702@acm.org>
	<CA+QY2RR-Vukh4YZiibUJ_po0SnCXTDfH=T4t7dLsDixK5ojkGw@mail.gmail.com>
Message-ID: <51520906.1000005@acm.org>

On 3/25/2013 2:57 PM, Eric Sproul wrote:

> I should have been more explicit-- I did have that set, but I never
> did find out why it wouldn't panic.

Oh, my bad; I misunderstood. I popped open the case when I got home 
yesterday and tried shorting the physical NMI header, with the exact 
same results ? the box just wedged hard. I also booted a linux livedvd, 
with the exact same outcome for both IPMI initiated and physical jumper 
shorted NMI's, the OS just wedged :(, so it doesn't seem an illumos 
specific problem.

I guess there's either a design issue with NMI generation on this 
specific board model, I've got a bum board, or something about my 
specific configuration is messing it up. Just for fun I'll try checking 
with supermicro support, but most likely I'll have to write off NMI 
crash dumps :(, unless something else looks wrong as I get further into 
the configuration process I don't think I want to try and RMA the board 
just for this.


From carlopmart at gmail.com  Wed Mar 27 08:22:21 2013
From: carlopmart at gmail.com (C. L. Martinez)
Date: Wed, 27 Mar 2013 12:22:21 +0000
Subject: [OmniOS-discuss] OmniOS as a kvm guest
Message-ID: <CAEjQA5J=cdxuXht+-79TKTaS7F3rOVMSx1aoU6NUEp0WAFuYGw@mail.gmail.com>

Hi all,

 Is it possible to run OmniOS as kvm guest under CentOS 6.4 x86_64
host?? Can I use virtio devices for this OmniOS guest??

Thanks.

From esproul at omniti.com  Wed Mar 27 09:40:55 2013
From: esproul at omniti.com (Eric Sproul)
Date: Wed, 27 Mar 2013 09:40:55 -0400
Subject: [OmniOS-discuss] OmniOS as a kvm guest
In-Reply-To: <CAEjQA5J=cdxuXht+-79TKTaS7F3rOVMSx1aoU6NUEp0WAFuYGw@mail.gmail.com>
References: <CAEjQA5J=cdxuXht+-79TKTaS7F3rOVMSx1aoU6NUEp0WAFuYGw@mail.gmail.com>
Message-ID: <CA+QY2RTX=VYDJC1LQN1Qy1jJUSQW_uqZpykc1F905=czkGspGA@mail.gmail.com>

Yes, OmniOS can run as a KVM guest.  There is limited virtio support
(vioblk only), and only in the unstable release at this time.  It
integrated too late for the current stable release to pick it up, but
it will be included in the next stable due out next month.

virtio-net support is being worked on by the illumos community, but
has not yet integrated.

Points of interest:
https://www.illumos.org/issues/3644
http://cr.illumos.org/~webrev/int0dh/virtio-net/

On Wed, Mar 27, 2013 at 8:22 AM, C. L. Martinez <carlopmart at gmail.com> wrote:
> Hi all,
>
>  Is it possible to run OmniOS as kvm guest under CentOS 6.4 x86_64
> host?? Can I use virtio devices for this OmniOS guest??
>
> Thanks.
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss

From esproul at omniti.com  Wed Mar 27 13:03:47 2013
From: esproul at omniti.com (Eric Sproul)
Date: Wed, 27 Mar 2013 13:03:47 -0400
Subject: [OmniOS-discuss] OmniOS as a kvm guest
In-Reply-To: <CAEjQA5JjjwbK+a0Jb0_=Hu5O8f5AsoNjfYN=3mA_zgdVtTOTtQ@mail.gmail.com>
References: <CAEjQA5J=cdxuXht+-79TKTaS7F3rOVMSx1aoU6NUEp0WAFuYGw@mail.gmail.com>
	<CA+QY2RTX=VYDJC1LQN1Qy1jJUSQW_uqZpykc1F905=czkGspGA@mail.gmail.com>
	<CAEjQA5JjjwbK+a0Jb0_=Hu5O8f5AsoNjfYN=3mA_zgdVtTOTtQ@mail.gmail.com>
Message-ID: <CA+QY2RQ1Cnkic_u+YGwMkJ6XqtHNCj2b6FdTtNTkh3=E=P4AYw@mail.gmail.com>

I don't know specifics about the virtio stuff.  You could hit Google
with that question and/or #illumos on IRC.  Whatever illumos
integrates with respect to virt* will eventually end up in OmniOS.

On Wed, Mar 27, 2013 at 10:50 AM, C. L. Martinez <carlopmart at gmail.com> wrote:
> On Wed, Mar 27, 2013 at 1:40 PM, Eric Sproul <esproul at omniti.com> wrote:
>> Yes, OmniOS can run as a KVM guest.  There is limited virtio support
>> (vioblk only), and only in the unstable release at this time.  It
>> integrated too late for the current stable release to pick it up, but
>> it will be included in the next stable due out next month.
>>
>> virtio-net support is being worked on by the illumos community, but
>> has not yet integrated.
>>
>> Points of interest:
>> https://www.illumos.org/issues/3644
>> http://cr.illumos.org/~webrev/int0dh/virtio-net/
>>
>
> Thanks Eric, but memory balloon driver will be integrated??

From kent at watsen.net  Thu Mar 28 12:33:49 2013
From: kent at watsen.net (Kent Watsen)
Date: Thu, 28 Mar 2013 12:33:49 -0400
Subject: [OmniOS-discuss] Can't reinstall OmniOS on CF drive
In-Reply-To: <5150E44A.5010101@watsen.net>
References: <5150E44A.5010101@watsen.net>
Message-ID: <515470ED.7070708@watsen.net>


I'm stumped.   Here's everything I've tried so far:

1. installing into a partition instead of "whole disk".  Works fine in 
VirtualBox but fails on the real disk

2. resetting the drive's geometry.  Had to use Linux to do this, but 
OmniOS reverted it back to its original values

3. manually creating the rpool/swap volume.  After the failure, I escape 
to shell.  Sure enough, "3230.54765606m" fails but "3230m" succeeds (too 
bad I can't tell the installer to use this value instead)

4. traced the installer's code per the stack trace.  Honestly, I wish 
instantiation.py wouldn't try to create swap at all - being a compact 
flash disk, I'm going to move swap (and dump, etc) to my raidz2-based 
pool afterwards anyways...

5. installed OpenIndiana.  Yes, it installed fine.  After it installed, 
I escaped to shell and saw it had chosen different sizes for the various 
ZFS volumes.  Then I tried installing OmniOS again, hoping that 
something OI had done would stick, but no dice

Why won't OmniOS install on this CF disk again?  - I'm using the same 
OmniOS install CD as before.  Could a BIOS setting make a difference 
(it's currently set to LBA)?   The only other thing I can think of is 
that the CF disk now has some blocks marked unusable.  But SMART info 
says that's not the case and I compared it to another identical 8GB CF 
disk and they're the same (two disks both marking the same number of 
blocks bad seems improbable)

Right now, the only way I can imagine getting OmniOS installed is by 
hacking the installer itself.  Actually, I tried already but file was 
read-only.  Didn't investigate enough to see if I could change that.  
Worst case, I suppose I could mount the ISO, twiddle some bits, and burn 
another CD, but I'm hoping someone has a better idea...anyone?

Thanks,
Kent



On 3/25/13 7:56 PM, Kent Watsen wrote:
>
> I have a machine whose root disk is a 8GB CF.  I installed OmniOS on 
> this drive a few weeks ago, but it won't let me do it  again now (see 
> install_log below).   The one crazy thing I see is that it's trying to 
> create a volume with a size of "3230.54765606m" - which seems like a 
> peculiar fraction to be passing into `zfs create`
>
> How could it be that I could install 'stable' on this drive before and 
> now, using the exact same OmniOS install CD, it won't let me? Any 
> ideas how to clear or circumvent the issue?
>
> Thanks,
> Kent
>
>
> 2013-03-25 16:16:56,393   InstallationLogger INFO       **** START ****
> PROGRESS REPORT: progress percent:0 Preparing for Installation
> PROGRESS REPORT: progress percent:100 TargetDiscovery completed.
> 2013-03-25 16:17:30,672   InstallationLogger INFO       Going to 
> perform final validation of desired target
> 2013-03-25 16:17:30,697   InstallationLogger.sysconfig INFO Opening 
> keyboard device: /dev/kbd
> 2013-03-25 16:17:30,698   InstallationLogger.sysconfig INFO Detected 
> following current keyboard layout: US-English
> 2013-03-25 16:17:30,698   InstallationLogger.sysconfig INFO console 
> type: Physical Console
> 2013-03-25 16:17:40,684   InstallationLogger.sysconfig INFO 
> Configuring NIC as: none
> 2013-03-25 12:17:00,022   InstallationLogger INFO Installation Device 
> Size: 7.58gbMB
> 2013-03-25 12:17:00,022   InstallationLogger INFO       Minimum 
> required size: 2.12gb
> 2013-03-25 12:17:00,022   InstallationLogger INFO Recommended size: 
> 4.12gb
> 2013-03-25 12:17:00,023   InstallationLogger INFO       Swap type: ZVOL
> 2013-03-25 12:17:00,024   InstallationLogger INFO       Swap size: 3.15gb
> 2013-03-25 12:17:00,024   InstallationLogger INFO       Dump type: ZVOL
> 2013-03-25 12:17:00,024   InstallationLogger INFO       Dump size: 
> 807.00mb
> PROGRESS REPORT: progress percent:0 Preparing for Installation
> PROGRESS REPORT: progress percent:100 PrepareTransfer completed.
> PROGRESS REPORT: progress percent:0 Preparing for Installation
> PROGRESS REPORT: progress percent:0 Preparing for Installation
> PROGRESS REPORT: progress percent:0 Preparing for Installation
> PROGRESS REPORT: progress percent:1 Preparing for Installation
> PROGRESS REPORT: progress percent:1 Preparing for Installation
> PROGRESS REPORT: progress percent:1 Preparing for Installation
> PROGRESS REPORT: progress percent:2 Preparing for Installation
> PROGRESS REPORT: progress percent:2 Preparing for Installation
> PROGRESS REPORT: progress percent:2 Preparing for Installation
> PROGRESS REPORT: progress percent:3 Preparing for Installation
> PROGRESS REPORT: progress percent:3 Preparing for Installation
> PROGRESS REPORT: progress percent:3 Preparing for Installation
> PROGRESS REPORT: progress percent:4 Preparing for Installation
> PROGRESS REPORT: progress percent:4 Preparing for Installation
> PROGRESS REPORT: progress percent:4 Preparing for Installation
> PROGRESS REPORT: progress percent:5 VarSharedDataset completed.
> 2013-03-25 12:17:07,955   InstallationLogger ERROR      cannot create 
> 'rpool/swap': volume size must be a multiple of volume block size
> 2013-03-25 12:17:07,956   InstallationLogger ERROR      Error occurred 
> during execution of 'TargetInitialization' checkpoint.
> Traceback (most recent call last):
>   File 
> "/usr/lib/python2.6/vendor-packages/solaris_install/engine/__init__.py", 
> line 828, in _execute_checkpoints
>     checkpoint.execute(dry_run)
>   File 
> "/usr/lib/python2.6/vendor-packages/solaris_install/target/instantiation.py", 
> line 410, in execute
>     self.create_swap()
>   File 
> "/usr/lib/python2.6/vendor-packages/solaris_install/target/instantiation.py", 
> line 205, in create_swap
>     swap.create(self.dry_run)
>   File 
> "/usr/lib/python2.6/vendor-packages/solaris_install/target/logical.py", line 
> 723, in create
>     logger=ILN, env={"LC_ALL": "C"})
>   File 
> "/usr/lib/python2.6/vendor-packages/solaris_install/__init__.py", line 
> 331, in check_call
>     raise CalledProcessError(popen.returncode, args, popen)
> CalledProcessError: Command '['/usr/sbin/zfs', 'create', '-p', '-V', 
> '3230.54765606m', 'rpool/swap']' returned unexpected exit status 1
> 2013-03-25 12:17:07,970   InstallationLogger ERROR      Checkpoint 
> TargetInitialization failed
> 2013-03-25 12:17:07,970   InstallationLogger ERROR      Command 
> '['/usr/sbin/zfs', 'create', '-p', '-V', '3230.54765606m', 
> 'rpool/swap']' returned unexpected exit status 1
> 2013-03-25 12:17:08,213   InstallationLogger ERROR      Install FAILED.
> Traceback (most recent call last):
>   File 
> "/usr/lib/python2.6/vendor-packages/solaris_install/text_install/ti_install.py", 
> line 336, in perform_ti_install
>     do_ti_install(install_data, screen, update_status_func)
>   File 
> "/usr/lib/python2.6/vendor-packages/solaris_install/text_install/ti_install.py", 
> line 270, in do_ti_install
>     raise ti_utils.InstallationError("Failed executing checkpoints")
> InstallationError: Failed executing checkpoints
> 2013-03-25 12:17:16,549   InstallationLogger INFO       User quit the 
> installer.
> 2013-03-25 12:17:16,549   InstallationLogger INFO       **** END ****
>
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss


From jesus at omniti.com  Thu Mar 28 13:12:17 2013
From: jesus at omniti.com (Theo Schlossnagle)
Date: Thu, 28 Mar 2013 13:12:17 -0400
Subject: [OmniOS-discuss] Can't reinstall OmniOS on CF drive
In-Reply-To: <515470ED.7070708@watsen.net>
References: <5150E44A.5010101@watsen.net>
	<515470ED.7070708@watsen.net>
Message-ID: <CACLsApst20YVufsboceFPCCx23uvKxZTfWgp-vVdkd4SJLuEqg@mail.gmail.com>

Can you please try using Kayak? It's a much more flexible install tool.

On Thu, Mar 28, 2013 at 12:33 PM, Kent Watsen <kent at watsen.net> wrote:

>
> I'm stumped.   Here's everything I've tried so far:
>
> 1. installing into a partition instead of "whole disk".  Works fine in
> VirtualBox but fails on the real disk
>
> 2. resetting the drive's geometry.  Had to use Linux to do this, but
> OmniOS reverted it back to its original values
>
> 3. manually creating the rpool/swap volume.  After the failure, I escape
> to shell.  Sure enough, "3230.54765606m" fails but "3230m" succeeds (too
> bad I can't tell the installer to use this value instead)
>
> 4. traced the installer's code per the stack trace.  Honestly, I wish
> instantiation.py wouldn't try to create swap at all - being a compact flash
> disk, I'm going to move swap (and dump, etc) to my raidz2-based pool
> afterwards anyways...
>
> 5. installed OpenIndiana.  Yes, it installed fine.  After it installed, I
> escaped to shell and saw it had chosen different sizes for the various ZFS
> volumes.  Then I tried installing OmniOS again, hoping that something OI
> had done would stick, but no dice
>
> Why won't OmniOS install on this CF disk again?  - I'm using the same
> OmniOS install CD as before.  Could a BIOS setting make a difference (it's
> currently set to LBA)?   The only other thing I can think of is that the CF
> disk now has some blocks marked unusable.  But SMART info says that's not
> the case and I compared it to another identical 8GB CF disk and they're the
> same (two disks both marking the same number of blocks bad seems improbable)
>
> Right now, the only way I can imagine getting OmniOS installed is by
> hacking the installer itself.  Actually, I tried already but file was
> read-only.  Didn't investigate enough to see if I could change that.  Worst
> case, I suppose I could mount the ISO, twiddle some bits, and burn another
> CD, but I'm hoping someone has a better idea...anyone?
>
> Thanks,
> Kent
>
>
>
>
> On 3/25/13 7:56 PM, Kent Watsen wrote:
>
>>
>> I have a machine whose root disk is a 8GB CF.  I installed OmniOS on this
>> drive a few weeks ago, but it won't let me do it  again now (see
>> install_log below).   The one crazy thing I see is that it's trying to
>> create a volume with a size of "3230.54765606m" - which seems like a
>> peculiar fraction to be passing into `zfs create`
>>
>> How could it be that I could install 'stable' on this drive before and
>> now, using the exact same OmniOS install CD, it won't let me? Any ideas how
>> to clear or circumvent the issue?
>>
>> Thanks,
>> Kent
>>
>>
>> 2013-03-25 16:16:56,393   InstallationLogger INFO       **** START ****
>> PROGRESS REPORT: progress percent:0 Preparing for Installation
>> PROGRESS REPORT: progress percent:100 TargetDiscovery completed.
>> 2013-03-25 16:17:30,672   InstallationLogger INFO       Going to perform
>> final validation of desired target
>> 2013-03-25 16:17:30,697   InstallationLogger.sysconfig INFO Opening
>> keyboard device: /dev/kbd
>> 2013-03-25 16:17:30,698   InstallationLogger.sysconfig INFO Detected
>> following current keyboard layout: US-English
>> 2013-03-25 16:17:30,698   InstallationLogger.sysconfig INFO console type:
>> Physical Console
>> 2013-03-25 16:17:40,684   InstallationLogger.sysconfig INFO Configuring
>> NIC as: none
>> 2013-03-25 12:17:00,022   InstallationLogger INFO Installation Device
>> Size: 7.58gbMB
>> 2013-03-25 12:17:00,022   InstallationLogger INFO       Minimum required
>> size: 2.12gb
>> 2013-03-25 12:17:00,022   InstallationLogger INFO Recommended size: 4.12gb
>> 2013-03-25 12:17:00,023   InstallationLogger INFO       Swap type: ZVOL
>> 2013-03-25 12:17:00,024   InstallationLogger INFO       Swap size: 3.15gb
>> 2013-03-25 12:17:00,024   InstallationLogger INFO       Dump type: ZVOL
>> 2013-03-25 12:17:00,024   InstallationLogger INFO       Dump size:
>> 807.00mb
>> PROGRESS REPORT: progress percent:0 Preparing for Installation
>> PROGRESS REPORT: progress percent:100 PrepareTransfer completed.
>> PROGRESS REPORT: progress percent:0 Preparing for Installation
>> PROGRESS REPORT: progress percent:0 Preparing for Installation
>> PROGRESS REPORT: progress percent:0 Preparing for Installation
>> PROGRESS REPORT: progress percent:1 Preparing for Installation
>> PROGRESS REPORT: progress percent:1 Preparing for Installation
>> PROGRESS REPORT: progress percent:1 Preparing for Installation
>> PROGRESS REPORT: progress percent:2 Preparing for Installation
>> PROGRESS REPORT: progress percent:2 Preparing for Installation
>> PROGRESS REPORT: progress percent:2 Preparing for Installation
>> PROGRESS REPORT: progress percent:3 Preparing for Installation
>> PROGRESS REPORT: progress percent:3 Preparing for Installation
>> PROGRESS REPORT: progress percent:3 Preparing for Installation
>> PROGRESS REPORT: progress percent:4 Preparing for Installation
>> PROGRESS REPORT: progress percent:4 Preparing for Installation
>> PROGRESS REPORT: progress percent:4 Preparing for Installation
>> PROGRESS REPORT: progress percent:5 VarSharedDataset completed.
>> 2013-03-25 12:17:07,955   InstallationLogger ERROR      cannot create
>> 'rpool/swap': volume size must be a multiple of volume block size
>> 2013-03-25 12:17:07,956   InstallationLogger ERROR      Error occurred
>> during execution of 'TargetInitialization' checkpoint.
>> Traceback (most recent call last):
>>   File "/usr/lib/python2.6/vendor-**packages/solaris_install/**engine/__init__.py",
>> line 828, in _execute_checkpoints
>>     checkpoint.execute(dry_run)
>>   File "/usr/lib/python2.6/vendor-**packages/solaris_install/**target/instantiation.py",
>> line 410, in execute
>>     self.create_swap()
>>   File "/usr/lib/python2.6/vendor-**packages/solaris_install/**target/instantiation.py",
>> line 205, in create_swap
>>     swap.create(self.dry_run)
>>   File "/usr/lib/python2.6/vendor-**packages/solaris_install/**target/logical.py",
>> line 723, in create
>>     logger=ILN, env={"LC_ALL": "C"})
>>   File "/usr/lib/python2.6/vendor-**packages/solaris_install/__**init__.py",
>> line 331, in check_call
>>     raise CalledProcessError(popen.**returncode, args, popen)
>> CalledProcessError: Command '['/usr/sbin/zfs', 'create', '-p', '-V',
>> '3230.54765606m', 'rpool/swap']' returned unexpected exit status 1
>> 2013-03-25 12:17:07,970   InstallationLogger ERROR      Checkpoint
>> TargetInitialization failed
>> 2013-03-25 12:17:07,970   InstallationLogger ERROR      Command
>> '['/usr/sbin/zfs', 'create', '-p', '-V', '3230.54765606m', 'rpool/swap']'
>> returned unexpected exit status 1
>> 2013-03-25 12:17:08,213   InstallationLogger ERROR      Install FAILED.
>> Traceback (most recent call last):
>>   File "/usr/lib/python2.6/vendor-**packages/solaris_install/text_**install/ti_install.py",
>> line 336, in perform_ti_install
>>     do_ti_install(install_data, screen, update_status_func)
>>   File "/usr/lib/python2.6/vendor-**packages/solaris_install/text_**install/ti_install.py",
>> line 270, in do_ti_install
>>     raise ti_utils.InstallationError("**Failed executing checkpoints")
>> InstallationError: Failed executing checkpoints
>> 2013-03-25 12:17:16,549   InstallationLogger INFO       User quit the
>> installer.
>> 2013-03-25 12:17:16,549   InstallationLogger INFO       **** END ****
>>
>> ______________________________**_________________
>> OmniOS-discuss mailing list
>> OmniOS-discuss at lists.omniti.**com <OmniOS-discuss at lists.omniti.com>
>> http://lists.omniti.com/**mailman/listinfo/omnios-**discuss<http://lists.omniti.com/mailman/listinfo/omnios-discuss>
>>
>
> ______________________________**_________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.**com <OmniOS-discuss at lists.omniti.com>
> http://lists.omniti.com/**mailman/listinfo/omnios-**discuss<http://lists.omniti.com/mailman/listinfo/omnios-discuss>
>



-- 

Theo Schlossnagle

http://omniti.com/is/theo-schlossnagle
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20130328/7c309c2d/attachment.html>

From gate03 at landcroft.co.uk  Thu Mar 28 19:07:38 2013
From: gate03 at landcroft.co.uk (Michael Mounteney)
Date: Fri, 29 Mar 2013 10:07:38 +1100
Subject: [OmniOS-discuss] Server hang -- hardware or software
Message-ID: <20130329100738.37e80d4b@dickless.landy.net>

Sun X2250 running bloody 2013_02_08.  Has an Intel 4 way GiB ethernet
card.

It hung hard yesterday and I wondered if anyone could advise on what
might be going on, as google throws up nothing relevant.  This message
appears on the console:

arl_dlpi_pending unsolicited ack for DL_UNITDATA_REQ on
e1000g2received unsolicited ack for DL_UNITDATA_REQ on e1000g3
received unsolicited ack for DL_UNITDATA_REQ on e1000g3
arl_dlpi_pending unsolicited ack for DL_UNITDATA_REQ on
e1000g1arl_dlpi_pending unsolicited ack for DL_UNITDATA_REQ on
e1000g2arl_dlpi_pending unsolicited ack for DL_UNITDATA_REQ on e1000g1

There is a screenshot at http://www.landcroft.co.uk/omniscreen.jpeg --
the hang happened several hours after the message from vboxdrv at
Mar 28 05:12:44 --- I know because I was sshing in at the time.

e1000g1 is one of the two built-in ethernet ports and is connected
to a Belkin hub/switch.  e1000g2 and e1000g3 are on the Intel ethernet
card and are connected directly via crossover CAT6 to two different
computers.  e1000g4 and e1000g5 are not used.  e1000g0 is connected to
a cable modem.

It seems significant that the three ports appearing in the message are
the three that are connected to computers on the local network here. I
wonder if maybe a power spike caused it;  although the whole system is
protected by surge protectors.

The hang was hard --- I had to press and hold the power button on the
machine to power cycle, so even ACPI wasn't working.

The question to this list is:  do I blame hardware and look at getting
a replacement machine, or could the OS have caused this ?

Thanks in expectation of the list's assistance.

Michael.

From illukas at inlink.ee  Fri Mar 29 02:47:23 2013
From: illukas at inlink.ee (illukas at inlink.ee)
Date: Fri, 29 Mar 2013 08:47:23 +0200
Subject: [OmniOS-discuss] Can't reinstall OmniOS on CF drive
In-Reply-To: <CACLsApst20YVufsboceFPCCx23uvKxZTfWgp-vVdkd4SJLuEqg@mail.gmail.com>
References: <5150E44A.5010101@watsen.net> <515470ED.7070708@watsen.net>
	<CACLsApst20YVufsboceFPCCx23uvKxZTfWgp-vVdkd4SJLuEqg@mail.gmail.com>
Message-ID: <515538FB.3030602@inlink.ee>


I have similar problem installing into memory stick (tried 4 gb & 12gb)

Installer tries to create rpool/swap 732,606249809m, but fails with 
error: volume size must be multiple of volume block size
Tried both stable & bloody

http://imageshack.us/photo/my-images/195/screenshotfrom201303281.png/
http://imageshack.us/photo/my-images/221/screenshotfrom201303281.png/

Regards
illukas



On 28.03.2013 19:12, Theo Schlossnagle wrote:
> Can you please try using Kayak? It's a much more flexible install tool.
>
> On Thu, Mar 28, 2013 at 12:33 PM, Kent Watsen <kent at watsen.net 
> <mailto:kent at watsen.net>> wrote:
>
>
>     I'm stumped.   Here's everything I've tried so far:
>
>     1. installing into a partition instead of "whole disk".  Works
>     fine in VirtualBox but fails on the real disk
>
>     2. resetting the drive's geometry.  Had to use Linux to do this,
>     but OmniOS reverted it back to its original values
>
>     3. manually creating the rpool/swap volume.  After the failure, I
>     escape to shell.  Sure enough, "3230.54765606m" fails but "3230m"
>     succeeds (too bad I can't tell the installer to use this value
>     instead)
>
>     4. traced the installer's code per the stack trace.  Honestly, I
>     wish instantiation.py wouldn't try to create swap at all - being a
>     compact flash disk, I'm going to move swap (and dump, etc) to my
>     raidz2-based pool afterwards anyways...
>
>     5. installed OpenIndiana.  Yes, it installed fine.  After it
>     installed, I escaped to shell and saw it had chosen different
>     sizes for the various ZFS volumes.  Then I tried installing OmniOS
>     again, hoping that something OI had done would stick, but no dice
>
>     Why won't OmniOS install on this CF disk again?  - I'm using the
>     same OmniOS install CD as before.  Could a BIOS setting make a
>     difference (it's currently set to LBA)?   The only other thing I
>     can think of is that the CF disk now has some blocks marked
>     unusable.  But SMART info says that's not the case and I compared
>     it to another identical 8GB CF disk and they're the same (two
>     disks both marking the same number of blocks bad seems improbable)
>
>     Right now, the only way I can imagine getting OmniOS installed is
>     by hacking the installer itself.  Actually, I tried already but
>     file was read-only.  Didn't investigate enough to see if I could
>     change that.  Worst case, I suppose I could mount the ISO, twiddle
>     some bits, and burn another CD, but I'm hoping someone has a
>     better idea...anyone?
>
>     Thanks,
>     Kent
>
>
>
>
>     On 3/25/13 7:56 PM, Kent Watsen wrote:
>
>
>         I have a machine whose root disk is a 8GB CF.  I installed
>         OmniOS on this drive a few weeks ago, but it won't let me do
>         it  again now (see install_log below). The one crazy thing I
>         see is that it's trying to create a volume with a size of
>         "3230.54765606m" - which seems like a peculiar fraction to be
>         passing into `zfs create`
>
>         How could it be that I could install 'stable' on this drive
>         before and now, using the exact same OmniOS install CD, it
>         won't let me? Any ideas how to clear or circumvent the issue?
>
>         Thanks,
>         Kent
>
>
>         2013-03-25 16:16:56,393   InstallationLogger INFO **** START ****
>         PROGRESS REPORT: progress percent:0 Preparing for Installation
>         PROGRESS REPORT: progress percent:100 TargetDiscovery completed.
>         2013-03-25 16:17:30,672   InstallationLogger INFO Going to
>         perform final validation of desired target
>         2013-03-25 16:17:30,697   InstallationLogger.sysconfig INFO
>         Opening keyboard device: /dev/kbd
>         2013-03-25 16:17:30,698   InstallationLogger.sysconfig INFO
>         Detected following current keyboard layout: US-English
>         2013-03-25 16:17:30,698   InstallationLogger.sysconfig INFO
>         console type: Physical Console
>         2013-03-25 16:17:40,684   InstallationLogger.sysconfig INFO
>         Configuring NIC as: none
>         2013-03-25 12:17:00,022   InstallationLogger INFO Installation
>         Device Size: 7.58gbMB
>         2013-03-25 12:17:00,022   InstallationLogger INFO Minimum
>         required size: 2.12gb
>         2013-03-25 12:17:00,022   InstallationLogger INFO Recommended
>         size: 4.12gb
>         2013-03-25 12:17:00,023   InstallationLogger INFO Swap type: ZVOL
>         2013-03-25 12:17:00,024   InstallationLogger INFO Swap size:
>         3.15gb
>         2013-03-25 12:17:00,024   InstallationLogger INFO Dump type: ZVOL
>         2013-03-25 12:17:00,024   InstallationLogger INFO Dump size:
>         807.00mb
>         PROGRESS REPORT: progress percent:0 Preparing for Installation
>         PROGRESS REPORT: progress percent:100 PrepareTransfer completed.
>         PROGRESS REPORT: progress percent:0 Preparing for Installation
>         PROGRESS REPORT: progress percent:0 Preparing for Installation
>         PROGRESS REPORT: progress percent:0 Preparing for Installation
>         PROGRESS REPORT: progress percent:1 Preparing for Installation
>         PROGRESS REPORT: progress percent:1 Preparing for Installation
>         PROGRESS REPORT: progress percent:1 Preparing for Installation
>         PROGRESS REPORT: progress percent:2 Preparing for Installation
>         PROGRESS REPORT: progress percent:2 Preparing for Installation
>         PROGRESS REPORT: progress percent:2 Preparing for Installation
>         PROGRESS REPORT: progress percent:3 Preparing for Installation
>         PROGRESS REPORT: progress percent:3 Preparing for Installation
>         PROGRESS REPORT: progress percent:3 Preparing for Installation
>         PROGRESS REPORT: progress percent:4 Preparing for Installation
>         PROGRESS REPORT: progress percent:4 Preparing for Installation
>         PROGRESS REPORT: progress percent:4 Preparing for Installation
>         PROGRESS REPORT: progress percent:5 VarSharedDataset completed.
>         2013-03-25 12:17:07,955   InstallationLogger ERROR  cannot
>         create 'rpool/swap': volume size must be a multiple of volume
>         block size
>         2013-03-25 12:17:07,956   InstallationLogger ERROR  Error
>         occurred during execution of 'TargetInitialization' checkpoint.
>         Traceback (most recent call last):
>           File
>         "/usr/lib/python2.6/vendor-packages/solaris_install/engine/__init__.py",
>         line 828, in _execute_checkpoints
>             checkpoint.execute(dry_run)
>           File
>         "/usr/lib/python2.6/vendor-packages/solaris_install/target/instantiation.py",
>         line 410, in execute
>             self.create_swap()
>           File
>         "/usr/lib/python2.6/vendor-packages/solaris_install/target/instantiation.py",
>         line 205, in create_swap
>             swap.create(self.dry_run)
>           File
>         "/usr/lib/python2.6/vendor-packages/solaris_install/target/logical.py",
>         line 723, in create
>             logger=ILN, env={"LC_ALL": "C"})
>           File
>         "/usr/lib/python2.6/vendor-packages/solaris_install/__init__.py",
>         line 331, in check_call
>             raise CalledProcessError(popen.returncode, args, popen)
>         CalledProcessError: Command '['/usr/sbin/zfs', 'create', '-p',
>         '-V', '3230.54765606m', 'rpool/swap']' returned unexpected
>         exit status 1
>         2013-03-25 12:17:07,970   InstallationLogger ERROR  Checkpoint
>         TargetInitialization failed
>         2013-03-25 12:17:07,970   InstallationLogger ERROR  Command
>         '['/usr/sbin/zfs', 'create', '-p', '-V', '3230.54765606m',
>         'rpool/swap']' returned unexpected exit status 1
>         2013-03-25 12:17:08,213   InstallationLogger ERROR  Install
>         FAILED.
>         Traceback (most recent call last):
>           File
>         "/usr/lib/python2.6/vendor-packages/solaris_install/text_install/ti_install.py",
>         line 336, in perform_ti_install
>             do_ti_install(install_data, screen, update_status_func)
>           File
>         "/usr/lib/python2.6/vendor-packages/solaris_install/text_install/ti_install.py",
>         line 270, in do_ti_install
>             raise ti_utils.InstallationError("Failed executing
>         checkpoints")
>         InstallationError: Failed executing checkpoints
>         2013-03-25 12:17:16,549   InstallationLogger INFO User quit
>         the installer.
>         2013-03-25 12:17:16,549   InstallationLogger INFO **** END ****
>
>         _______________________________________________
>         OmniOS-discuss mailing list
>         OmniOS-discuss at lists.omniti.com
>         <mailto:OmniOS-discuss at lists.omniti.com>
>         http://lists.omniti.com/mailman/listinfo/omnios-discuss
>
>
>     _______________________________________________
>     OmniOS-discuss mailing list
>     OmniOS-discuss at lists.omniti.com
>     <mailto:OmniOS-discuss at lists.omniti.com>
>     http://lists.omniti.com/mailman/listinfo/omnios-discuss
>
>
>
>
> -- 
>
> Theo Schlossnagle
>
> http://omniti.com/is/theo-schlossnagle
>
>
>
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20130329/581b5ad6/attachment.html>

From kent at watsen.net  Fri Mar 29 11:32:50 2013
From: kent at watsen.net (Kent Watsen)
Date: Fri, 29 Mar 2013 11:32:50 -0400
Subject: [OmniOS-discuss] Can't reinstall OmniOS on CF drive
In-Reply-To: <515538FB.3030602@inlink.ee>
References: <5150E44A.5010101@watsen.net> <515470ED.7070708@watsen.net>
	<CACLsApst20YVufsboceFPCCx23uvKxZTfWgp-vVdkd4SJLuEqg@mail.gmail.com>
	<515538FB.3030602@inlink.ee>
Message-ID: <5155B422.5070606@watsen.net>

An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20130329/7fac83c2/attachment.html>

From esproul at omniti.com  Fri Mar 29 13:14:30 2013
From: esproul at omniti.com (Eric Sproul)
Date: Fri, 29 Mar 2013 13:14:30 -0400
Subject: [OmniOS-discuss] Can't reinstall OmniOS on CF drive
In-Reply-To: <5155B422.5070606@watsen.net>
References: <5150E44A.5010101@watsen.net> <515470ED.7070708@watsen.net>
	<CACLsApst20YVufsboceFPCCx23uvKxZTfWgp-vVdkd4SJLuEqg@mail.gmail.com>
	<515538FB.3030602@inlink.ee> <5155B422.5070606@watsen.net>
Message-ID: <CA+QY2RTrEzWbHJK3Tkqc3hTghD9HPDeLM6=K67J1RD0y6GLN_A@mail.gmail.com>

On Fri, Mar 29, 2013 at 11:32 AM, Kent Watsen <kent at watsen.net> wrote:
> I've started to try the Kayak suggestion but have so far failed - the first
> laptop didn't have enough memory (it had 127MB, no idea what's needed)

127MB is almost certainly not enough.

> on the second laptop (a T400), OmniOS couldn't recognize its network
> interface - not good so a machine that's suppose to act as a server ;)

Laptops aren't the target platform.  OmniOS is aimed at servers, and
that means server-class hardware.  Luckily there is often sufficient
overlap in hardware support that things like desktops and laptops
generally work, but YMMV.

> The crazy thing is, I have no idea how flexible the Kayak installer is - I
> read that it has ZFS compression on by default, but what is it going to do
> for helping me install on this CF?

Putting aside the fact that CF seems a poor choice for an OS install
(slow, outdated IDE interface, poor random I/O performance), Kayak
puts some practical bounds on swap and dump volumes, and just won't
create them if the rpool is too small.

Nevertheless, I'm curious what Kayak would do with your device.  The
MakeSwapDump() function
(http://omnios.omniti.com/file.php/core/kayak/disk_help.sh#l128) is
where the calculation happens.  Kayak tries to make each of the swap
and dump volumes equal to 25% of physical memory, with a minimum of
1GB.  It then tries to see whether, with at least 2GB of swap/dump
reservations, there would still be a minimum of 10G free on the rpool
for the OS install and future updates.  Right there, we fail, and will
not make either swap or dump volumes on your 8G CF card.  The install
would proceed without them.

Eric

From kent at watsen.net  Sat Mar 30 15:51:16 2013
From: kent at watsen.net (Kent Watsen)
Date: Sat, 30 Mar 2013 15:51:16 -0400
Subject: [OmniOS-discuss] Can't reinstall OmniOS on CF drive
In-Reply-To: <CA+QY2RTrEzWbHJK3Tkqc3hTghD9HPDeLM6=K67J1RD0y6GLN_A@mail.gmail.com>
References: <5150E44A.5010101@watsen.net> <515470ED.7070708@watsen.net>
	<CACLsApst20YVufsboceFPCCx23uvKxZTfWgp-vVdkd4SJLuEqg@mail.gmail.com>
	<515538FB.3030602@inlink.ee> <5155B422.5070606@watsen.net>
	<CA+QY2RTrEzWbHJK3Tkqc3hTghD9HPDeLM6=K67J1RD0y6GLN_A@mail.gmail.com>
Message-ID: <51574234.7080701@watsen.net>


I tried Kayak, but gave up due to a bit of luck.  I happened to plug my 
CF into another machine and ran the installer again there and...it 
worked!  Identical motherboards and all, the only difference is that 
this other machine only had 4GB of memory installed whereas my main 
machine has 24GB installed.  So, for anyone having trouble with the 
installer, try changing how much memory is installed.

Regarding Kayak, I got stuck trying to a setup a DHCP server.  The 
instructions talk about using the ISC DHCP server, but `pkg search` only 
found SUN's and `dhcpconfigure` threw a Java NullPointerException...

Thanks,
Kent



On 3/29/13 1:14 PM, Eric Sproul wrote:
> On Fri, Mar 29, 2013 at 11:32 AM, Kent Watsen <kent at watsen.net> wrote:
>> I've started to try the Kayak suggestion but have so far failed - the first
>> laptop didn't have enough memory (it had 127MB, no idea what's needed)
> 127MB is almost certainly not enough.
>
>> on the second laptop (a T400), OmniOS couldn't recognize its network
>> interface - not good so a machine that's suppose to act as a server ;)
> Laptops aren't the target platform.  OmniOS is aimed at servers, and
> that means server-class hardware.  Luckily there is often sufficient
> overlap in hardware support that things like desktops and laptops
> generally work, but YMMV.
>
>> The crazy thing is, I have no idea how flexible the Kayak installer is - I
>> read that it has ZFS compression on by default, but what is it going to do
>> for helping me install on this CF?
> Putting aside the fact that CF seems a poor choice for an OS install
> (slow, outdated IDE interface, poor random I/O performance), Kayak
> puts some practical bounds on swap and dump volumes, and just won't
> create them if the rpool is too small.
>
> Nevertheless, I'm curious what Kayak would do with your device.  The
> MakeSwapDump() function
> (http://omnios.omniti.com/file.php/core/kayak/disk_help.sh#l128) is
> where the calculation happens.  Kayak tries to make each of the swap
> and dump volumes equal to 25% of physical memory, with a minimum of
> 1GB.  It then tries to see whether, with at least 2GB of swap/dump
> reservations, there would still be a minimum of 10G free on the rpool
> for the OS install and future updates.  Right there, we fail, and will
> not make either swap or dump volumes on your 8G CF card.  The install
> would proceed without them.
>
> Eric
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss


