severity: sfdsk: internal error, details
Explanation
Internal error occurred. details indicates the cause of the error.
severity indicates the severity of the message.
a) If part of or all of the disks registered with the root class are not recognized by the OS at OS startup, the following error message may be output.
ERROR: sfdsk: internal error, func=gds_dev_open(*,*,*) FAIL
b) If the major number 487 is already in use, the following message may be output at system startup.
ERROR: sfdsk: internal error, func=register_blkdev(sfdsk), errno=16
c) In the environment where the mirroring among servers is used, the following message may be output at node startup. (Values will be output to X)
ERROR: sfdsk: internal error,func=ioctl(dev=XXX,XXX, cmd=0xXXXXXXXX) FAIL(-19) proc=sdxservd(XXX)
d) When the sdxfix -C command is executed, the following message may be output.
dev indicates the device number of the disk.
WARNING: sfdsk: internal error, cannot get disk offset. dev=0xNNNNNNNN, cmd=HDIO_GETGEO, errno=5Resolution
In the event of a), the error has no effect on the system. Restore the state where the disks are recognized by the OS and reboot the system, and the message will no longer be output.
In the event of b), change the sfdsk driver major number to a number other than 487. For the major number changing method, see "8.8.1 Changing sfdsk Driver Major Number."
In the event of c), the system may have been in any one of the following status:
(c-1)
Status: Another node has been stopped.
Resolution: The error has no effect on the system. No action is required.
(c-2)
Status: An error has occurred in the network used in the mirroring among servers.
Resolution: Restore the network error.
In the event of d), a disk failure may have occurred. Check the disk of the displayed device number output to dev, and restore the disk if it has an error.
In other events, collect investigation material and contact field engineers.
sfdsklog: internal error, details
Explanation
Internal error occurred. details indicates the cause of the error.
a) If the major number 234 is already in use at system startup, the following message may be output on the system log.
sfdsklog: internal error, func=register_chrdev(sfdsklog) fail(-16)
At that time, loading the sfdsklog driver in GDS fails and GDS is not started. Therefore, the shared disk resource registration (clautoconfig command), GDS operation and accessing to the GDS volume fail.
Resolution
In the event of a), change the sfdsklog driver major number to 300 or higher.
For the sfdsklog driver major number changing method, see "8.8.2 Changing sfdsklog Driver Major Number."
In events other than a), collect investigation material and contact field engineers.