Table of Contents
Advertisement
Windows 9000 clients
Logged in but getting a "Permission Denied" message
The 9000 client cannot access the Active Directory server because the domain name was not
specified. Reconfigure the Active Directory settings, specifying the domain name. See the
9000 Storage Installation Guide
Verify button in the Active Directory Settings tab does not work
This issue has the same cause as the above issue.
Mounted drive does not appear in Windows Explorer
To make a drive appear in Explorer, after mounting it, log off and then log back on, or reboot the
machine. You can also open a DOS command window and access the drive manually.
Mounted drive not visible when using Terminal Server
Refresh the browser's view of the system by logging off and then logging back on.
9000 client auto-startup interferes with debugging
The 9000 client is set to start automatically, which can interfere with debugging a Windows 9000
client problem. To prevent this, reboot the machine in safe mode and change the Windows 9000
client service mode to manual, which enables you to reboot without starting the client.
1.
Open the Services control manager (Control Panel > Administrative Tools > Services).
2.
Right-click 9000 client Services and select Properties.
3.
Change the startup type to Manual, and then click OK.
4.
Debug the client problem. When finished, switch the Windows 9000 client service back to
automatic startup at boot time by repeating these steps and changing the startup type to
Automatic.
Synchronizing information on file serving nodes and the configuration
database
To maintain access to a file system, file serving nodes must have current information about the file
system. HP recommends that you execute ibrix_health on a regular basis to monitor the health
of this information. If the information becomes outdated on a file serving node, execute ibrix_dbck
-o to resynchronize the server's information with the configuration database. For information on
ibrix_health, see
NOTE:
The ibrix_dbck command should be used only under the direction of HP Support.
To run a health check on a file serving node, use the following command:
ibrix_health -i -h HOSTLIST
If the last line of the output reports Passed, the file system information on the file serving node
and Fusion Manager is consistent.
To repair file serving node information, use the following command:
ibrix_dbck -o -f FSNAME [-h HOSTLIST]
To repair information on all file serving nodes, omit the -h HOSTLIST argument.
Troubleshooting an Express Query Manual Intervention Failure (MIF)
An Express Query Manual Intervention Failure (MIF) is a critical error that occurred during Express
Query execution. These are failures Express Query cannot recover from automatically. After a MIF
occurrence the specific file system is logically removed from the Express Query and it requires a
manual intervention to perform the recovery. Although these errors inhibit the normal functionality
for more information.
"Monitoring cluster health" (page
Synchronizing information on file serving nodes and the configuration database 135
77).
HP IBRIX
Advertisement
Table of Contents
Troubleshooting
