ERROR: connection timeout
Explanation
Connection failed due to no response from sdxservd daemon.
Resolution
Confirm that sdxservd daemon process was started normally.
ERROR: not privileged
Explanation
Executed user is not a superuser.
Resolution
You need to have superuser authority for execution.
ERROR: option: illegal option
Explanation
option is illegal.
Resolution
See the Fix Messages described later, or the "Appendix B Command Reference."
ERROR: syntax error
Explanation
Executed command has a syntax error.
Resolution
See the Fix Messages described later, or the"Appendix B Command Reference."
ERROR: string: name too long
Explanation
Object name, file name or node identifier specified with string is too long.
Resolution
Specify the proper name.
ERROR: object: name contains invalid character "letter"
Explanation
Object name object contains an invalid character letter.
Resolution
You can only use alphanumeric characters, "-" (hyphen), and "_" (underscore) when specifying an object name.
ERROR: object: name starting with "_" or "-" is invalid
Explanation
Object name object starting with "-" (hyphen) or "_" (underscore) is invalid.
Resolution
Specify an object name that starts with an alphanumeric character.
ERROR: device: illegal physical disk name
Explanation
Physical disk name device is illegal.
Resolution
See "Appendix B Command Reference."
ERROR: object: object names must be unique within a class
Explanation
Object names within a class must be unique.
Resolution
Specify a unique object name.
ERROR: module: environment error, details
Explanation
The command cannot be executed due to an error in the environment. The error causes only a failure in command execution but has no effect on the system. Volumes can be accessed continuously.
module is the name of the module on which this event was detected (usually an internal variable name).
details indicates the error in detail.
Resolution
Collect investigation material and contact field engineers.
ERROR: class is a shadow class
Explanation
The class class is a shadow class. The attempted operation is not supported for shadow classes.
Resolution
See "Appendix B Command Reference," and specify a correct command name and class name.
ERROR: attribute: invalid attribute name
Explanation
The same attribute has already been specified.
Resolution
See "Appendix B Command Reference."
ERROR: attribute: attribute name duplicated
Explanation
The same attribute attribute has already been specified.
Resolution
You can only specify an attribute once.
ERROR: attribute=value: invalid attribute value
Explanation
Attribute value value is invalid.
Resolution
See "Appendix B Command Reference."
If "pslice=off: invalid attribute value" is output, the possible cause is that the FJSVsdx-bas package of GDS may not be installed normally. If this is the cause, reinstall FJSVsdx-bas.
ERROR: node: node name duplicated
Explanation
The same node identifier has already been specified.
Resolution
You can only specify a node identifier once.
ERROR: too many nodes in scope
Explanation
There are too many nodes specified in scope.
Resolution
Up to 4 nodes can be specified in a scope.
ERROR: class: cannot operate shared objects, cluster control facility not ready
Explanation
Cannot operate shared objects since cluster control is not operating.
Resolution
Start cluster control and try again.
ERROR: node: remote node cannot be specified for local class
Explanation
A remote node was specified for a local class.
Resolution
Specify the node identifier of the current node for a local class.
ERROR: node: remote node cannot be specified for root class
Explanation
A remote node was specified for a root class.
Resolution
Specify the node identifier of the current node for a local class.
ERROR: current node must be specified as scope
Explanation
Current node is not specified for shared class scope.
Resolution
Always specify a node set which includes current node as scope.
ERROR: multi-nodes must be specified for shared class
Explanation
Only one node is specified for shared class scope.
Resolution
Multiple node identifiers must be specified in a scope.
ERROR: node: unknown node
Explanation
Node node does not exist.
Resolution
First check the cluster system environment. Then, try again after changing the node identifier.
ERROR: class: not shared by the current node
Explanation
Scope of class does not include the current node.
In the cluster system, class created in another node is specified.
Resolution
Execute command on a node sharing class. Or, change the specified class name.
ERROR: node: current node not active in class
Explanation
Current node node is a standby node in shared class class.
Resolution
Execute the command from another active node.
ERROR: too many disks in class
Explanation
There are too many disks registered with class.
Resolution
Create a new class.
ERROR: device: not connected to node
Explanation
The physical disk device has not been connected to the node node, or device has not been registered with the cluster resource database.
Resolution
Check the system configuration and the resource configuration.
If device has not been connected to node, specify a correct physical device name and re-execute the command.
If device has not been registered with the resource database, perform resource registration to register device with the resource database, and re-execute the command.
ERROR: device: not a shared device
Explanation
Physical disk device is not a shared disk unit, or cluster shared disk definition may not be correct.
Resolution
Check the system configuration and execute the command.
ERROR: device: already exists in class
Explanation
Physical disk device is already registered with class.
Resolution
Same physical disk cannot be registered with more than one class. Specify a correct physical disk.
ERROR: device: already exists in another class
Explanation
Physical disk device is already registered with another class. This class is not shared by current node.
Resolution
Same physical disk cannot be registered with more than one class. Specify a correct physical disk.
ERROR: object: physical disk device not found
Explanation
The physical disk device that composes the object object was not found.
Resolution
The physical disk device may be connected incorrectly or a disk failure may have occurred.
Fix device connection or recover from disk failure. Alternatively, specify an object other than object.
ERROR: physical disk device not found
Explanation
The physical disk device was not found.
Resolution
The physical disk device may be connected incorrectly or a disk failure may have occurred.
Fix device connection or recover from disk failure.
ERROR: device: no such device
Explanation
There is no physical disk device.
Resolution
Specify a correct physical disk name.
ERROR: device: cannot open, errno=errno
Explanation
Cannot open physical disk device.
Resolution
Confirm that physical disk device is operating normally.
ERROR: device: not a hard disk
Explanation
Physical disk device is not a hard disk.
Resolution
GDS cannot manage devices other than hard disks.
ERROR: device: disk driver driver not supported
Explanation
Physical disk unit with the driver name driver is not supported.
Resolution
There is no resolution.
ERROR: device: illegal format
Explanation
Physical disk device format is illegal.
Resolution
Check the format status.
ERROR: object: device busy
Explanation
Object object is in use.
Possible cause:
Cause a: Attempted to register the native device (sd device) object that configures the mpath device of DM-MP.
Resolution
Change to unused status and execute the command again.
When the possible cause is (Cause a), perform the following resolutions:
When not using DM-MP, cancel the settings of DM-MP.
When using DM-MP, register mpth device for the class. Do not register the native device at this time. Also register the native device to the Excluded Device List. For the Exclude Device List, see "6.1 Creating Excluded Device List."
ERROR: object: linked to a cluster service
Explanation
Object object is used in a cluster application.
Resolution
Check the cluster environment settings.
ERROR: device: configuration information exists in private slice
Explanation
Configuration information exists in the private slice of physical disk device, and registering device failed.
The following events a) to d) are the possible causes.
a) device is already registered with another class.
b) device is registered with a class in another domain.
c) The entire SDX disk was copied or is being copied to device with the disk unit's copy function.
d) After registering device with the class, it was not removed normally, and the private slice and configuration information remain existent in device illegally.
Resolution
Check the system configuration and so on, and identify the cause among a) to d). If the cause is a) or b), specify a physical disk not registered with a class. In the event of c) or d), collect investigation material and contact field engineers.
ERROR: device: type cannot be specified except undef
Explanation
The class scope includes a node to which physical disk device is unconnected and the type can only be set to "undef" for registering device to the class.
Resolution
See "Appendix B Command Reference."
ERROR: class: device: type cannot be specified except undef
Explanation
Class class includes a switch group and the type can only be set to "undef" for registering physical disk device to class.
Resolution
See "Appendix B Command Reference."
ERROR: device: write error, errno=errno
Explanation
A write error occurred in physical disk device.
Resolution
A disk failure may have occurred. Identify the cause by referring to disk driver log messages and so on, and recover the disk.
If device is a write-locked disk that is connected to a switch group, register writable disks first.
ERROR: device: disk ID information differs from all disks in specified class
Explanation
The specified class includes no disk with the same disk ID information (class name and disk name) as that stored in the private slice of physical disk device. For this reason, device cannot be registered with the specified class.
Resolution
Check the system configuration and so on, and specify a physical disk and class name properly.
ERROR: object: name already assigned to another object
Explanation
Object name object already exists within class. You cannot create multiple objects with the same name.
Resolution
Specify another name and execute the command again.
ERROR: cannot connect to sdxcld
Explanation
Connecting to sdxcld, a GDS cluster linked daemon was unsuccessful.
Resolution
When unable to identify the cause, collect investigation material and contact field engineers.
ERROR: physical device driver returned an error, errno=errno
Explanation
Physical disk driver returned an error.
An error occurs in software lower than GDS (multipath driver , sd driver, for example) or in a hardware such as a disk device.
Resolution
Identify the cause by referring to error number and message log.
If this message is output during the operation for the class where the netmirror volume exists, the possible case is that the disk of another node cannot be accessed due to a node stop or network error. Check the status of the node or the network.
ERROR: special file operation failed, errno=errno
Explanation
Operating special file was unsuccessful.
Resolution
Identify the cause by referring to error number and GDS log message.
ERROR: sfdsk driver returned an error, errno=errno
Explanation
GDS driver returned an error.
Resolution
Identify the cause by referring to error number, GDS log message, and rsyslogd message.
ERROR: sfdsk driver returned a temporary error, try again for a whileExplanation
GDS driver returned a temporary error.
Resolution
Execute the command again after a while.
ERROR: class: class closed down
Explanation
class is closed. You cannot operate objects within a closed class.
Resolution
A number of disk failures may have occurred. Identify the cause by referring to object status, GDS log message, and rsyslogd message.
For information on recovery, see "D.1.4 Class Status Abnormality."
ERROR: class: class closed down on another node
Explanation
class is closed on another node. You cannot operate objects within a closed class.
Resolution
Recover closed class. A number of disk failures may have occurred. Identify the cause by referring to object status, GDS log message, and rsyslogd message.
For information on recovery, see "D.1.4 Class Status Abnormality."
ERROR: keep disk cannot be specified for local or shared classExplanation
Keep disk cannot be registered with local or shared class.
Resolution
Register keep disk with root class.
ERROR: too many keep disks specifiedExplanation
The number of specified keep disks exceeds that of undefined disks.
Resolution
When registering multiple keep disks, specify the same number or more as undefined disks at the same time.
ERROR: class: already root class exists
Explanation
You tried to create a new class when there is already a root class. You can only create one root class within a node.
Resolution
Specify the existing root class or a local class.
ERROR: device contains overlapping slices
Explanation
The physical disk device contains physical slices with overlapping cylinders.
Resolution
Correct the physical slice configuration using the parted(8) command.
ERROR: device : one or more free slice numbers are required, delete a slice by parted(8) command
Explanation
The number of slices created on the physical disk device has reached the upper limit (15). The slice numbers are all in use and device cannot be registered as a keep disk.
Resolution
Use the parted(8) command to remove one or more slices from device.
ERROR: device : no enough unassigned disk space, reserve enough space by parted(8) command
Explanation
The physical disk device does not have sufficient free disk space.
Resolution
Use the parted(8) command and create sufficient free disk space.
For the size, see "2.3.9 Disk Size."
ERROR: device : no unassigned disk space nor swap space, reserve enough space by parted(8) command
Explanation
The physical disk device does not have free disk space or swap area.
Resolution
Use the parted(8) command and create sufficient free disk space or swap area.
For the size, see "2.3.9 Disk Size."
ERROR: device: no enough unassigned disk space nor swap space, reserve enough space by parted(8) command
Explanation
Physical disk device does not have sufficient free disk space or swap area.
Resolution
Use the parted(8) command and create sufficient free disk space or swap area.
For the size see "2.3.9 Disk Size."
ERROR: device: invalid physical device, managed by driver
Explanation
Specified physical disk is managed by driver, and is therefore invalid.
Resolution
Confirm the I/O and cluster system configuration, and specify a correct physical disk name.
ERROR: device: IDE disk cannot be specified as spare disk
Explanation
The device is an IDE disk. It cannot be used as a spare disk.
Resolution
For spare disks, use disks other than IDE disks.
ERROR: class: no such class
Explanation
Cannot find class.
Resolution
Check GDS configuration.
ERROR: group: not a group
Explanation
group is not a group name.
Resolution
There is another object with the name group within class. Check configuration.
ERROR: group is a lower level stripe group
Explanation
Group group is a stripe group connected to another group. Disks and groups cannot be connected to or disconnected from group.
Resolution
Disconnect group from the higher level group as necessary.
ERROR: group: connected to a lower level stripe group
Explanation
Group group is connected to a lower level stripe group. Disks and groups cannot be connected to or disconnected from group.
Resolution
Disconnect the higher level stripe group of group from its higher level group as necessary.
ERROR: too many groups in class
Explanation
Class class already has the maximum number of groups possible. A maximum of 100 groups can be created within, and a maximum of 1024 groups can be created within a local class or a shared class.
Resolution
Create a new class.
ERROR: too many disks and/or groups are connected to group
Explanation
The maximum number of disks or lower level groups are already connected to group group.
Resolution
There is no resolution.
ERROR: object: smaller than stripe width of group group
Explanation
Since the available size of disk or lower level group indicated by object is smaller than the stripe width of group group, object cannot be connected to group.
Resolution
Execute the command after indicating a disk or lower level group with sufficient size, or remove group group and adjust the stripe width to a smaller size.
ERROR: class: three or more nodes exist in class scope
Explanation
The scope of class class includes 3 or more nodes. Classes whose scope includes 3 or more nodes cannot include switch groups.
Resolution
Specify a shared class of which scope is 2 nodes.
ERROR: disk: type disk exists in class
Explanation
Class class includes disk disk of the type type. The attempted operation is not supported for classes that include type type disks.
Resolution
Delete disk from class as needed and re-execute the command.
ERROR: class includes a group that cannot exist together with a switch group
Explanation
The class class includes one of the following groups and a switch group cannot be created.
Mirror group
Stripe group
Concatenation group to which any lower level switch group is not connected
Resolution
Specify a correct class name.
ERROR: active disk must be specified
Explanation
When creating a switch group, specify the active disk in the -a actdisk=disk option.
Resolution
Specify the option properly, referring to "Appendix B Command Reference."
ERROR: disk: active disk not specified by -d option
Explanation
Active disk disk was not specified in the -d option.
Resolution
When creating a switch group, specify one of the disks specified in the -d option of the sdxdisk -C command as the active disk.
ERROR: too many disks specified
Explanation
Too many disks specified.
Resolution
Specify a proper number of disks.
For the number of disks that can be connected to a group, see "2.3.3 Number of Disks."
ERROR: disk: physical scope is not included in class scope
Explanation
The physical scope of disk disk is not included in the class scope and disk cannot be connected to a switch group.
Resolution
Specify a correct disk name. For the physical scope of a disk, use the sdxinfo -D command and check the displayed DEVCONNECT field. For the class scope, use the sdxinfo -C command and check the displayed SCOPE field.
ERROR: disk: physical scope must be same as class scope
Explanation
The physical scope of the active disk matches the class scope and therefore the physical scope of an inactive disk must match the class scope. The physical scope of disk disk does not match the class scope and disk cannot be connected to the switch group as the inactive disk.
Resolution
Specify a correct disk name. For the physical scope of a disk, use the sdxinfo -D command and check the displayed DEVCONNECT field. For the class scope, use the sdxinfo -C command and check the displayed SCOPE field.
ERROR: disk: physical scope must include only node
Explanation
The physical scope of inactive disk disk can include only node node.
Resolution
Specify a correct disk name, referring to "Appendix B Command Reference."
ERROR: disk: class scope is not included in physical scope
Explanation
The class scope is not included in the physical scope of disk disk and disk cannot be connected to a group other than a switch group.
Resolution
Specify a correct disk name. For the physical scope of a disk, use the sdxinfo -D command and check the displayed DEVCONNECT field. For the class scope, use the sdxinfo -C command and check the displayed SCOPE field.
ERROR: disk: no such disk
Explanation
There is no disk.
Resolution
Check GDS configuration.
ERROR: object: already connected to group
Explanation
Disk or group indicated by object, is already connected to group group.
Resolution
Specify a correct disk name or group name.
ERROR: disk is a spare disk
Explanation
disk is a spare disk. You cannot connect a spare disk to a group.
Resolution
Change the disk attributes to undefined, and execute the command again.
ERROR: object not in status status
Explanation
Object status is not status status.
Resolution
Confirm that object status is status, and execute the command again.
ERROR: object too small
Explanation
Check the following causes:
a) The size of object is too small.
b) An attempt to register the disk object where the disk label is not the GPT type to a root class.
Resolution
a) Check the necessary object size and specify a larger object.
b) Change the disk label of the disk object to the GPT type with the parted(8) command.
ERROR: another disk must be connected to group
Explanation
You must connect another disk to group.
Resolution
Connect another disk and execute the command again.
ERROR: invalid physical slice number, pslice_num
Explanation
The specified physical slice number pslice_num is invalid.
Resolution
For the physical slice number pslice_num, specify an integer from 1 to 15.
ERROR: pslice is private slice
Explanation
Physical slice pslice is a private slice.
Resolution
If this message is output at the time of sdxdisk -M command execution, check whether the disk to which the physical slice pslice belongs is registered with a class in another domain. If it is registered, the disk cannot be registered with a class. If not, to register the disk to a class, it is necessary to delete the physical slice pslice, for example, with the parted(8) command.
If this message is output at the time of sdxdisk -C command execution, re-execute the sdxdisk -C command. When re-executing, do not specify the slice number of the physical slice pslice for the -v option.
ERROR: pslice: corresponding volume attributes must be specified
Explanation
Volume attributes corresponding to physical slice pslice is not specified.
Resolution
See "Appendix B Command Reference."
ERROR: object: invalid size
Explanation
Object size of object is invalid.
Resolution
See "Appendix B Command Reference."
ERROR: two or more keep disks cannot be connected to a groupExplanation
More than one keep disk cannot be connected to group.
Resolution
See "Appendix B Command Reference."
ERROR: two or more single disks cannot be connected to a groupExplanation
More than one single disk cannot be connected to a group.
Resolution
See "Appendix B Command Reference."
ERROR: both keep and single disks cannot be connected to a groupExplanation
Both keep and single disks cannot be connected to a group at the same time.
Resolution
See "Appendix B Command Reference."
ERROR: disk: keep disk cannot be connected to existing group
Explanation
Keep disk disk cannot be connected to an existing group.
Resolution
See "Appendix B Command Reference."
ERROR: disk: single disk cannot be connected to existing group
Explanation
Single disk disk cannot be connected to the existing group.
Resolution
See "Appendix B Command Reference."
ERROR: two or more IDE disks cannot be connected to a groupExplanation
More than one IDE disk cannot be connected to a group.
Resolution
When mirroring an IDE disk, use it with disks other than IDE disks.
ERROR: two or more disks cannot be connected to a group
Explanation
If the FJSVsdx-bas package of GDS is not installed, multiple disks cannot be connected to a group.
Resolution
If FJSVsdx-bas has not been installed successfully, reinstall it.
ERROR: group: a lower level switch group is connected
Explanation
A switch group has been connected to the group group and it is impossible to connect a disk to group or group to another group.
Resolution
Specify a correct higher level group name.
ERROR: disk: not a bootable device
Explanation
Disk disk cannot be booted.
Resolution
Confirm the disk configuration. When you cannot specify the cause, collect investigation material and contact field engineers.
ERROR: too few valid configuration database replicasExplanation
There is not sufficient valid configuration database for class. This message is displayed when the majority of disks registered with class are unavailable.
Leaving it as is may cause serious problems.
Resolution
For details, see "D.1.4 Class Status Abnormality."
ERROR: group: no ENABLE disk in group
Explanation
Group group does not have a disk in ENABLE status connected.
Resolution
See "D.1.2 Disk Status Abnormality" and recover disks connected to the group.
ERROR: msec: invalid delay value
Explanation
Delay time msec is invalid.
Resolution
See "Appendix B Command Reference."
ERROR: lgroup: mirror group cannot be connected to another group
Explanation
Since group lgroup is a mirror group, it cannot be connected to another group.
Resolution
Specify a correct lower level group name.
ERROR: lgroup: same type as higher level group hgroup
Explanation
Since the type attributes for group lgroup and higher level group hgroup are the same, lgroup cannot be connected to hgroup.
Resolution
Specify a correct group name.
ERROR: hgroup: same name as a lower level group
Explanation
For the higher level group name, name hgoup, which is the same as the lower level group was indicated.
Resolution
Different names must be indicated for higher level group and lower level group.
ERROR: hgroup: any group cannot be connected to a switch group
Explanation
Group hgroup is a switch group and any group cannot be connected to.
Resolution
Specify a correct group name.
ERROR: group: is a lower level concatenation group
Explanation
The group group is a concatenation group connected to another group. Any group cannot be connected to group.
Resolution
Disconnect group from the higher level group as needed and re-execute the command.
ERROR: lgroup: stripe group cannot be connected to concatenation group
Explanation
The group lgroup is a stripe group and cannot be connected to a concatenation group.
Resolution
Specify a correct group name.
ERROR: lgroup: switch group cannot be connected to mirror group
Explanation
The group lgroup is a switch group and cannot be connected to a mirror group.
Resolution
Specify a correct group name.
ERROR: lgroup: switch group cannot be connected to stripe group
Explanation
The group lgroup is a switch group and cannot be connected to a stripe group.
Resolution
Specify a correct group name.
ERROR: hgroup: disk is connected
Explanation
A disk is already connected to concatenation group hgroup, and a switch group cannot be connected.
Resolution
Specify a correct group name.
ERROR: size: must be more than zero
Explanation
size must be a positive integer.
Resolution
Specify the correct size.
ERROR: size: invalid size
Explanation
The indicated size size is invalid.
Resolution
See "Appendix B Command Reference."
ERROR: group: no such group
Explanation
There is no group.
Resolution
Specify a correct group name.
ERROR: group: not the highest level group
Explanation
Group group is not the highest level group.
Resolution
Disconnect group from the higher level group as necessary.
ERROR: too many volumes exist in object
Explanation
The maximum number of volumes, already exists in the object, that is a class, a group, or a single disk.
Resolution
Create volumes in another group or on a single disk as needed.
ERROR: too many volumes with physical slices in object
Explanation
In the object, the number of volumes which consist of physical slices has reached the maximum. object is a name of group or single disk.
Resolution
Change the physical slice attributes for volumes in object from on to off using the sdxattr -V command as needed, and execute the command again.
ERROR: group: volume with physical slice(s) cannot be created
Explanation
Although a physical slice cannot be created in group group, an attempt was made to create a volume with one or more physical slices.
Resolution
Create a volume without any physical slice for group either by:
Turning "off" the [Physical Slice] option in the Volume Configuration dialog box when creating the volume for group in GDS Management View
Using the -a pslice=off option when creating the volume for group with the sdxvolume -M command
If group is a mirror group, connect one or more disks to the group in order to create a volume with a physical slice.
ERROR: object: no enough space
Explanation
There is not enough space in the group or single disk indicated by object.
Resolution
Change the size you specify as needed.
After expanding the physical disk size of the group or single disk specified by object, if the volume size in the group or single disk is expanded by the sdxvolume -S command, this message is output. In this case, take one of the following actions.
Perform the following operations for the physical disk of which the size was expanded.
a1) Make the physical disk exchangeable with the sdxswap -O command or [Swap Physical Disk].
a2) Restore the status with the sdxswap -I command or [Restore Physical Disk].
b1) Perform the following operations for the group or single disk specified by object.
b1-1) Back up the data of all of the volumes in object.
b1-2) Delete all of the volumes from object.
b2) Perform the following operations for the disk of which the size was expanded.
b2-1) When the disk is connected to the group, disconnect the disk from the group.
b2-2) Make the physical disk exchangeable with the sdxswap -O command or [Swap Physical Disk].
b2-3) Restore the status with the sdxswap -I command or [Restore Physical Disk].
b2-4) If the disk is disconnected from the group in step b2-1), connect the disk to the group again.
b3) Perform the following operations for the group or single disk specified by object.
b3-1) Recreate the volume deleted in step b1-2).
b3-2) Restore the data of volume backed up in step b1-1).
c1) Perform the following operations for the group or single disk specified by object.
c1-1) Back up the data of all of the volumes in object.
c1-2) Delete all of the volumes from object.
c2) Perform the following operations for the disk of which the size was expanded.
c2-1) When the disk is connected to the group, disconnect the disk from the group.
c2-2) Delete the disk from the class.
c2-3) Register the disk to the class again.
c2-4) If the disk is disconnected from the group in step c2-1), connect the disk to the group again.
c3) Perform the following operations for the group or single disk specified by object.
c3-1) Recreate the volume deleted in step c1-2).
c3-2) Restore the data of volume backed up in step c1-1).
ERROR: disk: not a single disk
Explanation
The disk disk is not a single disk.
Resolution
Specify a correct disk name.
ERROR: disk: status disk connected to group
Explanation
disk in status status is connected to group.
Resolution
Restore the status of disk and execute the command again.
ERROR: status disk exists in group
Explanation
The disk in status status is connected to group, or it connected to the lower level group of group.
Resolution
Confirm the disk status, and please execute a command again after canceling the status status if necessary.
ERROR: disk: no such disk in group
Explanation
disk is not connected to group.
Resolution
Specify a correct disk name and group name.
ERROR: disk: device: device busy
Explanation
Disk disk (physical disk name is device ) is in use.
Resolution
Change to unused status, and execute the command again.
ERROR: too many nodes specifiedExplanation
Too many nodes were specified.
Resolution
Specify the nodes included in the scope of the class.
ERROR: option: cannot be specified for root nor local class
Explanation
Command option option cannot be specified for a root nor local class.
Resolution
See "Appendix B Command Reference."
ERROR: node: not in scope, class=class
Explanation
Node node is not included in the scope of the class class.
Resolution
Confirm your GDS configuration, specify a node included in the scope of the class, and try the command again.
ERROR: volume: cannot start, class closed down, node=node
Explanation
Starting volume volume was unsuccessful due to the class to which volume volume belongs was blockading it on node node.
Resolution
Recover the blockage of the class to which volume volume belongs. A number of disk failures may have occurred. Identify the cause by referring to object status, GDS log message, and rsyslogd message.
For information on recovery, see "D.1.4 Class Status Abnormality."
ERROR: volume: no such volume
Explanation
There is no volume.
Resolution
Specify a correct volume name.
ERROR: object in status status
Explanation
object is in status status.
Resolution
Confirm the object status, and cancel the status status if necessary.
ERROR: some ACTIVE volumes exist in class, node=node
Explanation
Volumes of class class are already active on node node, and volumes of class cannot be started or created on this node.
Resolution
Create volumes of class class on node node. Alternatively, as needed, stop all the volumes within class on node and then start or create volumes on this node.
If a cluster application to which class resources are registered is operating or is standby on node, before stopping volumes on node, stop the cluster application.
ERROR: volume: some ACTIVE volumes exist in class, node=node
Explanation
Volumes of class class are already active on node node, and volume volume cannot be started on this node.
Resolution
Stop all the volumes within class class on node node as needed, start volume volume on this node.
If a cluster application to which class resources are registered is operating or is standby on node, before stopping volumes on node, stop the cluster application.
ERROR: volume: active disk not connected to node
Explanation
The active disk of a switch group including switch volume volume is not connected to node node and the volume cannot be started on the node.
Resolution
If an inactive disk is connected to a switch group including volume, use the sdxattr -G command and switch the inactive disk to the active disk in order to start volume on node.
ERROR: volume: active disk of lower level group group is not connected to node
Explanation
The active disk of lower level switch group group is not connected to node node, and volume volume cannot be started on node. group is a lower level switch group that is connected to the highest level group to which volume belongs.
Resolution
If an inactive disk is connected to group, switch the active disk to the inactive disk with the sdxattr -G command in order to enable volume startup on node.
ERROR: lock is set on volume volume, node=node
Explanation
The "Lock volume" mode for volume volume on node node is turned on.
Resolution
Turn off the "Lock volume" mode, or use the -e unlock option as necessary.
However, if volume is the netmirror volume, lock the netmirror volume (including specifying -e unlock option) only as the restoration procedure in "7.16 Mirroring Among Servers." For details, see "7.16.5 Lock Volume of the Netmirror Volume."
ERROR: volume: cannot stop, class closed down, node=node
Explanation
Stopping volume volume was unsuccessful due to the class to which volume volume belongs was blockading it on node node.
Resolution
Recover the blockage of the class to which volume volume belongs. A number of disk failures may have occurred. Identify the cause by referring to object status, GDS log message, and rsyslogd message.
For information on recovery, see "D.1.4 Class Status Abnormality."
ERROR: object.volume: status slice exists in object
Explanation
Slice object.volume in status status exists in object.
Resolution
Confirm the object status, and cancel the status status if necessary.
If volume indicates the netmirror volume, this message may be output after an error of the network used for the mirroring among server is restored. In this case, if status indicates COPY, no resolution is required.
ERROR: object in status status, node=node
Explanation
object on node is in status status.
Resolution
Confirm the object status, and cancel the status status if necessary.
ERROR: volume: stripe type volume cannot be resized
Explanation
The volume volume cannot be resized since it is a volume created in a stripe group.
Resolution
See "Stripe Type Volume and Concatenation Type Volume Expansion" in "3.12 Online Volume Expansion."
ERROR: volume: concat type volume cannot be resized
Explanation
The volume volume cannot be resized since it is a volume created in a concatenation group.
Resolution
See "Stripe Type Volume and Concatenation Type Volume Expansion" in "3.12 Online Volume Expansion."
ERROR: volume: consists of multiple mirror slices
Explanation
The volume volume cannot be resized since it is a mirror volume that consists of multiple mirror slices.
Resolution
Disconnect disks and lower level groups from the mirror group so that volume is composed of only one mirror slice, and try this command again.
ERROR: spare disk connected for disk
Explanation
Spare disk is connected instead of disk.
Resolution
First recover the disk status.
ERROR: object.volume is only valid slice
Explanation
object.volume is the only valid slice within volume volume. You cannot continue your operation because data within volume may be lost if you continue your operation.
Resolution
If volume is a mirror volume, you will be able to continue your operation by recovering the mirroring (for example, by connecting a new disk to group).
If volume is not a mirror volume, remove volume as necessary.
ERROR: object: the last disk or group in lower level group group
Explanation
Object object is the only disk or group connected to the lower level group group. You cannot disconnect object from group.
Resolution
Disconnect group from the higher level group as necessary.
ERROR: object: not connected to the end of concatenation group group
Explanation
The object object is not the disk or switch group that was last connected to the concatenation group group. It is impossible to disconnect object from group.
Resolution
To disconnect disks and groups from group, perform disconnection in inverse order of connection. For the order of connecting disks and groups to group, use the dxinfo -G command and check the displayed DISKS field.
ERROR: object: disk space is assigned to volume volume
Explanation
Disk space of disk or lower switch group object is assigned to volume volume, and object cannot be disconnected from the concatenation group.
Resolution
If needed, remove volume first.
ERROR: group: inactive disk is connected
Explanation
The group group has a connected inactive disk and physical disk swap or disconnection cannot be performed for the active disk of the group.
Resolution
As needed, switch the active disk with the sdxattr -G command and perform physical disk swap or disconnection for the previous active disk.
ERROR: disk: not inactive disk
Explanation
The disk disk is the active disk of a lower level switch group, and physical disk swap cannot be performed.
Resolution
As needed, switch the active disk with the sdxattr -G command, and perform physical disk swap on the previous active disk.
ERROR: lgroup: no such group in hgroup
Explanation
Group lgroup is not connected to group hgroup.
Resolution
Specify a correct group name.
ERROR: one or more volumes exist in group
Explanation
One or more volumes exist in group group.
Resolution
First, remove the volume if necessary.
ERROR: disk connected to group
Explanation
disk is connected to group.
Resolution
First, disconnect the disk from group if necessary.
ERROR: disk: The last ENABLE disk in class cannot be removed
Explanation
When there is a disk in SWAP or DISABLE status in class, you cannot remove the last disk in ENABLE status.
Resolution
First recover the disk in SWAP or DISABLE status. Or, you can register a new disk with class.
ERROR: disk: cannot be removed to avoid class closing down
Explanation
Disk disk stores the configuration database and removal of disk will result in class closure. For this reason, the disk cannot be removed.
Resolution
Recover or remove a failed disk in the class that includes disk and then remove disk.
ERROR: one or more volumes exist in disk
Explanation
Volume exists in disk.
Resolution
First, remove the volume as needed.
ERROR: one or more groups exist in class
Explanation
Group exists in class.
Resolution
First, remove the group as needed.
ERROR: disk: status disk exists in class
Explanation
disk in status status exists in class.
Resolution
First, restore the disk in status status.
ERROR: volume: status volume exists in class, node=node
Explanation
volume in status status on node exists in class.
Resolution
First, change the volume status as needed.
ERROR: disk: no such disk
Explanation
There is no disk disk.
Resolution
Specify a correct disk name.
ERROR: volume: not associated with object
Explanation
You cannot specify slice by combining disk or group indicated by object, and volume indicated by volume.
Resolution
See "Appendix B Command Reference" and specify a correct disk or group name and volume name.
ERROR: volume is single volume
Explanation
Volume is a single volume. Slices of single volumes cannot be detached.
Resolution
Specify a correct volume name.
ERROR: volume: not a mirror volume
Explanation
Volume volume is not a mirror volume.
Resolution
Specify a correct volume name.
ERROR: object: not connected to the highest level group
Explanation
Disk or group indicated by object is not connected to the highest-level group.
Resolution
See "Appendix B Command Reference" and specify a correct disk name or group name.
ERROR: disk: The last ENABLE disk in class cannot be swapped
Explanation
You cannot swap the last ENABLE status disk in class.
Resolution
Depending on the configuration, use a different method to avoid such situations. For example, you can register a new disk with class.
ERROR: disk: keep disk cannot be swapped out
Explanation
Keep disk disk cannot be swapped.
Resolution
Change the type attribute of disk, and execute the command again.
ERROR: disk: volume in status status
Explanation
There is a volume related to disk in status status.
Resolution
First, recover the volume in status status.
ERROR: disk: the highest level group is not a mirror group
Explanation
The highest level group of disk disk is not a mirror group.
You cannot swap disk.
Resolution
Disconnect disk from the group, and execute the command in a situation where it is not connected to any group.
ERROR: disk: cannot be swapped to avoid class closing down
Explanation
The disk disk stores the configuration database and swapping disk will close down the class. Therefore, swapping the disk is prevented.
Resolution
Replace a failed disk included in the class to which disk is registered and swap disk.
ERROR: disk: device: device busy on node node
Explanation
Disk disk (the physical disk name is device) is in use on node.
Resolution
Change the status to unused and execute the command again.
ERROR: disk: device: cannot open, errno=errno
Explanation
Cannot open physical disk device.
Resolution
Perform any of the following procedures:
a) Confirm that physical disk device is operating normally.
b) If this message is output when restoring a physical disk of the swapped internal device, there may be a device name change. For checking a device name change, see "7.3.5.4 Swapping Internal Disks Registered with Root Classes or Local." If there is a device name change, reboot the system to solve it.
ERROR: disk: device: not a hard disk
Explanation
Physical disk device is not a hard disk.
Resolution
Specify a hard disk.
ERROR: disk: device: illegal format
Explanation
Physical disk device format is illegal.
Resolution
Check the format of the physical disk.
ERROR: disk busy - /dev/pslice
Explanation
Physical disk pslice is in use.
Resolution
Change to unused status and execute the command again.
ERROR: disk: device: linked to a cluster service
Explanation
Physical disk device is used in a cluster application.
Resolution
Check the settings for cluster environment.
ERROR: disk: device: not enough size
Explanation
Physical disk size is too small.
Resolution
Perform any of the following procedures:
a) Specify a physical disk with sufficient size.
b) If this message is output when restoring a physical disk of the swapped internal device, there may be a device name change. For checking a device name change, see "Swapping Internal Disks Registered with Root Classes or Local Classes [RHEL6]" in "7.3.5.4 Swapping Internal Disks Registered with Root Classes or Local." If there is a device name change, reboot the system to solve it.
ERROR: disk: device: not connected to node
Explanation
Physical disk device is not connected to node. Or, cluster shared disk definition may not be correct.
Resolution
Check the system configuration and execute the command.
ERROR: disk: device: invalid disk, managed by driver
Explanation
Specified disk (corresponding physical disk name is device) is managed by driver, and is therefore invalid.
Resolution
Confirm the I/O and cluster system configuration, and specify a correct physical disk name.
ERROR: object.volume: status slice exists in group
Explanation
Slice object.volume in status status already exists in group group.
Resolution
Check the object status and cancel status status if necessary.
ERROR: disk : device : invalid disk on node node, managed by driver
Explanation
On node node, physical disk device of disk disk has been managed by driver driver and cannot be handled.
Resolution
Check I/O configurations and cluster system configurations, and specify a correct physical disk name.
ERROR: disk : device : cannot open on node node, errno=errno
Explanation
Physical disk device cannot be opened on node node.
Resolution
Check whether or not the physical disk device is operating normally.
ERROR: disk : device : node : not a hard disk
Explanation
Physical disk device on node node is not a hard disk.
Resolution
Specify a hard disk.
ERROR: disk : device : node : illegal format
Explanation
The format of physical disk device on node node is incorrect.
Resolution
Check the format.
ERROR: disk busy on node node - / dev/pslice
Explanation
Physical disk pslice on node node is in use.
Resolution
Change the status to unused and retry the command.
ERROR: disk : device : node : linked to a cluster service
Explanation
Physical disk device on node node is being used by cluster applications.
Resolution
Check the cluster environment configurations.
ERROR: disk : device : node: not enough size
Explanation
The size of physical disk device on node node is too small.
Resolution
Replace it with a physical disk of sufficient size.
ERROR: disk : device : read error, errno=errno
Explanation
A read error occurred on physical disk device.
Resolution
The possible cause is a disk failure. Identify the cause based on disk driver log messages and so on and restore the disk.
ERROR: disk : device : node: read error, errno=errno
Explanation
A read error occurred on physical disk device on node node.
Resolution
The possible cause is a disk failure. Identify the cause based on disk driver log messages and so on and restore the disk.
ERROR: object: read error, errno=errno
Explanation
Read error occurred on the disk indicated by object, or on a disk connected to group indicated by object, or on a disk connected to a lower level of the group indicated by object.
Resolution
Disk failure may have occurred. Identify the cause by referring to disk driver log message, and promptly recover the disk. Otherwise, indicate another disk or group that is normal.
ERROR: object.volume : no such slice
Explanation
You cannot specify slice by combining disk or group indicated by object, and volume indicated by volume.
Resolution
See "Appendix B Command Reference" and specify a correct disk or group name and volume name.
ERROR: disk: not active disk
Explanation
Disk disk is not the active disk.
Resolution
Specify the active disk.
ERROR: disk: I/O error not occur
Explanation
An I/O error has not been occurred on the disk disk. There is no need to restore disk using the sdxfix -D command.
Resolution
There is no resolution.
ERROR: class: not close down
Explanation
Class class is not closed. Recovery class with the sdxfix -C command is not required.
Resolution
There is no resolution.
ERROR: no valid configuration databaseExplanation
No valid configuration database of the class is found. If all (or most of) the disks that are registered with the class are unavailable, this message is output.
Resolution
ERROR: class: closed down on all nodes in class scope
Explanation
During recovery of class class from the closed status, class was closed on all the nodes within the class scope.
Resolution
Re-execute the sdxfix -C command.
ERROR: disk: connected to switch group
Explanation
Disk disk is connected to a switch group and an I/O error status of the disk cannot be removed.
Resolution
Make disk exchangeable with the sdxswap -O command or [Operation]:[Swap Physical Disk] in GDS Management View to remove an I/O error status of disk. After this procedure, swap the physical disks of disk according to need and then make the disk usable again with the sdxswap -I command or [Operation]:[Restore Physical Disk] in GDS Management View.
ERROR: volume: cannot restart to copy, cancel current interrupted copy operation by sdxcopy command with -C option
Explanation
Copying process within volume could not be resumed.
Resolution
Cancel the interrupted copying process according to need and resume copying.
ERROR: attribute=value: cannot modify type attribute of root class
Explanation
The root class type attribute cannot be changed.
Resolution
Specify a correct class name.
ERROR: class: class names must be unique within a domain
Explanation
Class class with the same name as class already exists within the cluster domain.
Resolution
When renaming a class resulted in this message, specify another class name.
When expanding the class scope resulted in this message, see "Important Point 2" in "8.5 Migration from Single Nodes to Cluster System."
ERROR: class: volume minor numbers must be unique within a domain
Explanation
A volume with the same minor number as that of a volume in the class class was found within the cluster domain.
Resolution
ERROR: one or more disks not connected to node
Explanation
Disks that are not connected to node node or for which disk resources are not created yet exist in the class.
Resolution
Check the hardware configuration and the disk configuration within the class. If disk resources are not created yet, create those through the resource registration.
For the resource registration, see "6.3 Shared Disk Resource Registration."
ERROR: disk: IDE disk cannot be specified as spare disk
Explanation
The disk is an IDE disk. It cannot be used as a spare disk.
Resolution
For spare disks, use disks other than IDE disks.
ERROR: object: no such object
Explanation
There is no object.
Resolution
Specify a correct object name.
ERROR: class: shared objects information not yet available, try again for a while
Explanation
Share object information is not available yet.
Resolution
Wait until cluster control is activated, and execute the command again.
ERROR: node: node in stopped status
Explanation
You cannot proceed with operation since node is in stopped status.
Resolution
Start the node and try again.
ERROR: node: node in abnormal status
Explanation
node is in an abnormal status and cannot proceed with operation.
Resolution
Confirm the normal startup of node and try again.
ERROR: cluster communication failureExplanation
Cannot proceed with operation since communication failed with cluster.
Resolution
Check that the cluster system and GDS are operating normally.
After recovering, try again.
ERROR: cluster communication failure, sdxerrno=sdxerrno
Explanation
Cannot proceed with operation since communication failed with cluster.
Resolution
Check that the cluster system and GDS are operating normally.
After recovering, try again.
ERROR: cluster communication failure, remote-node=node, sdxerrno=sdxerrno
Explanation
Cluster communication with remote node node failed. Operation cannot be performed.
Resolution
Check that the cluster system and GDS are operating normally.
After recovering, try again.
ERROR: class: not a root class
Explanation
Class class is not a root class. The possible causes are as follows.
a) The specified class name is wrong.
b) An attempt to use a function that is only for a root class was made for a local class or a shared class.
c) In a system where the FJSVsdx-bas package of GDS is not installed normally, an attempt to create a local class group or a shared class group was made.
d) In a system where the FJSVsdx-bss package of GDS Snapshot is not installed normally, an attempt to perform proxy operation was made for a local class or a shared class.
Resolution
If the cause is a) or b), see "Appendix B Command Reference" and specify a correct class name. If it is c) or d), install FJSVsdx-bas or FJSVsdx-bss normally.
ERROR: disk: not a keep disk
Explanation
Disk disk is not a keep disk.
Resolution
See "Appendix B Command Reference" and specify a correct disk name.
ERROR: disk: not connected to any group
Explanation
Disk disk is not connected to a group.
Resolution
See "Appendix B Command Reference" and specify a correct disk name.
ERROR: volume: status volume exists in group
Explanation
There is volume in status status in group.
Resolution
Recover volume status, and execute the command again.
ERROR: disk: not a system disk
Explanation
Disk disk is not a system disk.
Resolution
Specify a correct disk name, and execute the command again.
ERROR: device: mandatory system disk must be registered to class
Explanation
he system disk device is not registered with the class class. device contains the slice currently operating as / (root), /usr, /var, /boot, or /boot/efi, and to perform system disk setting, it is necessary to register device with class.
Resolution
Complete preparations properly referring to "6.5.2.1.1 Operation Flow" or "Appendix B Command Reference" and execute the command again.
ERROR: disk: mandatory system disk must be specified
Explanation
The system disk disk was not specified. disk contains the slice currently operating as / (root), /usr, /var, /boot, or /boot/efi, and to cancel disk mirroring, it is necessary to specify disk.
Resolution
Specify all system disks with the slices currently operating as / (root), /usr, /var, /boot, or /boot/efi, and execute the command again.
ERROR: disk: two or more disks connected to group
Explanation
group to which disk is connected has two or more disks connected.
Resolution
See "Appendix B Command Reference" and complete preparation correctly. Then execute the command again.
ERROR: root file system not mounted on volumeExplanation
Root file system is not mounted on volume.
Resolution
Confirm the configuration, and see "Appendix B Command Reference."
ERROR: illegal slice nameExplanation
Slice name includes a "." (period).
Resolution
Specify the correct slice name.
ERROR: disk.volume cannot be operated on the current node, take over by sdxslice command with -T option
Explanation
Slice disk.volume cannot be operated on the current node.
Resolution
Take over the slice by executing sdxslice -T command.
ERROR: volume: physical slice attribute value is off
Explanation
The physical slice attribute value of volume volume is "off." A slice in a volume without physical slices cannot be detached.
Resolution
Retry the command after turning the physical slice attribute of volume to be "on" according to need.
ERROR: object: device busy on node node
Explanation
object is in use on node.
Resolution
Change to unused status and execute the command again.
ERROR: class: not a shared class
Explanation
class is not a shared class.
Resolution
Specify a shared class.
ERROR: param: invalid parameter name
Explanation
Parameter name param is invalid.
Resolution
See "Appendix B Command Reference."
ERROR: param =val: invalid parameter value
Explanation
Parameter value val is invalid.
Resolution
See "Appendix B Command Reference."
ERROR: param: parameter name duplicated
Explanation
The same parameter name param has already been specified.
Resolution
You can only use a parameter name once.
ERROR: copy_concurrency=val: value more than or equal to the number of actually running copy operations must be specified
Explanation
Value smaller than the number of copying currently in process has been specified for copy_concurrency parameter.
Resolution
Set a value more than or equal to the number of copying currently in process for copy_concurrency parameter.
ERROR: mode=string: access mode duplicated
Explanation
Multiple access modes have been specified.
Resolution
Specify only one access mode.
ERROR: mode=string: invalid access mode
Explanation
Access mode value string is invalid.
Resolution
See "Appendix B Command Reference."
ERROR: volume: already started with different access mode, node=node
Explanation
On the node node, an attempt was made to start the volume volume specifying the access mode, but the volume volume is already active in an access mode other than the specified mode.
Resolution
Stop the volume volume and restart it as needed.
ERROR: volume: related to proxy volume proxy
Explanation
Volume volume is a master volume related to proxy volume proxy.
Resolution
Cancel the relationship of master volume volume and proxy volume proxy according to need and execute again.
ERROR: volume: related to master volume master
Explanation
Volume volume is a proxy volume related to master volume master.
Resolution
Cancel the relationship of master volume master and proxy volume volume according to need and execute again.
ERROR: volume: related to proxy volume proxy with EC
Explanation
EC session exists between volume volume and proxy volume proxy.
Resolution
Cancel the relationship of master volume volume and proxy volume proxy according to need, and execute again.
ERROR: volume: related to master volume master with EC
Explanation
EC session exists between volume volume and master volume master.
Resolution
Use the sdxproxy Cancel command and cancel the EC session between master volume master and proxy volume volume according to need. Alternatively, as needed, cancel the relationship of master volume master and proxy volume volume, and execute again.
ERROR: volume: related to proxy volume proxy with TimeFinder
Explanation
There is a BCV pair between the volume volume and the proxy volume proxy.
Resolution
Break the relation between the master volume volume and the proxy volume proxy according to need, and try the command again.
ERROR: volume: related to master volume master with TimeFinder
Explanation
There is a BCV pair between the volume volume and the master volume master.
Resolution
Break the relation between the master volume master and the proxy volume volume according to need, and try the command again.
ERROR: volume: related to proxy volume proxy with SRDF
Explanation
There is an SRDF pair between the volume volume and the proxy volume proxy.
Resolution
Break the relation between the master volume volume and the proxy volume proxy according to need, and try the command again.
ERROR: volume: related to master volume master with SRDF
Explanation
There is an SRDF pair between the volume volume and the master volume master.
Resolution
Break the relation between the master volume master and the proxy volume volume according to need, and try the command again.
ERROR: proxy : no parted proxy volume in proxy group
Explanation
No parted proxy volume exists in proxy group proxy.
Resolution
According to need, part the proxy and retry the command.
ERROR: volume: parted proxy volume
Explanation
Volume volume is a proxy volume parted from master volume.
Resolution
Rejoin the proxy volume to the master volume or break the relationship between them according to need and try this command again.
ERROR: group: related to proxy group proxy
Explanation
Group group is a master group related to proxy group proxy.
Resolution
Cancel the relationship between master group group and proxy group proxy according to need, and execute again.
ERROR: group: related to master group master
Explanation
Group group is a proxy group related to master group master.
Resolution
Cancel the relationship between master group master and proxy group group according to need, and execute again.
ERROR: volume: related to master or proxy volume
Explanation
Volume volume is related to either master volume or proxy volume.
Resolution
Cancel the relationship between master and proxy according to need, and execute again.
ERROR: volume: joined to master volume master
Explanation
Volume volume is a proxy volume joined to master volume master.
Resolution
Part volume volume from master volume master, or cancel the relationship with master volume according to need, and execute again.
ERROR: volume: copying from master volume master
Explanation
Data is being copied from master volume master to volume volume.
Resolution
After the copying process is complete, execute again.
ERROR: volume: copying from proxy volume proxy
Explanation
Data is being copied from proxy volume proxy to volume volume.
Resolution
After the copying process is complete, execute again.
ERROR: class is root class
Explanation
The class class is the root class. The attempted operation is not supported for the root class.
Resolution
Specify a correct class name.
ERROR: object: not volume nor group
Explanation
The object object is neither a volume nor a group.
Resolution
Check the GDS configuration and specify the correct volume name or group name. Execute again.
ERROR: different types of objects, master=master, proxy=proxy
Explanation
Different types of objects master and proxy were specified as the master and proxy.
Resolution
As the master and proxy, specify a combination of volumes or groups.
ERROR: object: same name as master
Explanation
The object name specified for proxy is the same as the master's name, object.
Resolution
Different object names must be specified for master and proxy.
ERROR: group: not a mirror group
Explanation
Group group is not a mirror group.
Resolution
Specify a correct group name.
ERROR: no volume exists in group
Explanation
There are no volumes in group group.
Resolution
Use sdxvolume -M command to create a volume within group group, and execute again.
ERROR: too many proxy volumes are related to master
Explanation
There are too many proxy volumes related to master object master.
Resolution
Check the GDS configuration.
For details about the number of proxy volumes, see "2.3.13 Number of Proxy Volumes."
ERROR: master: corresponding proxy volume name must be specified
Explanation
There is no corresponding proxy volume name specified for master volume master.
Resolution
ERROR: proxy: proxy volume name duplicated
Explanation
The same proxy volume name proxy is specified for more than one master volume.
Resolution
Specify a different name, and execute again.
ERROR: volume: no such volume in group
Explanation
Volume volume does not exist in group group.
Resolution
Specify a correct volume name or group name, and execute again.
ERROR: object: object name duplicated
Explanation
The duplicate object name object was specified, or the group to which the volume object belongs and the volume object itself were specified at the same time.
Resolution
You can specify an object only once.
ERROR: proxy: already parted
Explanation
Proxy volume proxy is already parted.
Resolution
Nothing needs to be done.
ERROR: one point copy not availableExplanation
The OPC (One Point Copy) function is unavailable and proxy operations cannot be performed.
Resolution
See "(1) The Advanced Copy function cannot be used in master-proxy copying." in "D.1.8 Proxy Object Abnormality."
ERROR: proxy: already joined
Explanation
Proxy object proxy is already joined.
Resolution
Nothing needs to be done.
ERROR: proxy: not joined to master
Explanation
Proxy volume proxy is not joined to master volume.
Resolution
Join the proxy volume proxy to master volume according to need, and execute again.
ERROR: proxy: no such proxy object
Explanation
Proxy object proxy cannot be found.
Resolution
Specify a correct proxy object name.
ERROR: master: no such master object
Explanation
Master object master cannot be found.
Resolution
Specify a correct master object name.
ERROR: volume: exists in proxy group
Explanation
Volume volume is a proxy volume in proxy group.
Resolution
Specify a proxy group and execute again.
ERROR: group: not a proxy group
Explanation
group is not a proxy group group name.
Resolution
Check the GDS configuration, and specify a proxy group group name.
ERROR: volume: copying with EC
Explanation
Volume volume is in the process of EC copy.
Resolution
After the copying process is complete, execute again.
ERROR: volume: copying with OPC
Explanation
Volume volume is in the process of OPC copy.
Resolution
After the copying process is complete, execute again.
ERROR: volume: copying with TimeFinder
Explanation
Volume volume is being copied with TimeFinder.
Resolution
Execute the command again after the copying process is complete.
ERROR: volume: copying with SRDF
Explanation
Volume volume is being copied with SRDF.
Resolution
Execute the command again after the copying process is complete.
ERROR: volume: related to same master volume as proxy proxy, master=master
Explanation
Volume volume is related to the same master volume master as proxy volume proxy.
Resolution
Specify a correct volume name. For details, see "Appendix B Command Reference."
ERROR: master and proxy exist in same group group
Explanation
The specified master volume and proxy volume exist in the same group group.
Resolution
Specify volumes that exist in different groups.
ERROR: proxy: joined to master with EC, rejoin them by soft copy and try again
Explanation
Slices cannot be swapped since EC session in process between proxy proxy and master.
Resolution
Cancel the EC session by either of the following operations according to need and try this command again.
Part the master and the proxy once and rejoin them with the sdxproxy Rejoin -e softcopy command.
Break the relationship between the master and the proxy once and rejoin them with the sdxproxy Join -e softcopy command.
ERROR: proxy: joined to master with TimeFinder, rejoin them by soft copy and try again
Explanation
Slices cannot be swapped because there is a BCV pair between the proxy proxy and the master.
Resolution
Cancel the BCV pair by either of the following operations according to need and try this command again.
Part the master and the proxy once and rejoin them with the sdxproxy Rejoin -e softcopy command.
Break the relationship between the master and the proxy once and rejoin them with the sdxproxy Join -e softcopy command.
ERROR: proxy: joined to master with SRDF, rejoin them by soft copy and try again
Explanation
Slices cannot be swapped because there is an SRDF pair between the proxy proxy and the master.
Resolution
Cancel the SRDF pair by either of the following operations according to need and try this command again.
Part the master and the proxy once and rejoin them with the sdxproxy Rejoin -e softcopy command.
Break the relationship between the master and the proxy once and rejoin them with the sdxproxy Join -e softcopy command.
ERROR: volume: proxy volume cannot be specified when using TimeFinder
Explanation
You cannot specify volume when you perform parting, rejoining or restoring because there is a BCV pair between the proxy volume volume and the master.
Resolution
If you wish to perform parting, rejoining, or restoring, you must specify the group to which volume belongs when executing the command.
ERROR: volume: proxy volume cannot be specified when using SRDF
Explanation
You cannot specify volume when you perform parting, rejoining or restoring because there is an SRDF pair between the proxy volume volume and the master.
Resolution
If you wish to perform parting, rejoining, or restoring, you must specify the group to which volume belongs when executing the command.
ERROR: proxy: failed to start soft copy
Explanation
An error occurred when synchronization copying with the soft copy function was started between the proxy volume proxy and the master volume.
Resolution
Collect investigation material and contact field engineers.
ERROR: OPC not availableExplanation
The OPC function is unavailable.
Resolution
See "(1) The Advanced Copy function cannot be used in master-proxy copying." in "D.1.8 Proxy Object Abnormality."
ERROR: EC not availableExplanation
The EC function is unavailable.
Resolution
See "(1) The Advanced Copy function cannot be used in master-proxy copying." in "D.1.8 Proxy Object Abnormality."
ERROR: proxy: too many EC/OPC sessions
Explanation
The number of EC or OPC sessions within the physical disk (LU) or the disk array body has reached the upper limit of supported concurrent sessions. For this reason, a new EC or OPC session cannot be started.
Resolution
To make copying by EC or OPC available, wait until the running session ends, and try this command again. Alternatively, according to need, cancel the running session using the sdxproxy Cancel command, the sdxproxy Break command, or [Operation]:[Proxy Operation]:[Break] and try this command again.
ERROR: proxy: offset is different from master volume master
Explanation
Master volume master and proxy volume proxy have different top block (sector) numbers. The top block number is not a physical block number that indicates the offset on a physical disk, but is a logical block number that indicates the offset within a group (or a single disk) to which the volume belongs.
Resolution
As the proxy group, specify a group whose volume layout is consistent with the master group's.
For the top block (sector) number and size of volumes, use the sdxinfo command and check the 1STBLK field and the BLOCKS field of the displayed volume information.
ERROR: proxy: number of volumes is different from master group master
Explanation
Master group master and proxy group proxy include different numbers of volumes. The layout (offsets and sizes) of volumes within a master group and a proxy group must be consistent.
Resolution
For the proxy group, choose a group in which the layout of volumes is consistent with those of the master group.
ERROR: proxy: failed to start OPC, source=disk.volume, target=disk.volume, class=class
Explanation
An error occurred between the proxy volume proxy and the master volume when OPC started.
"source" indicates the copy source slice name, "target" indicates the copy destination slice name, and "class" indicates the class to which the copy source and the copy destination slices belong.
Resolution
Identify the cause by referring to GDS log messages, disk driver log messages, and ETERNUS Disk storage system log messages that were output right before the error occurrence, and recover the status.
ERROR: proxy: failed to start EC session, source=disk.volume, target=disk.volume, class=class
Explanation
An error occurred between the proxy volume proxy and the master volume when the EC session started.
"source" indicates the copy source slice name, "target" indicates the copy destination slice name, and "class" indicates the class to which the copy source and the copy destination slices belong.
Resolution
Identify the cause by referring to GDS log messages, disk driver log messages, and ETERNUS Disk storage system log messages that were output right before the error occurrence, and recover the status.
ERROR: copy region exceeds volume region, volume=volume, offset=blkno, size=size
Explanation
The region specified with the start block number blkno and the size size exceeds the region of the volume volume.
Resolution
Check the size of the volume volume using the sdxinfo command, and modify the copy region file.
ERROR: cannot open copy region file region_file, errno=errno
Explanation
Opening the copy region file region_file failed.
Resolution
Collect investigation material and contact field engineers.
ERROR: cannot read copy region file region_file, errno=errno
Explanation
Reading the copy region file region_file failed.
Resolution
Collect investigation material and contact field engineers.
ERROR: syntax error in copy region file region_file, line=line
Explanation
The copy region file region_file contains an error at the line indicated by line.
Resolution
Check contents of region_file.
ERROR: too many copy regions in copy region file region_file
Explanation
The copy region file region_file specifies too many copy regions.
Resolution
Modify region_file.
ERROR: copy region file region_file contains overlapping regions, line=line1, line=line2
Explanation
Copy regions file region_file specified in the lines indicated by line1 and line2 overlap.
Resolution
Check contents of region_file.
ERROR: OPC not available with multiple extentsExplanation
The disk unit may not support the OPC copy function with multiple extents or the function may not currently be available for some reason.
Resolution
Check the disk unit's hardware configuration. According to need, specify one copy region at a time and execute the command for every region.
ERROR: cannot get configuration information, sdxinfo(1) command failed
Explanation
The sdxinfo(1) command failed, and GDS configuration information could not be obtained.
Resolution
Remove the error after identifying the cause by referring to the message for the sdxinfo(1) command that was output right before the occurrence of the error, and try the sdxproxy Root command again.
ERROR: volume: alternative volume altvol already specified for volume curvol
Explanation
Another alternative volume volume was assigned to the volume curvol for which the alternative volume altvol has already been specified.
Resolution
You can specify only one alternative volume for a volume.
ERROR: volume: corresponding volume not specified in /etc/fstab
Explanation
The volume volume is not the alternative volume of a volume described in /etc/fstab as a file system or a swap area.
Resolution
Specify a volume that fits one of the following requirements.
Proxy volume of a master volume described in the /etc/fstab file
Master volume of a proxy volume described in the /etc/fstab file
Another proxy volume related to the master volume of a proxy volume described in the /etc/fstab file
If this message was output when a master or proxy group was specified and the sdxproxy Root command was executed, see "(2) Alternative boot environment setup fails resulting in an error numbered 60305. [EFI]" in "D.1.8 Proxy Object Abnormality."
ERROR: volume: read only volume
Explanation
The access mode of the volume volume is ro (read only). Since a read-only volume cannot be mounted, this cannot be configured for an alternative boot environment.
Resolution
Change the access mode attribute of the volume volume to rw (read and write) using the sdxattr -V command, and try this command again.
ERROR: alternative root volume must be specifiedExplanation
The alternative root volume has not been specified.
Resolution
You must specify the alternative root volume.
ERROR: volume: file system cannot be checked or repaired, command command failed, exit-status=exitstat
Explanation
The command command ( fsck(8) or xfs_repair(8) ) for the volume volume failed, and a file system on volume could not be inspected or repaired.
The exit status of the command command is exitstat. Inconsistency may have arisen in the file system on volume.
Resolution
Remove the error after identifying the cause by referring to the message for the command command that was output right before the occurrence of the error and to the manual for the command command. If required, restore the data on volume, for example, using the backed up data, and try the sdxproxy Root command again.
ERROR: volume: file system cannot be mounted, mount(8) command failed, exit-status=exitstat
details
Explanation
The mount(8) command for the volume volume failed, and the file system on volume could not be mounted.
The exit status of the mount(8) command is exitstat. details is the error message for the mount(8) command.
Resolution
Remove the error after identifying the cause based on details, and try the sdxproxy Root command again.
ERROR: volume: cannot change boot disks, efibootmgr(8) command failed, exit-status=exitstat
details
Explanation
The efibootmgr(8) command failed and the boot manager setting to boot from the volume volume was not set.
The exit status of the efibootmgr(8) command is exitstat. details is the error message for the efibootmgr(8) command.
Resolution
Remove the error after identifying the cause based on details, and try the sdxproxy Root command again.
ERROR: volume: file system cannot be unmounted, umount(8) command failed, exit-status=exitstat
details
Explanation
The umount(8) command for the volume volume failed, and the file system on volume temporarily mounted could not be unmounted.
The exit status of the umount(8) command is exitstat. details is the error message for the umount(8) command.
Resolution
Remove the error after identifying the cause based on details, unmount volume, and try the sdxproxy Root command again.
ERROR: class: not a shadow class
Explanation
The class class is not a shadow class.
Resolution
See "Appendix B Command Reference" and specify a proper command name and class name.
ERROR: device: no configuration information
Explanation
Since no configuration information resides in the private slice on the physical disk device or no private slice exists on device, device cannot be registered with a shadow class.
The possible causes are as follows.
a) device is not registered with a class in another domain yet, and the private slice has not been copied from the SDX disk to device with the disk unit's copy function. In addition, the disk is not a disk previously removed from a class with the sdxconfig Remove -e keepid command.
b) device is already registered with a class in another domain, but has not been enabled.
c) The private slice has been copied from the SDX disk to device with the disk unit's copy function, but the copy source SDX disk has not been enabled.
Resolution
Check on the system configuration and so on, and identify which cause among a), b) and c) applies. If the cause is a), see "Appendix B Command Reference" and specify a correct command name and physical disk name. If it is b), restore device in another domain. If it is c), restore the copy source SDX disk.
ERROR: device: registered with illegal class in another domain
Explanation
While the physical disk device is already registered with a different class in another domain, registering it with the same shadow class was attempted.
Resolution
You should register a disk registered with the same class in another domain with one shadow class.
ERROR: device: disk: not same as disk name diskname in another domain
Explanation
The physical disk device is already registered as diskname with a class in another domain. It cannot be registered with a shadow class as disk that is another disk name.
Resolution
Specify the same disk name diskname as in another domain.
ERROR: device: private slice size not same as another disk in class
Explanation
Since the physical disk device has the private slice that is unequal in size compared to the private slices on other disks registered with the shadow class class, it cannot be registered with class.
Resolution
Check on the system configuration and so on, and specify a correct disk name and shadow class name.
ERROR: device is bound to RAW device.
Explanation
The device to be registered has been bound to a RAW device. With GDS, you cannot register disks bound to a RAW device.
Resolution
Register a disk not bound to a RAW device. Alternatively, cancel the bind to a RAW device using the raw(8) command and then register.
ERROR: no license
Explanation
The command cannot be executed. The possible causes are as follows.
a) In a system where the FJSVsdx-cmd package of GDS is not installed normally, the sdxconfig command was used.
b) In a system where the FJSVsdx-ss package of GDS Snapshot is not installed normally, the sdxshadowdisk command was used.
Resolution
To use the sdxconfig command, install FJSVsdx-cmd normally. To use the sdxshadowdisk command, install FJSVsdx-ss normally.
ERROR: output file already existsExplanation
The specified output file is an existing file.
Resolution
Specify a nonexistent file name. To overwrite an existing file, use the -e update option.
ERROR: failed to create configuration fileExplanation
Configuration file creation failed.
Resolution
Check whether the specified path to the configuration file is correct.
ERROR: class: failed to get configuration information
Explanation
Acquisition of class configuration information failed.
Resolution
If a message is output right before this error has occurred, follow the message to take corrective actions. If a message is not output, collect investigation material and contact field engineers.
ERROR: proxy: proxy volume exists in class
Explanation
Proxy volume proxy exists in class.
Resolution
Break the relationship of proxy volume proxy to the master as needed.
ERROR: group: switch group exists in class
Explanation
Class class includes switch group group. The attempted operation is not supported for classes that include switch groups.
Resolution
Delete the group as needed and re-execute the command.
ERROR: failed to output configuration table
Explanation
Sending the configuration table to standard output or to a configuration file failed.
Resolution
Collect investigation material and contact field engineers.
ERROR: input file not foundExplanation
The specified input file does not exist.
Resolution
Specify a correct file name.
ERROR: class : not same as class name name in configuration table
Explanation
The specified class name class is different from the class name name in the configuration table.
Resolution
Specify a correct class name, or change the class name in the configuration table to class with the sdxconfig Convert command.
ERROR: disk : no such disk in configuration table
Explanation
The configuration table does not contain disk disk.
Resolution
Specify a correct disk name.
ERROR: device : no such device in configuration table
Explanation
The configuration table does not contain physical disk device.
Resolution
Specify a correct physical disk name.
ERROR: group : no such group in configuration table
Explanation
The configuration table does not contain group group.
Resolution
Specify a correct group name.
ERROR: object : exists in type group in configuration table
Explanation
In the configuration table object that is a disk or a lower level group is connected to a type type group. Disks connected to concat or stripe type groups and lower level groups connected to stripe type groups cannot be removed from configuration tables.
Resolution
Specify a correct disk name or group name.
ERROR: at least one object must remain in configuration tableExplanation
Removing the specified objects from the configuration table will result in no object in the configuration table. A configuration table needs to contain a minimum of one object.
Resolution
Specify correct object names.
ERROR: object.volume is only valid slice in configuration table
Explanation
In the configuration table slice object.volume is an only valid slice that comprises mirror volume volume. For this reason, object that is a disk or a lower level group cannot be removed from the configuration table.
Resolution
Specify a correct disk name or group name.
ERROR: class : not a local class
Explanation
Class class is not a local class.
Resolution
Specify a local class.
ERROR: file name too longExplanation
The specified file name contains too many characters.
Resolution
Specify a correct file name.
ERROR: failed to open input file, errno=errno
Explanation
Input file open failed.
Resolution
Identify the cause based on the error number errno.
ERROR: configuration table corrupted, sdxfunc=sdxfunc, sdxerrno=sdxerrno
Explanation
Contents of the configuration table are invalid.
Resolution
Collect investigation material and contact field engineers.
ERROR: class : already exists
Explanation
Class class already exists.
Resolution
Change the class name in the configuration table with the sdxconfig Convert command and re-execute the command.
ERROR: class : already exists in another node
Explanation
Class class already exists in another node.
Resolution
Change the class name in the configuration file with the sdxconfig Convert command and re-execute the command.
ERROR: device : assigned to disk1 and disk2 in configuration table
Explanation
In the configuration table one physical disk device is assigned to disks disk1 and disk2.
Resolution
Change the physical disk assigned to disk1 or disk2 in the configuration table with the sdxconfig Convert command and re-execute the command.
ERROR: device : failed to get physical disk information
Explanation
Acquisition of geometry information, partition table, or the device number of physical disk device failed.
Resolution
Check whether physical disk device is normally operating.
ERROR: device : size must be size blocks
Explanation
The physical disk device must have size blocks.
Resolution
Replace physical disk device with a physical disk that has size blocks. Alternatively, change physical disk device in the configuration table to another physical disk that has size blocks with the sdxconfig Convert command.
ERROR: device : private slice size must be size blocks
Explanation
The size of the private slice of physical disk device is different from that described in the configuration table and therefore the class object configuration cannot be restored. The private slice of device must have size blocks.
Resolution
Exchange physical disk device for a physical disk whose private slice size is size blocks. Alternatively, change physical disk device in the configuration table to another physical disk whose private slice size is size blocks with the sdxconfig Convert command.
ERROR: mismatch of class names in private slices on device1 and device2
Explanation
The class names of physical disks device1 and device2 stored in the private slices do not match and therefore device1 and device2 cannot be registered with one class.
Resolution
Check the system configuration and edit the physical disks described in the configuration table with the sdxconfig Convert command.
ERROR: device : mismatch of disk names, disk1 in private slice, disk2 in configuration table
Explanation
The disk name disk1 stored in the private slice does not match the disk name disk2 described in the configuration table and therefore physical disk device cannot be registered as disk disk2 with a class.
Resolution
Check the system configuration and edit the physical disks described in the configuration table with the sdxconfig Convert command.
ERROR: class : restoration based on configuration file failed
Explanation
Restoration of the class configuration based on configuration file file failed.
Resolution
When using multipath, register the native device to each node's Excluded Device List. For the Exclude Device List, see "6.1 Creating Excluded Device List"
Otherwise, collect investigation material and contact field engineers.
ERROR: class: some node trying to get class master privilege
Explanation
The current node or some other node is trying to obtain master privileges of shared class class.
Resolution
If necessary, try the command again after a while.
ERROR: class: class master not found
Explanation
The class master of shared class class is not found and no operation is possible for class.
Resolution
If necessary, try the command again after a while.
ERROR: found invalid device name at the shared disk definition file (rid=val)
Explanation
Shared disk unit resource information contains an error.
val is the misdefined shared disk unit's resource ID.
Resolution
The shared disk unit managed as a val resource is not one disk unit if seen from separate nodes.
Remove the incorrect resource information, and create a correct resource.
For shared disk unit removal and registration, see "6.3 Shared Disk Resource Registration."
ERROR: node : physical disk not found
Explanation
Some physical disks are no longer recognized by the OS after the node node restarted.
Confirm unrecognizable physical disks with the following method.
Execute the sdxinfo -D command on the relevant node.
Unrecognizable disks are those indicated by the asterisk (*) in the DEVNAM field in the command output.
Resolution
Unrecognizable physical disks may be failed disks. Check whether they are failed and perform certain maintenance such as disk swap, and then retry the relevant operation.
ERROR: found node(s) which udev environment setting has not been set correctly details
Explanation
Although the use of udev was attempted during the GDS processing, udev was not available due to an invalid environment.
This is a details environment issue.
Resolution
Collect investigation material and contact field engineers.
ERROR: node : no enough address space
Explanation
Memory allocation failed on node.
Resolution
Identify the cause of the memory or swap space insufficiency on node and take corrective action, and then retry the relevant operation.
ERROR: node : SWAP status disk is found
Explanation
A SWAPPED disk exists on node.
Resolution
Recover the SWAPPED disk on node.
ERROR: node : class closed down is found
Explanation
A closed class exists on node.
Resolution
Recover the closed class on node.
For the recovery method, see "D.1.4 Class Status Abnormality."
ERROR: you may not run this command while another command is runningExplanation
This command cannot be executed while other commands are running.
On a node in a cluster domain, the following commands cannot run together.
clautoconfig -f
sdxdisk -M
sdxdisk -R
sdxswap -O
sdxswap -I
sdxclass -R
sdxconfig Restore
sdxconfig Remove
Resolution
Execute the command again after the command is executed on another node.
When unmirroring the system disk of the GDS Management View on multiple nodes in the cluster system, and restarting the nodes at the same time, this message may be output on the system log of some nodes by the sdxclass command after the nodes are restarted. In this case, the object in the root class of the nodes are left without removed. Follow "9.3 Removing Volumes, Groups, and Classes" to remove the object in the root class.
ERROR: node : failed to access an internal file file, errno=errno
Explanation
Accessing the file file on node failed.
Resolution
Collect investigation material and contact field engineers.
ERROR: node : failed to obtain udev information from one of the devices
Explanation
A device whose udev information cannot be obtained exists on node.
Resolution
Collect investigation material and contact field engineers.
ERROR: node : failed to update configuration database
Explanation
Updating the configuration database failed.
Resolution
The possible cause of this failure is that all of or most of the disks registered with the class are no longer accessible.
Identify the cause and recover the disks to gain normal access.
If this message is output, the class is closed immediately. After recovering the disks, also restart the class and then retry the relevant operation.
ERROR: device : mklavel command failed
Explanation
Setting the device label failed.
The parted command is not installed, or failed.
Resolution
Install the parted command and re-execute it.
When an error occurs, collect investigation material and contact field engineers.
ERROR: volume: related to proxy volume proxy with QuickOPC
Explanation
QuickOPC session exists between volume volume and proxy volume proxy.
Resolution
Cancel the relationship of master volume volume and proxy volume proxy according to need, and execute again.
ERROR: volume: related to master volume master with QuickOPC
Explanation
QuickOPC session exists between volume volume and master volume master.
Resolution
Use the sdxproxy Cancel command and cancel the QuickOPC session between master volume master and proxy volume volume according to need. Alternatively, as needed, cancel the relationship of master volume master and proxy volume volume, and execute again.
ERROR: device: too large for class of MSDOS labeled disks
Explanation
The capacity of a physical disk device is 2 TB or larger, so it cannot be registered with the class of MSDOS labeled disks.
Resolution
Register disks with the size smaller than 2 TB. Or, register disks to a new class or a class of GPT labeled disks. The disk label type of a class can be viewed in the LABEL field that is displayed with the sdxinfo -C -e label command.
ERROR: volume: copying with QuickOPC
Explanation
Volume volume is in the process of QuickOPC copy.
Resolution
After the copying process is complete, execute again.
ERROR: QuickOPC not availableExplanation
The QuickOPC function is unavailable. Check the following causes:
a) Multiple proxy volumes are related to the master volume and the number of proxy volume to which QuickOPC sessions are set reaches the upper limit(15).
b) Other causes.
Resolution
For a), take one of the following actions and perform the operation again.
Cancel the QuickOPC session set to the operational master volume with the sdxproxy Cancel volume.
Cancel the relation of the operational master volume and the proxy volume to which QuickOPC sessions are set with the sdxproxy Break command.
For b), see "(1) The Advanced Copy function cannot be used in master-proxy copying." in "D.1.8 Proxy Object Abnormality."
ERROR: proxy: failed to start QuickOPC session, source=disk.volume, target=disk.volume, class=class
Explanation
An error occurred between proxy volume proxy and the master volume when QuickOP was initiated.
"source" indicates the copy source slice name, "target" indicates the copy destination slice name, and "class" indicates a class to which the copy source and destination slices belong.
Resolution
Identify the cause based on log messages of GDS, disk drivers, ETERNUS Disk storage system and such, and promptly recover the disk.
ERROR: patch levels are different between nodes in the class scopeExplanation
This message is output on one of the following:
a) The node where the setting of the parameter (SDX_EFI_DISK=on) is described in the GDS configuration parameter file /etc/opt/FJSVsdx/sdx.cf and the node not described exist together in the cluster system.
Conducting the following operation in this state will output this message.
Registration of disk to the shared class.
Changing the type from local class to the shared class.
b) Cannot install GDS I/O Monitor Option to the cluster system.
When setting the I/O Response Time Assurance Function for the shared class in this state, this message is output.
Resolution
Take the following action according to the cause, and then execute the operation again.
a) Use the same parameter value of SDX_EFI_DISK described in the GDS configuration parameter file for all nodes in the cluster system.
b) Install GDS I/O Monitor Option to all the nodes within the cluster system.
ERROR: device: disk label is not matched with class class
disk label of class = class-label
disk label of device = device-label
Explanation
Restoration of class cannot be performed because the disk label type of a physical disk device (device-label) is different from that of a class class (class-label) described in the configuration table.
Resolution
If a wrong configuration file is specified, specify the correct configuration file name.
If a correct configuration file is specified, perform one of the following operations. When you perform one of the following operations, data in volume area on the physical disk registered with class is not ensured. For restoring volume data, restore the backup data after the following operation:
Change the device disk label to class-label type with the parted(8) command and restore class again.
Restore class with -e mklabel option again.
ERROR: device: too large for root class
Explanation
The capacity of a physical disk device is 1 TB or larger, so it cannot be registered with a root class.
Resolution
Register disks with the size smaller than 1 TB with a root class.
ERROR: option1 and option2 cannot be specified at the same time
Explanation
The command options, option1 and option2, cannot be specified simultaneously.
Resolution
See "Appendix B Command Reference" and specify the applicable option.
ERROR: command is already running
Explanation
The command cannot be executed because the command command has already been run.
Resolution
Check that the process of command has stopped with the ps command, and then execute the command again.
ERROR: file already exists
Explanation
The processing cannot be executed because the file file has already been existed.
Resolution
Either delete the file file or move it to the other directory.
ERROR: device: failed to get multipath information on some node in physical scope
Explanation
The multipath information could not be obtained on any one of nodes where the physical disk device is connected.
Resolution
Check if the multipath software setting is correct on all nodes where the physical disk device is connected.
ERROR: device: failed to get device information on some node in physical scope
Explanation
The device information could not be obtained on any one of nodes where the physical disk device is connected.
Resolution
Check if the physical disk device operates normally on all nodes where it is connected.
ERROR: device: by-id file not found on some node in physical scope
Explanation
The by-id file cannot be found on any one of nodes where the physical disk device is connected.
Resolution
Check if the physical disk device operates normally on all nodes where it is connected.
ERROR: device: failed to get multipath information, details
Explanation
The multipath information of the physical disk device failed to be obtained.
Resolution
Check if the multipath software is set properly.
ERROR: device: failed to get device information, iscsiadm ret=ret
Explanation
The device information of the physical disk device failed to be obtained.
ret is the return value of the iscsiadm command.
Resolution
See the iscsiadm command manual to take corrective actions.
ERROR: device: by-id file not found
Explanation
The by-id file of the physical disk device cannot be found.
Resolution
Check if the physical disk device works properly.
ERROR: sfdsk driver is not startingExplanation
The sfdsk driver is not started.
Resolution
Execute the command again after the sfdsk driver is started.
ERROR: environment error, details
Explanation
The command cannot be executed due to an error in the environment.
Resolution
Collect investigation material and contact field engineers.
ERROR: netmirror group cannot be created in this environmentExplanation
The mirroring among servers is available when one of the following products is used.
PRIMECLUSTER Enterprise Edition
PRIMECLUSTER HA Server
PRIMECLUSTER Clustering Base and PRIMECLUSTER GDS
When attempting to create the netmirror group in the system where the above products are not properly installed, this message is output and the netmirror group cannot be created.
Resolution
Check that any product described in "Explanation" above is properly installed.
If this message is still output after any one of the above products is properly installed, collect investigation material and contact field engineers.
ERROR: one disk in each of nodes needs to be connected to a netmirror group
Explanation
This message is output under the following conditions when the second disk is connected to the netmirror group.
a. A disk is to be connected to the netmirror group where the other disk on the same node is already connected.
b. A disk already connected to the netmirror group or a disk to be connected to the netmirror group is not the device that has been created in the procedure "4.8 Disk Setting for Performing Mirroring among Servers."
Resolution
For the condition a, change the netmirror group configuration so that the iSCSI device for the disk of any node in the class scope can be included.
For the condition b, connect the iSCSI device that is set up according to "4.8 Disk Setting for Performing Mirroring among Servers"to the netmirror group.
ERROR: failed to initialize NVURMExplanation
The log (NVURM) for the Just Resynchronization Mechanism (JRM) failed to be initialized.
Resolution
Check the I/O error message of NVURM. If the disk has a failure, replace the disk.
ERROR: volume: file system uuid cannot be changed, xfs_admin(8) command failed, exit-status=exitstat
Explanation
The xfs_admin(8) command for the volume volume failed, and UUID of volume cannot be changed.
The exit status of the xfs_admin(8) command is exitstat. Inconsistency may have arisen in the file system on volume.
Resolution
Remove the error after identifying the cause by referring to the message for the xfs_admin(8) command that was output right before the occurrence of the error and to the manual for the xfs_admin(8) command. If required, restore the data on volume, for example, using the backed up data, and try the sdxproxy Root command again.
ERROR: cannot create netmirror group in root classExplanation
The netmirror group cannot be created in the root class.
Resolution
Create the netmirror group in the shared class.
ERROR: cannot connect three or more disks to netmirror groupExplanation
Three or more disks cannot be connected to the netmirror group.
Resolution
Connect maximum two disks to the netmirror group.
ERROR: cannot create netmirror group in class including other type group, single disk, or spare diskExplanation
The netmirror group cannot be created in a class where a group other than the netmirror group, the single disk, or the spare disk exists.
Resolution
Check if the specified class name, the group type attribute, and the object configuration in the class are correct.
If the specified class name or the group type attribute are incorrect, specify the correct class name and the correct group type attribute and then perform the operation again.
If the object configuration in the class is incorrect, correct the configuration.
ERROR: cannot create netmirror group in class other than shared classExplanation
The netmirror group cannot be created in a class other than the shared class.
Resolution
Create the netmirror group in the shared class.
ERROR: cannot create netmirror group in class when three or more nodes exist in class scopeExplanation
The netmirror group cannot be created in the shared class where the class scope includes 3 or more nodes.
Resolution
Create the netmirror group in the shared class where the class scope includes 2 nodes.
ERROR: cannot create group other than netmirror group in class including netmirror groupExplanation
A group other than the netmirror group cannot be created in a class where the netmirror group exists.
Resolution
Check if the specified class name, the group type attribute, and the object configuration in the class are correct.
If the specified class name or the group type attribute are incorrect, specify the correct class name and the correct group type attribute and then perform the operation again.
If the object configuration in the class is incorrect, correct the configuration.
ERROR: cannot disconnect disk from netmirror group including volumeExplanation
A disk cannot be disconnected from the netmirror group where the volume exists.
Resolution
When disconnecting the disk from the netmirror group, delete the volume first.
ERROR: cannot register disk other than undef disk with class including netmirror groupExplanation
In a class where the netmirror group exists, only the undef type disk can be registered.
Resolution
Check if the specified class name, the disk type attribute, and the object configuration in the class are correct.
If the specified class name or the disk type attribute are incorrect, specify the correct class name and the correct disk type attribute and then perform the operation again.
If the object configuration in the class is incorrect, correct the configuration.
ERROR: cannot connect group to netmirror groupExplanation
A group cannot be connected to the netmirror group.
Resolution
Connect a disk to the netmirror group.
If the specified group name is incorrect, specify the correct group name, and then perform the operation again.
ERROR: cannot connect netmirror group to other groupExplanation
The netmirror group cannot be connected to other groups.
Resolution
Specify the group other than the netmirror group, and then perform the operation again.
ERROR: cannot set jrm to off for netmirror volumeExplanation
The JRM attribute of the netmirror volume cannot be set to off.
Resolution
Specify on for the JRM attribute when creating the netmirror volume.
ERROR: cannot create volume in netmirror group including only one diskExplanation
The volume cannot be created in the netmirror group where only one disk is connected.
Resolution
Before creating the volume, connect 2 disks to the netmirror group.
ERROR: cannot detach slice temporarily from netmirror volumeExplanation
A slice of the netmirror volume cannot be temporarily detached.
Resolution
If the specified volume name is incorrect, specify the correct volume name, and then perform the operation again.
ERROR: cannot set three or more nodes to scope of class including netmirror groupExplanation
The class scope where the netmirror group exists cannot be changed to 3 or more nodes.
Resolution
If the specified class name is incorrect, specify the correct class name, and then perform the operation again.
ERROR: cannot change attribute value of disk in class including netmirror groupExplanation
If the netmirror group exists in a class, the disk type attribute in the class cannot be changed.
Resolution
If the specified class name is incorrect, specify the correct class name, and then perform the operation again.
ERROR: cannot perform proxy operation for netmirror objectExplanation
Join and Relate operations cannot be performed to the netmirror volume or the netmirror group.
Resolution
If the specified object is incorrect, specify the correct object, and then perform the operation again.
ERROR: class: same class id assigned to another class in scope
Explanation
The same class ID as the class ID of the class class is used in another class on the node to be added to the scope.
Resolution
Take the following steps to remove the class class, and after recovering the status, change the scope.
Back up the object configuration information of the class in which a node is added to the scope. (sdxconfig Backup command)
Stop the volume of the class in which a node is added to the scope. (sdxvolume -F command)
For the shared class, change the class in which a node is added to the scope to the local class. (sdxattr -C command)
Remove the object configuration information of the class in which a node is added to the scope. (sdxconfig Remove command)
Restore the object configuration information of the class in which a node is added to the scope. (sdxconfig Restore command)
Add a node to the scope in the restored local class. (sdxattr -C command)
ERROR: cannot change jrm to off for netmirror volumeExplanation
The JRM attribute of the netmirror volume cannot be changed to off.
Resolution
If the specified volume name is incorrect, specify the correct volume name, and then perform the operation again.
ERROR: cannot find local device
Explanation
The disk without the iSCSI device setting is connected to the netmirror group.
Resolution
Follow "4.8 Disk Setting for Performing Mirroring among Servers" to set the iSCSI device, and then, execute the operation again.
ERROR: file: failed to delete file
Explanation
The /var/opt/FJSVsdx/log/file file could not be deleted.
Resolution
Delete the /var/opt/FJSVsdx/log/file file if it exists. For the cluster configuration, check if the /var/opt/FJSVsdx/log/file file exists on all the nodes that configure the cluster.
If the file does not exist or this message is still output after deleting the file, collect investigation material, and then contact field engineers.
ERROR: cannot register number or more disks to class including netmirror group
Explanation
Cannot register number or more disks to the class where the netmirror group exists.
Resolution
Register up to number or less disks to the class where the netmirror group exists.
ERROR: cannot create netmirror group in class including number disks
Explanation
If number or more disks are registered in the class, the netmirror group cannot be created.
Resolution
Register up to number or less disks to the class where the netmirror group is to be created.
ERROR: cannot operate -e force option in class not including netmirror groupExplanation
The -e force option can only be used when specifying the disk connected to the netmirror group.
Resolution
Use the -e force option only when specifying the disk connected to the netmirror group.
ERROR: cannot open /etc/fstabExplanation
The /etc/fstab file cannot be opened, and the setting of the system disk mirroring cannot be confirmed. In this case, the parameter cannot be set.
Resolution
The /etc/fstab file may have an error. Check that the /etc/fstab file is normal, and then execute the command again.
ERROR: system disk is already mirroredExplanation
The parameter cannot be set because the system disk mirroring is already configured.
Resolution
Cancel the system disk mirroring once, and then execute the command again.
ERROR: cannot find root filesystem information in /etc/fstabExplanation
The information of the root file system is not described in the /etc/fstab file, and the configuration of the system disk mirroring cannot be confirmed. In this case, the parameter cannot be set.
Resolution
The /etc/fstab file may have an error. Check that the /etc/fstab file is normal, and then execute the command again.
ERROR: device: failed to update disk partition (errno=errno)
Explanation
The process to update a disk partition failed.
Resolution
When errno=16, make sure that the disk device has no error. After that, perform the operation again.
When errno is other than 16, contact field engineers.
ERROR: device: failed to delete a partition from the disk (errno=errno)
Explanation
The process to delete a partition from the disk failed.
Resolution
When errno=16, make sure that the disk device has no error. After that, perform the operation again.
When errno is other than 16, contact field engineers.
ERROR: device: failed to setup netmirror device
Explanation
The settings related to the mirroring among servers of the physical disk device failed.
Resolution
Collect investigation material and contact field engineers.
ERROR: cannot swap disk connected to netmirror group in local classExplanation
The disk connected to the netmirror group in the local class can not be swapped.
Resolution
Change the class to the shared class, and then perform the operation again.
ERROR: command command failed
Explanation
The command command cannot be executed.
Resolution
Collect investigation material, and contact field engineers.
ERROR: /boot file system not mountedExplanation
/boot file system is not mounted.
Resolution
Mount /boot file system first, and then execute the command again.
ERROR: cannot open /etc/opt/FJSVsdx/modules/sfdsk.confExplanation
/etc/opt/FJSVsdx/modules/sfdsk.conf cannot be opened.
Resolution
Collect investigation material, and contact field engineers.
ERROR: failed to create temporary fileExplanation
The temporary file cannot be created.
The possible causes are as follows:
a) /var file system is not mounted.
b) Insufficient capacity in /var/opt.
c) The file system is corrupted or the disk fails.
Resolution
Take the following steps, and then execute the command again:
1) Mount /var file system if it is not mounted.
2) If storage capacity in /var/opt is less than 100MB, delete unnecessary files to secure 100MB or more storage capacity in /var/opt. After that, restart the system.
If the cause of the error cannot be specified or the error occurs again after the command is executed, collect investigation material, and contact field engineers.
ERROR: cannot get partition number of file system including /bootExplanation
The partition number of the device of the file system including /boot cannot be obtained.
Resolution
Take the following steps:
Execute the following command to update the partition number information managed by GDS.
# /etc/opt/FJSVsdx/bin/sdxbootpart -SExecute the command that causes this error.
Execute sdxbootpart command only in the steps described in this manual or other GDS documents.
ERROR: failed to update /boot/efi/EFI/redhat/grub.cfgExplanation
/boot/efi/EFI/redhat/grub.cfg file cannot be updated.
Resolution
Collect investigation material, and contact field engineers.
ERROR: class: closing down class on node node, failed to update netmirror device information
Explanation
The class class has closed in the node node due to the device information of the netmirror group has failed to be updated.
Resolution
Take the following steps, and then execute the command again:
Restore the file or file system.
When no available capacity under /var/opt
Delete unnecessary files to secure 100MB or more free capacities under /var/opt. After that, restart the system.
When enough capacity available under /var/opt
Output the /var/opt/FJSVsdx/log/.sdxnetmirror_disable.db file by the cat command, and check that the output is not garbled.
If it is garbled, delete the file and then restart the system.
If it is not garbled, collect investigation material and contact field engineers.
Check that the class is not closed on the node which has not been restarted.
Execute the following command on the node which has not been restarted. If "yes" is displayed in the DOWN field, the class is closed.
# /etc/opt/FJSVsdx/bin/sdxdcdownRestore the class if it is closed in step 2.
Execute the following command on the node which has not been restarted.
# sdxfix -C -c class_nameERROR: class: failed to update netmirror device information
Explanation
The command has failed due to the device information of the netmirror group of class class has failed to be updated.
Resolution
Take the following steps, and then execute the command again:
When no available capacity under /var/opt
Delete unnecessary files to secure 100MB or more free capacities under /var/opt. After that, restart the system.
When enough capacity available under /var/opt
Output the /var/opt/FJSVsdx/log/.sdxnetmirror_disable.db file by the cat command, and check that the output is not garbled.
If it is garbled, delete the file and then restart the system.
If it is not garbled, collect investigation material and contact field engineers.
ERROR: I/O monitor option is not installedExplanation
GDS I/O Monitor Option was not installed correctly.
Resolution
Install the GDS I/O Monitor Option correctly when using the sdsdisk -M command or the sdxattr -C command to set up the I/O Response Time Assurance, or using the sdxinfo -I command to check the information of the I/O Times Response Assurance.
ERROR: class: cannot change iotimeout attribute value to on, concat or stripe group exist
Explanation
The iotimeout attribute of the class cannot be changed to on because concat or stripe type groups exist in the class class.
Resolution
Check if there is no mistake in the specified class name or the object configuration in the class class.
If there is a mistake in the specified class name, specify the correct class name and execute again.
If there is a mistake in the object configuration in the class, change it to the correct configuration.
ERROR: class: cannot create concat or stripe group, iotimeout attribute value is on
Explanation
Concat and stripe type groups cannot be created because the iotimeout attribute in class class is on.
Resolution
Check if there is no mistake in the specified class name or the iotimeout attribute value.
If there is a mistake in the specified class name, specify the correct class name and execute again.
If there is a mistake in the iotimeout attribute value of the class, use the sdxattr command to change the iotimeout attribute to off.
ERROR: only iotimeout attribute can be specifiedExplanation
Only the iotimeout attribute can be specified in the root class.
Resolution
Check if there is no mistake in the specified class name or the object configuration in the class class.
If there is a mistake in the specified class name, specify the correct class name and execute again.
If there is a mistake in the specified attribute, specify the correct attribute and execute again.
ERROR: class: cannot change iotimeout attribute value to on, netmirror group exist
Explanation
The iotimeout attribute of the class cannot be changed to on because netmirror type of group exists in the class class.
Resolution
Check if there is no mistake in the specified class name or the object configuration in the class class.
If there is a mistake in the specified class name, specify the correct class name and execute again.
If there is a mistake in the object configuration in the class, change it to the correct configuration.
ERROR: class: cannot create netmirror group, iotimeout attribute value is on
Explanation
Netmirror type group cannot be created because the iotimeout attribute in the class class is on.
Resolution
Check if there is no mistake in the specified class name or the iotimeout attribute value in the class class.
If there is a mistake in the specified class name, specify the correct class name and execute again.
If there is a mistake in the iotimeout attribute value of the class, use the sdxattr command to change the iotimeout attribute to off.
ERROR: netmirror DB file is invalid, volume=volume
Explanation
For the disks that make up the volume volume, the disk containing the latest data cannot be determined because there is an inconsistency in information to determine the disk containing the latest data.
Resolution
ERROR: object.volume is only not pre-detached slice
Explanation
The slice object.volume is the only slice that is not pre-detached in the netmirror volume volume.
Operation cannot be performed because continuing operation may result in data loss of volume.
Resolution
Wait until the other slice in volume is detached and it becomes INVALID.
After that, if the INVALID slice is restored, operation of object.volume can be performed.
When restoring the INVALID slice, see "(1) The netmirror slice that configures the netmirror volume is in INVALID state." in "D.1.6 Errors in the Mirroring Among Servers."
ERROR: volume: netmirror volume must be specified
Explanation
The netmirror volume must be specified.
Resolution
Specify the netmirror volume.
ERROR: failed to update netmirror DB file, volume=volume
Explanation
Update of netmirror device information has failed.
Resolution
If the INVALID status slice exists within the netmirror volume volume, and other nodes are LEFTCLUSTER or DOWN.
Synchronization copying of netmirror volume fails.
Restore the node first. After that, execute the sdxcopy -B command, for example, to perform the synchronization copying.
For how to recover from the LEFTCLUSTER state, see "PRIMECLUSTER Cluster Foundation (CF) Configuration and Administration Guide."
Otherwise
Take the following procedure to restore.
Restore the file system or file with all of the nodes.
When no available capacity under /var/opt
Delete unnecessary files to secure 100MB or more free capacities under /var/opt. After that, restart the system.
When enough capacity available under /var/opt
Output the /var/opt/FJSVsdx/log/.sdxnetmirror_disable.db file by the cat command, and check that the output is not garbled.
If it is garbled, delete the file and then restart the system.
If /var/opt on all of the nodes has capacity and the file is not garbled, collect investigation material and contact field engineers.
Depending on the slice status within the netmirror volume volume, take the following procedure.
When the NOUSE status slice does not exist in the netmirror volume volume.
Synchronization copying of netmirror volume fails.
Perform the synchronization copying by using the sdxcopy -B command, for example.
When the NOUSE status slice exists in the netmirror volume volume.
Restore NOUSE status of the slice. For details, see "(6) Slice configuring the volume is in NOUSE status." in "D.1.1 Slice Status Abnormality."
ERROR: node: physical disk read error
Explanation
A read error occurred on a physical disk on node node.
Resolution
The possible cause is a disk failure. Identify the cause based on disk driver log messages and so on and restore the disk.
ERROR: no valid slice left in sfdsk driver on node node
Explanation
Operation cannot be continued because no valid slices are left in the sfdsk driver of the node node.
Resolution
After verifying that the status of the network for mirroring among servers is normal, restart the node node and perform the operation again.
ERROR: group: type group not supported
Explanation
The class object configuration cannot be restored in RHEL8 because a type type group group exists in the configuration table.
Resolution
Remove concatenation groups and stripe groups from the configuration table with the sdxconfig Convert command.
For details on the removal method, see "Appendix B Command Reference."