Museum

Home

Lab Overview

Retrotechnology Articles

Online Manuals

⇒ rk(4) — Ultrix WS 2.0 VAX

Media Vault

Software Library

Restoration Projects

Artifacts Sought

Related Articles

dkio(4)

nbuf(4)

MAKEDEV(8)

uerf(8)

rk(4)

NAME

rk − RK711/RK07 disk interface

SYNTAX

controller hk0 at uba? csr 0177440 vector rkintr
disk rk0 at hk0 drive 0

DESCRIPTION

Files with minor device numbers 0 through 7 refer to various portions of drive 0; minor devices 8 through 15 refer to drive 1, and so forth.  The standard device names begin with “hk” followed by the drive number and then a letter a through h for partitions 0 through 7 respectively.  The character ? stands here for a drive number in the range 0 through 7. 

The block files access the disk using the system’s normal buffering mechanism and can be read and written without regard to physical disk records. There is also a raw interface that provides for direct transmission between the disk and the user’s read or write buffer.  A single read or write call results in exactly one I/O operation and therefore raw I/O is considerably more efficient when many words are transmitted.  The names of the raw files conventionally begin with an extra "r". 

In raw I/O, counts should be a multiple of 512 bytes (a disk sector).  Likewise seek calls should specify a multiple of 512 bytes.

The origin and size (in sectors) of the pseudodisks on each drive are as follows:

RK07 partitions:
diskstartlengthcyl
 rk?a0158840-240
rk?b1590610032241-392
rk?c0537900-814
rk?g2600427786393-813

RESTRICTIONS

In raw I/O read and write truncate file offsets to 512-byte block boundaries, and write overwrites the tail of incomplete blocks. Thus, in programs that are likely to access raw devices, read,write and lseek() should always deal in 512-byte multiples.

DIAGNOSTICS

The following messages are printed at the console:

rk%d%c: hard error sn%d. 
An unrecoverable error occurred during transfer of the specified sector of the specified disk partition. Either the error was unrecoverable, or a large number of retry attempts (including offset positioning and drive recalibration) could not recover the error.  Additional register information may be gathered from the system error log file, /usr/adm/syserr/syserr.<hostname>.

rk%d: write locked. 
The write protect switch was set on the drive when a write was attempted. The write operation is not recoverable.

rk%d: not ready. 
The drive was spun down or off line when it was accessed. The I/O operation is not recoverable.

rk%d: not ready (came back!). 
The drive was not ready. But after printing this message (which takes a fraction of a second), it was ready. The operation is recovered if no further errors occur.

hk%d: lost interrupt
A timer watching the controller detected no interrupt for an extended period while an operation was outstanding. This indicates a hardware or software failure. Spinning down drives while they are being accessed causes this error to occur. The error causes a UNIBUS reset and retry of the pending operations. If the controller continues to lose interrupts, this error will recur a few seconds later.

rk%d%c: soft ecc sn%d
This message is written to the system error log file only: A recoverable ECC error occurred on the specified sector in the specified disk partition. This happens normally a few times a week. If it happens more frequently than this, the sectors where the errors are occurring should be checked to see if the same physical location on the disk pack is causing the error. Errors in the same area on the disk pack indicate the pack is going bad. Random errors may be caused by a pack going bad or a pending hardware problem.

FILES

/dev/rk??? 
/dev/rrk???

SEE ALSO

dkio(4), nbuf(4), MAKEDEV(8), uerf(8)

Typewritten Software • bear@typewritten.org • Edmonds, WA 98026