.\" Copyright (c) 1980 Regents of the University of California.
.\" All rights reserved. The Berkeley software License Agreement
.\" specifies the terms and conditions for redistribution.
.\" @(#)up.4 6.2 (Berkeley) 5/16/86
up \- unibus storage module controller/drives
.B "controller sc0 at uba? csr 0176700 vector upintr
.B "disk up0 at sc0 drive 0"
This is a generic UNIBUS storage module disk driver.
It is specifically designed to work with the
Emulex SC-21 and SC-31 controllers.
adapted to other controllers (although bootstrapping will
not necessarily be directly possible.)
Files with minor device numbers 0 through 7 refer to various portions
minor devices 8 through 15 refer to drive 1, etc.
The standard device names begin with ``up'' followed by
the drive number and then a letter a-h for partitions 0-7 respectively.
The character ? stands here for a drive number in the range 0-7.
The block files access the disk via the system's normal
buffering mechanism and may be read and written without regard to
physical disk records. There is also a `raw' interface
which 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).
calls should specify a multiple of 512 bytes.
The driver interrogates the controller's holding register
to determine the type of drive attached. The driver recognizes
AMPEX DM980, AMPEX 9300, AMPEX Capricorn,
FUJITSU 160, and FUJITSU Eagle
(the Eagle is not supported by the SC-21).
The origin and size of the pseudo-disks on each drive are
.ta .5i +\w'000000 'u +\w'000000 'u +\w'000000 'u
hp?f 121440 10080 759-822
CDC 9766 300M drive partitions:
up?d 341696 15884 562-588
up?e 358112 55936 589-680
up?f 414048 861760 681-822
up?g 341696 158528 562-822
hp?f 121440 10080 759-822
AMPEX 9300 300M drive partitions:
up?d 341696 15884 562-588
up?e 358112 55936 589-680
up?f 414048 81312 681-814
up?g 341696 153664 562-814
AMPEX Capricorn 330M drive partitions:
hp?d 342016 15884 668-699
hp?e 358400 55936 700-809
hp?f 414720 109408 810-1023
hp?g 342016 182112 668-1023
FUJITSU 160M drive partitions:
up?f 121600 141600 380-822
up?g 49600 213600 155-822
hp?d 375360 15884 391-407
hp?e 391680 55936 408-727
hp?f 698880 109248 728-841
hp?g 375360 432768 391-841
It is unwise for all of these files to be present in one installation,
since there is overlap in addresses and protection becomes
The up?a partition is normally used for the root file system,
the up?b partition as a paging area,
and the up?c partition for pack-pack copying (it maps the entire disk).
On 160M drives the up?g partition maps the rest of the pack.
On other drives both up?g and up?h are used to map the
/dev/up[0-7][a-h] block files
/dev/rup[0-7][a-h] raw files
\fBup%d%c: hard error sn%d cs2=%b er1=%b er2=%b\fR. An unrecoverable
error occurred during transfer of the specified sector in the specified
The contents of the cs2, er1 and er2 registers are printed
in octal and symbolically with bits decoded.
The error was either unrecoverable, or a large number of retry attempts
(including offset positioning and drive recalibration) could not
\fBup%d: write locked\fR. The write protect switch was set on the drive
when a write was attempted. The write operation is not recoverable.
\fBup%d: not ready\fR. The drive was spun down or off line when it was
accessed. The i/o operation is not recoverable.
\fBup%d: not ready (flakey)\fR. The drive was not ready, but after
printing the message about being not ready (which takes a fraction
of a second) was ready. The operation is recovered if no further
\fBup%d%c: soft ecc sn%d\fR. A recoverable ECC error occurred on the
specified sector of the specified disk partition.
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 certain cylinders on the pack, spots on the carriage of the drive
\fBsc%d: lost interrupt\fR. A timer watching the controller detecting
no interrupt for an extended period while an operation was outstanding.
This indicates a hardware or software failure. There is currently a
hardware/software problem with spinning down drives while they are
being accessed which 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
truncate file offsets to 512-byte block boundaries,
scribbles on the tail of incomplete blocks.
in programs that are likely to access raw devices,
should always deal in 512-byte multiples.
A program to analyze the logged error information (even in its
present reduced form) is needed.
The partition tables for the file systems should be read off of each
pack, as they are never quite what any single installation would prefer,
and this would make packs more portable.
projects / unix-history / blob