|
Product: StorageExpress™ Backup Server
E6000, E6001, E6002, E6003, E6004, E6005, E6006, E6007, E6008, E6009,
E6010, E6012, E6013, E6014, E6015, E6016, E6017, E6018, E6019, E6020,
E6021, E6022, E6023, E6024, E6025, E6026, E6027, E6029, E6035, E6038,
E6039, E6047, E6048, E6049, E6052, E6053, E6054, E6055, E6056, E6058,
E6059, E6060, E6061, E6062, E6063, E6064, E6069, E6072, E6073, E6074,
E6076, E6079, E6080, E6081, E6082, E6084, E6091, E6092, E6093, E6094,
E6095, E6096, E6097, E6098, E6104, E6105, E6106, E6107, E6109, E6110,
E6111, E6113, E6200, E6205, E6501, E6502, E6900, E6909, E6910, E6946,
E6000 Error Formatting; Error code 1d2d70
Problem
User upgrades to ARCserve 5.01g and Exabyte 8205 no longer formats
correctly, generating the following error in the Tape Server log:
E6000 Error Formatting; Error code 1d2d70.
Resolution
Apply the patch located in ECN075.ZIP (available from the Cheyenne
Online Services) and add the following lines to the TAPESVR.CFG
file, found in the \ARCSERVE\NLM directory:
[CONFIG]
SPACEEOD=ENABLE
This will change the way ARCserve positions itself during the
format sequence.
Note: The Exabyte 2501 tape drive, when used with ARCserve version
5.01 or older, will generate the E6000 error message with any new
tape. Performing a Long Erase prior to formatting or upgrading to
ARCserve 5.01d or above will eliminate the problem.
E6001 - Error Erasing: [ARCserve error description]
E6002 - Error Copying: [ARCserve error description]
E6003 - Error Retensioning: [ARCserve error description]
E6004 - Error Setting Compression: [ARCserve error description]
E6005 - Device will not become ready - initialization required
E6006 - Logical unit does not respond to selection
E6007 - Logical unit failure
E6008 - Device communication failure
E6009 - Device communication parity error
E6010 - Track following positioning error
E6012 - Write error- head sync error during write
E6013 - Unrecovered read error
E6014 - Uncorrectable block encountered during read
E6015 - Error too long to correct
E6016 - Too many permanent read errors - cannot re-synchronize
E6017 - Incomplete block read (postamble not found)
E6018 - Recorded entity not found or basic media error
E6019 - Filemark or setmark not found
E6020 - End of data not detected - corrupt format
E6021 - Block sequence error
E6022 - Mechanical positioning error
E6023 - Servo-Mechanical positioning error
E6024 - Positioning error detected by read, space, or locate
E6029 - Synchronous data transfer error
Problem
An error has occurred between the controller card and the tape
drive. Disable Synchronous transfer or negotiation on the
controller
Resolution
All of the above error messages indicate the existence of a media
or hardware problem that is preventing a Tape Server operation from
being successfully completed.
See the Tape Drive Troubleshooting Checklist for the steps to take
to determine the exact nature of the the problem.
E6005, E6006, E6007
Solution
Power off the drive, then power back on. Unload the Tape Server
NLM, then reload. Check the SCSI terminators. Check the cables
connection your tape drives.
E6020
Description
This tape is bad. You can no longer use this tape.
E6029
Solution
Disable Synchronous transfer or negotiation. Depending on the
drive, you may have to alter the settings on the board.
E6035 - Parameter not supported - flash eeprom problem
Problem
This is a firmware error.
Resolution
The above error message indicates the existence of a media or
hardware problem that is preventing a Tape Server operation from
being successfully completed.
See the Tape Drive Troubleshooting Checklist for the steps to take
to determine the exact nature of the the problem.
E6038 - Not ready to ready transition
E6039 - Power on reset occurred
Problem
The power to the tape drive was interrupted, either by a deliberate
power-cycle, a faulty power supply or a service interruption.
Resolution for all of the above
All of the above error messages indicate the existence of a media
or hardware problem that is preventing a Tape Server operation from
being successfully completed.
See the Tape Drive Troubleshooting Checklist for the steps to take
to determine the exact nature of the the problem.
E6047 - Incompatible medium installed
E6048 - Cannot read medium - unknown format
Problem
An unknown tape format was used.
Resolution
The above error messages indicate the existence of a media or
hardware problem that is preventing a Tape Server operation from
being successfully completed.
See the Tape Drive Troubleshooting Checklist for the steps to take
to determine the exact nature of the the problem.
E6049 - Medium format is corrupt - DDS bad at group level
E6052 - Sequential positioning error
E6053 - Tape position error at beginning of media
E6054 - Physical end of tape encountered - tape position error at EOM
E6055 - Reposition error
E6056 - Read past end of medium
Problem
The tape drive failed to generate an Early Warning.
Resolution
All of the above error messages indicate the existence of a media
or hardware problem that is preventing a Tape Server operation from
being successfully completed.
See the Tape Drive Troubleshooting Checklist for the steps to take
to determine the exact nature of the the problem.
E6049 This tape is bad.
Solution
You need to use a new tape.
E6058 - Device has not self-configured yet
Problem
It is not possible to send commands to the drive because mechanism
tests are being executed.
Resolution
The above error message indicates the existence of a media or
hardware problem that is preventing a Tape Server operation from
being successfully completed.
See the Tape Drive Troubleshooting Checklist for the steps to take
to determine the exact nature of the the problem.
E6059 - Internal ram or diagnostic failure
E6060 - Diagnostics failure. Vendor unique
E6061 - Unspecified fatal error
E6062 - Time-out error
E6063 - SCSI Message error
E6064 - Internal software (firmware) error (44 00)
Problem
This error generally occurs with Exabyte tape drives. It means
that the firmware has encountered an internal problem. Exabyte has
requested that Cheyenne refer these problems back to them. Prior
to doing so, the user should be able to describe exactly when and
how the problem occurred and also have a debug file available. A
firmware update will be required to resolve the problem.
Note: The (44 00) error code may also mean "Internal Target Failure"
on different manufacturers' tape drives.
Resolution
All of the above error messages indicate the existence of a media
or hardware problem that is preventing a Tape Server operation from
being successfully completed.
See the Tape Drive Troubleshooting Checklist for the steps to take
to determine the exact nature of the the problem.
E6069 - SCSI parity error detected
E6072 - Command phase error
Problem
Too many parity errors have occurred during an attempted Command
phase.
Resolution
The above error messages indicate the existence of a media or
hardware problem that is preventing a Tape Server operation from
being successfully completed.
See the Tape Drive Troubleshooting Checklist for the steps to take
to determine the exact nature of the the problem.
E6073 - Data phase error
Problem
Too many parity errors have occurred during the Data-In and
Data-Out phases of an operation.
Resolution
The above error message indicates the existence of a media or
hardware problem that is preventing a Tape Server operation from
being successfully completed.
See the Tape Drive Troubleshooting Checklist for the steps to take
to determine the exact nature of the the problem.
E6074 - Logical unit failed self-configuration
E6076 - Write append error
Problem
If a WRITE or WRITE FILEMARKS command fails because the append
point was unreadable, this error occurs.
Resolution
The above error messages indicate the existence of a media or
hardware problem that is preventing a Tape Server operation from
being successfully completed.
See the Tape Drive Troubleshooting Checklist for the steps to take
to determine the exact nature of the the problem.
E6079 - Erase failure
E6080 - Cassette fault
E6081 - Media load or eject failed
E6082 - Unload tape failure
E6084 - Drive hardware error - servo or sensor
E6091 - Incorrect block length
E6094 - SCSI bus parity error
E6095 - Formatted Buffer Parity Error
E6096 - Media Error
E6097 - Error Counter Overflow
Problem
The maximum number of retries has been exhausted.
Resolution
All of the above error messages indicate the existence of a media
or hardware problem that is preventing a Tape Server operation from
being successfully completed.
See the Tape Drive Troubleshooting Checklist for the steps to take
to determine the exact nature of the the problem.
E6098 - Tape Motion Error
E6104 - Servo System Error
E6105 - Formatter Error
E6106 - Write Splice Error, Blank
E6107 - Write Splice Error, Overshoot
E6502: Find next session failed.
Problem
The algorithm that determines the next session number to be
appended to the tape has failed.
Resolution
All of the above error messages indicate the existence of a media
or hardware problem that is preventing a Tape Server operation from
being successfully completed.
See the Tape Drive Troubleshooting Checklist for the steps to take
to determine the exact nature of the the problem.
Add'l info from E6502 older cell: " Check TAPE$SVR.LOGlog for any
recorded errors. It will be most likely that a MEDIA Error or
HARDWARE error had occurred. The steps afterwards is based on the
Error Code data that is returned by the Tape Drive. Most common
steps are check cables, clean the heads, check termination, try a
new tape, upgrade the firmware, etc."
E6025 - Recovered with no ECC applied
Problem
The system recovered successfully from a soft error while
completing a command.
E6026 - Recovered with retries
Problem
One or more frames has to be rewritten by the drive in order to
complete a command successfully.
E6027 - Recovered with ECC applied
Problem
The system had to use ECC to successfully complete a command. This
means that there was a bad block, but the drive successfully
rewrote to another block.
Resolution
The above message indicates that a media or hardware problem was
encountered during a Tape Server operation and a successful retry
or recovery was accomplished. While the current operation did
complete successfully, these messages may indicate the existence of
a problem that could be exacerbated by continued use of the device.
Close monitoring of Tape Server operations is recommended and the
Tape Drive Troubleshooting Checklist should be consulted for steps
to be taken to determine the source of the problem.
E6092 - Fatal - Uncorrectable error
E6093 - Possible firmware error or catastrophic drive failure
Problem
The appearance of any of the above error messages is always
preceded by another coded error message and is included as an
indication of the severity of the stated error. The accompanying
text is the definition of the Tape Drive's Sense data as expressed
in a tape server debug log. For example, if a tape drive debug log
showed a SENSE KEY = 04h and bytes 12 and 13 are (44 00), the E6092
message will be used as follows:
E6064 - Internal Software (firmware) error (44 00)
E6092 - Fatal - Uncorrectable error
Resolution
This is an indication of a hardware error.
See the Tape Drive Troubleshooting Checklist for steps to be taken
to determine the exact nature of the problem.
E6109 - Failed to initialize list. Possibly out of memory.
Problem
There was insufficient memory available on the ARCserve Server to
complete the specified process.
Resolution
See Checking the File Server's Memory Status.
E6110 - Timed out trying to ERASE the log file. Erase is aborted
Problem
The log file has been locked in an open state by another process.
Resolution
Make sure that no other viewer or application is accessing the log
file.
E6111 - File grooming aborted: couldn't create temp file '[filename]'.
Try deleting the temp file and check file rights.
E6113 - Operation aborted: failed to open [temp or log] file '[temp or
file name]' for [input or output]
Problem
This error message indicates that ARCserve was unable to open a log
file. There are two variations of the message, depending on the
operation that ARCserve was attempting:
If ARCserve was trying to open the specified temporary file
that it uses to groom the Activity Log, the message reads: "Failed
to open temp file [temp file name] for output."
If ARCserve was trying to open the Activity Log itself, the
message reads: "Failed to open log file [log file name] for input."
Resolution
Check that there is sufficient disk space available on the ARCserve
volume for the file activity and make sure that the rights of the
user account created by the ARCserve installation process have not
been altered in any way. If this account cannot be readily
returned to its original state, it will be necessary to recreate
the ARCserve Job Queue.
See also ARCserve and File Server Disk Space Problems.
See also Recreating the ARCserve Job Queue.
E6200 - No data detected
Problem
This error message indicates that, during a SCSI Command operation,
the tape server received an unexpected BLANK CHECK error. BLANK
CHECK means that the drive has just passed over an area on the tape
and that the area has no readable data on it.
Resolution
Check the tape drive configuration information in the Device
Management screen at the file server console or in the ARCserve
Manager. Then unload and reload ARCserve. Check the Device
Management information again. If the tape drive's model number or
firmware information has changed, then either a signal or hardware
problem exists. This information should NOT change! Consult the
Tape Drive Troubleshooting Checklist for the steps to be taken to
troubleshoot a hardware problem.
E6200 failed to format tape
Problem
The error message indicates that a user had a Peripheral Vision
compression board installed on an Exabyte 8500 tape drive with
firmware 06L0. This device is a compression board/tape door which
attaches to most major tape drives (Exabyte, HP, Conner, etc). It
is designed to perform hardware-based data compression on tape
drives that do not already have hardware compression. In theory,
the device should be invisible to ARCserve, and products like it.
The user was receiving the above error, after which the drive would
lock up and have to be power-cycled before any further response
could be received.
Resolution
Peripheral Vision engineers were able to reproduce the problem.
They say that a firmware update to revision E1A3519D will resolve
the situation. Cheyenne and Exabyte will both be testing this
compression board. As of this time, it has not been certified by
Cheyenne software for use with ARCserve.
E6205 - Error opening file, TDRVDEF.CFG - no such file or directory.
Problem
The TDRVDEF.CFG file is created in the \ARCSERVE\NLM directory and
read by TAPESVR.NLM every time the ARCserve Tape Server is loaded.
If the Advanced Features menu is access from the Device Management
menu on the ARCserve Tape Manager screen, the user can redefine
certain tape server parameters. If any of the parameters are
changed and saved, a new file containing these parameters is called
TDRV.CFG and created in the same directory. This new file will be
run the next time ARCserve is loaded. The above error occurs when
TAPESVR.NLM is unable to find or read the original configuration
file.
Resolution
If the TDRVDEF.CFG file is corrupt, the user can delete the file,
run ASTOP and then ASTART. A new file will be created with the
default settings. If this does not resolve the problem, make sure
that the file attributes for TDRVDEF.CFG are set to READ/WRITE, and
not READ ONLY. Also, be sure that there is enough disk space on
the ARCserve volume for the file (normally 206 bytes).
E6501 - Job denied
This error message is generated when a job submitted to the Tape
Server was not allowed to be executed. "Job denied" will be followed
for the reason for the failure. Listed below are the most common
messages generated and the steps to be taken to resolve them.
Problem "Hardware Error"
A hardware error was detected while the tape server attempted to
communicate with the tape drive.
Resolution "Hardware Error"
Check the TAPE$SVR.LOG file for specific SCSI error messages, and
refer to the entries elseware in this section for possible
resolutions.
Problem "Volume header illegal block length"
This error may occur in ARCserve versions 5.01d and earlier because
the block size used to write to the tape in the drive is different
from the default block size that the Tape Server is currently
configured for and expects to see. Usually, this occurs when a
tape created with a different drive or a different Cheyenne backup
product is used with ARCserve 5.x. When this occurs, the tape
server will automatically software WRITE PROTECT the tape and will
not allow any ARCserve operations to destroy this tape.
Resolution "Volume header illegal block length"
1. Upgrade ARCserve to version 5.01e or later. The Tape Server in
ARCserve versions 5.01e and later will automatically adjust itself
to the block size of the tape in the drive.
2. If the data on the tape must be accessed immediately, the block
size used by the tape server can be reconfigured to match that of
the tape. In most cases, however, this should only be used as a
temporary measure, because changing the block size will cause any
other tapes already written by this ARCserve installation to be
unreadable, causing the same error to be generated. To do this,
perform the following steps:
- Using an ASCII text editor, open the TAPESVR.CFG file found in
the \ARCSERVE\NLM directory on the ARCserve server
- Add a section to the bottom of the file that appears as follows:
[CONFIG]
BLOCKSIZEx = y SCSIID z
where x is a numeral from 1 to 7 representing the occurrence of
this parameter (that is, multiple occurrences of the BLOCKSIZE
parameter may be included in the same [CONFIG] section, numbered
from 1 to 7);
where y is a numeral from 0 to 6 representing the block size
desired, according to the following table:
y Block Size
0 = 512
1 = 1024
2 = 2048
3 = 4096
4 = 8192
5 = 16384
6 = 32748 (ARCserve 5.01d only);
where z is a numeral from 0 to 6 representing the SCSI ID of the
tape drive.
- Save the changes to the file and restart ARCserve by typing
ASTOP and ASTART at the file server console. During the
initialization of the Tape Server, a message should appear on the
file server console indicating the block size change.
- Retry the ARCserve job as before.
3. If the data on the tape is not important, an explicit command
to FORMAT or ERASE the tape through the Tape Manager's Back-end
will allow the tape to be destroyed and the block size to be set
correctly.
E6900 - SCSI Timeout - Bus Free Phase Timout.
Problem
A SCSI command sent to the tape drive did not generate the expected
response before the end of the allotted timeout period. The tape
drive is either in a BUSY state (for an undetermined reason) or
communication on the SCSI bus is not being properly accomplished.
Resolution
1. Power cycle the tape drive.
2. Unload and reload the ARCserve by typing ASTOP and ASTART at
the file server console.
3. If the same error occurs, down the file server, cycle power to
all devices and reboot.
See also Tape Drive Troubleshooting Checklist.
E6909: Unknown Error
Problem
An error occurred after a SCSI Command has signalled completion.
The error returned by the host adapter could not be classified
under current error codes.
Resolution
Check the Tape Server Log (TAPE$SVR.LOG) for any other indications
of a problem.
See also the Tape Drive Troubleshooting Checklist.
E6910 - SCSI Timeout - General timeout error
Problem
This error message, possible accompanied by "Controller error, A5,"
is caused by a SCSI command having failed to signal its completion
to the host adapter.
Resolution
See the Tape Drive Troubleshooting Checklist, particularly the Host
Adapter Configuration settings. If the problem persists, use the
SHOTS parameters to slow down tape drive activity. See TAPESVR.CFG
Parameters.
E6946 : [0] Previous transmit ECB status = ffed
Problem
User was running NetWare* 4.1 and was getting, E6946:[0] Previous
transmit ECB status=ffed in his activity log.
Resolution
After unloading CLIENTS.NLM and increasing the number of remote
sessions, the problem disappeared.
This applies to:
|
