.\" Copyright (c) 1986 Regents of the University of California.
.\" All rights reserved. The Berkeley software License Agreement
.\" specifies the terms and conditions for redistribution.
.\" @(#)vd.4 6.2 (Berkeley) %G%
vd \- VERSAbus storage module controller/drives
.B "controller vd0 at vba? csr 0xffff2000 vector vdintr"
.B "disk dk0 at vd0 drive 0"
This is a generic VERSAbus storage module disk driver for the
Computer Consoles smd and smd-e disk controllers.
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 ``dk'' 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 1024 bytes (a disk block).
calls should specify a multiple of 1024 bytes.
The driver tries to access the last track on each drive
to determine the type of drive attached. The driver recognizes
six different drives: CDC FSD (160 MB), CDC 9766 (300 MB),
CDC XFSD (340 MB), CDC 515MB, Fujitsu 360 MB, and Fujitsu
The origin and size of the pseudo-disks on each drive are
.ta .5i +\w'000000 'u +\w'000000 'u +\w'000000 'u
FSD 160Mb drive partitions:
fsd?b 9600 12000 60 - 134
fsd?c 21600 109280 135 - 817
fsd?d 39840 91040 249 - 817
fsd?e 58080 72800 363 - 817
fsd?f 76320 54560 477 - 817
fsd?g 94560 36320 591 - 817
fsd?h 112800 18080 705 - 817
SMD (CDC 9766) 300Mb drive partitions:
smd?b 20064 13680 66 - 110
smd?c 33744 214928 111 - 817
smd?d 69616 179056 229 - 817
smd?e 105488 143184 347 - 817
smd?f 141360 107312 465 - 817
smd?g 177232 71440 583 - 817
smd?h 213104 35568 701 - 817
XFD 340Mb drive partitions:
xfd?b 20352 20352 53 - 105
xfd?c 40704 230400 106 - 705
xfd?d 79104 192000 206 - 705
xfd?e 117504 153600 306 - 705
xfd?f 155904 115200 406 - 705
xfd?g 194304 76800 506 - 705
xfd?h 232704 38400 606 - 705
FUJ 360Mb drive partitions:
fuj?b 19200 24000 60 - 134
fuj?c 43200 218560 135 - 817
fuj?d 79680 182080 249 - 817
fuj?e 116160 145600 363 - 817
fuj?f 152640 109120 477 - 817
fuj?g 189120 72640 591 - 817
fuj?h 225600 36160 705 - 817
XSD 515Mb drive partitions:
xsd?b 30528 30528 53 - 105
xsd?c 61056 345600 106 - 705
xsd?d 118656 288000 206 - 705
xsd?e 176256 230400 306 - 705
xsd?f 233856 172800 406 - 705
xsd?g 291456 115200 506 - 705
xsd?h 349056 57600 606 - 705
It is unwise for all of these partitions to be present in one installation,
since there is overlap in addresses and protection becomes
The ?a partition is normally used for the root file system,
and the ?b partition as a paging area.
The ?c partition maps the rest of the pack,
except the last 5 cylinders which are reserved for bad sector forwarding,
/dev/dk[0-7][a-f] dk block files
/dev/rdk[0-7][a-f] dk raw files
\fBvd%d: %s controller\fP.
This message is printed during autoconfiguration to identify
the type of controller, either ``smd'' or ``smde''.
During autoconfiguration the controller failed to respond to
\fBvd%d: diagnostic error\fP.
During autoconfiguration the controller failed to respond to
\fBdk%d: unknown drive type\fP.
The system was unable to identify the specified drive as
one of the drives described above; the drive will not be
\fBvd%d: drive %d: config error\fP.
The system encountered a hard error when it tried to configure
a drive during autoconfiguration.
\fBvd%d: starting drives, wait ... \fP.
This message indicates the system is about to tell the
controller to ``start'' the drives attached to it.
\fBdk%d: %s <ntrak %d, ncyl %d, nsec %d>\fP.
For each drive recognized during autoconfiguration the system
prints a message of this form. The drive type is displayed
as well as the geometry: tracks/cylinder, cylinders, and sectors/track.
\fBvd%d: lost interrupt, status %b, error code %x\fP.
The system failed to receive an interrupt from the controller after
submitting a request. The error status field of the device control
block is printed in hexadecimal followed by a symbolic description.
If this is an smde controller, the error code is also displayed.
The system attempts to abort the current request and simulate an
interrupt to unwedge the controller.
\fBvd%d: stray interrupt\fP.
The system received an unexpected interrupt; it is ignored.
\fBdk%d%c: hard error sn%d status %b ecode %x\fP.
An unrecoverable error was encountered. The sector number reported
is a physical sector number on the drive. The error status and code
are displayed as described previously. If the drive is write protected,
``status %b ecode %x'' will not be shown.
\fBdk%d%c: soft error sn%d status %b ecode %x\fP.
A recoverable error was detected by the controller. The status and
error code information will not be shown if the controller indicated
it corrected the error itself.
\fBvd%d: drive %d: couldn't reset\fP.
The system was unable to reconfigure a drive during a controller reset.
\fBvd%d: controller timeout\fP.
The controller failed to complete an operation within a reasonable
time. This message is usually followed by another message indicating
what operation timed out; e.g. ``during config'' for a configuration
scribble on the tail of incomplete blocks.
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