Skip Navigation Links | |
Exit Print View | |
Installing Oracle Solaris 11 Systems Oracle Solaris 11 Information Library |
Part I Oracle Solaris 11 Installation Options
1. Overview of Installation Options
Part II Installing Using Installation Media
2. Preparing for the Installation
System Requirements for LiveCD and Text Installations
Preparing a Boot Environment for Installing Multiple Operating Systems
Guidelines for Partitioning a System Prior To Installation
Guidelines for Partitioning a System During an Interactive Installation
x86: Setting Up Partitions During an Interactive Installation
Ensuring That You Have the Proper Device Drivers
How to Use the Oracle Device Detection Tool
Device Driver Utility Overview
How to Start the Device Driver Utility
How to Install Missing Drivers
How to List Your System in the HCL
Using Oracle Configuration Manager
5. Automated Installations That Boot From Media
6. Unconfiguring or Reconfiguring an Oracle Solaris instance
Part III Installing Using an Install Server
7. Automated Installation of Multiple Clients
8. Setting Up an Install Server
10. Provisioning the Client System
11. Configuring the Client System
12. Installing and Configuring Zones
13. Running a Custom Script During First Boot
14. Setting Up Oracle Configuration Manager For Use By AI Client Systems
This section provides guidelines for partitioning a system prior to installation or during an interactive installation. It also describes how to set up partitions on x86 and Solaris VTOC slices.
When installing Oracle Solaris from the LiveCD ISO image or from the text installer image, you can use the entire disk, or you can install the operating system on an x86 partition. In addition, with the text installer, you can install the operating system on a SPARC slice.
On x86 based systems, the installer uses GRUB, which supports booting multiple operating systems on one or more drives. You can create a partition for installing Oracle Solaris prior to installation as well as during an installation. After partitioning and installing the various operating systems, you can deploy any of them by selecting the appropriate menu entry in the GRUB menu at boot time.
Caution - Remember to back up your system prior to partitioning the hard drive. |
You can use the fdisk command to create or modify an Oracle Solaris fdisk partition. For instructions, see How to Create a Solaris fdisk Partition in Oracle Solaris Administration: Devices and File Systems. See also the fdisk(1M) man page.
Alternately, you can use commercial products or open-source tools to partition your hard drive.
Note - If you create Linux-swap partitions, note that Linux-swap uses the same partition ID that Oracle Solaris uses. During the installation, in the disk partitioning step, you can change the Linux-swap partition to an Oracle Solaris partition.
On an x86 based system, you can select, create, or modify partitions during a GUI installation or a text installation. For the text installer only, you can select, create, or modify VTOC slices during an interactive installation.
When installing Oracle Solaris, note the following important information about disk partitioning:
The installation overwrites the whole disk layout, if any of the following is true:
The disk table cannot be read.
The disk was not previously partitioned.
You select the entire disk for the installation.
If an existing fdisk partition is on an Oracle Solaris system and you make no modifications to the existing partitions, the installation overwrites the fdisk partition only. Other existing partitions are not changed.
Only one Solaris partition is allowed.
A Solaris partition must be used for the installation.
If there is an existing Solaris partition, that partition is selected by default. The partition can be a logical partition within an existing extended partition.
Changes you make to disk partitioning or slices are not implemented until you finish making the installer panel selections and the installation begins. At any point prior to the installation, you can cancel your changes and restore the original settings.
If the existing partition table cannot be read, proposed partitioning information is displayed.
Caution - In this case, all of the existing data on the disk is destroyed during the installation. |
During the installation, if you select the Partition the Disk option, the panel displays the existing fdisk partitions for the selected disk. Up to four primary partitions are displayed in the same order that they are laid out on the disk. Unused disk space is displayed for these primary partitions. The partition type, current size, and maximum available disk space for each partition are also displayed. If an extended partition exists, its logical partitions are also displayed in the disk layout order within the extended partition.
An fdisk partition cannot be larger than 2 TB, in order to be used for installing the OS. Disks or partitions that do not have enough space for a successful installation are labeled as such.
For installations on the x86 platform, you can make changes to disk partitioning by directly editing the entries in the installation screens. As you proceed through the installation, the recommended and minimum sizes for installing the software are also displayed.
The following table describes the disk partitioning options. Use this table to help you determine which option best suits your needs.
Table 2-2 Options for Partitioning a Disk During an Interactive Installation
|
For text installations on the SPARC platform, you can modify VTOC slices during the installation. For text installations on the x86 platform, you can modify a slice within a partition if that partition has not already been modified during the installation.
When setting up VTOC slices, keep the following in mind:
The installer displays the existing slices. The slices are displayed in the order in which they are laid out. The current size and maximum available size for each slice are also displayed.
Oracle Solaris must be installed in an Oracle ZFS root pool. By default, the slice that contains the root pool is labeled rpool by the installer. If you want to install the operating system on a slice that does not contain the root pool, change the type for that slice to rpool in the installer. During the installation, a ZFS root pool will be created on that slice.
Note - Because only one ZFS pool can be named rpool, if an rpool is already on the device, the installer will name any new pool using the format rpool#.
The size of a slice can be increased up to the maximum available size. To make more space available, you can change an adjoining slice to Unused, thereby making its space available to adjacent slices.
If the slice is not explicitly altered, the content of the slice is preserved during the installation.
The following table describes the options for modifying slices during a text installation.
Table 2-3 Options for Modifying VTOC Slices During a Text Installation
|