1.\" $NetBSD: up.4,v 1.4 1997/10/19 13:02:35 mrg 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. All advertising materials mentioning features or use of this software 15.\" must display the following acknowledgement: 16.\" This product includes software developed by the University of 17.\" California, Berkeley and its contributors. 18.\" 4. Neither the name of the University nor the names of its contributors 19.\" may be used to endorse or promote products derived from this software 20.\" without specific prior written permission. 21.\" 22.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND 23.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE 24.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE 25.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE 26.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL 27.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 28.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 29.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 30.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 31.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 32.\" SUCH DAMAGE. 33.\" 34.\" from: @(#)up.4 8.1 (Berkeley) 6/5/93 35.\" 36.Dd June 5, 1993 37.Dt UP 4 vax 38.Os BSD 4 39.Sh NAME 40.Nm up 41.Nd unibus storage module controller/drives 42.Sh SYNOPSIS 43.Cd "controller sc0 at uba? csr 0176700 vector upintr 44.Cd "disk up0 at sc0 drive 0" 45.Sh DESCRIPTION 46This is a generic 47.Tn UNIBUS 48storage module disk driver. 49It is specifically designed to work with the 50Emulex 51.Tn SC-21 52and 53.Tn SC-31 54controllers. 55It can be easily 56adapted to other controllers (although bootstrapping will 57not necessarily be directly possible.) 58.Pp 59The script 60.Xr MAKEDEV 8 61should be used to create the 62.Nm up 63special files; consult 64.Xr mknod 8 65if a special file needs to be made manually. 66It is recommended as a security precaution to not create special files 67for devices which may never be installed. 68.Sh DISK SUPPORT 69The driver interrogates the controller's holding register 70to determine the type of drive attached. The driver recognizes 71seven different drives: 72.Tn CDC 739762, 74.Tn CDC 759766, 76.Tn AMPEX DM Ns 980 , 77.Tn AMPEX 789300, 79.Tn AMPEX 80Capricorn, 81.Tn FUJITSU 82160, and 83.Tn FUJITSU 84Eagle 85(the Eagle is not supported by the SC-21). 86.Pp 87Special file names begin with 88.Sq Li up 89and 90.Sq Li rup 91for the block and character files respectively. The second 92component of the name, a drive unit number in the range of zero to 93seven, is represented by a 94.Sq Li ? 95in the disk layouts below. The last component of the name, the 96file system partition, is 97designated by a letter from 98.Sq Li a 99to 100.Sq Li h 101which also corresponds to a minor device number set: zero to seven, 102eight to 15, 16 to 23 and so forth for drive zero, drive two and drive 103three respectively (see 104.Xr physio 4 ) . 105The location and size (in 512 byte sectors) of the 106partitions for the above drives: 107.Bl -column header diskx undefined length 108.Tn CDC No 9762 partitions 109.Sy disk start length cyls 110 hp?a 0 15884 0-99 111 hp?b 16000 33440 100-309 112 hp?c 0 131680 0-822 113 hp?d 49600 15884 309-408 114 hp?e 65440 55936 409-758 115 hp?f 121440 10080 759-822 116 hp?g 49600 82080 309-822 117 118.Tn CDC No 9766 300M drive partitions: 119.Sy disk start length cyl 120 up?a 0 15884 0-26 121 up?b 16416 33440 27-81 122 up?c 0 500384 0-822 123 up?d 341696 15884 562-588 124 up?e 358112 55936 589-680 125 up?f 414048 861760 681-822 126 up?g 341696 158528 562-822 127 up?h 49856 291346 82-561 128 129.Tn AMPEX DM Ns No 980 partitions 130.Sy disk start length cyls 131 hp?a 0 15884 0-99 132 hp?b 16000 33440 100-309 133 hp?c 0 131680 0-822 134 hp?d 49600 15884 309-408 135 hp?e 65440 55936 409-758 136 hp?f 121440 10080 759-822 137 hp?g 49600 82080 309-822 138 139.Tn AMPEX No 9300 300M drive partitions: 140.Sy disk start length cyl 141 up?a 0 15884 0-26 142 up?b 16416 33440 27-81 143 up?c 0 495520 0-814 144 up?d 341696 15884 562-588 145 up?e 358112 55936 589-680 146 up?f 414048 81312 681-814 147 up?g 341696 153664 562-814 148 up?h 49856 291346 82-561 149 150.Tn AMPEX No Capricorn 330M drive partitions: 151.Sy disk start length cyl 152 hp?a 0 15884 0-31 153 hp?b 16384 33440 32-97 154 hp?c 0 524288 0-1023 155 hp?d 342016 15884 668-699 156 hp?e 358400 55936 700-809 157 hp?f 414720 109408 810-1023 158 hp?g 342016 182112 668-1023 159 hp?h 50176 291346 98-667 160 161.Tn FUJITSU No 160M drive partitions: 162.Sy disk start length cyl 163 up?a 0 15884 0-49 164 up?b 16000 33440 50-154 165 up?c 0 263360 0-822 166 up?d 49600 15884 155-204 167 up?e 65600 55936 205-379 168 up?f 121600 141600 380-822 169 up?g 49600 213600 155-822 170 171.Tn FUJITSU No Eagle partitions 172.Sy disk start length cyls 173 hp?a 0 15884 0-16 174 hp?b 16320 66880 17-86 175 hp?c 0 808320 0-841 176 hp?d 375360 15884 391-407 177 hp?e 391680 55936 408-727 178 hp?f 698880 109248 728-841 179 hp?g 375360 432768 391-841 180 hp?h 83520 291346 87-390 181.El 182.Pp 183The up?a partition is normally used for the root file system, 184the up?b partition as a paging area, 185and the up?c partition for pack-pack copying (it maps the entire disk). 186On 160M drives the up?g partition maps the rest of the pack. 187On other drives both up?g and up?h are used to map the 188remaining cylinders. 189.Sh FILES 190.Bl -tag -width Pa -compact 191.It Pa /dev/up[0-7][a-h] 192block files 193.It Pa /dev/rup[0-7][a-h] 194raw files 195.El 196.Sh DIAGNOSTICS 197.Bl -diag 198.It "up%d%c: hard error %sing fsbn %d[-%d] cs2=%b er1=%b er2=%b." 199An unrecoverable error occurred during transfer of the specified 200filesystem block number(s), 201which are logical block numbers on the indicated partition. 202The contents of the cs2, er1 and er2 registers are printed 203in octal and symbolically with bits decoded. 204The error was either unrecoverable, or a large number of retry attempts 205(including offset positioning and drive recalibration) could not 206recover the error. 207.Pp 208.It "up%d: write locked." 209The write protect switch was set on the drive 210when a write was attempted. The write operation is not recoverable. 211.Pp 212.It "up%d: not ready." 213The drive was spun down or off line when it was 214accessed. The i/o operation is not recoverable. 215.Pp 216.It "up%d: not ready (flakey)." 217The drive was not ready, but after 218printing the message about being not ready (which takes a fraction 219of a second) was ready. The operation is recovered if no further 220errors occur. 221.Pp 222.It "up%d%c: soft ecc reading fsbn %d[-%d]." 223A recoverable ECC error occurred on the 224specified sector of the specified disk partition. 225This happens normally 226a few times a week. If it happens more frequently than 227this the sectors where the errors are occurring should be checked to see 228if certain cylinders on the pack, spots on the carriage of the drive 229or heads are indicated. 230.Pp 231.It "sc%d: lost interrupt." 232A timer watching the controller detecting 233no interrupt for an extended period while an operation was outstanding. 234This indicates a hardware or software failure. There is currently a 235hardware/software problem with spinning down drives while they are 236being accessed which causes this error to occur. 237The error causes a 238.Tn UNIBUS 239reset, and retry of the pending operations. 240If the controller continues to lose interrupts, this error will recur 241a few seconds later. 242.El 243.Sh SEE ALSO 244.Xr hk 4 , 245.Xr hp 4 , 246.Xr uda 4 247.Sh HISTORY 248The 249.Nm up 250driver appeared in 251.Bx 4.0 . 252.Sh BUGS 253.Pp 254A program to analyze the logged error information (even in its 255present reduced form) is needed. 256.Pp 257The partition tables for the file systems should be read off of each 258pack, as they are never quite what any single installation would prefer, 259and this would make packs more portable. 260