.\" Copyright (c) 1980,1988, 1991 Regents of the University of California.
.\" Redistribution and use in source and binary forms, with or without
.\" modification, are permitted provided that the following conditions
.\" 1. Redistributions of source code must retain the above copyright
.\" notice, this list of conditions and the following disclaimer.
.\" 2. Redistributions in binary form must reproduce the above copyright
.\" notice, this list of conditions and the following disclaimer in the
.\" documentation and/or other materials provided with the distribution.
.\" 3. All advertising materials mentioning features or use of this software
.\" must display the following acknowledgement:
.\" This product includes software developed by the University of
.\" California, Berkeley and its contributors.
.\" 4. Neither the name of the University nor the names of its contributors
.\" may be used to endorse or promote products derived from this software
.\" without specific prior written permission.
.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
.\" @(#)up.4 6.4 (Berkeley) 3/27/91
.Nd unibus storage module controller/drives
.Cd "controller sc0 at uba? csr 0176700 vector upintr
.Cd "disk up0 at sc0 drive 0"
storage module disk driver.
It is specifically designed to work with the
adapted to other controllers (although bootstrapping will
not necessarily be directly possible.)
should be used to create the
if a special file needs to be made manually.
It is recommended as a security precaution to not create special files
for devices which may never be installed.
The driver interrogates the controller's holding register
to determine the type of drive attached. The driver recognizes
(the Eagle is not supported by the SC-21).
Special file names begin with
for the block and character files respectively. The second
component of the name, a drive unit number in the range of zero to
seven, is represented by a
in the disk layouts below. The last component of the name, the
file system partition, is
designated by a letter from
which also corresponds to a minor device number set: zero to seven,
eight to 15, 16 to 23 and so forth for drive zero, drive two and drive
The location and size (in 512 byte sectors) of the
partitions for the above drives:
.Bl -column header diskx undefined length
.Tn CDC No 9762 partitions
.Sy disk start length cyls
hp?f 121440 10080 759-822
.Tn CDC No 9766 300M drive partitions:
.Sy disk start length cyl
up?d 341696 15884 562-588
up?e 358112 55936 589-680
up?f 414048 861760 681-822
up?g 341696 158528 562-822
.Tn AMPEX DM Ns No 980 partitions
.Sy disk start length cyls
hp?f 121440 10080 759-822
.Tn AMPEX No 9300 300M drive partitions:
.Sy disk start length cyl
up?d 341696 15884 562-588
up?e 358112 55936 589-680
up?f 414048 81312 681-814
up?g 341696 153664 562-814
.Tn AMPEX No Capricorn 330M drive partitions:
.Sy disk start length cyl
hp?d 342016 15884 668-699
hp?e 358400 55936 700-809
hp?f 414720 109408 810-1023
hp?g 342016 182112 668-1023
.Tn FUJITSU No 160M drive partitions:
.Sy disk start length cyl
up?f 121600 141600 380-822
up?g 49600 213600 155-822
.Tn FUJITSU No Eagle partitions
.Sy disk start length cyls
hp?d 375360 15884 391-407
hp?e 391680 55936 408-727
hp?f 698880 109248 728-841
hp?g 375360 432768 391-841
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
.Bl -tag -width Pa -compact
.It Pa /dev/rup[0-7][a-h]
.It "up%d%c: hard error %sing fsbn %d[-%d] cs2=%b er1=%b er2=%b."
An unrecoverable error occurred during transfer of the specified
filesystem block number(s),
which are logical block numbers on the indicated partition.
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
.It "up%d: write locked."
The write protect switch was set on the drive
when a write was attempted. The write operation is not recoverable.
The drive was spun down or off line when it was
accessed. The i/o operation is not recoverable.
.It "up%d: not ready (flakey)."
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
.It "up%d%c: soft ecc reading fsbn %d[-%d]."
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
.It "sc%d: lost interrupt."
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.
reset, and retry of the pending operations.
If the controller continues to lose interrupts, this error will recur
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