Andrej Podzimek wrote: > Hello, > > I installed OpenSolaris 2008.05 on a VMWare machine. The machine runs on a > remote server. (Installation from the client's CD-ROM takes *extremely* > long.) When I tried to upgrade the system after installation, I found out > that it was impossible to activate the new BE. Is it possible to fix this > somehow without reinstalling the whole system? I don't know what kind of > partition was used, as the installer (GUI) didn't say a single word about > that. It is a 8 GB virtual drive with one single partition on it. > > A piece of output: > > andrej at prominence:~# pkg image-update > Checking that SUNWipkg (in '/') is up to date... > DOWNLOAD PKGS FILES XFER > (MB) > SUNWxdg-user-dirs-gtk 597/598 0/5 > 0.00/0.03 > PHASE ACTIONS > Removal Phase 12988/12988 > Install Phase 17216/17216 > Update Phase 76860/76860 > PHASE ITEMS > Reading Existing Index 9/9 > Indexing Packages 598/598 > pkg: unable to activate opensolaris-1 > > > --------------------------------------------------------------------------- > NOTE: Please review release notes posted at: > http://opensolaris.org/os/project/indiana/resources/rn3/ > > --------------------------------------------------------------------------- > > andrej at prominence:~# df > Filesystem 1K-blocks Used Available Use% Mounted on > rpool/ROOT/opensolaris > 4939301 3452940 1486361 70% / > swap 1672184 740 1671444 1% > /etc/svc/volatile > /usr/lib/libc/libc_hwcap1.so.1 > 4939301 3452940 1486361 70% /lib/libc.so.1 > swap 1671452 8 1671444 1% /tmp > swap 1671484 40 1671444 1% /var/run > rpool/ROOT/opensolaris/opt > 1490055 3695 1486361 1% /opt > rpool/export 1486380 19 1486361 1% /export > rpool/export/home 1639860 153500 1486361 10% /export/home > rpool 1486419 59 1486361 1% /rpool > rpool/ROOT 1486379 18 1486361 1% /rpool/ROOT > rpool/ROOT/opensolaris-1 > 5276842 3790481 1486361 72% /tmp/tmp8NgB9n > rpool/ROOT/opensolaris-1/opt > 1490054 3694 1486361 1% > /tmp/tmp8NgB9n/opt > > andrej at prominence:~# beadm list > > BE Active Active on Mountpoint Space > Name reboot Used > ---- ------ --------- ---------- ----- > opensolaris yes yes / 3.56G > opensolaris-1 no no /tmp/tmp8NgB9n 2.19G > > So I unmounted the image called opensolaris-1... But things got even worse. > > andrej at prominence:~# BE_PRINT_ERR=1; export BE_PRINT_ERR;
try BE_PRINT_ERR=true here. > andrej at prominence:~# beadm activate opensolaris-1 > beadm: Unable to activate opensolaris-1 This looks like you're probably hitting 2302 which is a ZFS bug fixed in build 98. > andrej at prominence:~# beadm mount opensolaris-1 > beadm: Unable to mount opensolaris-1 For the beadm mount sub-command you need to provide a mount point. > > What am I doing wrong? > > Regards, > > Andrej > > _______________________________________________ > caiman-discuss mailing list > caiman-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
