On 03/ 9/15 12:03 PM, Alexander Pyhalov wrote:
Predrag Zecevic [Unix Systems Administrator] писал 09.03.2015 11:17:
Hi all,
...
Activation of BE failed, and I tried again:
Hi.
Could you select new BE in grub menu on boot? After booting new BE, try beadm
activate it.
---
System Administrator of Southern Federal University Computer Center
Hi Alexander,
yes! That has worked (booted from Grub menu into latest 'Update'):
$ beadm list
BE Active Mountpoint Space Policy Created
oi151_hipster2015_0227 R - 26.0G static 2015-02-27 06:58
oi151_hipster2015_0310 N / 865M static 2015-03-10 06:52
$ pfexec beadm activate oi151_hipster2015_0310
Activated successfully
Many thanks. Hopefully, this will be solved soon... One day I might need to
reboot system remotelly.
Regards.
--
Predrag Zečević
Technical Support Analyst
2e Systems GmbH
Telephone: +49 6196 9505 815, Facsimile: +49 6196 9505 894
Mobile: +49 174 3109 288, Skype: predrag.zecevic
E-mail: [email protected]
Headquarter: 2e Systems GmbH, Königsteiner Str. 87,
65812 Bad Soden am Taunus, Germany
Company registration: Amtsgericht Königstein (Germany), HRB 7303
Managing director: Phil Douglas
http://www.2e-systems.com/ - Making your business fly!
_______________________________________________
openindiana-discuss mailing list
[email protected]
http://openindiana.org/mailman/listinfo/openindiana-discuss
