| Title: | VAX and Alpha VMS |
| Notice: | This is a new VMSnotes, please read note 2.1 |
| Moderator: | VAXAXP::BERNARDO |
| Created: | Wed Jan 22 1997 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 703 |
| Total number of notes: | 3722 |
Customer is running 3.2 kernel software on an Infoserver 150 and VAX 6.0.
Intermittently the customer is experiencing device timeouts on a cd services
offered by the infoserver. The strange thing about it is its always the same
reader that is having the problem. There are seven readers in the cabinet.
She has replaced this device with two other readers and the same problems
occur. Customer has already had HW (outside vendor) check out the
configuration. Apparently they say nothing is wrong.
I still believe there is a HW problem. The customer is unable to get this
device back at all. It goes into mount verification and then eventually
times out. There is no consistency in the time the device takes to do this.
Could this be an exhausted resource? Why are none of the other readers
failing if this was the case? Any and all help would be appreciated here.
I could not really find anything in STARs that pointed to a problem like
this or a recommended patch.
Thanks,
Susan M. Wahl
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 175.1 | UTRTSC::utoras-198-48-93.uto.dec.com::JurVanDerBurg | Change mode to Panic! | Wed Feb 12 1997 01:19 | 8 | |
Could it possible that the infoserver suffers from priority lockouts? What is the scsi id of the failing device? If a device with unit 0 tries to get the bus, but all other devices are active as well it may not get a chance in time to get to the bus. This is not so likely with only cd's on the bus, but it may be a start. Jur. | |||||