PRIMEQUEST System Disk Mirror for Windows User's Guide V1.0
Contents PreviousNext

Appendix B Messages> B.2 Service Messages

B.2.2 Service Error Messages (42XXX)

 


 

42000
STOP:Stopping of the service failed because of insufficient memory.

 

[Explanation]

Memory is insufficient and stopping the service failed.

[Resolution]

Check memory use and, for example, exit some running applications to increase available memory, and stop the F6GASRV service. For more information on how to stop the service, see "Starting/Stopping the Service."

 


 

42001
Stopping of the service failed because the driver was not executed.

 

[Explanation]

The PSDM driver is not running and stopping the service failed.

[Resolution]

If the system was not rebooted after the PSDM installation, reboot the system. In other situations, check the event log or other relevant information for a driver or system error and take action to resolve the error. After resolving the problem or error, stop the F6GASRV service. For more information on how to stop the service, see "Starting/Stopping the Service."

 


 

42002
Stopping of the service failed because an error occurred in the Windows Service Control Manager.

 

[Explanation]

An error occurred in the Windows Service Control Manager and stopping the service failed.

[Resolution]

Check the event log or other relevant information for a system error and take action to resolve the error, and then stop the F6GASRV service. For more information on how to stop the service, see "Starting/Stopping the Service."

 


 

42003
Stopping of the service failed because an error occurred in a Windows API.

 

[Explanation]

A Windows API error occurred and stopping the service failed.

[Resolution]

Check the event log or other relevant information for a system error and take action to resolve the error, and then stop the F6GASRV service. For more information on how to stop the service, see "Starting/Stopping the Service."

 


 

42004
Stopping of the service failed because of a program level inconsistency.

 

[Explanation]

The versions of the PSDM driver and the PSDM service are inconsistent and stopping the service failed.

[Resolution]

Check whether PSDM fixes are applied properly. If not, apply available fixes. In other situations, perform the overwrite installation of PSDM.

 


 

42005
Stopping of the service failed because a driver error occurred.

 

[Explanation]

An error occurred in the PSDM driver and stopping the service failed.

[Resolution]

Check the PSDM F6GADRV driver event log and take action to resolve the error, and then stop the F6GASRV service. For more information on how to stop the service, see "Starting/Stopping the Service."

 


 

42006
Changing of the EFI Boot Entry of the keep disk failed when the mirror group was created, because of insufficient memory.

group name: group
disk name: disk

 

[Explanation]

Memory is insufficient, and in the process of creating the mirror group group, the EFI boot entry of the mirror disk disk was not changed.

[Resolution]

Check memory use and, for example, exit some running applications to increase available memory. Additionally, if any, delete unnecessary boot entries with the bootcfg command. After performing these operations, retry mirroring setup.

 


 

42007
Changing of the EFI Boot Entry of the keep disk failed when the mirror group was created, because an error occurred in a Windows API.

group name: group
disk name: disk

 

[Explanation]

A Windows API error occurred, and in the process of creating the mirror group group, the EFI boot entry of the mirror disk disk was not changed.

[Resolution]

Check the event log or other relevant information for a system error and take action to resolve the error. Additionally, if any, delete unnecessary boot entries with the bootcfg command. After performing these operations, retry mirroring setup.

 


 

42008
Changing of the EFI Boot Entry of the keep disk failed when the mirror group was created, because a bootcfg command error occurred.

group name: group
disk name: disk

 

[Explanation]

A bootcfg command error occurred, and in the process of creating the mirror group group, the EFI boot entry of the mirror disk disk was not changed.

[Resolution]

Check the event log or other relevant information for a system error and take action to resolve the error. Additionally, if any, delete unnecessary boot entries with the bootcfg command. After performing these operations, retry mirroring setup.

When using ETERNUS disk array units, see also "Boot disk mirroring setup or operation fails in the environment connecting ETERNUS" in "Troubleshooting."

 


 

42009
Addition of the EFI Boot Entry of the disk failed when the mirror disk was added, because of insufficient memory.

group name: group
disk name: disk

 

[Explanation]

Memory is insufficient, and in the process of adding the mirror disk disk, the EFI boot entry was not added. disk will be INVALID.

[Resolution]

Check memory use and, for example, exit some running applications to increase available memory. Additionally, if any, delete unnecessary boot entries with the bootcfg command. After performing these operations, remove disk once and add it again. For more information on how to remove disks, see "Preparing for Disk Swap (Removing Disks);" for more information on how to add disks, see "Restoring Disks after Swapping (Adding Disks)."

 


 

42010
Addition of the EFI Boot Entry of the disk failed when the mirror disk was added, because an error occurred in a Windows API.

group name: group
disk name: disk

 

[Explanation]

A Windows API error occurred, and in the process of adding the mirror disk disk, the EFI boot entry was not added. disk will be INVALID.

[Resolution]

Check the event log or other relevant information for a system error and take action to resolve the error. Additionally, if any, delete unnecessary boot entries with the bootcfg command. After performing these operations, remove disk once and add it again. For more information on how to remove disks, see "Preparing for Disk Swap (Removing Disks);" for more information on how to add disks, see "Restoring Disks after Swapping (Adding Disks)."

 


 

42011
Addition of the EFI Boot Entry of the disk failed when the mirror disk was added, because a bootcfg command error occurred.

group name: group
disk name: disk

 

[Explanation]

A bootcfg command error occurred, and in the process of adding the mirror disk disk, the EFI boot entry was not added. disk will be INVALID.

[Resolution]

Check the number of disk partitions on the mirror source disk, and if 10 or more partitions exist, delete unnecessary ones to reduce the number to nine or less. Additionally, check the event log or other relevant information for a system error and take action to resolve the error. Additionally, if any, delete unnecessary boot entries with the bootcfg command. After performing these operations, retry mirroring setup.

When using ETERNUS disk array units, see also "Boot disk mirroring setup or operation fails in the environment connecting ETERNUS" in "Troubleshooting."

 


 

42012
Internal error.

 

[Explanation]

An internal error occurred in the PSDM service.

[Resolution]

Collect information for troubleshooting and contact your local customer support.

 


 

42013
An internal error occurred during editing of the EFI Boot Entry.

group name: group
disk name: disk

 

[Explanation]

In the process of editing the EFI boot entry, an internal error occurred in the PSDM service.

[Resolution]

Collect information for troubleshooting and contact your local customer support.

 


 

42014
Changing of the EFI Boot Entry of the keep disk failed when the mirror group was created, because there was no valid Boot Entry.

group name: group
disk name: disk

 

[Explanation]

No valid EFI boot entry exists, and in the process of creating the mirror group group, the EFI boot entry of the mirror disk disk was not changed.

[Resolution]

Check the event log or other relevant information for a system error and take action to resolve the error. Additionally, with the bootcfg command, check the EFI entry and set the boot entry names properly.

 


Contents PreviousNext

All Rights Reserved, Copyright(C) FUJITSU LIMITED 2008