Skip Navigation Links | |
Exit Print View | |
![]() |
Oracle Solaris 10 9/10 Installation Guide: Custom JumpStart and Advanced Installations |
1. Where to Find Solaris Installation Planning Information
2. Custom JumpStart (Overview)
3. Preparing Custom JumpStart Installations (Tasks)
4. Using Optional Custom JumpStart Features (Tasks)
5. Creating Custom Rule and Probe Keywords (Tasks)
6. Performing a Custom JumpStart Installation (Tasks)
7. Installing With Custom JumpStart (Examples)
8. Custom JumpStart (Reference)
9. Installing a ZFS Root Pool With JumpStart
Problems With Setting Up Network Installations
Problems With Booting a System
Booting From Media, Error Messages
Booting From Media, General Problems
Booting From the Network, Error Messages
Booting From the Network, General Problems
Initial Installation of the Solaris OS
x86: To Check IDE Disk for Bad Blocks
To Continue Upgrading After a Failed Upgrade
x86: Problems With Solaris Live Upgrade When You Use GRUB
System Panics When Upgrading With Solaris Live Upgrade Running Veritas VxVm
x86: Service Partition Not Created by Default on Systems With No Existing Service Partition
To Install Software From a Network Installation Image or From the Solaris Operating System DVD
To Install From the Solaris Software - 1 CD or From a Network Installation Image
When you use Solaris 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 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
# cd /mnt/etc
# cp vfstab vfstab.501
# 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.
# cp vfstab.novxfs vfstab
# cd /mnt/etc
# 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.
# 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 Solaris 10 9/10 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 Solaris partition, you must re-create the service partition before you install the Solaris 10 9/10 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 Solaris 10 9/10 OS.
If you want to include a service partition on the disk that contains the Solaris partition, choose one of the following workarounds.