Error Cannot Mount Boot Environment By Icf File /etc/lu/icf.2
By user12625760 on May 27, 2008 It took a bit of work but I managed to pursuade my old laptop to live upgrade to nevada build 90 with ZFS root. First I upgraded to build 90 on ufs and then created a BE on zfs. The reason for the two step approach was to reduce the risk a bit. Bear in mind this is all new in build 90 and I am not an expert on the inner workings of live upgrade. So there are no guarantees. The upgrade failed at the last minute with this error: ERROR: File not found in top level dataset for BE
» Common Live Upgrade Problems By User12611829-Oracle on Jun 30, 2011 As I have worked with customers deploying Live Upgrade in their environments, several problems seem to surface over and over. With this blog article, I will try to collect these troubles, as well as suggest some workarounds. If this sounds like the beginnings of a Wiki, you would be right. At present, there is not enough material for one, so we will use this blog for the time being. I do expect new material to be posted on occasion, so if you wish to bookmark it for future reference, https://blogs.oracle.com/chrisg/entry/liveupgrade_ufs_zfs a permanent link can be found here. To help with your navigation, here is an index of the common problems. lucreate(1M) copies a ZFS root rather than making a clone luupgrade(1M) and the Solaris autoregistration file Watch out for an ever growing /var/tmp Without any further delay, here are some common Live Upgrade problems. Live Upgrade copies over ZFS root clone This was introduced in Solaris 10 10/09 https://blogs.oracle.com/bobn/entry/common_live_upgrade_errors (u8) and the root of the problem is a duplicate entry in the source boot environments ICF configuration file. Prior to u8, a ZFS root file system was not included in /etc/vfstab, since the mount is implicit at boot time. Starting with u8, the root file system is included in /etc/vfstab, and when the boot environment is scanned to create the ICF file, a duplicate entry is recorded. Here's what the error looks like. # lucreate -n s10u9-baseline Checking GRUB menu... System has findroot enabled GRUB Analyzing system configuration. Comparing source boot environment file systems with the file system(s) you specified for the new boot environment. Determining which file systems should be in the new boot environment. Updating boot environment description database on all BEs. Updating system configuration files. Creating configuration for boot environment . Source boot environment is . Creating boot environment . Creating file systems on boot environment . Creating file system for > in zone on . The error indicator -----> /usr/lib/lu/lumkfs: test: unknown operator zfs Populating file systems on boot environment . Checking selection integrity. Integrity check OK. Populating contents of mount point >. This should not happen ------> Copying. Ctrl-C and cleanup If you weren't
Server if required. lustatus Boot Environment Is Active Active Can Copy Name Complete Now On Reboot Delete Status -------------------------- -------- ------ --------- ------ -------- Primary yes yes yes no - Secondary yes no no https://www.slac.stanford.edu/grp/cd/soft/unix/liveUpgrade.html yes - ludelete Secondary ERROR: mount: /dev/dsk/c1t1d0s0 is not this fstype ERROR: cannot mount mount point device ERROR: failed to mount file system on ERROR: cannot mount boot environment by https://www.veritas.com/support/en_US/article.000007301 icf file ERROR: Cannot mount BE
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success Licensing Programs Licensing Process ABOUT About Corporate Profile Corporate Leadership Newsroom Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet Creating a Solaris alternate boot environment via lucreate may error with the message "vxfs mount: ERROR: V-3-21264 allowable number of mount points exceeded" due to incorrect device entries in /etc/vfstab Article:000007301 Publish: Article URL:http://www.veritas.com/docs/000007301 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your Profile Logout Sign in to Subscribe Please sign in to set up your subscription. Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem Creating a Solaris alternate boot environment via lucreate may error with the message "vxfs mount: ERROR: V-3-21264 allowable number of mount points exceeded" due to incorrect device entries in /etc/vfstab Solution Issue:Using lucreate to create a Solaris alternate boot environment (BE) may fail with the following VxFS error message. For example:# /usr/sbin/lucreate -c benv1 -n benv2 -C /dev/dsk/c2t0d0s0 -m /:/dev/dsk/c1t2d0s0:ufs -m -:/dev/dsk/c1t2d0s1:swap -m /usr:/dev/dsk/c2d0s7:ufs -m /var:/dev/dsk/c1t2d0s5:ufs -m /opt:/dev/dsk/c1t2d0s6:ufs Discovering physical storage devices ...Creating