Mounting Miniroot At Error Unable To Mount Boot Environment
Contents |
Upgrade and Upgrade PlanningPrevious: Initial Installation of the Solaris OSNext: Appendix B Additional SVR4 Packaging Requirements (Reference)Upgrading the Solaris OS Upgrading, Error Messages No upgradable disks Cause: A error: unable to determine the configuration of the current boot environment swap entry in the /etc/vfstab file is causing the upgrade to fail.
Error: All Datasets Within A Be Must Have The Canmount Value Set To Noauto
Solution: Comment out the following lines in the /etc/vfstab file: All swap files and slices on disks not my oracle support being upgraded Swap files that are no longer present Any unused swap slices usr/bin/bzcat not found Cause: Solaris Live Upgrade fails because of needing a patch cluster. Solution: A patch is needed to install Solaris Live Upgrade. Ensure that you have the most recently updated patch list by consulting http://sunsolve.sun.com. Search for the info doc 72099 on the SunSolve web site. Upgradeable Solaris root devices were found, however, no suitable partitions to hold the Solaris install software were found. Upgrading using the Solaris Installer is not possible. It might be possible to upgrade using the Solaris Software 1 CDROM. (x86 based systems only) Cause: You cannot upgrade with the Solaris Software - 1 CD because you do not have enough space. Solution: To upgrade, you can either create a swap slice that is larger than or equal to 512 Mbytes or use another method of upgrading such as the Solaris installation from Solaris Operating System DVD, a net installation image, or JumpStart. ERROR: Could not select locale (x86 based systems only) Cause: When you test your JumpStart profile by using the pfinstall -D command, the dry run test fails under the following conditions: The profile contains the locale keyword. You're testing a release that contains GRUB software. Starting with the Solaris 10 1/06 release, the GRUB boot loader facilitates booting different operating systems installed on your system with the GRUB menu. With the introduction of GRUB software, the miniroot is compressed. The software can no longer find the list of locales from the compressed miniroot. The miniroot is the smallest possible Solaris root (/) fi
» 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, a permanent link can be found here. To help with your navigation, here is an index http://docs.oracle.com/cd/E19253-01/819-6396/troubleshooting-16510/index.html 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 (u8) and the root of the problem is a duplicate entry in the source boot environments ICF configuration file. Prior to u8, a ZFS https://blogs.oracle.com/bobn/entry/common_live_upgrade_errors 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 paying close attention, you might not even know this is an error. The symptoms are lucreate times that are way too long due to the extraneous copy, or the one that alerted me to the problem, the root file system is filling up - again thanks to a red
Joined: Dec 6, 2014 Messages: 42 Thanks Received: 11 Trophy Points: 11 I'm currently unable to update my FreeNAS install any longer, and an update is queued. I tried applying the updates via https://forums.freenas.org/index.php?threads/updates-failing-on-freenas-9-3.26828/ the web UI, but an error pops up in the web UI (it disappears too http://tpegeot.free.fr/wiki/index.php5?n=Solaris.TroubleshootingLU quickly for me to capture, but the same text gets logged). I get the following errors in the system log when I do so: Code:Jan 17 13:23:09 callisto updated.py: [freenasOS.Update:699] Unable to mount boot-environment FreeNAS-9.3-STABLE-201501162230 Jan 17 13:23:17 callisto updated.py: [freenasOS.Update:741] Update got exception during update: Unable to mount boot-environment FreeNAS-9.3-STABLE-201501162230 Jan 17 13:23:18 callisto manage.py: [middleware.exceptions:38] [MiddlewareError: Unable unable to to mount boot-environment FreeNAS-9.3-STABLE-201501162230] Anyone have any idea what is going on here? Show : My System Specs FreeNAS version: FreeNAS-9.3-STABLE-201501241715 Motherboard: ASRock C2750D4I Mini-ITX Server board CPU: Intel Atom C2750 2.4 GHz 8 cores (Avoton) RAM: Crucial CT2KIT102472BD160B 2x 8GB PC3-12800 1600MHz ECC RAM Disks: 6x WD Red 3TB WD30EFRX-68E SATA (via LSI 9211-8i SAS controller, crossflashed to P20 IT) Power supply: SilverStone Tek ST45SF-G 450W Fully Modular SFX 80+ Gold Certified mounting miniroot at Case: SilverStone Tek DS380B (currently without SAS backplane) Boot device: Kingston DataTraveler SE9 64GB USB Flash Drive Hostname: callisto demon, Jan 17, 2015 #1 sef FreeNAS Experienced iXsystems Joined: Sep 21, 2012 Messages: 181 Thanks Received: 15 Trophy Points: 26 The update for 20150115
View Edit History Print Solaris / TroubleshootingLU Unable to verify whether boot environment