6.3 HP StoreAll 9300/9320 Storage Administrator Guide (AW549-96072, June 2013)

Mounted drive not visible when using Terminal Server
Refresh the browser's view of the system by logging off and then logging back on.
StoreAll client auto-startup interferes with debugging
The StoreAll client is set to start automatically, which can interfere with debugging a Windows
StoreAll client problem. To prevent this, reboot the machine in safe mode and change the Windows
StoreAll 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 StoreAll 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 StoreAll 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 “Monitoring cluster health” (page 95).
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
of the Express Query, they are typically due to another unrelated event in the cluster or the file
system. Therefore, most of the work to recover from an Express Query MIF is to check the health
of the cluster and the file system and take corrective actions to fix the issues caused by these events.
Once the cluster and file system have an OK status, the MIF status can be cleared since the Express
Query service will be recovering and restarting automatically.
Synchronizing information on file serving nodes and the configuration database 141