All rights reserved. The Berkeley software License Agreement
specifies the terms and conditions for redistribution.
@(#)cy.4 6.3 (Berkeley) 07/08/88
"device yc0 at cy0 drive 0"
The Tapemaster controller board is actually a Multibus controller accessed through a Halversa Multibus to VERSAbus converter card.
cy%d: timeout or err during init, status=%b. The controller timed out or an error occurred on a nop command during autoconfiguration; the controller may be hung.
cy%d: configuration failure, status=%b. The controller timed out or an error occurred on a configure command during autoconfiguration; the controller may be hung.
yc%d: no write ring. An attempt was made to write on the tape drive when no write ring was present; this message is written on the terminal of the user who tried to access the tape.
yc%d: not online. An attempt was made to access the tape while it was offline; this message is written on the terminal of the user who tried to access the tape.
cy%d: i/o size too large. A read or a write request exceeded the maximum transfer size for the controller - 32 kilobytes; this message is written on the terminal of the user who made the read or write request.
yc%d: hard error bn%d status=%b. A tape error occurred at block bn; the cy error register is printed in hexadecimal with the bits symbolically decoded. Any error is fatal on non-raw tape; when possible the driver will have retried the operation which failed several times before reporting the error. For known errors, the trailing %s is one of the following:
timeout, timeout1, timeout2, timeout3, timeout4. Time out errors; this may be due to trying to read a blank tape or the controller failing to interrupt or the drive dropping off-line.
non-existent memory. A controller transfer to memory timed out.
blank tape. The controller detected a blank tape when data was expected.
micro-diagnostic, missing diagnostic jumper. An error occurred in the micro-diagnostics or the diagnostic mode jumper was not installed while attempting to execute a diagnostics command.
eot/bot detected. The controller unexpectedly encountered end-of-tape or beginning-of-tape during an operation.
retry unsuccessful. An error occurred which could not be recovered by repeated retries.
fifo over/under-flow. The controller was unable to transfer data to the drive fast enough. This usually occurs because a transfer was performed without using the controller's internal buffer.
drive to controller parity error. A parity error was detected by the controller in data transferred between the drive and the controller's internal buffer.
prom checksum. The controller thinks its PROM is corrupted.
time out tape strobe (record length error). The controller timed out while looking for an inter-record gap. This usually occurs because the records on the tape are larger than expected (or can be handled).
tape not ready. The drive does not respond; usually the power has been turned off or a cable has come off.
write protected. A write ring was present in the tape when a write was attempted.
invalid link pointer. An invalid pointer was encountered in a tape parameter block.
unexpected file mark. A tape file mark was encountered while trying to read or space.
invalid byte count. An invalid byte count parameter was encountered in a tape parameter block.
unidentified hardware error, streaming terminated. These should not happen.
yc%d: lost interrupt. The controller failed to respond with an interrupt signifying completion of the current command. The system will attempt to abort the outstanding command and reset the controller.
cy%d: reset failed. The system was unable to reset the controller. This is normally preceded by another message from the driver.