This topic explains how to identify when lost logical unit numbers
(LUN) are preventing the metadata server from starting correctly.
Context
This problem can occur in situations such as a recent complete power
failure, and when the metadata LUNs were not available at the time that the
metadata server started. Use the following steps if you attempted to start
the metadata server using the startserver command, and the metadata
server did not start:
Steps
- View log.std to determine the cause of the problem.
- Search for a message that reads, "No master disk found." If you find the message, continue with the next step. Otherwise,
this is not the problem.
- Search for a message that begins, "Tank.Bootstrap
file does not match." If you find the message,
continue with the next step. Otherwise, this is not the problem.
- Make sure that you have Subsystem Device Driver installed
on the metadata server.
- Run the lsvpcfg command to determine if you have the required
LUNs. If no LUNs are listed or the list is incomplete, continue
with the next step.
- Restart the system to find any available storage LUNs.
- Contact your support representative if the LUNs are still not available.