From longmode at rediffmail.com  Mon Jul  2 14:20:11 2018
From: longmode at rediffmail.com (karthik)
Date: 2 Jul 2018 14:20:11 -0000
Subject: [OmniOS-discuss] =?utf-8?q?Boot_failure_after_OmniOS_CE_install?=
Message-ID: <20180702142011.23598.qmail@f4mail-235-196.rediffmail.com>

Hello,On my desktop system recently, I wiped out a Windows 10/Ubuntu 16(MBR) dual boot setup so that I can install(via DVD) to install OmniOS CE(latest stable release) .OmniOS has an option of installing onto a custom zpool named rpool,so I installed in this manner.After install ,the BSD loader fails to boot the OS, just displays an error &quot;start not found&quot; as shown in the below link:https://pasteboard.co/HstyCuG.pngAlso(after install) I gave ? in the OK prompt and scrolled down to the list of available commands. The beadm command was missing as shown in the below link:https://pasteboard.co/HstDr26.pngI also tried workaround 2 mentioned in the below link, but that did not help:https://wiki.openindiana.org/oi/MBR reinstall after illumos loader updateMy desktop rig is: Intel Core i7 6700(skylake),ASUS Z170 ProGaming Motherboard,8GB Corsair DDR4 RAM,1 TB Seagate Hard Disk,LG SATA DVD-RW drive.This rig has no AMD or Nvidia graphics cardHow to get these issues resolved?ThanksKarthik
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20180702/3ae591aa/attachment.html>

From paladinemishakal at gmail.com  Mon Jul  9 10:33:40 2018
From: paladinemishakal at gmail.com (Lawrence Giam)
Date: Mon, 9 Jul 2018 18:33:40 +0800
Subject: [OmniOS-discuss] OmniOS r1510
Message-ID: <CAGueQCcoGaDJ29Emgc1tzt43-=1_kJU67s=9MxWaajgoymBiyg@mail.gmail.com>

Hi All,

Can I check if Seagate 1200.2 (ST200FM0133) is supported by OmniOS R151014?

Thanks & Regards.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20180709/a1fe63b7/attachment.html>

From danmcd at kebe.com  Mon Jul  9 13:53:16 2018
From: danmcd at kebe.com (Dan McDonald)
Date: Mon, 9 Jul 2018 09:53:16 -0400
Subject: [OmniOS-discuss] OmniOS r1510
In-Reply-To: <CAGueQCcoGaDJ29Emgc1tzt43-=1_kJU67s=9MxWaajgoymBiyg@mail.gmail.com>
References: <CAGueQCcoGaDJ29Emgc1tzt43-=1_kJU67s=9MxWaajgoymBiyg@mail.gmail.com>
Message-ID: <3798E2C4-48CA-41FB-BE43-3C0F1AB2FB0A@kebe.com>



> On Jul 9, 2018, at 6:33 AM, Lawrence Giam <paladinemishakal at gmail.com> wrote:
> 
> Hi All,
> 
> Can I check if Seagate 1200.2 (ST200FM0133) is supported by OmniOS R151014?

Even if OmniTI were still supporting OmniOS, r151014 would've been EOSLed by now.  See this old page:

	https://omnios.omniti.com/wiki.php/ReleaseCycle

for example.

Dan


From paladinemishakal at gmail.com  Tue Jul 10 01:34:24 2018
From: paladinemishakal at gmail.com (Lawrence Giam)
Date: Tue, 10 Jul 2018 09:34:24 +0800
Subject: [OmniOS-discuss] OmniOS r1510
In-Reply-To: <3798E2C4-48CA-41FB-BE43-3C0F1AB2FB0A@kebe.com>
References: <CAGueQCcoGaDJ29Emgc1tzt43-=1_kJU67s=9MxWaajgoymBiyg@mail.gmail.com>
	<3798E2C4-48CA-41FB-BE43-3C0F1AB2FB0A@kebe.com>
Message-ID: <CAGueQCeWSLc139R_myqMJ7i28T8P2cXBh1_JLP5VCjzEAXufjw@mail.gmail.com>

I know R151014 is EOL but I am still running legacy stuff so no choice for
me. I checked in the illumos hardware list and I cannot find it there so I
thought of asking.

The disk controller is LSI 3008 which I know is supported but I am not very
sure if the SSD will be, so I would like to check first.

On Mon, Jul 9, 2018 at 9:53 PM, Dan McDonald <danmcd at kebe.com> wrote:

>
>
> > On Jul 9, 2018, at 6:33 AM, Lawrence Giam <paladinemishakal at gmail.com>
> wrote:
> >
> > Hi All,
> >
> > Can I check if Seagate 1200.2 (ST200FM0133) is supported by OmniOS
> R151014?
>
> Even if OmniTI were still supporting OmniOS, r151014 would've been EOSLed
> by now.  See this old page:
>
>         https://omnios.omniti.com/wiki.php/ReleaseCycle
>
> for example.
>
> Dan
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20180710/bc424813/attachment.html>

From pasztor at sagv5.gyakg.u-szeged.hu  Fri Jul 20 00:46:05 2018
From: pasztor at sagv5.gyakg.u-szeged.hu (=?iso-8859-2?Q?P=C1SZTOR_Gy=F6rgy?=)
Date: Fri, 20 Jul 2018 02:46:05 +0200
Subject: [OmniOS-discuss] ami instance upgrade problems
Message-ID: <20180720004605.GA12498@linux.gyakg.u-szeged.hu>

Hi,

I'm learning amazon, so I thought it would be nice, if I'd play with an
omnios inside my free tier experiments instead of linux.
I installed omnios from the "official" source: ami-0169c5108d1bdfd57
(Yes, I choose Ohio instead of N. Virginia to play at)

One small sidenote: ipv6 is not enabled in the official image, however I
configured so for the instance. After install I manually run this:
ipadm create-addr -T addrconf xnf0/v6
Well, it solved everything. It seems way more simpleer then toying with
linux.

But... I can not update my instance.
pkg update created the omnios-1 be, but I can not activate it.
root at ip-172-31-28-110:~# beadm list
BE       Active Mountpoint     Space Policy Created
omnios   NR     /              801M  static 2018-05-04 18:52
omnios-1 -      /tmp/tmpTvggQP 158M  static 2018-07-20 00:15
root at ip-172-31-28-110:~# beadm activate -v omnios-1
be_do_installboot: device c4t0d0
be_do_installboot: install failed for device c4t0d0.
  Command: "/usr/sbin/installboot -m -f /tmp/tmpTvggQP/boot/pmbr /tmp/tmpTvggQP/boot/gptzfsboot /dev/rdsk/c4t0d0s0"
  Errors:
open: No such file or directory
Unable to open device /dev/rdsk/c4t0d0s0
be_run_cmd: command terminated with error status: 1
Unable to activate omnios-1.
Error installing boot files.
root at ip-172-31-28-110:~# ls -l /dev/rdsk/*t0d0s0
lrwxrwxrwx   1 root     root          34 Jul 18 22:07 /dev/rdsk/c1t0d0s0 -> ../../devices/xpvd/xdf at 51712:a,raw
lrwxrwxrwx   1 root     root           8 Jul 20 00:21 /dev/rdsk/c4t0d0s0 -> c1t0d0s0
root at ip-172-31-28-110:~# /usr/sbin/installboot -m -f /tmp/tmpTvggQP/boot/pmbr /tmp/tmpTvggQP/boot/gptzfsboot /dev/rdsk/c1t0d0s0 
bootblock version installed on /dev/rdsk/c1t0d0s0 is more recent or identical
Use -F to override or install without the -u option

root at ip-172-31-28-110:~# zpool status -v
  pool: syspool
 state: ONLINE
  scan: none requested
config:

        NAME        STATE     READ WRITE CKSUM
        syspool     ONLINE       0     0     0
          c4t0d0    ONLINE       0     0     0

errors: No known data errors
root at ip-172-31-28-110:~# echo | format
Searching for disks...done


AVAILABLE DISK SELECTIONS:
       0. c1t0d0 <Xen-Virtual disk-1.0-8.00GB>
          /xpvd/xdf at 51712
Specify disk (enter its number): Specify disk (enter its number): 


Well, I'm stucked at this point. I don't know how could I fix these.
I assume, the problem is, somewhere around the c4 vs c1 numbering, so it
try to open the wrong device.

Note.: So let's just assume, it should work, without running the installboot
command.

root at ip-172-31-28-110:~# cd /usr/sbin
root at ip-172-31-28-110:/usr/sbin# mv installboot installboot.save
root at ip-172-31-28-110:/usr/sbin# ln -s ../bin/true installboot
root at ip-172-31-28-110:/usr/sbin# beadm activate -v omnios-1
be_do_installboot: device c4t0d0
  Command: "/usr/sbin/installboot -m -f /tmp/tmpTvggQP/boot/pmbr /tmp/tmpTvggQP/boot/gptzfsboot /dev/rdsk/c4t0d0s0"
Activated successfully
root at ip-172-31-28-110:/usr/sbin# reboot
OmniOS 5.11     omnios-r151026-b6848f4455       June 2018
root at ip-172-31-28-110:~# beadm list
BE       Active Mountpoint Space Policy Created
omnios   -      -          3.66M static 2018-05-04 18:52
omnios-1 NR     /          1.01G static 2018-07-20 00:15

Will. It's a very dirty hack. Is there a nicer way to fix this c4 vs c1
thing?
Btw.: it seems installboot would give back false, even if it could open the
device, because it already has the same version of boot block. Shouldn't
that circumstance checked on behalf of beadm?

Cheers,
gyu

From al.slater at scluk.com  Wed Jul 25 09:08:54 2018
From: al.slater at scluk.com (Al Slater)
Date: Wed, 25 Jul 2018 10:08:54 +0100
Subject: [OmniOS-discuss] ami instance upgrade problems
In-Reply-To: <20180720004605.GA12498@linux.gyakg.u-szeged.hu>
References: <20180720004605.GA12498@linux.gyakg.u-szeged.hu>
Message-ID: <a2cdf974-9517-9a2c-d9ab-1b3e88f9b7c1@scluk.com>

Hi,

The problem is caused, I think, by device numbering differences in xen
versus ec2.

I solved this problem when creating my AMIs by the following procedure.

1.  Create an extra volume in EC2 with the same size as the instance
boot volume.

2.  Attach the extra volume to the instance.

3.  zpool attach the extra volume (c1t1d0?)
   zpool attach rpool c4t0d0 c1t1d0

4.  zpool detach the original volume with incorrect name (c4t0d0)
   zpool detach rpool c4t0d0

5.  zpool attach the original volume with the proper name (c1t0d0)
   zpool attach rpool c1t1d0 c0t0d0

6.  zpool detach the extra volume.
   zpool detach rpool c1t1d0

7.  Detach the extra volume from the instance and delete it.

Double check all disk names in your instances first!

regards

Al

On 20/07/18 01:46, P?SZTOR Gy?rgy wrote:
> Hi,
> 
> I'm learning amazon, so I thought it would be nice, if I'd play with an
> omnios inside my free tier experiments instead of linux.
> I installed omnios from the "official" source: ami-0169c5108d1bdfd57
> (Yes, I choose Ohio instead of N. Virginia to play at)
> 
> One small sidenote: ipv6 is not enabled in the official image, however I
> configured so for the instance. After install I manually run this:
> ipadm create-addr -T addrconf xnf0/v6
> Well, it solved everything. It seems way more simpleer then toying with
> linux.
> 
> But... I can not update my instance.
> pkg update created the omnios-1 be, but I can not activate it.
> root at ip-172-31-28-110:~# beadm list
> BE       Active Mountpoint     Space Policy Created
> omnios   NR     /              801M  static 2018-05-04 18:52
> omnios-1 -      /tmp/tmpTvggQP 158M  static 2018-07-20 00:15
> root at ip-172-31-28-110:~# beadm activate -v omnios-1
> be_do_installboot: device c4t0d0
> be_do_installboot: install failed for device c4t0d0.
>   Command: "/usr/sbin/installboot -m -f /tmp/tmpTvggQP/boot/pmbr /tmp/tmpTvggQP/boot/gptzfsboot /dev/rdsk/c4t0d0s0"
>   Errors:
> open: No such file or directory
> Unable to open device /dev/rdsk/c4t0d0s0
> be_run_cmd: command terminated with error status: 1
> Unable to activate omnios-1.
> Error installing boot files.
> root at ip-172-31-28-110:~# ls -l /dev/rdsk/*t0d0s0
> lrwxrwxrwx   1 root     root          34 Jul 18 22:07 /dev/rdsk/c1t0d0s0 -> ../../devices/xpvd/xdf at 51712:a,raw
> lrwxrwxrwx   1 root     root           8 Jul 20 00:21 /dev/rdsk/c4t0d0s0 -> c1t0d0s0
> root at ip-172-31-28-110:~# /usr/sbin/installboot -m -f /tmp/tmpTvggQP/boot/pmbr /tmp/tmpTvggQP/boot/gptzfsboot /dev/rdsk/c1t0d0s0 
> bootblock version installed on /dev/rdsk/c1t0d0s0 is more recent or identical
> Use -F to override or install without the -u option
> 
> root at ip-172-31-28-110:~# zpool status -v
>   pool: syspool
>  state: ONLINE
>   scan: none requested
> config:
> 
>         NAME        STATE     READ WRITE CKSUM
>         syspool     ONLINE       0     0     0
>           c4t0d0    ONLINE       0     0     0
> 
> errors: No known data errors
> root at ip-172-31-28-110:~# echo | format
> Searching for disks...done
> 
> 
> AVAILABLE DISK SELECTIONS:
>        0. c1t0d0 <Xen-Virtual disk-1.0-8.00GB>
>           /xpvd/xdf at 51712
> Specify disk (enter its number): Specify disk (enter its number): 
> 
> 
> Well, I'm stucked at this point. I don't know how could I fix these.
> I assume, the problem is, somewhere around the c4 vs c1 numbering, so it
> try to open the wrong device.
> 
> Note.: So let's just assume, it should work, without running the installboot
> command.
> 
> root at ip-172-31-28-110:~# cd /usr/sbin
> root at ip-172-31-28-110:/usr/sbin# mv installboot installboot.save
> root at ip-172-31-28-110:/usr/sbin# ln -s ../bin/true installboot
> root at ip-172-31-28-110:/usr/sbin# beadm activate -v omnios-1
> be_do_installboot: device c4t0d0
>   Command: "/usr/sbin/installboot -m -f /tmp/tmpTvggQP/boot/pmbr /tmp/tmpTvggQP/boot/gptzfsboot /dev/rdsk/c4t0d0s0"
> Activated successfully
> root at ip-172-31-28-110:/usr/sbin# reboot
> OmniOS 5.11     omnios-r151026-b6848f4455       June 2018
> root at ip-172-31-28-110:~# beadm list
> BE       Active Mountpoint Space Policy Created
> omnios   -      -          3.66M static 2018-05-04 18:52
> omnios-1 NR     /          1.01G static 2018-07-20 00:15
> 
> Will. It's a very dirty hack. Is there a nicer way to fix this c4 vs c1
> thing?
> Btw.: it seems installboot would give back false, even if it could open the
> device, because it already has the same version of boot block. Shouldn't
> that circumstance checked on behalf of beadm?
> 
> Cheers,
> gyu
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss
> 

From pasztor at sagv5.gyakg.u-szeged.hu  Wed Jul 25 13:56:53 2018
From: pasztor at sagv5.gyakg.u-szeged.hu (=?iso-8859-2?Q?P=C1SZTOR_Gy=F6rgy?=)
Date: Wed, 25 Jul 2018 15:56:53 +0200
Subject: [OmniOS-discuss] ami instance upgrade problems
In-Reply-To: <a2cdf974-9517-9a2c-d9ab-1b3e88f9b7c1@scluk.com>
References: <20180720004605.GA12498@linux.gyakg.u-szeged.hu>
	<a2cdf974-9517-9a2c-d9ab-1b3e88f9b7c1@scluk.com>
Message-ID: <20180725135653.GC31130@linux.gyakg.u-szeged.hu>

Hi,

"Al Slater" <al.slater at scluk.com> ?rta 2018-07-25 10:08-kor:
> The problem is caused, I think, by device numbering differences in xen
> versus ec2.
> 
> I solved this problem when creating my AMIs by the following procedure.
> 
> 1.  Create an extra volume in EC2 with the same size as the instance
> boot volume.
> 
> 2.  Attach the extra volume to the instance.
> 
> 3.  zpool attach the extra volume (c1t1d0?)
>    zpool attach rpool c4t0d0 c1t1d0
> 
> 4.  zpool detach the original volume with incorrect name (c4t0d0)
>    zpool detach rpool c4t0d0
> 
> 5.  zpool attach the original volume with the proper name (c1t0d0)
>    zpool attach rpool c1t1d0 c0t0d0
> 
> 6.  zpool detach the extra volume.
>    zpool detach rpool c1t1d0
> 
> 7.  Detach the extra volume from the instance and delete it.
> 
> Double check all disk names in your instances first!

Nice trick tho!
Checked, worked. I mean at least if I run a beadm activate omnios-1 it says
Activated succesfully. And on omnios-1, the installboot is not diverted to
true. -> I could clean up the garbage now, and destroy the old omnios be.

Cheers,
Gyu

From jub at matchcut.at  Fri Jul 27 07:31:02 2018
From: jub at matchcut.at (=?utf-8?Q?J=C3=BCrgen_Bereuter?=)
Date: Fri, 27 Jul 2018 09:31:02 +0200
Subject: [OmniOS-discuss] beadm activate error
Message-ID: <5A0F500F-3FBA-4E5B-8FC6-DBFD016ACC8F@matchcut.at>

Hello,
i have a strange situation on a Dell R320 server with the omniosce 20180530 (also with the r151026). I installed omnios on a usb stick inside the server, not on the hdds.
When i pkg update, the new boot environment is not activated, it starts with the original  boot environment. When i try to activate the new one with beadm, there is this error:

$ sudo beadm activate -v omnios-2                                                                                                                    
be_do_installboot: device c5t0d0
be_do_installboot: install failed for device c5t0d0.
  Command: "/usr/sbin/installboot -m -f /tmp/.be.BDaasb/boot/pmbr /tmp/.be.BDaasb/boot/gptzfsboot /dev/rdsk/c5t0d0s1"
  Errors:
open: No such file or directory
Unable to open device /dev/rdsk/c5t0d0s1
be_run_cmd: command terminated with error status: 1
Unable to activate omnios-2.
Error installing boot files.


Obviously, there is no device with dev/rdsk/c5* on my system. When i change the device to the correct one,  beadm says there are problems with opening or reading the tmp directory. Although zpool says so:

  pool: rpool
 state: ONLINE
  scan: none requested
config:

        NAME        STATE     READ WRITE CKSUM
        rpool       ONLINE       0     0     0
          c5t0d0    ONLINE       0     0     0

errors: No known data errors

I exported and re-imported the rpool, which changed the device-name from c6* to c5*.
The usb was formated as fat32 with mbr, on a mac. Shpuld i use a special format for omnios/illumos?
Thanks!


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

From alka at hfg-gmuend.de  Fri Jul 27 13:15:24 2018
From: alka at hfg-gmuend.de (Guenther Alka)
Date: Fri, 27 Jul 2018 15:15:24 +0200
Subject: [OmniOS-discuss] How to create an installer/ bootable recovery iso
 from a running system?
In-Reply-To: <a2cdf974-9517-9a2c-d9ab-1b3e88f9b7c1@scluk.com>
References: <20180720004605.GA12498@linux.gyakg.u-szeged.hu>
	<a2cdf974-9517-9a2c-d9ab-1b3e88f9b7c1@scluk.com>
Message-ID: <070db93d-f150-5223-7aaf-510ff3d0fa85@hfg-gmuend.de>

Question:

Is it possible to create a bootable iso installer from a configured and 
at best online from a running system (that works then like the regular 
OS iso installer)?

Intention is to reinstall the fully configued Oi/OmniOS from this iso 
for disaster recovery with the help of the regular installer process.

I have done this in the past with a Linux appliance where this was part 
of the distribution and where you are able to create a bootable 
installer DVD on the fly to restore the system after a crash or to go 
back to a former state. Simple and genious. A bootable USB stick can be 
easily created from the iso with the Rufus tool.


Gea
@napp-it.org

From jstockett at molalla.com  Fri Jul 27 14:48:19 2018
From: jstockett at molalla.com (Jeff Stockett)
Date: Fri, 27 Jul 2018 14:48:19 +0000
Subject: [OmniOS-discuss] beadm activate error
In-Reply-To: <5A0F500F-3FBA-4E5B-8FC6-DBFD016ACC8F@matchcut.at>
References: <5A0F500F-3FBA-4E5B-8FC6-DBFD016ACC8F@matchcut.at>
Message-ID: <ce66b0ec32504bdbbe7195e83fe558eb@molalla.com>

FWIW - I ran into this problem with R151024 on an R720 also when trying to install on a USB stick - the install worked and would boot, but updating would not.

From: OmniOS-discuss <omnios-discuss-bounces at lists.omniti.com> On Behalf Of J?rgen Bereuter
Sent: Friday, July 27, 2018 12:31 AM
To: omnios-discuss at lists.omniti.com
Subject: [OmniOS-discuss] beadm activate error

Hello,
i have a strange situation on a Dell R320 server with the omniosce 20180530 (also with the r151026). I installed omnios on a usb stick inside the server, not on the hdds.
When i pkg update, the new boot environment is not activated, it starts with the original  boot environment. When i try to activate the new one with beadm, there is this error:

$ sudo beadm activate -v omnios-2
be_do_installboot: device c5t0d0
be_do_installboot: install failed for device c5t0d0.
  Command: "/usr/sbin/installboot -m -f /tmp/.be.BDaasb/boot/pmbr /tmp/.be.BDaasb/boot/gptzfsboot /dev/rdsk/c5t0d0s1"
  Errors:
open: No such file or directory
Unable to open device /dev/rdsk/c5t0d0s1
be_run_cmd: command terminated with error status: 1
Unable to activate omnios-2.
Error installing boot files.



Obviously, there is no device with dev/rdsk/c5* on my system. When i change the device to the correct one,  beadm says there are problems with opening or reading the tmp directory. Although zpool says so:

  pool: rpool
 state: ONLINE
  scan: none requested
config:

        NAME        STATE     READ WRITE CKSUM
        rpool       ONLINE       0     0     0
          c5t0d0    ONLINE       0     0     0

errors: No known data errors

I exported and re-imported the rpool, which changed the device-name from c6* to c5*.
The usb was formated as fat32 with mbr, on a mac. Shpuld i use a special format for omnios/illumos?
Thanks!


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20180727/5a4cf943/attachment-0001.html>

From pasztor at sagv5.gyakg.u-szeged.hu  Sun Jul 29 11:54:37 2018
From: pasztor at sagv5.gyakg.u-szeged.hu (=?iso-8859-2?Q?P=C1SZTOR_Gy=F6rgy?=)
Date: Sun, 29 Jul 2018 13:54:37 +0200
Subject: [OmniOS-discuss] beadm activate error
In-Reply-To: <5A0F500F-3FBA-4E5B-8FC6-DBFD016ACC8F@matchcut.at>
References: <5A0F500F-3FBA-4E5B-8FC6-DBFD016ACC8F@matchcut.at>
Message-ID: <20180729115437.GH24037@linux.gyakg.u-szeged.hu>

Hi,

"J?rgen Bereuter" <jub at matchcut.at> ?rta 2018-07-27 09:31-kor:
> $ sudo beadm activate -v omnios-2                                                                                                                    
> be_do_installboot: device c5t0d0
> be_do_installboot: install failed for device c5t0d0.
>   Command: "/usr/sbin/installboot -m -f /tmp/.be.BDaasb/boot/pmbr /tmp/.be.BDaasb/boot/gptzfsboot /dev/rdsk/c5t0d0s1"
>   Errors:
> open: No such file or directory
> Unable to open device /dev/rdsk/c5t0d0s1
> be_run_cmd: command terminated with error status: 1
> Unable to activate omnios-2.
> Error installing boot files.
> 
> 
> Obviously, there is no device with dev/rdsk/c5* on my system. When i change the device to the correct one,  beadm says there are problems with opening or reading the tmp directory. Although zpool says so:

It's not a nice sulution, but until a better official sulition is
published, you can do the same, what I've just described a couple of days
ago regarding my ami instance upgrade problems.

Regards,
Gyu

