1.\" Copyright (c) 1991, 1993, 19801988 2.\" The Regents of the University of California. All rights reserved. 3.\" 4.\" %sccs.include.redist.man% 5.\" 6.\" @(#)up.4 8.1 (Berkeley) 06/05/93 7.\" 8.Dd 9.Dt UP 4 vax 10.Os BSD 4 11.Sh NAME 12.Nm up 13.Nd unibus storage module controller/drives 14.Sh SYNOPSIS 15.Cd "controller sc0 at uba? csr 0176700 vector upintr 16.Cd "disk up0 at sc0 drive 0" 17.Sh DESCRIPTION 18This is a generic 19.Tn UNIBUS 20storage module disk driver. 21It is specifically designed to work with the 22Emulex 23.Tn SC-21 24and 25.Tn SC-31 26controllers. 27It can be easily 28adapted to other controllers (although bootstrapping will 29not necessarily be directly possible.) 30.Pp 31The script 32.Xr MAKEDEV 8 33should be used to create the 34.Nm up 35special files; consult 36.Xr mknod 8 37if a special file needs to be made manually. 38It is recommended as a security precaution to not create special files 39for devices which may never be installed. 40.Sh DISK SUPPORT 41The driver interrogates the controller's holding register 42to determine the type of drive attached. The driver recognizes 43seven different drives: 44.Tn CDC 459762, 46.Tn CDC 479766, 48.Tn AMPEX DM Ns 980 , 49.Tn AMPEX 509300, 51.Tn AMPEX 52Capricorn, 53.Tn FUJITSU 54160, and 55.Tn FUJITSU 56Eagle 57(the Eagle is not supported by the SC-21). 58.Pp 59Special file names begin with 60.Sq Li up 61and 62.Sq Li rup 63for the block and character files respectively. The second 64component of the name, a drive unit number in the range of zero to 65seven, is represented by a 66.Sq Li ? 67in the disk layouts below. The last component of the name, the 68file system partition, is 69designated by a letter from 70.Sq Li a 71to 72.Sq Li h 73which also corresponds to a minor device number set: zero to seven, 74eight to 15, 16 to 23 and so forth for drive zero, drive two and drive 75three respectively (see 76.Xr physio 4 ) . 77The location and size (in 512 byte sectors) of the 78partitions for the above drives: 79.Bl -column header diskx undefined length 80.Tn CDC No 9762 partitions 81.Sy disk start length cyls 82 hp?a 0 15884 0-99 83 hp?b 16000 33440 100-309 84 hp?c 0 131680 0-822 85 hp?d 49600 15884 309-408 86 hp?e 65440 55936 409-758 87 hp?f 121440 10080 759-822 88 hp?g 49600 82080 309-822 89 90.Tn CDC No 9766 300M drive partitions: 91.Sy disk start length cyl 92 up?a 0 15884 0-26 93 up?b 16416 33440 27-81 94 up?c 0 500384 0-822 95 up?d 341696 15884 562-588 96 up?e 358112 55936 589-680 97 up?f 414048 861760 681-822 98 up?g 341696 158528 562-822 99 up?h 49856 291346 82-561 100 101.Tn AMPEX DM Ns No 980 partitions 102.Sy disk start length cyls 103 hp?a 0 15884 0-99 104 hp?b 16000 33440 100-309 105 hp?c 0 131680 0-822 106 hp?d 49600 15884 309-408 107 hp?e 65440 55936 409-758 108 hp?f 121440 10080 759-822 109 hp?g 49600 82080 309-822 110 111.Tn AMPEX No 9300 300M drive partitions: 112.Sy disk start length cyl 113 up?a 0 15884 0-26 114 up?b 16416 33440 27-81 115 up?c 0 495520 0-814 116 up?d 341696 15884 562-588 117 up?e 358112 55936 589-680 118 up?f 414048 81312 681-814 119 up?g 341696 153664 562-814 120 up?h 49856 291346 82-561 121 122.Tn AMPEX No Capricorn 330M drive partitions: 123.Sy disk start length cyl 124 hp?a 0 15884 0-31 125 hp?b 16384 33440 32-97 126 hp?c 0 524288 0-1023 127 hp?d 342016 15884 668-699 128 hp?e 358400 55936 700-809 129 hp?f 414720 109408 810-1023 130 hp?g 342016 182112 668-1023 131 hp?h 50176 291346 98-667 132 133.Tn FUJITSU No 160M drive partitions: 134.Sy disk start length cyl 135 up?a 0 15884 0-49 136 up?b 16000 33440 50-154 137 up?c 0 263360 0-822 138 up?d 49600 15884 155-204 139 up?e 65600 55936 205-379 140 up?f 121600 141600 380-822 141 up?g 49600 213600 155-822 142 143.Tn FUJITSU No Eagle partitions 144.Sy disk start length cyls 145 hp?a 0 15884 0-16 146 hp?b 16320 66880 17-86 147 hp?c 0 808320 0-841 148 hp?d 375360 15884 391-407 149 hp?e 391680 55936 408-727 150 hp?f 698880 109248 728-841 151 hp?g 375360 432768 391-841 152 hp?h 83520 291346 87-390 153.El 154.Pp 155The up?a partition is normally used for the root file system, 156the up?b partition as a paging area, 157and the up?c partition for pack-pack copying (it maps the entire disk). 158On 160M drives the up?g partition maps the rest of the pack. 159On other drives both up?g and up?h are used to map the 160remaining cylinders. 161.Sh FILES 162.Bl -tag -width Pa -compact 163.It Pa /dev/up[0-7][a-h] 164block files 165.It Pa /dev/rup[0-7][a-h] 166raw files 167.El 168.Sh DIAGNOSTICS 169.Bl -diag 170.It "up%d%c: hard error %sing fsbn %d[-%d] cs2=%b er1=%b er2=%b." 171An unrecoverable error occurred during transfer of the specified 172filesystem block number(s), 173which are logical block numbers on the indicated partition. 174The contents of the cs2, er1 and er2 registers are printed 175in octal and symbolically with bits decoded. 176The error was either unrecoverable, or a large number of retry attempts 177(including offset positioning and drive recalibration) could not 178recover the error. 179.Pp 180.It "up%d: write locked." 181The write protect switch was set on the drive 182when a write was attempted. The write operation is not recoverable. 183.Pp 184.It "up%d: not ready." 185The drive was spun down or off line when it was 186accessed. The i/o operation is not recoverable. 187.Pp 188.It "up%d: not ready (flakey)." 189The drive was not ready, but after 190printing the message about being not ready (which takes a fraction 191of a second) was ready. The operation is recovered if no further 192errors occur. 193.Pp 194.It "up%d%c: soft ecc reading fsbn %d[-%d]." 195A recoverable ECC error occurred on the 196specified sector of the specified disk partition. 197This happens normally 198a few times a week. If it happens more frequently than 199this the sectors where the errors are occurring should be checked to see 200if certain cylinders on the pack, spots on the carriage of the drive 201or heads are indicated. 202.Pp 203.It "sc%d: lost interrupt." 204A timer watching the controller detecting 205no interrupt for an extended period while an operation was outstanding. 206This indicates a hardware or software failure. There is currently a 207hardware/software problem with spinning down drives while they are 208being accessed which causes this error to occur. 209The error causes a 210.Tn UNIBUS 211reset, and retry of the pending operations. 212If the controller continues to lose interrupts, this error will recur 213a few seconds later. 214.El 215.Sh SEE ALSO 216.Xr hk 4 , 217.Xr hp 4 , 218.Xr uda 4 219.Sh HISTORY 220The 221.Nm up 222driver appeared in 223.Bx 4.0 . 224.Sh BUGS 225.Pp 226A program to analyze the logged error information (even in its 227present reduced form) is needed. 228.Pp 229The partition tables for the file systems should be read off of each 230pack, as they are never quite what any single installation would prefer, 231and this would make packs more portable. 232