xref: /netbsd-src/share/man/man4/man4.vax/hp.4 (revision 946379e7b37692fc43f68eb0d1c10daa0a7f3b6c)
1.\"	$NetBSD: hp.4,v 1.15 2014/10/27 16:20:48 wiz Exp $
2.\"
3.\" Copyright (c) 1991, 1993, 19801988
4.\"	The Regents of the University of California.  All rights reserved.
5.\"
6.\" Redistribution and use in source and binary forms, with or without
7.\" modification, are permitted provided that the following conditions
8.\" are met:
9.\" 1. Redistributions of source code must retain the above copyright
10.\"    notice, this list of conditions and the following disclaimer.
11.\" 2. Redistributions in binary form must reproduce the above copyright
12.\"    notice, this list of conditions and the following disclaimer in the
13.\"    documentation and/or other materials provided with the distribution.
14.\" 3. Neither the name of the University nor the names of its contributors
15.\"    may be used to endorse or promote products derived from this software
16.\"    without specific prior written permission.
17.\"
18.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
19.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
20.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
21.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
22.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
23.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
24.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
25.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
26.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
27.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
28.\" SUCH DAMAGE.
29.\"
30.\"	from: @(#)hp.4	8.1 (Berkeley) 6/5/93
31.\"
32.Dd June 5, 1993
33.Dt HP 4 vax
34.Os
35.Sh NAME
36.Nm hp
37.Nd
38.Tn MASSBUS
39disk interface
40.Sh SYNOPSIS
41.Cd "hp0 at mba0 drive 0"
42.Cd "hp* at mba? drive ?"
43.Sh DESCRIPTION
44The
45.Nm hp
46driver
47is a generic MASSBUS disk driver which handles the standard
48.Tn DEC
49controllers.
50It is typical of a block-device disk driver; block
51.Tn I/O
52is
53described in
54.Xr physio 4 .
55.Pp
56The script
57.Xr MAKEDEV 8
58should be used to create the special files; if a special file
59needs to be created by hand consult
60.Xr mknod 8 .
61It is recommended as a security precaution to not create special files
62for devices which may never be installed.
63.Pp
64The first sector of each disk contains both a first-stage bootstrap program
65and a disk label containing geometry information and partition layouts (see
66.Xr disklabel 5 .
67This sector is normally write-protected, and disk-to-disk copies should
68avoid copying this sector.
69The label may be updated with
70.Xr disklabel 8 ,
71which can also be used to write-enable and write-disable the sector.
72The next 15 sectors contain a second-stage bootstrap program.
73.Sh DISK SUPPORT
74During autoconfiguration or whenever a drive comes on line for the first time,
75or when a drive is opened after all partitions are closed,
76the first sector of the drive is examined for a disk label.
77If a label is found, the geometry of the drive and the partition tables
78are taken from it.
79If no label is found, a fake label is created by the driver, enough
80so that a real label can be written.
81.Pp
82The hp?a partition is normally used for the root file system,
83the hp?b partition as a paging area,
84and the hp?c partition for pack-pack copying (it maps the entire disk).
85On disks larger than about 205 Megabytes, the hp?h partition
86is inserted prior to the hp?d or hp?g partition;
87the hp?g partition then maps the remainder of the pack.
88.Sh FILES
89.Bl -tag -width /dev/rhp[0-7][a-h] -compact
90.It Pa /dev/hp[0-7][a-h]
91block files
92.It Pa /dev/rhp[0-7][a-h]
93raw files
94.El
95.Sh DIAGNOSTICS
96.Bl -diag
97.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."
98An unrecoverable error occurred during transfer of the specified
99filesystem block number,
100which is a logical block number on the indicated partition.
101If the transfer involved multiple blocks, the block range is printed as well.
102The parenthesized fields list the actual disk sector number
103relative to the beginning of the drive,
104as well as the cylinder, track and sector number of the block.
105The
106.Tn MASSBUS
107status register is printed in hexadecimal and
108with the error bits decoded if any error bits other than
109.Tn MBEXC
110and
111.Tn DTABT
112are set.
113In any case the contents of the two error registers are also printed
114in octal and symbolically with bits decoded.
115(Note that er2 is what old
116.Tn RP06
117manuals would call
118.Tn RPER3 ;
119the terminology
120is that of the
121.Tn RM
122disks).
123The error was either unrecoverable, or a large number of retry attempts
124(including offset positioning and drive recalibration) could not
125recover the error.
126.Pp
127.It "hp%d%c: soft ecc reading fsbn %d [of %d-%d] (hp%d bn %d cn %d tn %d sn %d)."
128A recoverable
129.Tn ECC
130error occurred on the
131specified sector of the specified disk partition.
132If the transfer involved multiple blocks, the block range is printed as well.
133The parenthesized fields list the actual disk sector number
134relative to the beginning of the drive,
135as well as the cylinder, track and sector number of the block.
136This happens normally
137a few times a week.
138If it happens more frequently than
139this the sectors where the errors are occurring should be checked to see
140if certain cylinders on the pack, spots on the carriage of the drive
141or heads are indicated.
142.Pp
143.El
144.Sh SEE ALSO
145.Xr physio 4 ,
146.Xr up 4 ,
147.Xr disklabel 5 ,
148.Xr disklabel 8 ,
149.Xr MAKEDEV 8 ,
150.Xr mknod 8
151.Sh HISTORY
152The
153.Nm
154driver appeared in
155.Bx 4.0 .
156.Pp
157A new
158.Nm
159driver showed up in
160.Nx 1.2 .
161.Sh BUGS
162.Tn DEC Ns -standard
163.Xr bad144 8
164bad-block handling should be used.
165.Pp
166.Tn DEC Ns -standard
167error logging should be supported.
168.Pp
169A program to analyze the logged error information (even in its
170present reduced form) is needed.
171