Locating the operating system upgrade program. Watch Live Upgrade fail. # zfs create arrakis/temp # lucreate -n test Checking GRUB menu... I changed my filesystem layout with ZFS a little bit (replaced a directory with a filesystem) and subsequently discovered that I had made a total hash of my Live Upgrade configuration yes
The Solaris OS is now owned by Oracle. May 7 17:33:01
Once the liveupgrade is messed up, then its better to start from the beginning.Also not all the time ludelete will work to destroy the alternative BE.Here we will see the tricks Creating initial configuration for primary boot environment
Searching /dev for possible boot environment filesystem devices Updating system configuration files. c6t60A9800057396D64685A4D7A52675733d0
Solution - Just execute - # devfsadm -v -C It will clear any broken device links under /dev or unreferenced device links under /dev directory. Use whatever method you prefer (vi, perl, grep). Checking selection integrity. Creating snapshot for
Adding patches to the BE
Removing incomplete BE
checkpatches.sh -p 119081-25 124628-05 ... File propagation successful Copied GRUB menu from PBE to ABE No entry for BE
Creating file system for in zone on . The only way to fix it is to uninstall the given package and re-install it after the zone has been upgraded. mount: Please run fsck and try again luupdall: WARNING: Could not mount the Root Slice of BE:"solenv2".
to /rpool/zones/sdev, it does not get mounted on /mnt/rpool/zones/sdev as a loopback filesystem and you'll get usually the follwoing error: ERROR: unable to mount zones: /mnt/rpool/zones/sdev must not be group readable. Had to do some cleanup afterwards and your tips set things straight again. There is a man page for this in section 4, so it is somewhat of a public interface but please take note of the warning The lutab file must not be FIX?
Mounting file systems for boot environment
Saving existing file in top level dataset for BE as //boot/grub/menu.lst.prev. However, don't forget to check Solaris™ Live Upgrade Software: Minimum Patch Requirements! oracle_user=xxxx oracle_pw=xxxx http_proxy_host=xxxx http_proxy_port=xxxx http_proxy_user=xxxx http_proxy_pw=xxxx For more details refer "Oracle Solaris 10 9/10 Installation Guide: Planning for Installation and Upgrade". As with the previous problem, this is also easy the zonepath ZFSs are busy.
© Copyright 2017 kelcours.com. All rights reserved.