command: severity: module: internal error, details
Explanation
An internal error occurred.
details gives you the cause of the error, command the command name, severity the severity of message, and module the module name (usually the internal function name) where the event was detected.
a) The following message may be output if the sdxcopy -C command is executed at node startup or during GDS command execution. If the sdxcopy -C command has ended normally (the exit status is 0), there is no problem.
sdxcopy: ERROR: SDX_COPY_STATUS_WAIT2: internal error, sdxerrno=145
b) If the sdxvolume -M command is executed when I/O to the physical disk is disabled due to a failure or other causes, the following message may be output.
sdxvolume: ERROR: internal error (mv_create,sdxerrno=0)
c) If the sdxdisk -M command is executed when I/O to the physical disk is disabled due to a failure or other causes, the following message may be output.
sdxdisk: ERROR: internal error (td_regist,sdxerrno=4207)
d) If the sdxdisk -R command, the sdxconfig Remove command, or the sdxclass -R command is executed when I/O to the physical disk is disabled due to a failure or other causes, the following message may be output.
command: ERROR: internal error (td_delete,sdxerrno=4120)
Resolution
In the event of a), if the exit status of the sdxcopy -C command is 0, the message a) may be ignored. For the sdxcopy -C command's exit status, refer to the following message recorded in the sdxservd daemon's log file /var/opt/FJSVsdx/msglog/sdxservd.log.
SDX:sdxservd: INFO: command exited, exit-status=exitstat: sdxcopy -C -c class -v volume,...
In the event of b) or c), check the physical disk status and the I/O route status. If an error exists, restore the error and then execute the command again.
In the event of d), the class is closed. Follow "(1) Class becomes closed status during operation." in "D.1.4 Class Status Abnormality."
In other events, collect investigation material and contact field engineers.
