The following table contains the list of unsafe-device query failure error messages that are sent to the system logs and/or to the SSP applications.
Table A-12 Unsafe-Device Query Error Messages
Error Message |
Probable Cause |
Suggested Action |
---|---|---|
unsafe_devices: couldn't determine name of unsafe device major_number |
The mechanism that the DR daemon uses to combine a driver name with a major number failed so that no name could be discovered. If this failure occurs, the DR daemon constructs a string for the device, marking it as "(unknown, major_number)". |
This message notifies the user that the DR daemon was unable to find the name of one of the devices, but it does not constitute a correctable error. The daemon can use the major number to identify the drive. |
WARNING: board board_number not checked for unsafe devices. |
While the DR daemon was examining the system boards for unsafe devices, the daemon encountered a failure that prevented it from examining one of the system boards (board_number). This error message may be indicative of a more serious problem. |
You may have to stop and restart the DR daemon to recover the domain from this error. Check the size of the DR daemon. If should be between 300- and 400-Kbytes. If it is not within this range, stop the daemon, then restart it. If you cannot recover the domain from this error, you should report this error to your Sun service representative, providing as much information from the system logs as possible. |
NGDR Error: unsafe_devices: libdevinfo failed. |
The DR daemon cannot determine the names of unsafe major devices because it cannot use the libdevinfo API. This API must be used to search the device tree for the names of all of the unsafe major devices. |
Make sure that the domain contains the correct version of the libdevinfo API and that the domain does not contain version mismatches between any of the DR daemon's libraries, the operating environment on the domain, or the daemon itself. If you cannot determine the cause of this error, report it to your Sun service representative, providing as much information from the system logs as possible. |
NGDR Error: create_ctlr_array: count mismatch [internal error] |
Communication protocol was breached over the existence of AP controllers. To the AP librarian, the domain has a certain number of AP controllers. However, to the DR daemon, the domain has a different number of AP controllers. |
Check to determine the correct amount of AP controllers in the domain, and correct the error. Also, check the size of the DR daemon. It should be between 300- and 400-Kbytes. If it is not within this range, stop the daemon then restart it. |