.\" 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
.\" @(#)hp.4 6.5 (Berkeley) 3/27/91
.Cd "disk hp0 at mba0 drive 0"
is a generic Massbus disk driver which handles both the standard
controllers and the Emulex
It is typical of a block-device disk driver; block
should be used to create the special files; if a special file
needs to be created by hand consult
It is recommended as a security precaution to not create special files
for devices which may never be installed.
The first sector of each disk contains both a first-stage bootstrap program
and a disk label containing geometry information and partition layouts (see
This sector is normally write-protected, and disk-to-disk copies should
avoid copying this sector.
The label may be updated with
which can also be used to write-enable and write-disable the sector.
The next 15 sectors contain a second-stage bootstrap program.
This driver handles both standard
During autoconfiguration or whenever a drive comes on line for the first time,
or when a drive is opened after all partitions are closed,
the first sector of the drive is examined for a disk label.
If a label is found, the geometry of the drive and the partition tables
recognized according to the
and default partitions are used.
For the Emulex controller the drive type register should be configured
to indicate the drive is an
When this is encountered,
the driver checks the holding register to find out
the disk geometry and, based on this information, decides what
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 is the file system partition
and 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 following disks are supported:
Capricorn (32 sectors/track),
Eagle (48 sectors/track),
9300. The default layout and size (in sectors) of the
partitions for these drives:
.Bl -column header diskx undefined length
.Sy disk start length cyls
hp?f 121440 10080 759-822
.Sy disk start length cyls
hp?d 341696 15884 562-588
hp?e 358112 55936 589-680
hp?f 414048 86176 681-822
hp?g 341696 158528 562-822
.Sy disk start length cyls
hp?f 121220 219296 290-814
hp?g 49324 291192 118-814
.Sy disk start length cyls
hp?f 125888 120466 281-558
hp?g 49910 192510 115-558
.Sy disk start length cyls
hp?f 121220 50424 290-410
.Sy disk start length cyls
hp?d 376000 15884 235-244
hp?e 392000 307200 245-436
hp?f 699200 308600 437-629
hp?g 376000 631800 235-629
.Tn CDC No 9775 partitions
.Sy disk start length cyls
hp?d 376320 15884 294-306
hp?e 392960 307200 307-546
hp?f 700160 377440 547-841
hp?g 376320 701280 294-841
.Tn CDC No 9730 partitions
.Sy disk start length cyls
hp?f 121600 141600 380-822
hp?g 49600 213600 155-822
.Tn AMPEX No Capricorn partitions
.Sy disk start length cyls
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 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
.Tn FUJITSU No 2361 partitions
.Sy disk start length cyls
hp?d 376320 15884 294-306
hp?e 392960 307200 307-546
hp?f 700160 377408 547-841
hp?g 363520 701248 294-841
.Tn AMPEX No 9300 partitions
.Sy disk start length cyl
hp?d 341696 15884 562-588
hp?e 358112 55936 589-680
hp?f 414048 81312 681-814
hp?g 341696 153664 562-814
The hp?a partition is normally used for the root file system,
the hp?b partition as a paging area,
and the hp?c partition for pack-pack copying (it maps the entire disk).
On disks larger than about 205 Megabytes, the hp?h partition
is inserted prior to the hp?d or hp?g partition;
the hp?g partition then maps the remainder of the pack.
All disk partition tables are calculated using the
.Bl -tag -width /dev/rhp[0-7][a-h] -compact
.It Pa /dev/rhp[0-7][a-h]
.It "hp%d%c: hard error %sing fsbn %d [of %d-%d] (hp%d bn %d cn %d tn %d sn %d) mbsr=%b er1=%b er2=%b."
An unrecoverable error occurred during transfer of the specified
which is a logical block number on the indicated partition.
If the transfer involved multiple blocks, the block range is printed as well.
The parenthesized fields list the actual disk sector number
relative to the beginning of the drive,
as well as the cylinder, track and sector number of the block.
status register is printed in hexadecimal and
with the error bits decoded if any error bits other than
are set. In any case the contents of the two error registers are also printed
in octal and symbolically with bits decoded.
(Note that er2 is what old
The error was either unrecoverable, or a large number of retry attempts
(including offset positioning and drive recalibration) could not
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
operation is not recoverable.
.It "hp%d%c: soft ecc reading fsbn %d [of %d-%d] (hp%d bn %d cn %d tn %d sn %d)."
specified sector of the specified disk partition.
If the transfer involved multiple blocks, the block range is printed as well.
The parenthesized fields list the actual disk sector number
relative to the beginning of the drive,
as well as the cylinder, track and sector number of the block.
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 hp%d: ntracks %d, nsectors %d: unknown device.
During autoconfiguration one of the above messages may appear
on the console indicating the appropriate drive type was recognized.
The last message indicates the drive is of a unknown type.
In this case, the correct geometry is set, and one partition is created
that contains the entire drive.
error logging should be supported.
A program to analyze the logged error information (even in its
present reduced form) is needed.
projects / unix-history / blob