Using Disk and Volume Status Information
Problem Situations and Solutions
Dell PowerVault 660F and 224F Storage Systems Troubleshooting
This chapter contains status message information, troubleshooting procedures, and common problems and solutions. It also has a separate section for troubleshooting the Dell PowerVault 660F and 224F storage systems.
If a disk or volume fails, it is important to repair the disk or volume as quickly as possible to avoid data loss. Because time is critical, Array Manager makes it easy for you to locate problems quickly. In the Status column of the list view, you can view the status of a disk or volume. The status also appears in the graphical view of each disk or volume. If the status is not Healthy for volumes or Online for disks, use this section to determine the problem and then fix it. Topics include:
One of the following disk status descriptions will always appear in the Status column of the disk in the right pane of the console window. If there is a problem with a disk, you can use this troubleshooting chart to diagnose and correct the problem
.
One of the following volume status descriptions will always appear in the graphical view of the volume and in the Status column of the volume in list view. If there is a problem with a volume, you can use this troubleshooter to diagnose and correct the problem.
These definitions appear in the Status line and indicate the condition of array disks.
This section describes commands and procedures that can be used in troubleshooting. Topics covered include:
Use Rescan to update disk information. This operation may take a few minutes if there are a number of devices attached to the system. You will see a message "Getting hardware configuration. Please wait." while the rescan is occurring.
If this does not properly update the disk information, you may need to reboot your system.
A RAID 5 volume's status can appear as Failed Redundancy and the disk's status is Offline. The disk's name may be Missing, and an error icon (X) appears on the missing or offline disk. In this case, do the following.
Reactivating a volume attempts to restart all volumes regardless of the volume's state. If data corruption exists, you can reactivate the volume and then run the chkdsk utility. However, in the case of a mirrored or RAID-5 volume, reactivating a volume with stale data can cause that data to be used when it is inaccurate.
Reactivating a volume should be done only if you understand that the volume's data, which might be corrupted, will be restored. For example, if one mirror in a mirrored volume fails and data is written to the remaining mirror, the data is now out of sync. Then, if the remaining mirror (the one with accurate data) fails and the first mirror is reactivated, the stale data becomes "real" data.
For this reason, it is important to act on data failures as soon as possible. You should use care when reactivating volumes.
You should be able to repair a RAID-5 volume if it is in a state of Failed Redundancy, and if there is unallocated space on another dynamic disk available. To avoid data loss, you should attempt to repair the volume as soon as possible.
Make sure that the underlying physical disk is turned on, plugged in, and attached to the computer. No other user action is possible for basic volumes unless the volumes are mirrored or RAID-5 volumes that were originally created in NT Disk Administrator. The repair of these volumes is covered in the next topic.
Use Microsoft Windows NT Disk Administrator to repair basic mirrored or RAID-5 volumes if you are running Windows NT 4.0. For Windows 2000, there is a command available form the context menu for repairing basic mirrored or RAID-5 volumes.
![]() |
CAUTION! In Windows NT 4.0, Disk Administrator should never be used while Array Manager is running, especially if there are tasks running on the controller at the time. Data loss can occur if both applications are running simultaneously. |
Array Manager is tested with the controller firmware and drivers provided on the CD. To avoid possible conflicts or inconsistencies between the controller firmware and drivers, it is recommended to use these firmware and driver versions, or later. The most current versions can be obtained from Dell's web site at:
http://support.dell.com/us/en/filelib/
It is also recommended to obtain and apply the latest Dell PowerEdge Server System BIOS on a periodic basis to benefit from the most recent improvements. Please refer to the Dell PowerEdge System Documentation for more information.
This section contains additional trouble-shooting problem areas. Topics include:
![]() |
Note: If you are using the Dell PowerVault 660F RAID controller and the PowerVault 224F enclosure, see the next major section, Dell PowerVault 660F and 224F Storage Systems Troubleshooting, for additional issues specific to that controller and enclosure. |
Check:
Check:
Check:
Situation:
Microsoft Windows NT/2000 is not aware of the status of these disks. Most likely, the virtual disks that were associated with these have been deleted.
Check:
To remove these error status objects from the Disks node, the computer must be restarted to allow Windows NT/2000 to find the current information.
Situation:
If the type of disk shows No Signature, you need to write a signature to the disk. When creating a new virtual disk, the software must write a signature to the virtual disk that prepares it for use. This signature is not written automatically in case this disk has been merged from another operating system and the configuration information needs to be kept intact.
Check:
To write the configuration data to a disk, right-click on the disk under the Disks node and choose Write Signature.
The corresponding virtual disk has been removed, or the disk has been rendered inactive because of a problem.
Check:
Once you have repaired the disk, controller, or cable problem, you need to:
The remote computer that you were connected to has been disconnected from your console. Most often, there is a problem with the network connection and the transmissions timed out. This can also occur if the remote machine was restarted or the service on the remote machine was stopped.
Check:
Make sure that the remote machine is turned on and is available to the network, and that the service is started. Reconnect to the resource.
The installation detects any drivers that you have installed for PowerEdge RAID controllers. If these drivers (and/or the card itself) are installed after the software is installed, support for the controller will need to be added.
Check:
Close the console. Open the Array Manager Service Manager and check the box next to the appropriate controller. This action will restart the service, and the disks should be available the next time you launch the console.
When an operation is grayed out in a menu, the task cannot be performed on the object at this time. Certain operations are valid only for certain types of objects. (For example: RAID levels that are not fault tolerant will not allow you to check the consistency of the virtual disk.) If there is a task currently running on that object, wait until it has finished and try again. Otherwise, the operation may not be appropriate at this time.
If this was a virtual disk, then check that the virtual disk still exists. If it no longer exists, use the Remove Disk command to remove the disk from the list of disks.
Repair any disk, controller, or cable problems and make sure that the physical disk is turned on, plugged in, and attached to the computer. From the View pull-down menu, select Rescan. The disk should change from Offline to Online, but the volumes remain Failed. (If they do not change to Online, you may need to reboot.) Right-click on the disk and select Reactivate Disk. The disk status changes to Healthy. (You can also select each volume one at a time and select Reactivate Volume.) It is recommended you do a chkdsk.
If the disk status remains Offline and Missing and you determine that the disk has a problem that cannot be repaired, you can remove the disk from the system (using the Remove Disk command). However, before you can remove the disk, you must delete all volumes on the disk. You can save any mirrored volumes on the disk by removing the mirror that is on the Missing disk instead of the entire volume. Deleting a volume destroys the data in the volume, so you should remove a disk only if you are absolutely certain that the disk is permanently damaged and unusable.
Use the Reactivate Disk command to bring the disk back online. If the disk status remains Offline, check the cables and disk controller, and make sure that the physical disk is healthy. Correct any problems and try to reactivate the disk again. If the disk reactivation succeeds, any volumes on the disk should automatically return to the Healthy status.
The disk has been moved to your computer from another Microsoft Windows NT/2000 computer and has not been set up for use. Only dynamic disks display this status. To add the disk so that it can be used, right-click on the disk and select Merge Foreign Disk. All existing volumes on the disk will be visible and accessible.
Because a volume can span more than one disk (e.g., a mirrored volume), it is important that you first verify your disk configurations and then move the entire disk set that the volume is on. If only part of the disk set is moved, some of the volumes will show Failed Redundancy or Failed error condition.
The Help file uses a technology known as HTML Help, a Microsoft standard. Some software will attempt to update the core files with an older version of HTML Help and make Array Manager's Help file unusable. The required HTML Help update is located on the Array Manager CD-ROM in the Help Update folder. Double-click on HHUPD.EXE and follow the instructions.
HH is Microsoft's HTML Help format, which reads precompiled HTML files for Array Manager's Help sections.
Check:
Delete the HH.DAT file in your Windows directory. Deleting this file will remove any customizations that have been made to your HTML help files.
Let autocheck run, but do not worry about the message. Autocheck will finish and the reboot will be complete. If you have a large system (more than 1 gigabyte), this may take about 10 minutes.
There are several situations where this occurs.
This occurs when you log in to the local computer originally as a local user, local administrator, or domain user and the remote computer is not in your domain or a trusted domain. The Windows security model does not allow you to have access under these circumstances. The workaround is to log in to your local computer with an account that has the same user name and password as an administrator account on the remote computer.
Access can be denied here if you do not type in a user name and password that match a local or domain administrator account on the remote computer or if you mistype the login information.
If the remote computer is not on or there are network problems, you will get the message "Connection Failed."
Another situation where you may get an error message is when you have just done a client-only installation of Array Manager and you bring up the Array Manager client and attempt to connect to a remote server that has Windows 2000 Disk Management.
Array Manager assumes that its client will connect first to a remote server running Array Manager before connecting to a system running Windows 2000 Disk Management.
Once you connect to a server with Array Manager, you will then be able to connect successfully to a remote system running Disk Management.
Windows 2000 Disk Management is the disk and volume management program that comes with Windows 2000. Because Array Manager and Disk Management are related programs, Array Manager is able to remotely manage the storage on a Windows 2000 computer with Disk Management.
If you are having problems connecting to a NetWare® server, use the ping and nslookup TCP/IP network diagnostic tools to determine whether the managed node system is accessible from the console and whether the system running the managed server has a legal DNS name. If the managed server does not have a DNS name, you can check the Hosts file on the client to see whether the server is listed. Otherwise, you will need to use the IP address.
When you want to connect to a NetWare server, Array Manager expects the server to be identified by one of three types of entries:
If you identify the name of the machine by a NetWare server's name that is not one of the three items above, the connection will fail. It is suggested that the name assigned to the NetWare server be the same name as its DNS or Hosts file entry.
Note that the DNS and Hosts file entries do not allow for a computer name that consists of all numbers. In addition, the DNS name does not allow a computer name that starts with a number. If the NetWare server has a numeric name or a name that starts with a number, you can use the IP address to identify that server. You can also put quotation marks around the computer's name for the entry in DNS or the Hosts file (such as "12345").
The Hosts file has to be on the client computer that has the Array Manager console.
This section presents possible problem situations with accompanying solutions for the Dell PowerVault 660F and 224F storage systems. The problem situations are organized as follows:
The situations in the first three topics are categorized by their event number. A brief discussion of event messages is included at the beginning of this section in the topic Event Monitoring and Logging. The fourth topic describes general problems not related to a specific event.
You will also find a full listing of the events associated with the Dell PowerVault 660F RAID controller at the end of this section in the topic Dell PowerVault 660F RAID Controller Events Listing.
Event messages help identify significant incidents such as an array disk failure or an array disk addition. Event monitoring and logging starts when the Array Manager managed node starts up. If the managed node service (Disk Management Service) stops in Microsoft Windows NT or the Array Manager Service stops in NetWare, then event monitoring and logging stops. If array disks are S.M.A.R.T. (Self Monitoring Analysis and Reporting Technology) enabled, the RAID controllers check array disks for failure predictions, and if found, pass this information on to the Array Manager console. Array Manager immediately displays an alert icon on the array disk and also raises an alert under the Events tab and in the Windows NT event log. Windows NT has three event logs; the Dell OpenManage Array Manager uses the Application log.
![]() |
Note: When a controller's I/O is paused, Array Manager does not receive S.M.A.R.T. events. |
The following incidents are included in this topic:
Because of some unknown error on the controller, the rebuild has failed.
Try rescanning the controller: from the Array Manager tree view, click to expand the Arrays storage object, right-click the PV660F Subsystem object, and then select Rescan from the context menu that comes up. This action will update the controller status within the GUI.
If the controller has been removed and reinserted, check to see that the controller is inserted correctly: the DB9 connector should be located at the top of the module. For details, see the Dell PowerVault 660F and 224F Storage Systems Service Manual. Also, check that all cable connections are correctly and firmly connected. Try to rebuild again: right-click the Array Disk storage object in the tree view, and then select Rebuild from the context menu that comes up.
If controller and connections are correct and the problem continues, contact customer service.
One of the following may have occurred:
Then access the Array Manager console, click to expand the Arrays storage object, right-click the PV660F Subsystem storage object, and select Rescan from the context menu that comes up. This action will update the controller status.
A memory error was detected during the warm boot scan, which may result in possible data loss.
Power cycle the PV660F subsystem.
If the error persists:
If Enclosure Management has been enabled, check to see whether one or more LS modules has failed. LS modules are cards installed in slots at the front of the enclosure. Each LS module has an SES processor that monitors environmental functions and a Loop Redundancy Circuit (LRC) function, which maintains the viability of the Fibre Channel loop. See the Dell PowerVault 660F and 224F Storage Systems Installation and Troubleshooting Guide for troubleshooting tips.
If the controller entered Conservative Cache mode because of user's intended action, proceed per user's intent. When finished, right-click the controller and select either Enable Partner controller or Enable BBU to exit Conservative Cache mode.
If the BBU battery is low, recondition the battery. If the battery needs to be replaced, see the Dell PowerVault 660F and 224F Storage Systems Service Manual. Then access the Array Manager console, and in the tree view, click to expand the Arrays storage object, right-click the PV660F Subsystem storage object to bring up the context menu, and select Rescan. This action will update the controller.
If there is an Expand Capacity or Add Virtual Disk operation in progress, wait until this activity has finished. Then access the Array Manager console, and in the tree view, click to expand the Arrays storage object, right-click the PV660F Subsystem storage object to bring up the context menu, and select Rescan. This action will update the controller.
See also Conservative Cache Mode in the Configuring the Dell PowerVault 660F RAID Controller chapter.
![]() |
Note: Nexus refers to the state in which both redundant controllers are in communication. In this state, each controller can copy write-back data to its partner controller and can determine whether the other controller is operating. |
Go to the Array Manager console and click to expand the Arrays storage object, right-click the PV660F Subsystem storage object, and select Rescan from the context menu that comes up. This action will update the partner controller. If the situation does not improve, try one of the following (Rescan as before when necessary after troubleshooting the partner controller):
If none of these solutions apply, contact customer service.
The Media Access Control (MAC) address is corrupted.
Replace the controller according to the Dell PowerVault 660F and 224F Storage Systems Service Manual. Then go to the Array Manager console and click to expand the Arrays storage object, right-click the PV660F Subsystem storage object, and select Rescan from the context menu that comes up. This action will update the controller status.
The Media Access Control (MAC) address has been lost or was not set.
Replace the controller according to the Dell PowerVault 660F and 224F Storage Systems Service Manual. Then go to the Array Manager console and click to expand the Arrays storage object, right-click the PV660F Subsystem storage object, and select Rescan from the context menu that comes up. This action will update the controller status.
![]() |
Note: LS modules are cards installed in slots at the front of the enclosure. Each LS module has an SES processor that monitors environmental functions and a Loop Redundancy Circuit (LRC) function, which maintains the viability of the Fibre Channel loop. |
Check that the Fibre Channel cable is connected to the controller and the switch box. If not, reconnect it as necessary. If the Fibre Channel cable is connected, try replacing the cable. See the Dell PowerVault 660F and 224F Storage Systems Installation and Troubleshooting Guide for troubleshooting the LS and I/O modules.
When troubleshooting is complete, go to the Array Manager console and click to expand the Arrays storage object, right-click the PV660F Subsystem storage object, and select Rescan from the context menu that comes up. This action will update the Fibre Channel.
If problem persists, contact customer service.
The following incidents are included in this topic:
To locate a fan, right-click the bad fan and click Properties. The Enclosure ID field indicates the ID number of the enclosure where this fan is located.
See the Dell PowerVault 660F and 224F Storage Systems Installation and Troubleshooting Guide on how to troubleshoot the Advanced Cooling Module (ACM). See the Dell PowerVault 660F and 224F Storage Systems Service Manual for part replacement procedures.
After troubleshooting or replacing the ACM, go to the Array Manager console and click to expand the Arrays storage object, right-click the PV660F Subsystem storage object, and select Rescan from the context menu that comes up. This action will update the fan status within the GUI.
See the Dell PowerVault 660F and 224F Storage Systems Installation and Troubleshooting Guide on how to troubleshoot the power supply. See the Dell PowerVault 660F and 224F Storage Systems Service Manual for part replacement procedures.
![]() |
Note: LS modules are cards installed in slots at the front of the enclosure. Each LS module has an SES processor that monitors environmental functions and a Loop Redundancy Circuit (LRC) function, which maintains the viability of the Fibre Channel loop. |
After troubleshooting or replacing the power supply, go to the Array Manager console and click to expand the Arrays storage object, right-click the PV660F Subsystem storage object, and select Rescan from the context menu that comes up. This action will update the power supply status within the GUI.
Check all fans to see whether they are functioning properly. If yes, check that the ambient temperature is within limit. If necessary, adjust the room temperature. If the problem persists, power-cycle the system. If this does not solve the problem, replace the affected Advanced Cooling Module (ACM). See the Dell PowerVault 660F and 224F Storage Systems Installation and Troubleshooting Guide on how to troubleshoot the ACM. See the Dell PowerVault 660F and 224F Storage Systems Service Manual for part replacement procedures.
After fixing the temperature problem, go to the Array Manager console and click to expand the Arrays storage object, right-click the PV660F Subsystem storage object, and select Rescan from the context menu that comes up. This action will update the temperature and/or the fan status within the GUI.
The LS module connection may be broken or the management hardware is bad. LS modules are cards installed in slots at the front of the enclosure. Each LS module has an SES processor that monitors environmental functions and a Loop Redundancy Circuit (LRC) function, which maintains the viability of the Fibre Channel loop
Check to see that the LS module is enabled.
Follow the Dell PowerVault 660F and 224F Storage Systems Installation and Troubleshooting Guide for troubleshooting an LS module. For part replacement, see the Dell PowerVault 660F and 224F Storage Systems Service Manual.
After resolving the hardware problem and providing corrective action, go to the Dell OpenManage Array Manager interface and click to expand the Arrays storage object, right-click the PV660F Subsystem storage object, and select Rescan. This action will update the enclosure status within the GUI.
The enclosure has duplicate loop IDs (soft addressing).
Make sure shelf ID switches on all PV660s and PV224s in the subsystem are set to different numbers. See the Dell PowerVault 660F and 224F Storage Systems Installation and Troubleshooting Guide on how to set shelf IDs.
A battery backup unit (BBU) with a low charge was found on the controller.
If this message occurs without power failure, replace the BBU.
To replace the BBU, see the Dell PowerVault 660F and 224F Storage Systems Service Manual for part replacement procedures.
The BBU requires two reconditioning cycles prior to first time use. This reconditioning process will take several hours and cannot be interrupted. Refer to the Recondition command in the chapter Configuring the Dell PowerVault 660F RAID Controller for detailed instructions on performing a BBU recondition.
After troubleshooting or replacing the BBU, go to the Array Manager console and click to expand the Arrays storage object, right-click the PV660F Subsystem storage object, and select Rescan from the context menu that comes up. This action will update the BBU status within the GUI.
The BBU requires two reconditioning cycles prior to using for the first time. This reconditioning process will take several hours and cannot be interrupted. Refer to the Recondition command in the chapter Configuring the Dell PowerVault 660F RAID Controller for detailed instructions on performing a BBU recondition.
Recondition or replace the BBU. See the Dell PowerVault 660F and 224F Storage Systems Service Manual for part replacement procedures.
After troubleshooting or replacing the BBU, go to the Array Manager console and click to expand the Arrays storage object, right-click the PV660F Subsystem storage object, and select Rescan from the context menu that comes up. This action will update the BBU.
The following incidents are included in this topic:
Many of the incidents in this section can be resolved by replacing one or more drives. The procedure for replacing a drive is as follows:
If the virtual disk is offline, try forcing it online with the Force Online command. Right-click the disk and select Force Online from the context menu that appears. See the Force Online command in the chapter Configuring the Dell PowerVault 660F RAID Controller for detailed instructions.
If you cannot force the virtual disk online, remove and replace the affected hard drive. See the topic Procedure for Replacing a Drive at the beginning of this section for instructions on replacing a drive.
If you still get a hard disk error after replacing the drive, contact customer service.
A hard disk predicted a future failure condition. This disk may fail soon.
Replace and rebuild the drive. See the topic Procedure for Replacing a Drive at the beginning of this section for instructions on replacing and rebuilding a drive.
If the rebuild was cancelled, that disk will remain in an unusable state until a successful rebuild has been performed on it.
See Rebuild in the chapter Configuring the Dell PowerVault 660F RAID Controller for instructions.
Try to rebuild the drive again. See Rebuild in the chapter Configuring the Dell PowerVault 660F RAID Controller for instructions.
If the problem persists, replace the disk drive. It may be helpful to look at the other events that were generated in order to identify the malfunctioning drive.
See the topic Procedure for Replacing a Drive at the beginning of this section for instructions on replacing a drive.
It may not be possible to recover from this error; therefore, you may lose your virtual disk.
Try to rebuild the virtual disk. See Rebuild in the chapter Configuring the Dell PowerVault 660F RAID Controller for instructions.
If the problem persists, contact customer service.
A hard disk failed because the user either changed the status to Offline or removed the hard disk.
A drive is usually manually taken offline to replace it. If the drive was physically removed from the enclosure, replace and rebuild the drive (using a drive at least as large as the other disk drives in the virtual disk).
See the topic Procedure for Replacing a Drive at the beginning of this section for instructions on replacing and rebuilding a drive.
If the drive has been removed or has failed, replace the drive.
If the time-out cannot be reset on the existing array disk, replace the disk.
See the topic Procedure for Replacing a Drive at the beginning of this section for instructions on replacing and rebuilding a drive.
It may be necessary to do a complete reboot after the drive is replaced.
If you need more help, contact customer service.
Check all cables, making sure they are correctly and firmly connected and that none are crossed. See the Dell PowerVault 660F and 224F Storage Systems Installation and Troubleshooting Guide for cabling procedures.
Replace the affected disk. See the topic Procedure for Replacing a Drive at the beginning of this section for instructions on replacing and rebuilding a drive.
The array disk encountered too many errors, causing the drive to fail and its status to change to Offline.
It is not possible to recover this physical drive. Replace the disk drive. See the topic Procedure for Replacing a Drive at the beginning of this section for instructions on replacing and rebuilding a drive.
If the replacement drive still does not work, contact customer service.
Drive failed to spin up during controller bootup.
Check that the new array disk is seated properly. If not, remove and reinsert the disk.
If the problem persists, see the Dell PowerVault 660F and 224F Storage Systems Installation and Troubleshooting Guide on how to troubleshoot the Fibre Channel hard disk drives.
When completed, go to the Array Manager console and click to expand the Arrays storage object, right-click the PV660F Subsystem storage object, and select Rescan. This action will update the array disk status within the GUI.
A previously configured array disk no longer appears in the Array Manager GUI.
Make sure that all enclosures are powered on.
Remove and reinsert the physical drive. Then go to the Array Manager console and click to expand the Arrays storage object, right-click the PV660F Subsystem storage object, and select Rescan to verify that the replacement drive has been recognized.
If the drive is still missing or not found, try replacing the drive. See the topic Procedure for Replacing a Drive at the beginning of this section for instructions on replacing and rebuilding a drive.
If the replacement drive does not work, contact customer service.
Communication to a drive on a particular channel has failed.
If this event appears for all existing drives, then a Loop ID problem may be present. See the Dell PowerVault 660F and 224F Storage Systems Installation and Troubleshooting Guide on how to troubleshoot the I/O module.
If the drive has failed, replace the drive. See the topic Procedure for Replacing a Drive at the beginning of this section for instructions on replacing and rebuilding a drive.
If the replacement drive does not work, contact customer service.
Try performing a Consistency Check again. If the problem persists, replace the disk drive. It may be helpful to look at the other events that were generated in order to identify the malfunctioning drive. See the topic Procedure for Replacing a Drive at the beginning of this section for instructions on replacing and rebuilding a drive.
![]() |
Note: A virtual disk that is Critical will be shown as Degraded status within the Array Manager console. |
Try performing a consistency check again. If the problem persists, replace the disk drive(s). It may be helpful to look at the other events that were generated in order to identify the malfunctioning drive(s). See the topic Procedure for Replacing a Drive at the beginning of this section for instructions on replacing and rebuilding a drive.
An array disk failed.
Replace the affected disk. See the topic Procedure for Replacing a Drive at the beginning of this section for instructions on replacing and rebuilding a drive.
If you have a non-fault-tolerant virtual disk, a single array disk failure may have caused the virtual drive to go offline. If you have a fault tolerant virtual disk, multiple array disk failures may have caused the virtual drive to go offline.
Try making the virtual drive Online.
Verify through the LED lights that power is supplied to the enclosure.
Identify the location of the failed drive(s). If necessary, refer to the Dell PowerVault 660F and 224F Storage Systems Installation and Troubleshooting Guide.
Replace the array disk(s) if necessary. See the topic Procedure for Replacing a Drive at the beginning of this section for instructions on replacing and rebuilding a drive.
It may not be possible to recover from this error. Contact customer service.
One fault tolerant virtual disk has been degraded.
Replace the array disk. See the topic Procedure for Replacing a Drive at the beginning of this section for instructions on replacing and rebuilding a drive.
Reinsert the controller and power on the system and/or the controller.
Initialize the virtual disk manually. See the Initialize command in the chapter Configuring the Dell PowerVault 660F RAID Controller for instructions.
When completed, go to the Array Manager console and click to expand the Arrays storage object, right-click the PV660F Subsystem storage object, and select Rescan to verify that the virtual disk has been initialized and is recognized.
Replace the array disk. See the topic Procedure for Replacing a Drive at the beginning of this section for instructions on replacing and rebuilding a drive.
Replace the array disk. See the topic Procedure for Replacing a Drive at the beginning of this section for instructions on replacing and rebuilding a drive.
See Expand Capacity in the chapter Configuring the Dell PowerVault 660F RAID Controller for more information.
A bad sector was found on an array disk during one of the following operations: consistency check, rebuild, or RAID expansion.
For information on consistency check and rebuild functions, see Check Consistency and Rebuild in the chapter Configuring the Dell PowerVault 660F RAID Controller.
If the problem persists, replace the hard disk. See the topic Procedure for Replacing a Drive at the beginning of this section for instructions on replacing and rebuilding a drive.
This section contains the following general problem situations:
The Assign Global HotSpare function will be selectable only when disks are available within the system.
Add drives to the system. See the topic Dell PowerVault 660F and 224F Storage Systems Installation and Troubleshooting Guide for instructions on adding new drives.
After adding the new drives, go to the Array Manager console and click to expand the Arrays storage object, right-click the PV660F Subsystem storage object, and select Rescan.
This action will update the drive status within the GUI. You are now ready to create a hot spare.
Make sure that the situation you have supports the Expand Capacity command. See Expand Capacity in the chapter Configuring the Dell PowerVault 660F RAID Controller for more information.
A virtual disk has not been made visible to the operating system.
For a direct connect, reboot the system to recognize the virtual disk.
For a SAN connection, two steps must be performed after creating a virtual disk before the virtual disk will appear in the Disks folder.
Once these two steps have been performed, the virtual disk will appear in the Disks folder of the Array Manager console.
All of the available space on the NT disk has already been used in the creation of one or more volumes for that disk. A volume cannot be created on an NT disk when there is no available used space.
Add a new virtual disk or expand the capacity of the existing array disk. See Add Virtual Disk and Expand Capacity in the chapter Configuring the Dell PowerVault 660F RAID Controller for more information.
A volume that has been marked as a primary partition cannot be deleted. Primary partitions are protected because they contain a bootable operating system.
To override this protection feature, delete the virtual disk that the primary partition belongs to. See Delete Virtual Disk in the chapter Configuring the Dell PowerVault 660F RAID Controller for detailed instructions.
Only the last virtual disk that was created can be deleted.
Delete the virtual disks in the reverse order that they were created. See the topic Delete Virtual Disk in the chapter Configuring the Dell PowerVault 660F RAID Controller for detailed instructions.
The partner controller has different firmware. This may occur during the replacement of a failed controller.
Both controllers must have the same version of firmware to operate in a redundant configuration. If a failed controller is replaced with a controller with a different version of firmware, the replacement controller will not be allowed to start and will be disabled by the existing controller.
Use the following procedure to download a common firmware image:
![]() |
Note: If an empty enclosure is available, the firmware can be downloaded to the replacement controller without having to power off the subsystem. However, this will not work if the replacement controller has more recent firmware. |
The Enclosure Management Advanced controller option is disabled.
Change the Enclosure Management Advanced controller option to enabled. See the Advanced Controller Options section of the Configuring the Dell PowerVault 660F RAID Controller chapter for details.
If the Enclosure Management Advanced controller option is already enabled, perform a Rescan on the PV660F Subsystem storage object. If this isn't successful, perform a Reset on the controller object. See the Reset command in the Configuring the Dell PowerVault 660F RAID Controller chapter for details.
This table describes the events that are generated by the controller. The events are displayed in the Events tab of the Array Manager console or through Windows NT Event Viewer or Windows 2000 Event Viewer.