This section provides suggestions for and information about alternative troubleshooting tools and techniques.
Ping Your NAS System
If you are unable to connect to the NAS system using the NAS Manager, try to ping the NAS system. From a client system, click the Start button, click Run, and then type cmd. At the command prompt in the cmd.exe window, type ping system_name, and then press <Enter>.
NOTE: The default system name is DELLxxxxxxx, where xxxxxxx is the system's service tag number. For
example, if your service tag number is 1234567, type http://DELL1234567. You can also access the
system directly through secure port 1279 by connecting to https://DELLxxxxxxx:1279, where xxxxxxx is the
system's service tag number.
If you can ping the NAS system but cannot access it through the NAS Manager, your NAS system might still be booting into the Windows® Storage Server 2003 operating system and might not have started the Microsoft® Internet Information Services (IIS).
NOTE: It may take several minutes for the NAS system to boot, depending on your configuration and the
amount of storage attached to the system.
My Network Places
If you have a client system running Windows 2000, Windows 2003, or Windows XP on the same subnet as the NAS system, double-click My Network Places. Browse through the network and locate your NAS system.
System LEDs and Beep Codes
If your NAS system is not booting or responding properly, you can diagnose some problems using the system's LEDs and beep codes. For more information about the LEDs and beep codes, see your system's Installation and Troubleshooting Guide.
Remote Desktop
You can use the Remote Desktop to connect to your NAS system from a client system. You can access Remote Desktop through the NAS Manager.
To access Remote Desktop from the NAS Manager, perform the following steps:
Log in to the NAS Manager.
Click Maintenance.
Click Remote Desktop.
Enter the administrator user name and password and click OK.
NOTE: The default administrator user name is administrator and the default password is
powervault.
Troubleshooting
Use the following tables to help you troubleshoot various conditions that might occur on your NAS system:
Table 10-5, "Hardware-RAID NAS System Internal RAID Controller Card"
NOTE: Some of the procedures refer to a software-RAID, a hardware-RAID, and an external storage
configuration NAS system. For instructions on how to determine the configuration of your NAS system,
see "Determining a NAS System's Configuration" in "NAS Manager."
Table 10-1. General Troubleshooting
Issue
Possible Cause
Resolution
I just created a new volume on my system but cannot see the volume on Windows Explorer through Remote Desktop.
Remote Desktop cannot update to show a new volume during the session in which it was created.
Log off Remote Desktop. When you reconnect to Remote Desktop, the volume should be visible.
I see the following error message in the event log:
WMI ADAP was unable to load the winspool.drv performance library due to an unknown problem within the library: 0x0
This is an issue with the WDAP Performance library and is documented on Microsoft's website.
Connect to the system via Remote Desktop, and then open a local command prompt. Type the following command: WINMGMT/CLEARADAP. When the prompt returns, type WINMGMT/RESYNCPERF winmgmt service PID.
I have just enabled FTP services on my NAS system, but I am unable to upload files using FTP even though I am the administrator.
By default, no user has write privileges on the default FTP site.
The FTP permissions must be configured using the Microsoft Management Console (MMC). To access the MMC, log into Remote Desktop. Right click My Appliance, and select Manage.Double-click internet Information Services, and then right-click FTP Sites. Set the permissions in the FTP Sites Properties window.
I have deleted an FTP share and folder from my NAS system. However, when I use Remote Desktop to confirm the removal, I can still see the shared folder in the FTP section of the MMC.
By default, this folder is not deleted by the NAS Manager.
Manually remove this listing from the listed shared folders in the FTP section of the MMC.
I cannot connect to or ping the NAS system after turning it on.
The NAS system has not finished booting.
Wait at least 5 minutes for the NAS system to finish booting.
I cannot connect to the NAS system using the IPX protocol.
IPX networks require that you assign an IPX network number to all clients. By default, the NAS system does not assign an IPX number to the network.
Change the IPX protocol on the NAS system to manually detect frame types. See "Configuring the IPX Protocol" in "Advanced Features."
After restoring files from a backup, the modified dates of folders are inconsistent.
The modified dates of folders reflect either the date you performed the restore or the date the folder was modified.
Do not take action. This design issue occurs only with folders; the files' modified dates are consistent.
When connecting to my NAS system using Remote Desktop, I receive a message that the Terminal Server has exceeded the maximum number of allowed connections.
The NAS system supports only two current Remote Desktop sessions at a time.
Log off of the other Remote Desktop sessions.
The system summary and the task manager show twice as many processors as are actually installed in the system.
The NAS system provides a hyperthreading option, which allows one physical processor to appear to the operating system and other applications as two logical processors.
Do not take action. Your NAS system is operating correctly.
The NIC LED on the front panel of the NAS system is not lit.
A network connection problem exists.
Ensure that a network cable is properly connected to one of the NIC connectors on the back panel of the NAS system. Do not use a crossover cable. If the NIC LED is still not lit, see "Troubleshooting an Integrated NIC" in your system Installation and Troubleshooting Guide.
The monitor screen is blank when connected to the NAS system.
The video cable may not be connected securely or the monitor may be faulty.
Inspect the video cable connection and ensure that the cable is connected properly to the NAS system.
Try to connect to the NAS Manager using a client system. If the client system is able to connect to the NAS Manager, replace the monitor.
All four hard-drive operation LEDs on the NAS system are blinking green.
The green flash pattern indicates that the RAID volumes are being rebuilt.
Wait at least 5 minutes, and then try to reconnect to the NAS system.
The NAS system may not be booting properly.
You may not be allowing enough time for the NAS system to boot or a system alert may be occurring.
The NAS system requires at least 5 minutes to boot.
Connect a monitor to the NAS system or use console redirection to view the boot routine of the system. If a system alert occurs (system message, beep code, or amber hard-drive LEDs) during boot, see "Indicators, Messages, and Codes" in the Installation and Troubleshooting Guide for information on resolving the problem.
Power-on self test (POST) does not occur when the system is turned on or rebooted, but a beep code is heard.
A number of conditions can cause a beep code during POST.
Write down the number of beeps, and see "Indicators, Messages, and Codes" in the Installation and Troubleshooting Guide for information on resolving the problem.
POST does not occur when the NAS system is turned on or rebooted, and a beep code does not occur.
The BIOS may need to be updated, or a memory module or microprocessor needs to be reseated or replaced.
Without disconnecting the power source, reboot the NAS system by pressing <Ctrl><Alt><Delete>. You may need to repeat this key combination several times. If the system now POSTs, upgrade the BIOS to the latest version.
If the system still does not POST, try booting the system with each individual memory module. See the Installation and Troubleshooting Guide for more information. If the system does not boot with a certain memory module installed, then that module is defective.
If the system does not POST with any of the memory modules, reseat the processor as explained in the Installation and Troubleshooting Guide. If the system does not boot, try replacing the processor with a working processor. If the system does not boot, the system board may be defective. See "Getting Help" in the system Installation and Troubleshooting Guide.
I do not know the name of my NAS system.
The name of the NAS system can be viewed in My Network Places.
Double-click My Network Places on the desktop of the client system and look for NAS system name. The default name for the NAS system is DELLxxxxxxx, where xxxxxx is the system's service tag. For example, if the service tag is 1234567, the system name is DELL1234567. You can find the service tag on the top cover of the NAS system.
After using Remote Desktop to connect to my NAS system, I am unable to type using my native language.
The NAS system is set to English, the default language.
Most character sets are installed by default on your system. If your language character set is not installed, you can install your native language character set from the Multilingual Support CD that was shipped with your system. For installation instructions, see "Advanced Features."
The NAS system is attached to a DHCP network, but I cannot connect to it through the NAS Manager.
The DHCP server may have issued a new DHCP address to the NAS system.
If the NAS system has been powered down for a period of time predetermined by the DHCP server, the NAS system acquires a new DHCP address from that server. The DHCP server may not have yet replicated the new address with the NAS system name.
Wait approximately 15 minutes for the address to be replicated and then try connecting again or try connecting to the NAS system again using the IP address.
I cannot connect to the NAS system using a static IP address.
A NAS system has been moved to a new network or new subnet and I cannot connect.
The connection settings may need to be refreshed.
If the NAS system is using DHCP, open a command line on the system and use the ipconfig utility to release and renew the IP address.
If DHCP is not being used, verify that all NAS system network interface settings are correct.
After reinstallation, a message displays that says An error has occurred during installation. Please see the Windows Event Log for details.
Either an error occurred while installing a component during the reinstallation or the reinstallation was interrupted.
See the Windows Application Event Log and the c:\dell\install\error.tag file to determine which error occurred during the reinstallation, and then reinstall your system again.
When you try to open the Shares page using the NAS Manager, the page times out.
Depending on the configuration of your client system, the Shares page may time out when the number of shares exceed 20,000 shares.
Change the settings of your client system or manage large numbers of shares through Remote Desktop.
Table 10-2. NAS Manager
Issue
Possible Cause
Resolution
I am trying to select the Administer My Appliance link on the opening page of the NAS Manager, but the link does not function properly.
The user account that you used to log in to the domain does not have administrator privileges. The link does not work for users without administrator privileges.
Type the address of the NAS Manager in your browser. For SSL connections, type: https://servername:1279 or https://IPaddress:1279
I have just deleted a volume, and now I am unable to view my shares in the NAS Manager.
If a volume with shares is deleted, then the NAS Manager cannot display any shares until the shares that were directed to the deleted volume are removed.
Use Remote Desktop to remove the shares for the deleted volume. Exit the NAS Manager, and restart the system. The shares should now be visible.
I have just added an HTTP share but cannot see it from the NAS Manager.
For security purposes, directory browsing is not enabled by default on an HTTP share directed to the same folder or volume as another share.
To enable directory sharing for an HTTP share, from the NAS Manager Maintenance page, click Remote Desktop, and then modify the Web sharing properties of the folder.
I have just changed the IP address of my system, and now I cannot administer it through the NAS Manager.
Although the IP address changed, your local host is still trying to communicate with the system using the old IP address. It takes approximately 15 minutes for the IP address to automatically update on most networks.
Close Microsoft Internet Explorer. Reconnect using the newly created IP address. Type: https://IPaddress:1279. It takes approximately 15 minutes for the DNS server to recognize the new IP address.
I can only see the first 100 items in the NAS Manager Web user interface.
The NAS Manager will only display 100 items per page.
To display the next 100 items, click the down-arrow icon at the top of the list.
In the NAS Manager, if I click OK and then click Cancel, it doesn't seem to cancel the operation.
Clicking Cancel does not dynamically stop an update to the system after you click OK.
If an operation has been performed in error, the system administrator must change the setting back manually.
When I select the Check All box and then deselect one or more choices on some screens in the NAS Manager, the Check All box remains selected.
The Check All box is not automatically deselected. However, this does not mean that all items in the list are selected.
This behavior does not affect functionality. The Check All box does not indicate what has specifically been selected or deselected.
I have changed the password for the administrator account; however, several minutes have passed and I have not been prompted for the new password.
The NAS Manager does not automatically refresh the account information for the administrator while in the NAS Manager. Instead, it performs the refresh as a timed function.
The password was successfully changed. If you want to confirm that the new password is in effect, close the browser, and then reconnect. The new password should work, but the old one should not.
I am looking for a topic on the context-sensitive online help in the NAS Manager, but it says No Topic Available.
Some sections of the NAS Manager do not have context-sensitive help.
For information on a specific function, see the Windows Storage Server 2003 Help, which is available by logging into a Remote Desktop Session and clicking the Start button and selecting Help and Support. You can also see the appropriate section in this Administrator's Guide.
I tried to clear the FTP log or the Web (HTTP) Shares log in the Maintenance section of the NAS Manager, but I received an error message and the log was not cleared.
The logs are currently locked by the NAS system for the FTP service and to support the NAS Manager. The logs cannot be cleared in the NAS Manager.
Connect to the NAS system using Remote Desktop and clear these logs by using Microsoft Management Console (MMC). You can access MMC by logging into a Remote Desktop session and then right-clicking My Appliance and selecting Manage.
While viewing the properties of a user, I selected the General tab. The fields for this user are now all blank.
You were already on the General tab and the page did not refresh properly.
Select Cancel or click Back on your browser. Reselect the user for whom you want to view properties.
I added members to a local group using the NAS Manager, but when I click OK, the screen only refreshes.
You might have removed and then added the same member to the local group. This may cause the screen to refresh instead of update correctly.
Reselect the Local Groups tab in the NAS Manager primary menu. Add or remove the appropriate members to or from the local group.
I cannot change the WINS addresses when I click Network on the NAS Manager primary menu, click Network Interfaces, and then click WINS in the Tasks list.
The NAS Manager grays out the WINS Servers Configuration page unless you set the IP Address Configuration page to Use the following IP settings.
To set the WINS addresses from the NAS Manager, click Network on the primary menu, click Interfaces, and click IP in the Tasks list. On the IP Address Configuration page, click the radio button for Use the following IP settings, and then type the IP address, Subnet mask, and the default gateway in the appropriate text boxes.
In the column for the percent used on the Shadow Copies page, the percentage of space used appears to be inaccurate.
You need to verify the amount of space being used by Shadow Copy.
To verify how much space Shadow Copy is using, select a volume, and then select Properties. This page displays the amount of space used by Shadow Copy on that volume.
Table 10-3. Server for NFS
Issue
Possible cause
Resolution
I cannot access the NAS Manager from my Red Hat® Linux client system.
The NAS Manager is not supported by the Red Hat Linux operating system and does not work with the NAS Manager.
Use a client system running Windows to connect to the NAS Manager.
While updating client access to an NFS share, the No Access option is displayed, but the Root option is not.
Only the All Machines category options are displayed during this update.
Add the appropriate client systems, and then select OK. After you have added the client system, navigate back to the NFS tab for this share and select the correct options for the individual Client Machines.
Every time I try to obtain a directory listing from an NFS client on the root of a system volume, I get an error message, such as Permission Denied.
The problem you are experiencing involves a System Volume Information directory created by Microsoft Index Server. The NFS service does not have access to this directory and returns an error message to the client when trying to list its properties.
This issue only occurs when sharing the root of a drive letter.
Ignore this error. The System Volume Information directory is not used by NFS clients or your system by default.
When updating the client system's access to an NFS share, the All Machines client group is reset from the No Access access type to Read-Write access.
The NAS Manager might reset the All Machines client system's group to Read-Write when the client systems do not have read-only or read-write access.
Add a client system that has read-write or read-only access, and then set the All Machines client system group to No Access.
My NAS system is experiencing low NFS performance.
NFS write-back cache is disabled.
If your system is not part of a cluster, you can enable NFS write-back cache to improve performance. See "Advanced Features" for more information.
The NFS client system group All Machines is reset to No Access when another client system group is set with the same access permissions and root.
Setting a client group to use the same permissions as All Machines causes All Machines to be reset to No Access.
Access the NAS system's desktop and modify the NFS share properties of the folder directly.
I am getting inconsistent map definitions when I use the NAS Manager and the MMC to create user name maps.
Modifications to user name maps are cached and may not take effect immediately.
Use only one tool to administer user name maps.
Table 10-4. Macintosh and AppleTalk
Issue
Possible cause
Resolution
I cannot create AppleTalk shares on a new NAS system.
AppleTalk protocol is not enabled by default on new or reinstalled systems.
From a Macintosh client, users cannot modify or delete a file that a Windows client has accessed.
The time between clients and the system is not properly synchronized.
Ensure that clients have their time synchronized to within 10 minutes of the time zone.
After modifying properties of the AppleTalk protocol, File Services for Macintosh does not restart.
File Services for Macintosh can not establish communication to the local Remote Procedure Call (RPC) service.
Restart the workstation service.
A user cannot access an AppleTalk share.
The share may need to be authenticated for the user.
If Apple Authentication is used, create a user and assign an 8-character (or less) password for authentication.
If Microsoft Authentication is used, ensure that the correct user name and password are being used. The user may also not have the correct privileges to access the share. Passwords greater than 8-characters are not supported without a Microsoft Authentication agent.
NOTE: Table 10-5 provides hardware-RAID NAS system-specific troubleshooting information.
Disregard this information if you have a software-RAID or an external storage NAS system.
For instructions on how to determine the configuration of your NAS system, see "Determining a NAS
System's Configuration" in "NAS Manager."
Table 10-5. Hardware-RAID NAS System Internal RAID Controller Card
Issue
Possible cause
Resolution
The LED on a hard drive on my NAS system is blinking amber.
A hard drive is offline on the CERC SATA controller, which is most likely caused by a failed hard drive.
Shut down the NAS system. Ensure that the power and data cables are correctly connected to the hard drive. Boot the system. If the hard drive still fails, run Dell online hard drive diagnostics. See the Dell OpenManage Server Administrator documentation on the system's Resource CD for more information about how to run the diagnostics. If the application fails, replace the hard drive.
The NAS system hangs during POST.
The controller is not being detected.
Shut down the NAS system. Check the PCI riser card connection to the CERC SATA card and ensure that it is seated correctly. Also check the cable and power connections for the hard drives.
If the system still hangs, perform the following steps:
Shut down the NAS system.
Check the PCI riser connection to the CERC SATA card.
Try installing the CERC SATA card in the other PCI slot (if available).
If the system can now see the card, replace the riser card.
The CERC SATA card cannot see any hard drives attached to the system.
The hard drives are not connected correctly.
Shut down the NAS system. Reseat the CERC SATA card and make sure that power and data cables from each of the hard drives are connected to the CERC SATA card correctly.