Dell OpenManage Array Manager User's Guide Version 3.6
Windows Operating System Disks: Basic and Dynamic
Array and Hard Disk Menu Commands
This chapter describes conceptual and procedural information about how Array Manager implements basic and dynamic disks. It also includes general disk functions.
![]() |
Note There are particular considerations regarding dynamic disks and volumes on NetWare, Windows Server 2003, and Linux. See "Dynamic Disk and Volume Support on NetWare, Windows Server 2003, and Linux" for more information. |
On a Windows system, you can expand the Disks object in the Array Manager tree view to display the operating system disks recognized by Windows Disk Management. These operating system disks can be either basic or dynamic. In conceptual terms, a basic disk is similar to a hard disk in that it does not support RAID functions. A dynamic disk is similar to an array disk in that it can support RAID functions. You can convert a basic disk to dynamic in order to apply RAID functions to the disk.
When you install the Windows operating system, your disks are automatically initialized as basic. You can upgrade them to dynamic after the Array Manager installation is complete. See "Upgrading a Basic Disk to Dynamic" for more information.
There are particular considerations regarding dynamic disks and volumes on NetWare, Windows Server 2003, and Linux. See "Dynamic Disk and Volume Support on NetWare, Windows Server 2003, and Linux" for more information.
A basic disk adheres to the partition-oriented scheme of a Windows operating system. A basic disk can have up to either four primary partitions or three primary partitions plus an extended partition. This extended partition can be subdivided into a number of logical drives.
You can create only primary and extended partitions on basic disks. You should create partitions on basic disks if you want computers running Microsoft Windows 98 or earlier, or MS-DOS to access these partitions.
Dynamic disks are created by upgrading basic disks using Array Manager. A dynamic disk is a physical disk that can contain dynamic volumes created with Array Manager. A dynamic volume organizes space on one or more physical disks by using a specific type of volume layout. The five types of dynamic volumes are simple, spanned, mirrored, striped, and RAID-5.
On a dynamic disk, space is organized through volumes rather than partitions. Because a dynamic disk does not have the partitioning scheme used by Windows 95/98 and MS-DOS, you cannot access dynamic disks through those operating systems.
For more information on the dynamic volume types, see the "Dynamic Volume Types" in the "Volumes" chapter.
There are particular considerations regarding dynamic disks and volumes on NetWare, Windows Server 2003, and Linux. See "Dynamic Disk and Volume Support on NetWare, Windows Server 2003, and Linux" for more information.
This section's topics are:
Array Manager allows you to do the following on basic disks:
You cannot perform the following tasks on a basic disk:
Use the Create Volume wizard to create primary partitions and extended partitions on a basic disk.
![]() |
Note If the disk already has either four primary partitions or three primary partitions and one extended partition, Array Manager displays a message that you have exceeded the number of partitions and will not let you create any more. Click OK and return to the Array Manager console. |
An extended partition can be subdivided into as many as 32 logical drives. You can use all or part of the free space in an extended partition when creating logical drives. An extended partition or a logical drive cannot span multiple disks.
The Status column in list view displays Formatting and displays the percentage of completion of the format process. The logical drive status changes to Healthy when formatting is complete, and the logical drive becomes available for use.
In the graphical view, removable-media devices are labeled Removable. They are considered basic disks.
You can create only one primary partition on removable-media devices. You cannot create extended partitions, logical drives, or dynamic volumes on removable-media devices. You cannot upgrade removable-media devices to dynamic volumes. Removable-media devices can contain only one primary partition and can be formatted with FAT or NTFS. You cannot mark a primary partition on a removable-media device as active.
On Windows Server 2003 you need to use the native Disk Management utility (not Array Manager) to upgrade a basic disk to dynamic. For information on accessing the native Disk Management on Windows Server 2003, see "Dynamic Disk and Volume Support on NetWare, Windows Server 2003, and Linux."
On Windows 2000, Array Manager can upgrade a basic disk that contains partitions, logical drives, or Disk Administrator volumes. Array Manager converts the partitions and logical drives to simple dynamic volumes and the Disk Administrator volumes to dynamic volumes of the appropriate corresponding RAID type. This capability is called encapsulation and is described in more detail in "Upgrade Disks with Legacy Volumes to Dynamic on Windows 2000" in the next chapter, "Volumes."
When Array Manager creates a partition on a basic disk, Array Manager checks whether the partition is the last one on the disk, and then reserves 1MB at the end of the disk for future upgrade needs. When you upgrade from basic to dynamic, the partition needs to align with the cylinder boundary, which may result in a cylinder size (usually 7.8MB) that is left on the disk. This cylinder size is displayed as unallocated disk space.
Warning! After you upgrade a basic disk to a dynamic disk, you will not be able to revert back to a basic disk until you first delete all the dynamic volumes on the disk. Then you can use the Revert to Basic Disk command to revert the disk back to a basic disk. Make sure to back up your data in this scenario before deleting any volumes, or your data will be lost!
![]() |
Note There are particular considerations regarding dynamic disks and volumes on NetWare, Windows Server 2003, and Linux. See "Dynamic Disk and Volume Support on NetWare, Windows Server 2003, and Linux" for more information. |
This section's topics are:
When you upgrade a dynamic disk, Array Manager writes a small database onto the upgraded disk to store volume management information about the disk and all other dynamic disks present on your system. This database is what gives a dynamic disk many advantages:
There are particular considerations regarding dynamic disks and volumes on NetWare, Windows Server 2003, and Linux. See "Dynamic Disk and Volume Support on NetWare, Windows Server 2003, and Linux" for more information.
Although Windows 2000 can access dynamic disks created with Array Manager, the dynamic volumes on these dynamic disks cannot be changed without Array Manager.
Virtual disks of Fibre Channel storage in a Storage Area Network (SAN) can be converted to dynamic disks, but this should be done with the following considerations:
There are particular considerations regarding dynamic disks and volumes on NetWare, Windows Server 2003, and Linux. See "Dynamic Disk and Volume Support on NetWare, Windows Server 2003, and Linux" for more information.
You can create dynamic volumes on dynamic disks only. To create and delete simple, spanned, striped, mirrored, and RAID-5 volumes, see "Creating a Dynamic Volume" in the "Volumes" chapter.
There are particular considerations regarding dynamic disks and volumes on NetWare, Windows Server 2003, and Linux. See "Dynamic Disk and Volume Support on NetWare, Windows Server 2003, and Linux" for more information.
You can extend simple and spanned volumes without having to locate unallocated contiguous space on the disk. See "Extending a Dynamic Simple or Spanned Volume" in the "Volumes" chapter.
There are particular considerations regarding dynamic disks and volumes on NetWare, Windows Server 2003, and Linux. See "Dynamic Disk and Volume Support on NetWare, Windows Server 2003, and Linux" for more information.
A dynamic disk may appear as a missing disk when it is corrupted, powered down, or disconnected. You can reactivate a dynamic disk to bring it back online.
There are particular considerations regarding dynamic disks and volumes on NetWare, Windows Server 2003, and Linux. See "Dynamic Disk and Volume Support on NetWare, Windows Server 2003, and Linux" for more information.
Dynamic disks with a Foreign status are disks that have been moved from another computer. You cannot reactivate a foreign disk. To change a foreign disk's status and enable it to be seen as a part of the current computer system, you will need to use the command Merge Foreign Disk. For details on how this command is done, see the next topic "Moving a Dynamic Disk to Another Computer."
There are particular considerations regarding dynamic disks and volumes on NetWare, Windows Server 2003, and Linux. See "Dynamic Disk and Volume Support on NetWare, Windows Server 2003, and Linux" for more information.
Before you disconnect the disks, make sure the status of the volumes on the disks is Healthy. If the status is not Healthy, you should repair the volumes before you move the disks. You need to prepare disks for removal in some cases. See "Prepare to Remove." It is also recommended that you back up all data on your volumes before you move disks to another computer.
![]() |
Note The ability to move dynamic disks to another computer is not supported with SAN storage. Only basic disks can be moved between servers on a SAN. Refer to the Dell OpenManage Storage Consolidation software documentation for more information. In addition, dynamic disks and dynamic volumes are only supported on the Windows 2000 operating system. |
You can revert a dynamic disk to basic if there are no volumes on the disk. If volumes exist, you must delete them before you can revert the disk. Disks shown in Array Manager to be unreadable or to be Foreign disks can be reverted, but doing so causes you to lose all existing data on the reverted disk.
There are particular considerations regarding dynamic disks and volumes on NetWare, Windows Server 2003, and Linux. See "Dynamic Disk and Volume Support on NetWare, Windows Server 2003, and Linux" for more information.
This section on general disk functions has the following topics:
![]() |
Note For disk troubleshooting information, see "Disk Troubleshooting Procedures." |
Use this procedure to add a new disk to your system and make the disk visible to Array Manager.
![]() |
Note If the disk you are adding already contains data, you must format the disk using the controller BIOS before the disk can be used by Array Manager. Until you format the disk using the controller BIOS, the disk will have an Offline or Foreign status and may generate other errors. |
Array Manager should detect the new disk after you click Rescan. However, if Array Manager does not detect the new disk, you may need to restart your computer.
New disks are added to the computer as basic disks. On Windows 2000, you can update basic disks that contain data to dynamic. See the section "Upgrade Disks with Legacy Volumes to Dynamic on Windows 2000" in the "Volumes" chapter.
SMART alerts are event messages predicting that a disk may fail in the near future. If an array disk is receiving SMART alerts, you should replace the disk. Use the following procedures to replace a disk receiving SMART alerts.
If the disk is part of a redundant virtual disk:
If the disk is not part of a redundant virtual disk:
When Array Manager rescans disks, it scans all attached disks for disk configuration changes. It also updates information on removable media, CD-ROM drives, basic volumes, file systems, and drive letters.
Every time you remove or add disks to a computer, you must click Rescan and then verify that the disk information is correct.
From the View pull-down menu, select Rescan, or select the Rescan icon from the toolbar.
A rescan can take several minutes, depending on the number of devices installed.
Use this option to refresh drive letter, file system, volume, and removable-media information. Refresh also checks to see whether unreadable volumes are now readable. However, it does not scan hardware. To update hardware information, use Rescan instead.
Windows requires that a disk have a signature on it before it can be used. Most controllers require that the write signature be added manually.
When you create a virtual disk and then do a rescan, the newly created virtual disk appears under the Disks storage object. If the disk needs a signature to be written manually, its icon will display an error symbol. Also, its type will be listed as "No Disk Signature" in the disks displayed in the right pane of the console. If left unsigned, the disk cannot be used.
Use the following steps to write a disk signature. This procedure assumes that you have already created the virtual disk.
Once a signature is written on a disk, the disk is displayed as a basic disk. You can create partitions on the basic disk, or you can upgrade the disk to dynamic to create volumes on it.
Array Manager supports Self Monitoring Analysis and Reporting Technology (S.M.A.R.T.) on array disks that are S.M.A.R.T. enabled.
S.M.A.R.T. performs predictive failure analysis on each disk and sends alerts if a disk failure is predicted. The RAID controllers check array disks for failure predictions and, if found, pass this information to the Array Manager console. Array Manager immediately displays an alert icon on the disk. Array Manager also raises an alert under the Events tab and in the Windows Event Log.
![]() |
Note When a controller's I/O is paused, you will not receive S.M.A.R.T. events. |
This section describes the following commands for working with array disks:
The Initialize command prepares an array disk for use as a member of a virtual disk. For details, see the "Initialize Array Disks."
|
Caution This is a data-destructive command. Any virtual disks residing on this array disk will be removed. |
The Rebuild function is enabled only when a disk has failed. You can rebuild failed disks only in redundant arrays.
![]() |
Note For information on performing a rebuild on the CERC SATA1.5/2s controller, see Rebuild (CERC SATA1.5/2s Controller). |
A global hot spare is an unused backup disk that is part of the array group. Hot spares remain in standby mode. When an array disk that is used in a virtual disk fails, the assigned hot spare is activated to replace the failed array disk without interrupting the system or requiring your intervention. When a hot spare is activated, it rebuilds the data for all redundant virtual disks that were using the failed array disk.
You can change the hot spare disk assignment by unassigning a disk and choosing another disk to assign, as needed.
For more information on hot spares, see "Understanding Hot Spares."
![]() |
Note Global hot spares must be assigned and unassigned manually. They are not assigned to specific virtual disks. On PERC Subsystem 1 controllers, there are size requirements for the hot spare. See "Considerations for Hot Spares (PERC Subsystem 1)" for more information. If you want to assign a hot spare to a virtual disk (it will replace any array disk that fails in the virtual disk) then use the "Configure Dedicated Hot Spare" command. For more information on hot spares, see "Understanding Hot Spares." |
Use this operation to unassign the global hot spare disk.
You can set to Online only an array disk that is part of a redundant virtual disk that has been set to Offline.
You can set to Offline only an array disk that is part of a redundant virtual disk that has been set to Online.
Before you remove any physical disk from an enclosure, it is recommended that you perform this operation to prevent data loss.
![]() |
Note This procedure is not supported on the CERC ATA100/4ch, CERC SATA1.5/6ch, or CERC SATA1.5/2s controllers. In addition, this procedure is only supported for hotswap array disks (disks that reside in a carrier). |
![]() |
Note On PERC 2, 2/Si, 3/Si, and 3/Di controllers, this procedure is only supported for hotswap array disks (disks that reside in a carrier). In addition, you may need to perform a rescan for the new disk to be displayed in the Array Manager tree view. |
The Blink command allows you to find an array disk within an enclosure by blinking one of the light-emitting diodes (LEDs) on the disk. The LEDs could blink from 30 seconds to indefinitely. You may want to use this command to locate an array disk that has failed.
To blink an array or hard disk:
![]() |
Note This procedure is not supported on the CERC ATA100/4ch, CERC SATA1.5/6ch, or CERC SATA1.5/2s controllers. In addition, this procedure is only supported for hotswap array disks (disks that reside in a carrier). |
![]() |
Note When using an Ultra SCSI, Ultra2 SCSI, Ultra160 SCSI, LSI 1020, or LSI 1030 controller, the Blink and Unblink commands apply to hard disks contained in carriers that can be inserted into a server or an enclosure. If the hard disk is not contained in a carrier but is instead designed to be connected with a SCSI cable (typically a ribbon cable), then the Blink and Unblink commands are disabled. |
The Unblink command allows you to cancel the Blink command.
To unblink an array or hard disk:
![]() |
Note This procedure is not supported on the CERC ATA100/4ch, CERC SATA1.5/6ch, or CERC SATA1.5/2s controllers. In addition, this procedure is only supported for hotswap array disks (disks that reside in a carrier). |
![]() |
Note When using an Ultra SCSI, Ultra2 SCSI, Ultra160 SCSI, LSI 1020, or LSI 1030 controller, the Blink and Unblink commands apply to hard disks contained in carriers that can be inserted into a server or an enclosure. If the hard disk is not contained in a carrier but is instead designed to be connected with a SCSI cable (typically a ribbon cable), then the Blink and Unblink commands are disabled. |
This command removes the disk space occupied by an orphan or dead disk segment.
A segment may be designated as dead if it is logically bad, is physically damaged, or resides on a disk that has been disconnected from and then reconnected to the controller.
Use this command to display the array or hard disk properties. Array disks are attached to RAID controllers (PERC Subsystem 1 and 2) and hard disks are attached to non-RAID SCSI controllers (SCSI Subsystem). The PERC 3/Di and PERC 4/Di controllers, however, can run in RAID/SCSI mode; these controllers handle one channel in RAID mode and the other channel in non-RAID SCSI mode.
To display the disk properties:
Disk properties may include:
![]() |
Note If you have PERC Subsystem 1 and PERC Subsystem 2 RAID controllers, the Unallocated Space field displays the available space. If you have SCSI (non-RAID) controllers, the field displays "N/A" (Not Applicable). If a controller is running in RAID/SCSI mode, the disks attached to the SCSI channel are displayed as "Hard Disk 0:1" instead of "Array Disk 0:1". Because the disks attached to the SCSI channel are not used to build virtual disks, they will also display "N/A" in the Unallocated Space field, just like the disks on non-RAID controllers. |
![]() |
Note Negotiated and capable speeds are not displayed for PERC 2/SC, PERC 2/DC, CERC ATA100/4ch, CERC SATA1.5/6ch, CERC SATA1.5/2s, Ultra SCSI, or Ultra2 SCSI. New SCSI drives manufactured since the introduction of the Ultra 320 SCSI drives will display this negotiated and capable speed information from Array Manager if your controller supports reporting them. If the drive was manufactured before that time, the negotiated and capable speed fields might display "not available". |
![]() |
Note Array disks for the PERC 2/SC, 2/DC, 3/SC, 3/DCL, 3/DC, 3/QC, 4/SC, 4/DC, 4e/DC, 4/Di, 4e/Si, 4e/Di, and CERC ATA100/4ch controllers display Ready status if they are not part of a virtual disk and Online status if they are part of a virtual disk. |
![]() |
Note Array disks for the PERC 2, PERC 2/Si, PERC 3/Si, PERC 3/Di, CERC SATA1.5/6ch, and CERC SATA1.5/2s controllers display Ready status regardless of whether they are a part of a virtual disk or not. Ready status for these controllers means the disk is operational. |