`<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'><br><br><div><hr id="stopSpelling">From: sim.ple@live.nl<br>To: jg@osn.de<br>Subject: RE: [OmniOS-discuss] Upgrading from OI to OmniOS<br>Date: Thu, 4 Dec 2014 12:45:10 +0100<br><br>
<style><!--
.ExternalClass .ecxhmmessage P {
padding:0px;
}
.ExternalClass body.ecxhmmessage {
font-size:12pt;
font-family:Calibri;
}
--></style>
<div dir="ltr">Hi,<br> Not a stupid question at all.<br>I fought with this for quite a while. I did it in quite an elaborate way and I am certain this can be done in fewer steps so I hope that one of the guru's in here can step in to correct my way of doing this.<br>Perhaps with a pkg install entire sort of a command ?<br><br>But anyway the following works for me :<br><br>On a vm I install the Omnios vm and configure it<br>In this vm I do a beadm create BEname.<br>Do:<br>beadm mount BEname /mnt<br><br>create a compressed file of this BE<br><code class="ecxjava ecxplain"><br>tar --create --bzip2 --absolute-names
--preserve-permissions --preserve-order --verbose
--file=/tmp/omni.tar.bz2
/mnt</code><br><br>Copy this to the machine where you want to install to e.g. /tmp<br><br>On the destination (vm)machine create a BE ( beadm create whatever and also mount it on e.g /mnt)<br>cd to /mnt on the destination and rm -rf *<br><br>untar the bz2 file (cd /tmp) :<br><br><code class="ecxjava ecxplain">tar --extract --bzip2 --absolute-names --preserve-permissions --same-owner --verbose --file=</code><code class="ecxjava ecxplain">omni.tar.bz2</code><br><br>This will populate the /mnt with the omnios be<br>On this machine (destination) I also do a <br><br><code class="ecxjava ecxplain">:;zpool status rpool <br></code><br>to identify the disks used by rpool and then do e.g. <br><br><code class="ecxjava ecxplain">ls -l /dev/dsk/</code><code class="ecxjava ecxplain">c4t50014EE002EC010Bd0s0</code><br><br>and register the physical device in the bootenv.rc file of the omnios<br><br><code class="ecxjava ecxplain">:;vi /mnt/boot/solaris/bootenv.rc</code><br><br>and add e.g. lines like:<br><br><div class="ecxline ecxnumber49 ecxindex48 ecxalt2"><code class="ecxjava ecxplain">setprop bootpath /scsi_vhci/disk</code><code class="ecxjava ecxcolor1">@g50014ee002ec010b</code><code class="ecxjava ecxplain">:a</code></div><div class="ecxline ecxnumber50 ecxindex49 ecxalt1"><code class="ecxjava ecxplain">setprop altbootpath /scsi_vhci/disk</code><code class="ecxjava ecxcolor1">@g50014ee0ad96d82a</code><code class="ecxjava ecxplain">:a </code><code class="ecxjava ecxplain"><== in case of mirror</code></div><div class="ecxline ecxnumber51 ecxindex50 ecxalt2"><code class="ecxjava ecxplain">setprop bootfile kernel/amd64/unix</code></div><code class="ecxjava ecxplain"><br></code>After this do:<br><code class="ecxjava ecxplain">:;/usr/sbin/devfsadm -r /mnt</code><br><br>Now you can reboot into your new Omni bootenv and clean stuff up. Again do not upgrade zfs version until satiesfied.<br><br>I am certain this can be a lot better but this works 4 me (being an autodidact)<br><br>HTH<br>And as others usually end their helpful hints,... typo's courtesy of ehh my keyboard...<br><br>R<br><br><br><br><div>> Date: Wed, 3 Dec 2014 18:20:40 +0100<br>> From: jg@osn.de<br>> To: sim.ple@live.nl<br>> Subject: Re: [OmniOS-discuss] Upgrading from OI to OmniOS<br>> <br>> Hi Randy,<br>> <br>> sorry this may be a stupid question, but how can I install<br>> a fresh Omnios in an existing bootenv? Or how do you create<br>> the bootenv? bootadm create ?<br>> <br>> Kind regards,<br>> <br>> - Joerg<br>> <br>> On 03.12.2014 13:44, Randy S wrote:<br>> > should have send this to the list.... again.... ;-)<br>> ><br>> > ------------------------------------------------------------------------<br>> ><br>> ><br>> > Hi,<br>> ><br>> > The safest way I could think of to do this is as follows:<br>> > create a bootenv in OI en install Omnios fresh into this<br>> > Start omnios and if you need any settings you can mount the be of OI to<br>> > e.g. /mnt and copy the config files from there to the Omnios install.<br>> ><br>> > I had to keep track of config files in /etc and /kernel/drv<br>> > I have noticed that both oses are quite compatible<br>> ><br>> > Above procedure can first be tested with vm's<br>> ><br>> > Do not upgrade any pools untill you are satisfied with the new situation<br>> > since there might be a diff in zfs version. If you do you won't be able<br>> > to go back to your OI install.<br>> ><br>> > Please first test with vm's!<br>> ><br>> > Rgds<br>> ><br>> > R<br>> ><br>> ><br>> ><br>> >> Date: Tue, 2 Dec 2014 14:47:50 +0000<br>> >> From: cal-s@blue-bolt.com<br>> >> To: omnios-discuss@lists.omniti.com<br>> >> Subject: [OmniOS-discuss] Upgrading from OI to OmniOS<br>> >><br>> >> Hi<br>> >><br>> >> I have a server hosting 65TB of RAIDZ2 storage that's currently running<br>> >> OI (oi_151a8), which i really want to get off of given that OI has<br>> >> bitten the dust support-wise. I found one brief discussion on the topic<br>> >> but it wasn't terribly detailed and was missing critical steps like<br>> >> configuration protection/retention. I'd like to preserve network and esp<br>> >> LDAP (client) settings as they were kind of a pain to establish in the<br>> >> first instance for quick reapplication. If anyone has or is interested<br>> >> in cobbling together a checklist of steps to upgrade OI to OmniOS that<br>> >> takes configuration into account, i'd very much appreciate seeing it.<br>> >><br>> >> thank you<br>> >><br>> >> - cal sawyer<br>> >> _______________________________________________<br>> >> OmniOS-discuss mailing list<br>> >> OmniOS-discuss@lists.omniti.com<br>> >> http://lists.omniti.com/mailman/listinfo/omnios-discuss<br>> ><br>> ><br>> > _______________________________________________<br>> > OmniOS-discuss mailing list<br>> > OmniOS-discuss@lists.omniti.com<br>> > http://lists.omniti.com/mailman/listinfo/omnios-discuss<br>> ><br>> <br>> -- <br>> OSN Online Service Nuernberg GmbH, Bucher Str. 78, 90408 Nuernberg<br>> Tel: +49 911 39905-0 - Fax: +49 911 39905-55 - http://www.osn.de<br>> HRB 15022 Nuernberg, USt-Id: DE189301263, GF: Joerg Goltermann<br></div> </div></div> </div></body>
</html>`