Skip Navigation Links | |
Exit Print View | |
Oracle Solaris 10 1/13 Installation Guide: Live Upgrade and Upgrade Planning Oracle Solaris 10 1/13 Information Library |
Part I Upgrading With Live Upgrade
1. Where to Find Oracle Solaris Installation Planning Information
4. Using Live Upgrade to Create a Boot Environment (Tasks)
5. Upgrading With Live Upgrade (Tasks)
6. Failure Recovery: Falling Back to the Original Boot Environment (Tasks)
7. Maintaining Live Upgrade Boot Environments (Tasks)
8. Upgrading the Oracle Solaris OS on a System With Non-Global Zones Installed
Part II Upgrading and Migrating With Live Upgrade to a ZFS Root Pool
10. Live Upgrade and ZFS (Overview)
11. Live Upgrade for ZFS (Planning)
12. Creating a Boot Environment for ZFS Root Pools
13. Live Upgrade for ZFS With Non-Global Zones Installed
A. Live Upgrade Command Reference
Problems With Setting Up Network Installations
Problems With Booting a System
Error Messages When Booting From Media
General Problems When Booting From Media
Booting From the Network, Error Messages
General Problems When Booting From the Network
Initial Installation of the Oracle Solaris OS
x86: How to Check an IDE Disk for Bad Blocks
Upgrading the Oracle Solaris OS
General Problems When Upgrading
How to Continue Upgrading After a Failed Upgrade
x86: Problems With Live Upgrade When You Use GRUB
System Panics When Upgrading With Live Upgrade Running Veritas VxVm
How to Upgrade When Running Veritas VxVm
x86: Service Partition Not Created by Default on Systems With No Existing Service Partition
C. Additional SVR4 Packaging Requirements (Reference)
When you use Live Upgrade while upgrading and running Veritas VxVM, the system panics on reboot unless you upgrade by using the following procedure. The problem occurs if packages do not conform to Oracle Solaris advanced packaging guidelines.
Roles contain authorizations and privileged commands. For more information about roles, see Configuring RBAC (Task Map) in System Administration Guide: Security Services.
# lumount inactive-boot-environment-name mount-point
For example:
# lumount solaris8 /mnt
For example:
# cd /mnt/etc
For example:
# cp vfstab vfstab.501
For example:
# sed '/vx\/dsk/s/^/#/g' < vfstab > vfstab.novxfs
The first character of each line is changed to #, which makes the line a comment line. Note that this comment line is different than the system file-comment lines.
For example:
# cp vfstab.novxfs vfstab
For example:
# cd /mnt/etc
For example:
# cp system system.501
# sed '/forceload: drv\/vx/s/^/*/' <system> system.novxfs
The first character of each line is changed to *, which makes the line a command line. Note that this comment line is different than the vfstab file comment lines.
For example:
# touch vx/reconfig.d/state.d/install-db
# luumount inactive-boot-environment-name
# init 0
OK boot -s
Several messages and error messages that contain “vxvm” or “VXVM” are displayed that can be ignored. The inactive boot environment becomes active.
# cp /etc/vfstab.original /etc/vfstab # cp /etc/system.original /etc/system
# init 6
If you install the Oracle Solaris 10 8/11 OS on a system that does not currently include a service or diagnostic partition, the installation program might not create a service partition by default. If you want to include a service partition on the same disk as the Oracle Solaris partition, you must re-create the service partition before you install the Oracle Solaris 10 8/11 OS.
If you installed the Solaris 8 2/02 OS on a system with a service partition, the installation program might not have preserved the service partition. If you did not manually edit the fdisk boot partition layout to preserve the service partition, the installation program deleted the service partition during the installation.
Note - If you did not specifically preserve the service partition when you installed the Solaris 8 2/02 OS, you might not be able to re-create the service partition and upgrade to the Oracle Solaris 10 8/11 OS.
If you want to include a service partition on the disk that contains the Oracle Solaris partition, choose one of the following workarounds.