JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Solaris 11.1 Administration: Devices and File Systems     Oracle Solaris 11.1 Information Library
search filter icon
search icon

Document Information


1.  Managing Removable Media (Tasks)

2.  Writing CDs and DVDs (Tasks)

3.  Managing Devices (Tasks)

4.  Dynamically Configuring Devices (Tasks)

5.  Managing USB Devices (Tasks)

6.  Using InfiniBand Devices (Overview/Tasks)

7.  Managing Disks (Overview)

What's New in Disk Management?

Support for Booting From EFI (GPT) Labeled Disks

Installation Support on Large Disks

Advanced Format Disk Support

Where to Find Disk Management Tasks

Overview of Disk Management

Disk Terminology

About Disk Labels

EFI (GPT) Disk Label

Comparison of the EFI Label and the VTOC Label

Restrictions of the EFI Disk Label

x86: Support for EFI-Labeled Disks

Installing a System With an EFI-Labeled Disk

Managing Disks With EFI Labels

Troubleshooting Problems With EFI Disk Labels

About Disk Slices

Using Raw Data Slices

format Utility

When to Use the format Utility

Guidelines for Using the format Utility

Formatting a Disk

Partitioning a Disk

Partition Table Terminology

Displaying Partition Table Information

Using the Free Hog Slice

8.  Managing Disk Use (Tasks)

9.  Administering Disks (Tasks)

10.  Setting Up Disks (Tasks)

11.  Configuring Storage Devices With COMSTAR (Tasks)

12.  Configuring and Managing the Oracle Solaris Internet Storage Name Service (iSNS)

13.  The format Utility (Reference)

14.  Managing File Systems (Overview)

15.  Creating and Mounting File Systems (Tasks)

16.  Configuring Additional Swap Space (Tasks)

17.  Copying Files and File Systems (Tasks)

18.  Managing Tape Drives (Tasks)


What's New in Disk Management?

The following disk management features are new in this Oracle Solaris release:

Support for Booting From EFI (GPT) Labeled Disks

Oracle Solaris installation features can install an EFI (GPT) disk label on a ZFS root pool disk or disks by using DVD, USB, and automated installation methods. UEFI firmware support and the introduction of GRUB 2 provides the ability to boot from a GPT labeled disk. This means that you can use whole disks for the root pool disk or disks on SPARC systems with GPT enabled firmward and on most x86 based systems. Otherwise, systems are installed with a VTOC (SMI) disk label on the root pool disk. For example:

# zpool status rpool
  pool: rpool
 state: ONLINE
  scan: none requested

    rpool     ONLINE       0     0     0
      c2t0d0  ONLINE       0     0     0

errors: No known data errors

For an example of a EFI (GPT) disk label on a root pool disk, see Example 9-3.

Installation Support on Large Disks

New Oracle Solaris installations are no longer limited to the first 2 TiB of the disk on x86 platforms. Oracle Solaris now uses EFI (GPT) partitioning for new installations to enable all of the disk space on the boot device to be used. On x86 platforms, large disk installation is supported through the introduction of GRUB 2 as the default boot loader.

For more information, see Chapter 2, Administering the GRand Unified Bootloader (Tasks), in Booting and Shutting Down Oracle Solaris 11.1 Systems.

Advanced Format Disk Support

Previous Oracle Solaris releases support disks with a physical block size and a logical block size of 512 bytes. This is the traditional disk block size that is an industry standard.

Currently, disk manufacturers are providing larger capacity disks, also known as advanced format (AF) disks, which is a general term that describes a hard disk drive that exceeds a 512-byte block size.

AF disks are generally in the 4-KB block size range, but vary as follows:

For comparison purposes, Oracle Solaris introduces the 512-byte native (512n) disk term, which is a traditional disk with 512-byte block size.

Oracle Solaris releases support advanced format disks, in additional to traditional 512n disks, in the following ways:

Review the following considerations before purchasing advanced format drives to be used on an Oracle Solaris system: