[OmniOS-discuss] beadm activate error

[Jeff Stockett]

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: <https://omniosce.org/ml-archive/attachments/20180727/5a4cf943/attachment-0001.html>