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