C.3.2 Error Messages (42000-42099)

42000

ERROR: read error on status slice object.volume, class=class:

      volume info:devno(maj,min)=v_devno(v_maj,v_min)

      device info:devno(maj,min)=p_devno(p_maj,p_min)

                  devname=device

      error info: blk in disk=blknodk, blk in slice=blknosl,

                  length=length, resid=resid, errno=errno

Explanation

Read request sent to slice object.volume in status status terminated abnormally. Read request sent to volume configured by this slice, or to slice accessible in isolation was returned as error.
You must attempt recovery as soon as possible since the application may cease normal operation.

Resolution

Disk failure may have occurred. Identify the cause by referring to disk driver log message, and promptly recover the disk.

42001

ERROR: write error on status slice object.volume, class=class:

      volume info:devno(maj,min)=v_devno(v_maj,v_min)

      device info:devno(maj,min)=p_devno(p_maj,p_min)

                  devname=device

      error info: blk in disk=blknodk, blk in slice=blknosl,

                  length=length, resid=resid, errno=errno

Explanation

Write request sent to slice object.volume in status status terminated abnormally. Write request sent to volume configured by this slice, or to slice accessible in isolation was returned as error.
You must attempt recovery as soon as possible since the application may cease normal operation.

Resolution

Disk failure may have occurred. Identify the cause by referring to disk driver log message, and promptly recover the disk.

42002

ERROR: open error on status slice object.volume, class=class:

      volume info:devno(maj,min)=v_devno(v_maj,v_min)

      device info:devno(maj,min)=p_devno(p_maj,p_min)

                  devname=device

      error info: oflag=oflag, errno=errno

Explanation

Open request sent to slice object.volume in status status terminated abnormally. Open request sent to volume configured by this slice, or to slice accessible in isolation was returned as error.
You must attempt recovery as soon as possible since the application may cease to operate normally.

Resolution

Disk failure may have occurred. Identify the cause by referring to disk driver log message, and promptly recover the disk.

42003

ERROR: read error and writeback error on status slice object.volume, class=class:

      volume info:devno(maj,min)=v_devno(v_maj,v_min)

      device info:devno(maj,min)=p_devno(p_maj,p_min)

                  devname=device

      error info: blk in disk=blknodk, blk in slice=blknosl,

                  length=length, resid=resid, errno=errno

Explanation

Read request and writeback request sent to slice object.volume in status status terminated abnormally. Read request sent to volume configured by this slice, or to slice accessible in isolation was returned as error.
You must attempt recovery as soon as possible since the application may not operate normally.
Writeback is a process to read data from other slices in the event of a read error.

Resolution

Disk failure may have occurred. Identify the cause by referring to disk driver log message, and promptly recover the disk.

42006

ERROR: volume: closed down volume, class=class

Explanation

volume has closed down.

Resolution

Promptly attempt recovery by identifying the cause of failure by referring to GDS log message that was output immediately before the error.
For information on recovery, see "D.1.3 Volume Status Abnormality."

42007

ERROR: class: cannot startup class, no valid configuration database, sdxerrno=errno

Explanation

Could not startup class, since valid class configuration database could not be found.
This message is output when all disks (or the majority of disks) registered with class are unavailable.

Resolution

See "D.1.4 Class Status Abnormality."

42008

ERROR: class: cannot startup class, too few valid configuration database replicas, sdxerrno=errno

Explanation

Could not startup class, due to insufficient number of valid databases.
This message is output when many disks registered with class are unavailable.

Resolution

See "D.1.4 Class Status Abnormality."

42009

ERROR: class: closing down class, no valid configuration database

Explanation

class was closed since no valid class configuration database was found.
This message is output when all disks (or the majority of disks) registered with class are unavailable.

Resolution

See "D.1.4 Class Status Abnormality."

42010

ERROR: class: closing down class, too few valid configuration database replicas

Explanation

class was closed due to insufficient number of valid database.
This message is output when many disks registered with class are unavailable.

Resolution

See "D.1.4 Class Status Abnormality."

42011

ERROR: failed to send request message on node node, details

Explanation

Sending request message from node was unsuccessful.

Resolution

Collect investigation material and contact field engineers.

42012

ERROR: timeout on receiving reply message from node node, details

Explanation

Timeout occurred while receiving a reply message from a remote node node.

Resolution

Collect investigation material and contact field engineers.

42013

ERROR: rejected request message on remote node node, details

Explanation

Processing a request message on a remote node node was unsuccessful.

Resolution

Investigate the node message log and take necessary actions. If recovery is impossible, collect investigation material and contact field engineers.

42014

ERROR: class: failed to start type volumes, status volume volume exists, node=node

Explanation

Starting volumes within the class class failed on the node node since the status volume volume exists.
type is the class type attribute.

Resolution

volume is in abnormal status. First, you must recover normal status.
For information on recovery, see "D.1.3 Volume Status Abnormality."

42015

ERROR: class: failed to start and standby type volumes, status volume volume exists, node=node

Explanation

Starting and putting on standby volumes within the class class failed on the node node since the status volume volume exists.
type is the class type attribute.

Resolution

volume is in abnormal status. First, you must recover normal status.
For information on recovery, see "D.1.3 Volume Status Abnormality."

42016

ERROR: class: failed to stop and standby type volumes, status volume volume exists, node=node

Explanation

Stopping and putting on standby volumes within the class class failed on the node node since the status volume volume exists.
type is the class type attribute.

Resolution

volume is in abnormal status. First, you must recover normal status.
For information on recovery, see "D.1.3 Volume Status Abnormality."

42017

ERROR: class: failed to stop type volumes, status volume volume exists, node=node

Explanation

Stopping volumes within the class class failed on the node node since the status volume volume exists.
type is the class type attribute.

Resolution

volume is in abnormal status. First, you must recover normal status.
For information on recovery, see "D.1.3 Volume Status Abnormality."

42018

ERROR: class: failed to start type volumes, class closed down, node=node

Explanation

Starting volumes failed since the class class has been closed down.
type is the class type attribute.

Resolution

Recover closed class. There may be multiple disk failures. Identify the cause based on object status, GDS log message, and rsyslogd message.
For information on recovery, see "D.1.4 Class Status Abnormality."

42019

ERROR: class: failed to start and standby type volumes, class closed down, node=node

Explanation

Starting and putting on standby volumes failed. since the class class has been closed down.
type is the class type attribute.

Resolution

42020

ERROR: class: failed to stop and standby type volumes, class closed down, node=node

Explanation

Stopping and putting on standby volumes failed. Since the class class has been closed down.
type is the class type attribute.

Resolution

42021

ERROR: class: failed to stop type volumes, class closed down, node=node

Explanation

Stopping volumes failed since the class class has been closed down.
type is the class type attribute.

Resolution

42022

ERROR: class: closing down class, cluster-wide lock failure, sdxerrno=sdxerrno

Explanation

Abnormal exclusive control between cluster system nodes occurred. Since the process cannot be continued, class will be closed.

Resolution

Collect investigation material and contact field engineers.

42023

ERROR: class: cannot startup class, cluster-wide lock failure, sdxerrno=errno

Explanation

Abnormal exclusive control between cluster system nodes occurred. Since the process cannot be continued, class could not be started.

Resolution

Collect investigation material and contact field engineers.

42024

ERROR: class: closing down class, cluster communication failure, sdxerrno=sdxerrno

Explanation

Transmission failure between cluster system nodes occurred. Since the process cannot be continued, class will be closed.

Resolution

Collect investigation material and contact field engineers.

42025

ERROR: class: cannot operate in cluster environment, created when cluster control facility not ready

Explanation

The class class cannot be used in a cluster environment since it was created when the cluster control facility was inactive. This message is output when one of the following operations is performed.

After class was created resource registration was performed on a node where resource registration was not complete.
In a cluster environment where resource registration is complete, class was created in single user mode.
A single node with class was changed over to a cluster system.

Resolution

See "(1) The error message "ERROR: class: cannot operate in cluster environment, ..." is output, and the operation cannot be conducted on the class class." in "D.1.10 Cluster System Related Error."

42026

ERROR: proxy: failed to copy with OPC, source=disk.volume, target=disk.volume, class=class

Explanation

While performing copying between proxy volume proxy and master volume with the OPC function, an I/O error occurred, and the copying process failed.
"source" specifies the original slice name, "target" the mirror slice name, and "class" to which the original slice and mirror slice belong.

Resolution

Identify the cause by referring to the log messages for GDS, disk driver, and ETERNUS Disk storage system that were output right before the occurrence of the error, and restore.

42027

ERROR: proxy: failed to copy with EC, source=disk.volume, target=disk.volume, class=class

Explanation

While performing copying between proxy volume proxy and master volume with the EC function, an I/O error occurred, and the copying process failed.
"source" specifies the original slice name, "target" the mirror slice name, and "class" to which the original slice and mirror slice belong.

Resolution

Identify the cause by referring to the log messages for GDS, disk driver, and ETERNUS Disk storage system that were output right before the occurrence of the error, and restore.

42028

ERROR: proxy: failed to copy with TimeFinder, source=disk, target=disk, class=class

Explanation

Copying failed due to an I/O error caused while conducting copying between the proxy group proxy and the master group with TimeFinder.
"source" is the name of the copy source disk, "target" is the name of the copy destination disk, and "class" is the name of the class to which the copy source and destination disks belong.

Resolution

Identify the cause by referring to the log messages for GDS, the log messages for disk drivers, and the log messages for Dell EMC storage units that were output right before the occurrence of the error, and restore.

42029

ERROR: proxy: failed to copy with SRDF, source=disk, target=disk, class=class

Explanation

Copying failed due to an I/O error caused while conducting copying between the proxy group proxy and the master group with SRDF.
"source" is the name of the copy source disk, "target" is the name of the copy destination disk, and "class" is the name of the class to which the copy source and destination disks belong.

Resolution

42030

ERROR: proxy: failed to start OPC, source=disk.volume, target=disk.volume, class=class

Explanation

An error occurred between proxy volume proxy and the master volume when OPC 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.

42031

ERROR: proxy: failed to stop OPC, source=disk.volume, target=disk.volume, class=class

Explanation

When stopping OPC between proxy volume proxy and master volume, an error occurred.
"source" specifies the original slice name, "target" the mirror slice name, and "class" to which the original slice and mirror slice belong.

Resolution

Identify the cause by referring to the log messages for GDS, disk driver, ETERNUS Disk storage system that were output right before the occurrence of the error, and restore.

42032

ERROR: proxy: failed to start EC session, source=disk.volume, target=disk.volume, class=class

Explanation

An error occurred between proxy volume proxy and the master volume when EC 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.

42033

ERROR: proxy: failed to stop EC session, source=disk.volume, target=disk.volume, class=class

Explanation

When stopping EC session between proxy volume proxy and master volume, an error occurred.
"source" specifies the original slice name, "target" the mirror slice name, and "class" to which the original slice and mirror slice belong.

Resolution

Identify the cause by referring to the log messages for GDS, disk driver, and ETERNUS Disk storage system that was output right before the occurrence of the error, and restore.

42034

ERROR: proxy: failed to suspend EC session, source=disk.volume, target=disk.volume, class=class

Explanation

When temporarily suspending EC session between proxy volume proxy and master volume, an error occurred.
"source" specifies the original slice name, "target" the mirror slice name, and "class" to which the original slice and mirror slice belong.

Resolution

Identify the cause by referring to the log messages for GDS, disk driver, and ETERNUS Disk storage system that were output right before the occurrence of the error, and restore.

42035

ERROR: proxy: failed to resume EC session, source=disk.volume, target=disk.volume, class=class

Explanation

When resuming EC session between proxy volume proxy and master volume, an error occurred.
"source" specifies the original slice name, "target" the mirror slice name, and "class" to which the original slice and mirror slice belong.

Resolution

Identify the cause by referring to the log messages for GDS, disk driver, and ETERNUS Disk storage system that were output right before the occurrence of the error, and restore.

42036

ERROR: proxy: failed to establish BCV pair, STD=disk, BCV=disk, class=class

Explanation

Error occurred while establishing a BCV pair between the proxy group proxy and the master group.
"STD" is the disk name of the standard device, "BCV" is the disk name of the BCV device, and "class" is the name of the class to which the standard and BCV devices belong.

Resolution

42037

ERROR: proxy: failed to cancel BCV pair, STD=disk, BCV=disk, class=class

Explanation

Error occurred while canceling a BCV pair between the proxy group proxy and the master group.
"STD" is the disk name of the standard device, "BCV" is the disk name of the BCV device, and "class" is the name of the class to which the standard and BCV devices belong.

Resolution

42038

ERROR: proxy: failed to split BCV pair, STD=disk, BCV=disk, class=class

Explanation

Error occurred while splitting a BCV pair between the proxy group proxy and the master group.
"STD" is the disk name of the standard device, "BCV" is the disk name of the BCV device, and "class" is the name of the class to which the standard and BCV devices belong.

Resolution

42039

ERROR: proxy: failed to re-establish BCV pair, STD=disk, BCV=disk, class=class

Explanation

Error occurred while re-establishing a BCV pair between the proxy group proxy and the master group.
"STD" is the disk name of the standard device, "BCV" is the disk name of the BCV device, and "class" is the name of the class to which the standard and BCV devices belong.

Resolution

42040

ERROR: proxy: failed to establish SRDF pair, source=disk, target=disk, class=class

Explanation

Error occurred while establishing an SRDF pair between the proxy group proxy and the master group.
"source" is the name of the source disk, "target" is the name of the target disk, and "class" is the name of the class to which the source and target disks belong.

Resolution

42041

ERROR: proxy: failed to cancel SRDF pair, source=disk, target=disk, class=class

Explanation

Error occurred while canceling an SRDF pair between the proxy group proxy and the master group.
"source" is the name of the source disk, "target" is the name of the target disk, and "class" is the name of the class to which the source and target disks belong.

Resolution

42042

ERROR: proxy: failed to split SRDF pair, source=disk, target=disk, class=class

Explanation

Error occurred while splitting an SRDF pair between the proxy group proxy and the master group.
"source" is the name of the source disk, "target" is the name of the target disk, and "class" is the name of the class to which the source and target disks belong.

Resolution

42043

ERROR: proxy: failed to re-establish SRDF pair, source=disk, target=disk, class=class

Explanation

Error occurred while re-establishing an SRDF pair between the proxy group proxy and the master group.
"source" is the name of the source disk, "target" is the name of the target disk, and "class" is the name of the class to which the source and target disks belong.

Resolution

42044

ERROR: disk is bound to RAW device. disabled disk, class=class

Explanation

The disk disk registered with GDS was found that it was bound to a RAW device, and the disk was disabled.

Resolution

Cancel the bind to a RAW device using the raw(8) command for the disk registered with GDS. You may not bind disks registered with GDS to RAW devices.

42049

ERROR: proxy: failed to copy with QuickOPC, source=disk.volume, target=disk.volume, class=class

Explanation

Copying failed due to an I/O error caused while conducting copying between the proxy volume proxy and the master volume with QuickOPC function.

"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 by referring to the log messages for GDS, disk driver and ETERNUS Disk storage system that were output right before the occurrence of the error, and restore it.

42050

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 QuickOPC session 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 by referring to the log messages for GDS, disk driver and ETERNUS Disk storage system that were output right before the occurrence of the error, and restore it.

42051

ERROR: proxy: failed to stop QuickOPC session, source=disk.volume, target=disk.volume, class=class

Explanation

An error occurred between proxy volume proxy and the master volume when QuickOPC session was stopped.

"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 by referring to the log messages for GDS, disk driver and ETERNUS Disk storage system that were output right before the occurrence of the error, and restore it.

42052

ERROR: failed to detach slice:

        volume info: devno(maj,min)=v_devno(v_maj,v_min)

        device info: devno(maj,min)=p_devno(p_maj,p_min)

Explanation

The slice detachment by the I/O error failed..

Resolution

Recover the LEFTCLUSTER state. For how to recover the LEFTCLUSTER state, see "PRIMECLUSTER Cluster Foundation (CF) Configuration and Administration Guide."

42054

ERROR: volume: failed to lock netmirror volume, class=class

Explanation

Failed to lock the netmirror volume. After outputting this message, the class class is closed down.

Resolution

Stop both the nodes first, and then start from a node other than the nodes of which the message was output.

42055

ERROR: check the iSCSI device has timeout, iSCSI=num

Explanation

This message is output on the system log when the iSCSI disk registered in a class cannot be recognized after the number of seconds specified by the tuning parameter SDX_STARTUP_WAIT_TIME. num is the number of the iSCSI devices that cannot be recognized.

See

For SDX_STARTUP_WAIT_TIME, see "6.2 Using iSCSI Disk."

Resolution

Check the iSCSI disk. If the disk has a failure, resotre the failed part. If the disk does not have a failure, take the following procedure.

On the system log, check what time the following message has been output.
```
Mon Day HH:MM:SS node devlabel: devlabel service started/restarted
```

The following message is output on the system log after the above message in procedure 1 has been output. Check what time the last message has been output.

[sd device]

Mon Day HH:MM:SS node kernel: sd host:channel:id:lun:[device] Attached SCSI disk

[mpath device]

Mon Day HH:MM:SS node multipathd: device [maj:min]: path added to devmap dmpath

Each variable indicates the following meaning.

Variable	Meaning
Mon	month
Day	date
HH	hour
MM	minute
SS	second
node	node name
host	host number
channel	channel number
id	id number
lun	lun number
device	sdX (X indicates the device identifier)
maj	major number
min	minor number
dmpath	mpathX (X indicates the device identifier)

Calculate the time by the following formula and set the time for the tuning parameter SDX_STARTUP_WAIT_TIME.
[Formula]
```
Time difference between the messages 1 and 2 above + 10 + 1800 (seconds)
```
See
For how to set up SDX_STARTUP_WAIT_TIME, see "6.2 Using iSCSI Disk."

42056

ERROR: netmirror DB file is invalid, class=class, volume=volume

Explanation

The disk containing the latest data cannot be determined because inconsistency exists in the information to specify the disk containing the latest data.

Resolution

See "7.16.8 Restoration when the Latest Disk Cannot Be Selected Automatically."

42057

ERROR: failed to add boot entry entry, exit-status=exitstat

Explanation

The boot entry entry cannot be added to the boot option selection screen of the EFI boot manager.

The cause for this error message is as follows:

If the exit-status is other than 137, the efibootmgr(8) command has ended abnormally with the exit status exitstat.

If the exit-status is 137, the efibootmgr(8) command has not ended within 300 seconds.

Resolution

Collect investigation material, and contact field engineers.

42058

ERROR: failed to delete boot entry entry, exit-status=exitstat

Explanation

The boot entry entry cannot be deleted from the boot option selection screen of the EFI boot manager.

The cause for this error message is as follows:

If the exit-status is other than 137, the efibootmgr(8) command has ended abnormally with the exit status exitstat.

If the exit-status is 137, the efibootmgr(8) command has not ended within 300 seconds.

Resolution

Collect investigation material, and contact field engineers.

42059

ERROR: failed to get boot entry information, exit-status=exitstat

Explanation

The boot entry information of the boot option selection screen of the EFI boot manager cannot be obtained.

The cause for this error message is as follows:

If the exit-status is other than 137, the efibootmgr(8) command has ended abnormally with the exit status exitstat.

If the exit-status is 137, the efibootmgr(8) command has not ended within 300 seconds.

Resolution

Collect investigation material, and contact field engineers.

42060

ERROR: failed to change display order of boot entry, exit-status=exitstat

Explanation

The display order of boot entries of the boot option selection screen of the EFI boot manager cannot be changed.

The cause for this error message is as follows:

If the exit-status is other than 137, the efibootmgr(8) command has ended abnormally with the exit status exitstat.

If the exit-status is 137, the efibootmgr(8) command has not ended within 300 seconds.

Resolution

Collect investigation material, and contact field engineers.

42061

ERROR: failed to open temporary file, sdxfunc=sdxfunc, errno=errno

Explanation

A temporary file cannot be opened.

Resolution

Collect investigation material, and contact field engineers.

42062

ERROR: class: timeout on waiting configuration database relocation

Explanation

Timeout occurred while waiting for the completion of the configuration database relocation of the class class.

Resolution

If this message is output when starting the system, start the system again.

If this message is output when restoring the class, execute the command again.

If this message is still output, collect investigation material and contact field engineers.

42063

ERROR: class: closing down class, failed to update netmirror NVURM information

Explanation

Class class was closed because NVURM information of the netmirror group could not be updated.

Resolution

Take the following actions:

When no capacity available 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_nvurm_class 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.

42064

ERROR: failed to update netmirror NVURM information, class=class, volume=volume

Explanation

NVURM information of the netmirror group could not be updated.

Resolution

Take the following actions:

When no capacity available 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_nvurm_class 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.

42065

ERROR: class: closing down class, failed to update netmirror device information

Explanation

Class class was closed because the device information of the netmirror group could not be updated.

Resolution

Take the following actions:

When no capacity available 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.

42066

ERROR: hangup detected

Explanation

Either a hang-up in the GDS daemon or the driver was detected.
The system panics after this message is output.

42067

ERROR: class: failed to start volume volume, status slice in local node must be recovered

Explanation

The netmirror volume volume of class class cannot start because the slice of the operating node is detached (is on status).

Resolution

Restore the slice status of the operating node before forcibly starting the cluster application.

Refer to "7.16.6 Operation on Only One Node" for restoration procedure.

42068

ERROR: failed to update netmirror device information, class=class

Explanation

The device information of netmirror group in class class has failed to be updated.

Resolution

Take the following actions:

When no capacity available 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.

42069

ERROR: lock is set on volume volume, node=node

Explanation

Failed in starting volume due to the starting lock of volume volume is set in the node node.

Resolution

To start the volume, turn off the "Lock volume" mode, or use the -e unlock option.

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."

If this message is output during the startup of cluster application that includes netmirror volume, see "7.16.8 Restoration when the Latest Disk Cannot Be Selected Automatically" and restore.

For details, see "7.16.5 Lock Volume of the Netmirror Volume."

42070

ERROR: class: failed to start volume volume, slice in local node must be recovered

Explanation

Netmirror volume volume of the class class cannot be started due to failure in the slice state of the started node.

Resolution

Check the slice status on the disk of the started node before forcibly starting the cluster application and then restore.

When the slice is in ACTIVE or STOP status
Disk failure may have occurred.
For resolutions, see "(1) Mirror slice configuring the mirror volume is in INVALID status.." in "D.1.1 Slice Status Abnormality."
For others
See "D.1.1 Slice Status Abnormality."

42071

ERROR: val: interval must be integer

Explanation

The hang-up monitoring function cannot be started because the value of monitoring interval (SDX_HCHK_INTERVAL) of hang-up monitoring function configured in the GDS settings file /etc/opt/FJSVsdx/sdx.cf is not a numerical value.
This message is not output to the log file (sdxservd.log) of daemon indicated in "C.3 Daemon Messages."

Resolution

Refer to "How to change parameters" in "6.12.2 Hang-up Monitoring Function" in order to edit the value configured in SDX_HCHK_INTERVAL of GDS settings file /etc/opt/FJSVsdx/sdx.cf.
Restart the system or restart the service using the following command.
# /usr/bin/systemctl restart fjsvsdxhealth.service

Check that the service is in running state with the following command.

# /usr/bin/systemctl status fjsvsdxhealth.service
* fjsvsdxhealth.service - PRIMECLUSTER Global Disk Services hang up monitor service
   ...
   Active: active (running) ...
...

42072

ERROR: val: too small interval

Explanation

The hang-up monitoring function cannot be started because the value of monitoring interval (SDX_HCHK_INTERVAL) of hang-up monitoring function configured in the GDS settings file /etc/opt/FJSVsdx/sdx.cf is smaller than the allowed value.
This message is not output to the log file (sdxservd.log) of daemon indicated in "C.3 Daemon Messages."

Resolution

Refer to "How to change parameters" in "6.12.2 Hang-up Monitoring Function" in order to edit the value configured in SDX_HCHK_INTERVAL of GDS settings file /etc/opt/FJSVsdx/sdx.cf.
Restart the system or restart the service using the following command.
# /usr/bin/systemctl restart fjsvsdxhealth.service

Check that the service is in running state with the following command.

# /usr/bin/systemctl status fjsvsdxhealth.service
* fjsvsdxhealth.service - PRIMECLUSTER Global Disk Services hang up monitor service
   ...
   Active: active (running) ...
...

42073

ERROR: val: too large interval

Explanation

The hang-up monitoring function cannot be started because the value of monitoring interval (SDX_HCHK_INTERVAL) of hang-up monitoring function configured in the GDS settings file /etc/opt/FJSVsdx/sdx.cf is larger than the allowed value.
This message is not output to the log file (sdxservd.log) of daemon indicated in "C.3 Daemon Messages."

Resolution

Refer to "How to change parameters" in "6.12.2 Hang-up Monitoring Function" in order to edit the value configured in SDX_HCHK_INTERVAL of GDS settings file /etc/opt/FJSVsdx/sdx.cf.
Restart the system or restart the service using the following command.
# /usr/bin/systemctl restart fjsvsdxhealth.service

Check that the service is in running state with the following command.

# /usr/bin/systemctl status fjsvsdxhealth.service
* fjsvsdxhealth.service - PRIMECLUSTER Global Disk Services hang up monitor service
   ...
   Active: active (running) ...
...

42074

ERROR: val: criterion must be integer

Explanation

The hang-up monitoring function cannot be started because the value of conclusion time (SDX_HCHK_CRITERION) of hang-up monitoring function configured in the GDS settings file /etc/opt/FJSVsdx/sdx.cf is not a numerical value.
This message s not output to the log file (sdxservd.log) of daemon indicated in "C.3 Daemon Messages."

Resolution

Refer to "How to change parameters" in "6.12.2 Hang-up Monitoring Function" in order to edit the value configured in SDX_HCHK_CRITERION of GDS settings file /etc/opt/FJSVsdx/sdx.cf.
Restart the system or restart the service using the following command.
# /usr/bin/systemctl restart fjsvsdxhealth.service

Check that the service is in running state with the following command.

# /usr/bin/systemctl status fjsvsdxhealth.service
* fjsvsdxhealth.service - PRIMECLUSTER Global Disk Services hang up monitor service
   ...
   Active: active (running) ...
...

42075

ERROR: val: too small criterion

Explanation

The hang-up monitoring function cannot be started because the value of conclusion time (SDX_HCHK_CRITERION) of hang-up monitoring function configured in the GDS settings file /etc/opt/FJSVsdx/sdx.cf is smaller than the allowed value.
This message s not output to the log file (sdxservd.log) of daemon indicated in "C.3 Daemon Messages."

Resolution

Refer to "How to change parameters" in "6.12.2 Hang-up Monitoring Function" in order to edit the value configured in SDX_HCHK_CRITERION of GDS settings file /etc/opt/FJSVsdx/sdx.cf.
Restart the system or restart the service using the following command.
# /usr/bin/systemctl restart fjsvsdxhealth.service

Check that the service is in running state with the following command.

# /usr/bin/systemctl status fjsvsdxhealth.service
* fjsvsdxhealth.service - PRIMECLUSTER Global Disk Services hang up monitor service
   ...
   Active: active (running) ...
...

42076

ERROR: val: too large criterion

Explanation

The hang-up monitoring function cannot be started because the value of conclusion time (SDX_HCHK_CRITERION) of hang-up monitoring function configured in the GDS settings file /etc/opt/FJSVsdx/sdx.cf is larger than the allowed value.
This message is not output to the log file (sdxservd.log) of daemon indicated in "C.3 Daemon Messages"

Resolution

Refer to "How to change parameters" in "6.12.2 Hang-up Monitoring Function" in order to edit the value configured in SDX_HCHK_CRITERION of GDS settings file /etc/opt/FJSVsdx/sdx.cf.
Restart the system or restart the service using the following command.
# /usr/bin/systemctl restart fjsvsdxhealth.service

Check that the service is in running state with the following command.

# /usr/bin/systemctl status fjsvsdxhealth.service
* fjsvsdxhealth.service - PRIMECLUSTER Global Disk Services hang up monitor service
   ...
   Active: active (running) ...
...

42077

ERROR: interval val isn't larger than criterion val

Explanation

The hang-up monitoring function cannot be started because the value of conclusion time (SDX_HCHK_CRITERION) of hang-up monitoring function configured in the GDS settings file /etc/opt/FJSVsdx/sdx.cf is greater than or equal to the value of monitoring interval (SDX_HCHK_INTERVAL).
This message is not output to the log file (sdxservd.log) of daemon indicated in "C.3 Daemon Messages."

Resolution

Refer to "How to change parameters" in "6.12.2 Hang-up Monitoring Function" in order to edit the value configured in either of SDX_HCHK_CRITERION or SDX_HCHK_INTERVAL of GDS settings file /etc/opt/FJSVsdx/sdx.cf.
Restart the system or restart the service using the following command.
# /usr/bin/systemctl restart fjsvsdxhealth.service

Check that the service is in running state with the following command.

# /usr/bin/systemctl status fjsvsdxhealth.service
* fjsvsdxhealth.service - PRIMECLUSTER Global Disk Services hang up monitor service
   ...
   Active: active (running) ...
...

42078

ERROR: failed to update netmirror device information:

         volume info:    devno(maj,min)=v_devno(v_maj,v_min)

         device info:    devno(maj,min)=p_devno(p_maj,p_min)

Explanation

The device information of the netmirror group failed to be updated.

Resolution

Take the following actions:

When no capacity available 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.

42079

ERROR: failed to resume suspended volume by I/O error:

         volume info:    devno(maj,min)=v_devno(v_maj,v_min)

         device info:    devno(maj,min)=p_devno(p_maj,p_min)

Explanation

The suspended I/O failed to be resumed due to an I/O error.

Resolution

Collect investigation material and contact field engineers.