|Skip Navigation Links|
|Exit Print View|
|System Administration Guide: Devices and File Systems Oracle Solaris 10 8/11 Information Library|
This section describes new disk management features in the Oracle Solaris release.
For a complete listing of new Oracle Solaris features and a description of Oracle Solaris releases, see Oracle Solaris 10 8/11 What’s New.
Oracle Solaris 10 8/11: This Oracle Solaris release provides the diskinfo command that you can use to display the relationship between disk paths and disk slots (or bays) for devices that are found on the system. Devices that can be identified by the diskinfo command are generally JBODs and direct-attached devices in blade systems.
You can use the diskinfo -a command to display information about all the disks on the system. For example:
# diskinfo -a Enclosure path: 0631AM1028 Chassis Serial Number: 0631AM1028 Chassis Model: Sun-Fire-X4200-Server Label Disk name Vendor Product Vers ---------- ---------------------- -------- ---------------- ---- HD0 c1t0d0 FUJITSU MAY2073RCSUN72G 0401 HD1 c1t1d0 FUJITSU MAY2073RCSUN72G 0401
After you identify the disks on the system, you can display disk path information for a specific device. For example:
# diskinfo -d c1t1d0 -p Enclosure path: 0631AM1028 Chassis Serial Number: 0631AM1028 Chassis Model: Sun-Fire-X4200-Server Label Disk name Vendor Product Vers ---------- ---------------------- -------- ---------------- ---- HD1 c1t1d0 FUJITSU MAY2073RCSUN72G 0401 Physical path -------------------------------- 0: /pci@0,0/pci1022,7450@2/pci1000,3060@3/sd@1,0
With multiple enclosures on a system, display all the disks within a specific enclosure. For example:
# diskinfo -e 0631AM1028 Enclosure path: 0631AM1028 Chassis Serial Number: 0631AM1028 Chassis Model: Sun-Fire-X4200-Server Label Disk name Vendor Product Vers ---------- ---------------------- -------- ---------------- ---- HD0 c1t0d0 FUJITSU MAY2073RCSUN72G 0401 HD1 c1t1d0 FUJITSU MAY2073RCSUN72G 0401
For more information, see diskinfo(1M).
Solaris 10 9/10: Previous Solaris releases supported a disk sector size of 512 bytes. In this Oracle Solaris release, disks with sector sizes of 512 bytes, 1024 bytes, 2048 bytes, or 4096 bytes are supported. Large sector disks provide greater disk capacity, higher reliability, and greater efficiency for data transfer and faster drive maintenance.
The ability to boot and install from a large sector disk is not currently supported.
Oracle Solaris 10 10/09: In previous Solaris releases, you could not install and boot the Solaris OS from a disk that was greater than 1 TB in size. In this Solaris release, you can install and boot the Solaris OS from a disk that is up to 2 TB in size. In previous releases, you also had to use an EFI label for a disk that is larger than 1 TB. In this release, you can use the VTOC label on any size disk, but the addressable space by the VTOC is limited to 2 TB.
The Oracle Solaris disk drivers and disk utilities have been updated to provide the following support:
Installing and booting the Oracle Solaris OS on a two-terabyte disk must be connected to a system that runs a 64-bit kernel, with a minimum of 1.5 GB of memory.
You can use the format -e utility to label a disk of any size with a VTOC label, but the addressable space is limited to 2 TB.
The default label that is used by the format utility and the installation software for a disk that is less than 2 TB in size is a VTOC label.
You can use the fdisk utility on a disk that is greater than 1 TB on x86 systems. Support is added for up to 2-TB partitions in the MBR for non-EFI partition types. This support means that Solaris partitions can go up to 2 TB. Other non-EFI partitions may be subject to a limit depending on partition type.
When the fdisk utility is run on a disk that is greater than 2 TB in size, a warning message is displayed to indicate that you cannot create a non-EFI partition that is greater than 2 TB.
The Solaris Volume Manager software has been modified to create metadevices that support physical disks with VTOC labels up to 2 TB in size.
Keep in mind that you cannot move a disk over 1 TB with a legacy MBR or a legacy VTOC to a previous Solaris release. EFI labeled disks continue to work as in previous Solaris releases.
For more information about the EFI label changes in this release, see EFI Disk Label.
Solaris 10 8/07: This Solaris release provides support for the Internet Storage Name Service (iSNS) protocol in the Solaris iSCSI target and initiator software. The iSNS protocol allows for the automated discovery, management, and configuration of iSCSI devices on a TCP/IP network.
In this Solaris release, you can use the iscsitadm command to add access to an existing third-party iSNS server or you can user the Solaris iSNS server to automatically discover the iSCSI devices in your network. The iSNS server can be specified by hostname or IP address. After you add the iSNS server information, you will need to enable access to the server.
For information about configuring the Oracle Solaris iSCSI target to use a third-party iSNS server, see Chapter 14, Configuring Oracle Solaris iSCSI Targets and Initiators (Tasks) and iscsitadm(1M).
Solaris 10 8/07: This Solaris release provides support for iSCSI target devices, which can be disk or tape devices. Previous Solaris releases provide support for iSCSI initiators. The advantage of setting up Solaris iSCSI targets is you might have existing Fibre-Channel devices that can be connected to clients without the cost of Fibre-Channel HBAs. In addition, systems with dedicated arrays can now export replicated storage with ZFS or UFS file systems.
You can use the iscsitadm command to set up and manage your iSCSI target devices. For the disk device that you select as your iSCSI target, you'll need to provide an equivalently sized ZFS or UFS file system as the backing store for the iSCSI daemon.
After the target device is set up, use the iscsiadm command to identify your iSCSI targets, which will discover and use the iSCSI target device.
For more information, see Chapter 14, Configuring Oracle Solaris iSCSI Targets and Initiators (Tasks), iscsiadm(1M), and iscsitadm(1M).
Solaris 10 1/06: The GRUB boot menu has replaced the previous method for booting an x86 system. In the area of disk management, you use the GRUB interface when booting from an alternative device to replace a system disk or when installing the bootblocks.
The GRUB boot environment provides the following features:
Solaris failsafe boot – A Solaris failsafe boot option that boots into the miniroot so you can recover from a problem that is preventing the system from booting without having to boot from an alternative device. Use the arrow keys to select the following option from the GRUB boot menu and then press return:
You'll need to reboot the system after using the Solaris failsafe boot option.
Network boot – Boot from the network by pressing the F12 key during the BIOS configuration phase.
Single-user boot – Boot to single-user mode by selecting this option from the Solaris failsafe boot menu:
Then, use the e (edit) option to add the -s single-user option. For example:
kernel /platform/i86pc/multiboot -s
Press return and then press the b key to boot the system. Press control-D to boot the system back to multiuser mode.
In the GRUB environment, you cannot use the fmthard command to install the boot blocks automatically when run on an x86 system. You must install the boot blocks separately.
For detailed feature information and instructions on using the new GRUB based booting on x86 systems, see Booting an x86 Based System by Using GRUB (Task Map) in System Administration Guide: Basic Administration.
This feature is not available on SPARC systems.
Solaris 10 1/06: The SCSI driver, ssd or sd, supports 2 terabytes and greater. The SCSI driver, ssd or sd, is limited to 2 TB in previous Solaris releases.
The format utility can be used to label, configure, and partition these larger disks. For information about using the EFI disk label on large disks and restrictions with the fdisk utility, see Restrictions of the EFI Disk Label.