C H A P T E R 11

Need ideas on fixing this please: (I'm remote & not on site to manually fix)Dell OpenManage shows physical disk failed OM log errors: Storage Drive 5: Drive Slot sensor f. SOLVED Dell Poweredge 2900 Virtual Disk Degrated - No option to rebuild - Spiceworks. May 06, 2017 05:43:55 Disk or disk bay 2 (Drive Slot (Bay) - Drive 2): Deassertion: In Critical Array. By what I notice, the drive 2 failed, then drive in slot 3 start to rebuild in order to get into the array, and after completing rebuild., drive 2 went online again, maybe because the lack of stress allow it to, how ever, drive 2 was the one. This may limit your ability to restore data resiliency in the event of drive failure (s).' RecommendedAction: 'Add additional capacity to the storage pool, or free up capacity. The minimum recommended reserve varies by deployment, but is approximately 2 drives' worth of capacity.' The drive is rebuilding or performing a RAIDmigration, strip size migration, capacity expansion, or logical drive extension, or is erasing. Ok;Tue Dec 30 10:;Storage Drive 1: Drive Slot sensor for Storage, drive fault was deasserted The spare was in but not part of the pool for the RAID. I added it as a global swap and the RAID added it in during a reboot and the degrade was gone and back to normal.

Managing Hard Disk Drives

This chapter discusses the following topics.

Hard Disk Drive Locations

The Sun Fire X4540 server can contain up to 48 SATA hard disk drives. The hard disk drive locations are numbered sequentially from 0 to 47, starting at the front left corner and incrementing left to right and front to rear (see FIGURE 11-1). The nomenclature for the locations is DISKn, where n is the location number.

FIGURE 11-1 Disk Drive Locations (Boot disks shown in gray)

Disk Drive Status and LEDs

Each hard disk drive has a sensor that is used to communicate the state of the slot. The hard disk drives use IPMI (Intelligent Platform Management Interface) sensors to convey a slot state, as shown in TABLE 11-1:

TABLE 11-1 Disk Drive Status Sensors
State	Event	Description
0	Device Not Present	The drive bay is empty.
1	Device Installed	The drive is detected. Used by remote management applications.
2	Ready for Device Removal	A drive is unmounted and ready to be physically removed. Controls the OK to Remove LED.
3	Device Faulted	Causes the service processor to illuminate the individual disk drive fault LED.

Inside the Sun Fire X4540 server chassis, each of the 48 hard disk drives has three LEDs, as shown in TABLE 11-2.

The individual LED locator can be used to control both the fault and removal LEDs through an IPMI OEM command. The service processor controls the fault and removal LEDs automatically, based on events in the disk drive sensors.

TABLE 11-2 Disk Drive LED Indicators
LED	Event	Description
Green	Disk drive activity	Controlled by hardware. Does not require SP interaction.
Amber	Hard disk drive failure	Controlled by the SP over the SP-12C bus. Relies on the operating system driver to set appropriately.
Blue	Hard disk drive ready for removal	Controlled by the SP over the SP-12C bus. The operating system determines that the drive has been halted and is ready to be removed.

EFI Disk Label Overview

Extensible Firmware Interface (EFI) is an Intel standard used as a replacement for the PC BIOS. It is responsible for the power-on self-test (POST) process, booting the operating system, and providing an interface between the operating system and the physical hardware. EFIs provides the following capabilities:

System-independent device drivers.
Delegation of networking and memory management issues to the firmware instead of the OS.
EFI selection and loading of the operating system, which removes the need for a boot loader.

The Solaris 10 OS provides support for EFI Labels for disks that are larger than 1 terabyte on systems that run a 64-bit Solaris kernel. The Extensible Firmware Interface GUID Partition Table (EFI GPT) disk label provides support for physical disks and virtual disk volumes.

You can download the EFI specification at:

http://www.intel.com/technology/efi/main_specification.htm

You can use the format -e command to apply an EFI label to a disk if the system is running the appropriate Solaris release. However, you should review the important information in Restrictions of the EFI Disk Label before attempting to apply an EFI label.

For additional information about EFI disk labels, managing disks with EFI labels, EFI disk label restrictions, and troubleshooting problems with EFI disk labels, refer to the Solaris 10 Systems Administration Guide at:

http://docs.sun.com

Converting EFI Label to SMI (Solaris) Label on the Sun Fire X4540 Disk

The ZFS system uses EFI labels to label whole disks that are added to a ZFS storage pool. If you convert an EFI label on disk that is part of a ZFS storage pool, you can erase the data on that disk.

Caution - Do not attempt to convert an EFI label to an SMI label using theformat(1M) command.

To convert an EFI disk label to an SMI (Solaris) label, delete the EFI fdisk partition, then create a new Solaris fdisk partition.

1. Use fdisk to delete the EFI fdisk partition.

CODE EXAMPLE 11-1 EFI to SMI Disk Label Conversion
(The partition is now deleted. The menu reappears, as shown in Step 2.)

2. Create the new partition.

3. Verify that Solaris2 fdisk has been created on the same disk.

Dell R710 Drive Slot Sensor For Storage Drive Fault Was Asserted

The above display confirms that the Solaris2 fdsik has been created.

For additional information about converting EFI and SMI disk labels, refer to the Solaris 10 Systems Administration Guide at:

http://docs.sun.com

About HDtool

You can use the HDtool utility to view the hard drive configuration. The following example shows the Sun Fire X4540 disks in the HDtool display.

For additional information about installing and using HDto