MSCP disk controller
ra* at mscpbus? drive?
ra device provides access to MSCP
disks such as: RC25, RX50, RD51, RD52, RD53, RA60, RA80, and RA81.
- block mode MSCP disk unit u, partition p
- raw mode MSCP disk unit u, partition p
- ra0: don't have a partition table for ...; using (s,t,c)=(X,Y,Z)
- The controller found a drive whose media identifier (e.g. `RA 25') does not have a default partition table. A temporary partition table containing only an `a' partition has been created covering the entire disk, which has the indicated numbers of sectors per track (s), tracks per cylinder (t), and total cylinders (c). Give the pack a label with the disklabel(8) utility.
- ra0: drive will not come on line
- The drive will not come on line, probably because it is spun down. This should be preceded by a message giving details as to why the drive stayed off line.
- uda0: attempt to bring ra0 on line failed: `detail'
- The drive could not be brought on line. The detail message tells why.
- uda0: ra0: unknown type N
- The type index of the named drive is not known to the driver, so the drive will be ignored.
- ra0: changed types! was X now Y
- A drive somehow changed from one kind to another, e.g., from an RA80 to an
RA60. The numbers printed are the encoded media identifiers (see
<vax/mscp.h>for the encoding). The driver believes the new type.
- ra0: uda0, unit N, size = N sectors
- The named drive is on the indicated controller as the given unit, and has that many sectors of user-file area. This is printed during configuration.
- ra0: bad block report: N
- The drive has reported the given block as bad. If there are multiple bad blocks, the drive will report only the first; in this case this message will be followed by `+ others'. Get DEC to forward the block with EVRLK.
- ra0: bad lbn (N)?
- The drive has reported an invalid command error, probably due to an invalid block number. If the lbn value is very much greater than the size reported by the drive, this is the problem. It is probably due to an improperly configured partition table. Other invalid commands indicate a bug in the driver, or hardware trouble.
- ra0: duplicate ONLINE ignored
- The drive has come on-line while already on-line. This condition can probably be ignored (and has been).
- ra0: io done, but no buffer?
- Hardware trouble, or a bug; the drive has finished an I/O request, but the response has an invalid (zero) command reference number.
- ra0: bogus REPLACE end
- The drive has reported finishing a bad sector replacement, but the driver never issues bad sector replacement commands. The report is ignored. This is likely a hardware problem.
- ra0: unknown opcode 0x%x status 0x%x ignored
- The drive has reported something that the driver cannot understand. Perhaps DEC has been inventive, or perhaps your hardware is ill. This is followed by a hex dump of the offending packet.
- ra0%c: hard error %sing fsbn N [of X-Y] (ra0 bn N cn N tn N sn N).
- An unrecoverable error occurred during transfer of the specified filesystem block number(s), which are logical block numbers 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.