Dynamic Reconfiguration User's Guide 2.5.1 |
Contents
![]() ![]() |
Chapter 7 Messages and DR Error Conditions on Solaris 9 OS and Solaris 10 OS | > 7.1 Command Messages | > 7.1.3 drc messages |
If the remedy says "Respond in the manner directed by the system console message.", please refer to section 7.2 "Console Messages" and follow the remedy suggested to take an appropriate action.
Message |
|
Cause |
Executed command by non super user |
Remedy |
Execute command by super user |
Message |
drc: cannot open /dev/FJSVhwr/pwrctl2: System call error Message |
Cause |
Cannot access to System Control Facility (SCF) driver |
Remedy |
Ensure SCF driver package is properly installed |
Message |
|
Cause |
Another drc Command is already being executed |
Remedy |
drc command cannot be executed simultaneously |
Message |
|
Cause |
System is not setup to execute DR. |
Remedy |
Refer to "2.3 DR Configuration and Administration Issues" to enable DR. |
Message |
|
Cause |
DR module cannot be found. |
Remedy |
Ensure FJSVdr package is properly installed. |
Message |
drc: ioctl() failed: system call error message |
Cause |
Displayed "Operation not supported": |
Remedy |
Displayed the "Operation not supported": |
Message |
drc: Specified system board is not installed (sbXY). |
Cause |
Specified system board is not installed. |
Remedy |
Be sure the specified system board is installed |
Message |
drc: Incorrect memory mode (sbXY). |
Cause |
Specified system board is running in interleaved mode |
Remedy |
Check the specified system board |
Message |
drc: Board Type is different (sbXY). |
Cause |
While connecting: The system board type is different from other system boards in the partition. While transporting: The system board type is different from the destination system board. |
Remedy |
Check the specified system board |
Message |
drc: CPU clock frequency is different (sbXY). |
Cause |
While connecting: The CPU type on the system board is different from the current partition. While transporting: The CPU type on the system board is different from the destination partition. |
Remedy |
Check the specified system board |
Message |
drc: System board is in use by another partition (sbXY). |
Cause |
Specified system board is already used in another partition |
Remedy |
Check the specified system board |
Message |
|
Cause |
Status of the system board became invalid during the DR process |
Remedy |
Please contact our customer service. |
Message |
|
Cause |
Status of system board does not change within the fixed time. |
Remedy |
Please contact our customer service. |
Message |
drc: Unable to connect the specified system board (sbXY). |
Cause |
Specified system board is not connectable status |
Remedy |
Check the specified system board |
Message |
|
Cause |
System call failed |
Remedy |
Check swap allocation or memory resources and try again |
Message |
|
Cause |
DR module terminated abnormally. |
Remedy |
Respond in the manner directed by the system console message |
Message |
drc: Unable to disconnect the specified system board (sbXY incorrect PID). |
Cause |
Specified system board does not exist in the target partition. |
Remedy |
Check the specified system board. |
Message |
drc: Unable to disconnect the specified system board (sbXY incorrect status). |
Cause |
Specified system board is not able to be disconnected. |
Remedy |
Check the specified system board. |
Message |
drc: Unable to disconnect the specified system board (sbXY last system board). |
Cause |
Specified system board is the last one |
Remedy |
Check the specified system board. |
Message |
|
Cause |
Specified PID does not exist. |
Remedy |
Check the specified PID |
Message |
|
Cause |
1) DR operation was executed with the 32bit Solaris system or older Solaris release such as Solaris 7 OS. OR 2) DR operation is executed on hardware that does not support DR. |
Remedy |
For requirements of DR process, please refer to "1.2 DR Requirements". |
Message |
|
Explanation |
Another DR is already being executed on the partition |
Remedy |
Additional DR processes can be executed after the current DR is completed. |
Message |
|
Explanation |
Connection Script(Script name:####)exit illegally. |
Remedy |
Check the connection script. |
Message |
|
Explanation |
System is not setup to execute DR |
Remedy |
Refer to "2.3 DR Configuration and Administration Issues" to enable DR. |
Message |
|
Explanation |
DR operation is being canceled despite DR is not executing. |
Remedy |
Cancel command is only supported while DR is executing. |
Message |
|
Cause |
Connection Script(Script name:####)exit illegally |
Remedy |
Check the connection script |
Message |
|
Cause |
Fail to configure the CPU. |
Remedy |
Respond in the manner directed by the console message. |
Message |
|
Cause |
Fail to configure the I/O. |
Remedy |
Respond in the manner directed by the console message. |
Message |
|
Cause |
Fail to configure the system board |
Remedy |
Respond in the manner directed by the console message. |
Message |
|
Cause |
Fail to configure the memory |
Remedy |
Respond in the manner directed by the console message. |
Message |
|
Cause |
Fail to delete the processor set. |
Remedy |
Respond in the manner directed by the console message. |
Message |
|
Explanation |
Fail to disconnect the system board. |
Remedy |
Respond in the manner directed by the console message. |
Message |
|
Explanation |
Fail to get the system board status. |
Remedy |
Respond in the manner directed by the console message. |
Message |
|
Explanation |
Fail to offline the CPU of processor id # |
Remedy |
Manually offline the processor by psradm(1M) and re-execute the DR. Refer to section 5.2.2 "DR detach failed with "Fail to offline the CPU.[processor_id=#]"". |
Message |
|
Explanation |
Fail to online the CPU of processor id # |
Remedy |
Respond in the manner directed by the console message. |
Message |
|
Explanation |
Fail to release the CPU. |
Remedy |
Respond in the manner directed by the console message. |
Message |
|
Explanation |
Fail to release the I/O. |
Remedy |
Respond in the manner directed by the console message. |
Message |
|
Explanation |
Fail to release the system board. |
Remedy |
Respond in the manner directed by the console message. |
Message |
|
Explanation |
Fail to release the memory. |
Remedy |
Confirm whether there are enough free memory spaces. If so, respond in the manner directed by the console message. If not, after making more free memory spaces available, respond in the manner directed by the console message. |
Message |
|
Explanation |
Fail to remove the CPU from the processor set. |
Remedy |
Manually remove the processor from the processor set by psrset(1M) and re-execute DR. |
Message |
|
Explanation |
Fail to unbind processes from the CPU. |
Remedy |
Manually unbind the processes by pbind(1M) and re-execute DR. |
Message |
|
Explanation |
Fail to unconfigure the CPU. |
Remedy |
Respond in the manner directed by the console message. |
Message |
|
Explanation |
Fail to unconfigure the I/O. |
Remedy |
Respond in the manner directed by the console message. |
Message |
|
Explanation |
Fail to unconfigure the system board. |
Remedy |
Respond in the manner directed by the console message. |
Message |
|
Explanation |
Fail to unconfigure the memory. |
Remedy |
Confirm whether there are enough free memory spaces. If so, respond in the manner directed by the console message. |
Message |
|
Explanation |
The status of devices is illegal. |
Remedy |
Respond in the manner directed by the console message |
Message |
|
Explanation |
The kernel memory exists on the DR target system board. |
Remedy |
[ GP7000F model 1000/2000 and PRIMEPOWER 800/1000/2000 ] [ PRIMEPOWER 900/1500/2500 ] |
Message |
|
Explanation |
Cannot disconnect the system board due to insufficient memory. |
Remedy |
Increase free memory and execute again. |
Message |
|
Explanation |
Fail to get the status of processor. |
Remedy |
Respond in the manner directed by the console message |
Message |
|
Explanation |
Recovery failed after the interruption of DR. |
Remedy |
Execute error recovery directed by Chapter 5. |
Message |
|
Explanation |
Cannot disconnect the system board due to insufficient swap space. |
Remedy |
Increase free swap space and execute again. |
Message |
|
Explanation |
Fail to cancel the memory detaching operation. |
Remedy |
Respond in the manner directed by the console message |
Message |
|
Explanation |
Fail to check the status of bound processes. |
Remedy |
Manually unbind the processes by pbind(1M) and re-execute DR. |
Message |
|
Explanation |
DR environment is not set up. |
Remedy |
Please comment out "ftrace_atboot = 1" line in /etc/system to disable this configuration. After this reboot the system. |
Message |
|
Explanation |
An I/O device on the outgoing system board is still referenced. |
Remedy |
Confirm that the displayed I/O device is not in use and repeat the DR operation. If this error message appears again, please contact our customer service. |
Message |
|
Explanation |
Fail to assign the board. |
Remedy |
Respond in the manner directed by the console message. |
Message |
|
Explanation |
Fail to unassign the board. |
Remedy |
Respond in the manner directed by the console message. |
Message |
|
Explanation |
Board is already connected. |
Remedy |
Check the system board status by drcstat command and re-execute correct DR command. |
Message |
|
Explanation |
Device suspension failed. |
Remedy |
Repeat the action. If the message persists, please contact our customer service. |
Message |
|
Explanation |
The device cannot be resumed. |
Remedy |
Please contact our customer service |
Message |
|
Explanation |
Devices failed to suspend. |
Remedy |
Repeat the action. If the message persists, please contact our customer service. |
Message |
|
Explanation |
Devices failed to resume. |
Remedy |
Please contact our customer service |
Message |
|
Explanation |
Failed to stop kernel thread. |
Remedy |
Please contact our customer service |
Message |
|
Explanation |
Fail to stop picld |
Remedy |
Respond in the manner directed by the console message. |
Message |
|
Explanation |
Fail to stop drd |
Remedy |
If this error message appears and system board disconnect operation fails, please repeat the action. |
Message |
|
Explanation |
There may be inconsistency in the system. |
Remedy |
Please contact our customer service. |
Message |
|
Explanation |
There is not enough real memory to detach memory on system board X. |
Remedy |
Check the amount of available real memory, and repeat the action. If this error message appears again, please contact our customer service. |
Message |
|
Explanation |
The DR operation is refused. |
Remedy |
Respond in the manner directed by the other message. |
Message |
|
Explanation |
The DR operation is canceled. |
Remedy |
Respond in the manner directed by the other message. |
Message |
|
Explanation |
There is non-relocatable (kernel) memory on the system board. |
Remedy |
The target board with kernel memory cannot be disconnected by DR. |
Message |
|
Explanation |
Invalid argument is passed to the driver or there may be inconsistency in the |
Remedy |
Repeat the action. If this error message appears again, please contact |
Message |
|
Explanation |
There may be inconsistency in the system. |
Remedy |
Please contact our customer service. |
Message |
|
Explanation |
Invalid operation. |
Remedy |
Repeat the action. If this error message appears again, please contact |
Message |
|
Explanation |
Board is configured or busy. |
Remedy |
Repeat the action. If this error message appears again, please contact |
Message |
|
Explanation |
Invalid argument is passed to the driver or there may be inconsistency in the |
Remedy |
Repeat the action. If this error message appears again, please contact |
Message |
|
Explanation |
Fail to execute cfgadm for the I/O device which has ap_id ######. |
Remedy |
Respond in the manner directed by the console message. |
Message |
|
Explanation |
Fail to restart picld. |
Remedy |
Respond in the manner directed by the console message. |
Contents
![]() ![]() |