[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | sco_unix |
|
| Moderator: | AVNGRS::BOELKE |
|
| Created: | Mon Mar 26 1990 |
| Last Modified: | Thu May 22 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 2574 |
| Total number of notes: | 9709 |
2566.0. "Error Messages for DAC960 SCO Unix" by CSCMA::EARNEST () Thu Apr 03 1997 16:55
Technical Note Mylex Corporation
Product : DAC960 No : 016
Reference : DAC960 SCO Unix Driver & Utility Error Messages (1.0)
Dated 12-27-93
Alphabetical list of ERROR MESSAGES for DAC960 SCO Unix Drivers and
Utilities:
A few of these errors can be caused by an Installation Abort
situation. In this situation, DAC960 does not respond to commands
properly and will not be functional at all. To verify if the DAC960
is in an Installation Abort condition, reset the system or do a power
cycling and look for the message "Installation Aborted" on the con-
sole, after the DAC960 BIOS sign on message and the firmware version
messages are displayed. This message will NOT be displayed when a
system WARM BOOT (CTL_ALT_DEL) is done.
/usr/share/lib/terminfo is unaccessible
The file mentioned in the error message is either not present or
accessible. Make sure only superuser is running this utility.
0xff in ISR
This condition should never occur. Replace DAC960, if seen.
A manual rebuild must now be performed. That rebuild will report the
cause of the error
The last standby rebuild resulted in an error. In order to get a
more detailed error message, do a manual rebuild on the same drive.
The standby rebuild can fail if:
1. The drive that is being rebuilt fails during the rebuild
process.
2. One of the source drives had some bad blocks during the
rebuild operation.
3. The newly added drive that replaced a failed drive, did
not work properly.
4. One of the source drives failed during the operation.
Make sure a qualified drive is being used. Check the cables,
drive, terminators and power supply.
Adapter not installed ..... Exiting
The appropriate DAC960 is not present in the system. Make sure
the DAC960 is present in the system and recognized by the system, when
the OS boots up.
Asynchronous rebuild had error(s)
Indicates an error during the Rebuild process. The error is
displayed if:
1. The drive that is being rebuilt fails during the rebuild
process.
2. One of the source drives had some bad blocks during the
rebuild operation.
3. The newly added drive that replaced a failed drive, did
not work properly.
4. One of the source drives failed during the operation.
Make sure a qualified drive is being used. Check the cables,
drive, terminators and power supply.
Channel Busy ... TRY LATER
In DAC960SH/CHDEV utility, trying to stop a channel when one or
more devices on that channel are busy, results in this message. This
message is normally seen when DAC960 is doing some operation (rebuild,
check consistency) that can't be temporarily stopped.
chdev: Not now
When a channel is stopped, the utility will only accept the
string "resume" to restart the channel. Attempting to kill this
process will result in this message.
corrupted terminfo entry
The Unix terminfo entry that is selected currently by this user
is having some corrupted entries. Reload terminfo database for the
currently selected terminal.
Dac1: Warning No Active UNIX Partition
An informative message to inform that no Active Unix partition
has been detected on the System drive.
dac960sh: Can't run on serial terminals .. Exiting !!
DAC960SH should be run by "root" user from the system console
only.
dacmon1d: Adapter not installed ..... Exiting !
DACMON daemon could not locate any DAC960 adapter or driver. Make
sure the DAC960 is plugged in an EISA BUS master slot and is EISA
configured in it. IF DACMON2d fails with the same message, make sure
the "mkdev dacdisk" command has been executed and at least one of the
System drives of the second DAC960 has been partitioned.
dacmon1d: DAC960 internal log structures getting full. PLEASE SHUTDOWN
AND RESET THE SYSTEM IN THE NEAR FUTURE
The DAC960 device and other state changes are logged internally
on the controller. Over a period of time a few systems may show up
this error message. Once seen immediately shutdown the system, do a
power cycling and reboot.
dacmon1d: FATAL ERROR x. DAEMON IS DEAD
The DAC960 returned an error for a command sent to it. This will
kill the DACMON?D daemon immediately. If problem persists, replace
DAC960 or system.
dacmon1d: Replacement table full. No further automatic standby will
take place. To flush the replacement buffer, please down the machine
and reset it sometime in the near future. dacmon1d
In case of DAC960, upto eight Standby replacements are allowed
take place, before the DAC960 needs to be reset and started all over.
Each standby replacement event is recorded in the table.
dacmon1d: WRITE-BACK ERROR HAS OCCURRED
If one or more System drives are set in WRITE BACK mode, the
Operating System will get a write done status, immediately after the
data has been written to the DAC960 cache. After a while the DAC960
will write the cached data to the disk drives. If this physical disk
write operation fails, then DAC960 will report this error status. The
system may exhibit data loss on these blocks.
Device [x:y] is in unknown state
The device is in an unknown state. Use the Start device option in
the toolkit to set the state of the device.
Driver detected Invalid Command!
Should normally not occur. If seen, replace the system and try
again.
Driver Error Code = x
Should normally not occur. If seen, replace the system and try
again.
Driver got a weird command
Should normally not occur. If seen, replace the system and try
again.
ERROR !! An error occurred while replacing [chn x,tgt y] by [chn x,tgt
y']
During a Standby Rebuild, an error occurred when the standby
drive tried to replace the failed drive. A Standby drive failure will
normally result in this message. Make sure a qualified drive is being
used. Check the cables, drive, terminators and power supply.
Error getting device info
The device status command returned an error. Make sure the DAC960
is configured properly using the DACCF utility. If problem persists,
replace DAC960 and try again.
Error in broadcast
The utility is not able to broadcast messages to all the logged
in terminals of the system. Make sure "wall" utility is available and
accessible in the /usr/bin or /bin directory of the system.
error in ioctl
The IOCTL call to the DAC960 driver retuned an error. Make sure
the latest version of the driver is installed and configured in the
unix kernel.
error in open
The device files /dev/rhd00, /dev/rda100 are all present and
accessible. Make sure only "root" superuser runs this utility.
Error in Rebuild
Indicates an error during the Rebuild process. The error is
displayed if:
1. The drive that is being rebuilt fails during the rebuild
process.
2. One of the source drives had some bad blocks during the
rebuild operation.
3. The newly added drive that replaced a failed drive, did
not work properly.
4. One of the source drives failed during the operation.
Make sure a qualified drive is being used. Check the cables,
drive, terminators and power supply.
Error on drive x, STAT: a ERR: b
Can't read the absolute sector of a device. If problem persists,
reinitialize the System drive x or replace the DAC960.
Error status x from DAC while 'killing' device
The DAC960 returned an error status, when a device was killed.
Should normally not occur. If problem persists, replace DAC960 or
system.
Error status from DAC = x
DAC960 returned an error code for a command sent to it. If
problem persists replace DAC960.
Failed to start .. Exiting
OR
Failed to start device
OR
Failed to start the device. Device is DEAD
The selected drive can't be started and hence can't be involved
in any DAC960 operations. During system boot up or at a user request,
the DAC960 issues a series of commands to start a drive. If any of
these commands fail, the above error message is displayed. Make sure
a qualified drive is being used. Check the cables, drive , terminators
and power supply.
FATAL ERROR
The device files /dev/rhd00, /dev/rda100 are all present and
accessible. Make sure only "root" superuser runs this utility.
FATAL ERROR x. DAEMON IS DEAD
The DAC960 returned an error for a command sent to it. This will
kill the DACMON?D daemon immediately. If problem persists, replace
DAC960 or system.
Fatal Error, can not access DAC .. Exiting
The device files /dev/rhd00, /dev/rda100 are all present and
accessible. Make sure only "root" superuser runs this utility.
I don't know anything about your ??? terminal
I don't know how to deal with your ??? terminal
OR
I need to know a more specific terminal type than ???
The terminfo variable in Unix is not set properly or if set
properly, is not defined in the terminfo database. Make sure "root"
user is executing this utility. Make sure the utility is being run
from the system console screen and not from a terminal connected to
the system.
Illegal Choice
The device selected to rebuild is not the correct device. Only a
device whose state is DEAD or WR_ONLY (designated by XXXX in the
device matrix) can be rebuild. Please note XXXX designation in the
device matrix also stands for a unavailable device.
Invalid Channel
The channel number specified in the option is not a valid channel
for this DAC960 controller.
Invalid Option
The option selected is not legal for the operation being per-
formed.
Invalid System Drive number
The System drive number specified in the option is not a valid
number for this DAC960 configuration.
Invalid table number
The table number specified in the option is not a valid table
number.
Invalid target
The target number specified in the option is not a valid target
for this DAC960 controller.
Mismatch in number of adapters
The number of DAC960 adapters present in the system changed while
the system was running the DAC960TK utility. This should not normally
happen. If seen at any time, the system in total could be the suspect.
New disk too small
A manual rebuild operation will start only when the drive under
rebuild has a size which is more or equal to the configured size of
the drive it replaces. Replace the new drive with a disk of size same
or larger than the failed drive and reissue the rebuild command.
Not allowed under UNIX
This operation is not supported by the utility that is being
used.
NOTE : The last standby rebuild encountered errors. Read the rebuild
bad-block table to clear this flag; then run a manual rebuild
Use the DACCF utility to read the rebuild bad block table and
save to a file. The manual rebuild is also likely to show up the same
errors. Data loss may also take place under this condition.
NOTE : Write-back error occurred !! Read the write-back bad-block
table to see which blocks had write-back errors, and to clear this
flag
Use the DACCF utility to read the Write-back bad block table and
save to a file. These errors are fatal errors and system may exhibit
data loss on these blocks.
Out of Resources
The driver ran out of resources to send a command to the DAC960.
If seen, the driver or the system is the likely suspect.
Rebuild Error
Indicates an error during the Rebuild process. The error is
displayed if:
1. The drive that is being rebuilt fails during the rebuild
process.
2. One of the source drives had some bad blocks during the
rebuild operation.
3. The newly added drive that replaced a failed drive, did
not work properly.
4. One of the source drives failed during the operation.
Make sure a qualified drive is being used. Check the cables,
drive, terminators and power supply.
SCSI Hard Disk Init Read Error
The driver is not able to read the System drive. Make sure all
System drives are ONLINE and accessible.
Standby rebuild had error(s)
Indicates an error during the Standby Rebuild process. The error
is displayed if:
1. The drive that is being rebuilt fails during the rebuild
process.
2. One of the source drives had some bad blocks during the
rebuild operation.
3. The newly added drive that replaced a failed drive, did
not work properly.
4. One of the source drives failed during the operation.
Make sure a qualified drive is being used. Check the cables,
drive, terminators and power supply.
System Drive x does not exist
The System drive number specified in the option is not configured
in this DAC960 controller.
terminfo entry too long
OR
terminfo file for ??? terminal is not readable
OR
TERMINFO pathname for device exceeds 512 characters
The terminfo variable in Unix is not set properly or if set
properly, is not readable in the terminfo database. Make sure the
"root" user is executing this utility. Make sure the utility is being
run from the system console screen and not from a terminal connected
to the system. Make sure the terminfo entries in the database is not
corrupted, for the currently selected terminfo variable.
This command is currently implemented only under DOS
Some of the toolkit commands can be used only under DOS.
This option is not available if invoked from SysAdmin Shell
If the toolkit options are to be used on another DAC960 control-
ler, select the other DAC960 from the main menu of DAC960sh utility
and then enter the toolkit.
This utility can only be invoked from 'ansi' terminal
DAC960SH should be run by "root" user from the system console
only.
This utility has to be invoked from DAC SysAdm Shell
CHDEVSH and RBLDSH are utilities that are called by the DAC960SH
utility and can't be run by themselves.
Unable to get current state of device
The DAC960 returned an error while trying to get the status of a
device. If problem persists, replace the card.
Unable to select a DAC960
There are no other DAC960 present in the system and hence can't
be selected. Make sure the DAC960 is properly inserted in a BUS mas-
tering EISA slot and is EISA configured.
WARNING! Replacement disk too small .... Enter y to proceed :
At the start of the rebuild, the utility will check the size of
the replacement disk. If the replacement disk is smaller than the
original disk, the user is prompted (with a warning) to answer "y" or
"n" for the rebuild to continue.
WRITE-BACK ERROR HAS OCCURRED
If one or more System drives are set in WRITE BACK mode, the
Operating System will get a write done status, immediately after the
data has been written to the DAC960 cache. After a while the DAC960
will write the cached data to the disk drives. If this physical disk
write operation fails, then DAC960 will report this error status. The
system may exhibit data loss on these blocks.
Note : The file /usr/dac960/dac01log and /usr/dac960/dac02log store
all the log information for first and second DAC960 respectively.
DACMON1D and DACMON2D daemon need to be run for the to record informa-
tion in the respective log files.
| T.R | Title | User | Personal
Name | Date | Lines
|
|---|