Specifications

Note
If the previous warning message appears with non-zero values for the
key fields, it indicates an error on the hard disk at the given block
number.
If you know the name of the file containing the bad block, you can
create a directory in the root directory called /badtracks and move the
offending file to that directory. Use the mv(C) command to move the
file. This prevents any further access to the bad block.
Long Delays Accessing a SCSI Device
If you experience long delays (greater than four seconds) before
accessing a SCSI device, the problem is likely caused by an
interrupt vector conflict. Interrupt vector conflicts are often
reported at boot time. If you see a conflict at boot time, change
the interrupt vector of one of the conflicting boards. For
instructions, see your EISA Series User’s Guide.
Note
You must execute the System Configuration program to reflect any
changes to hardware interrupt vectors.
Under certain circumstances, interrupt vector conflicts are not
reported at boot time. For instance, because of the way in which
information is stored for the Enhanced mode driver, conflicts with
the SCSI adapter card are not detected at boot time. You can verify
a suspected interrupt vector conflict by using the System
Configuration program to check the IRQ for the SCSI adapter card.
Compare this number with the IRQ values for other hardware to
detect any conflicts.
Also, some 8-bit networking cards have a default interrupt vector
setting of IRQ 2, which is automatically reset to IRQ 9. The System
Configuration program does not reflect this automatic change. If
you are using one of these 8-bit networking cards and you
experience long delays when accessing a SCSI device, make sure
that no other hardware has an interrupt vector of IRQ 9. If
another piece of hardware is using an interrupt vector of IRQ 9,
reconfigure it to use a different, unused interrupt vector.
InstaIling Software Drivers for UNIX
7-15