.\" Copyright (c) 1990, 1991 The Regents of the University of California.
.\" This code is derived from software contributed to Berkeley by
.\" the Systems Programming Group of the University of Utah Computer
.\" 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
.\" @(#)rd.4 5.2 (Berkeley) 3/27/91
.Cd "master hpib? at scode?"
.Cd "disk rd? at hpib? slave?"
Only a small number of possible
but others can easily be added by adding tables to the driver.
It is a typical block-device driver; see
should be used to create the
if a special file needs to be made manually.
The driver interrogates the controller
to determine the type of drive attached.
The driver recognizes the following drives:
7912, 7914, 7933, 7936, 7937, 7945,
7962, 7963, 9122, 9134, 7912, 7936,
not all of which have been tested.
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 is the
which also corresponds to a minor device number sets: zero to seven,
eight to 15, 16 to 23 and so forth for drive zero, drive two and drive
The location and size (in sectors) of the
partitions for these drives:
.Bl -column header diskx undefined length
.Tn 7945/7946 No partitions:
.Sy disk start length cyls
.Sy disk start length cyls
.Sy disk start length cyls
.Sy disk start length cyls
.Tn 7914CT/P No partitions:
.Sy disk start length cyls
rd?f 179648 78400 802-1151
rd?g 56448 201600 252-1151
rd?h 81088 176960 362-1151
.Sy disk start length cyls
rd?e 64764 100800 257-656
rd?f 165564 89712 657-1012
rd?g 48636 206640 193-1012
rd?h 64764 190512 257-1012
.Sy disk start length cyls
rd?f 113344 46200 736-1035
rd?g 40810 118734 265-1035
rd?h 58520 101024 380-1035
.Sy disk start length cyls
rd?e 99866 165646 167-443
rd?f 265512 165646 444-720
rd?g 83720 706238 140-1320
rd?h 431158 358800 721-1320
.Sy disk start length cyls
.Sy disk start length cyls
rd?e 100737 120540 117-256
rd?f 220416 120540 256-395
rd?h 341817 259161 397-697
.Sy disk start length cyls
rd?e 100737 246246 63-216
rd?f 346983 246246 217-370
rd?g 84747 1031355 53-697
rd?h 593229 522873 371-697
.Tn 7957B/7961B No partitions:
.Sy disk start length cyls
rd?f 115668 44226 918-1268
rd?g 48888 111006 388-1268
rd?h 65268 94626 518-1268
.Tn 7958B/7962B No partitions:
.Sy disk start length cyls
rd?e 65772 121716 174-495
rd?f 187488 109620 496-785
rd?g 49518 247590 131-785
rd?h 65772 231336 174-785
.Tn 7959B/7963B No partitions:
.Sy disk start length cyls
rd?e 82404 303912 218-1021
rd?f 386316 207900 1022-1571
rd?g 65772 528444 174-1571
rd?h 82404 511812 218-1571
The eight partitions as given support four basic, non-overlapping layouts,
though not all partitions exist on all drive types.
In the first layout there are three partitions and a ``bootblock'' area.
The bootblock area is at the beginning of the disk and holds
the standalone disk boot program.
partition is for the root file system,
is a paging/swapping area, and
The second layout is the same idea,
but has a larger paging/swapping partition
a smaller ``everything else'' partition
This layout is better for environments which run many large processes.
The third layout is a variation of the second,
partition into two partitions,
The final layout is intended for a large, single file system second disk.
It is also used when writing out the boot program since it is the only
partition mapping the bootblock area.
.Bl -tag -width /dev/rrd[0-7][a-h] -compact
.It Pa /dev/rrd[0-7][a-h]
.It "rd%d err: v%d u%d, R0x%x F0x%x A0x%x I0x%x, block %d"
An unrecoverable data error occurred during transfer of the
specified block on the specified disk.
The current disk partitioning is totally bogus.
drives have 256 byte sectors which are mapped to 512 byte
``sectors'' by the driver.
drives have an odd number of sectors per cylinder,
the disk geometry used is not always accurate.
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.
A program to analyze the logged error information (even in its
present reduced form) is needed.
projects / unix-history / blob