thanks for the quick responses. as soon as i wrote my help request, i
realized that most, (but unfortunately not all) the errors were on
target 2, lun 0, which is my rz10 disk. this is also the last disk on
the scsi chain. i noticed a couple errors (but only one or two) were
also associated with my tape drive, which is on the other scsi
controller. i will try moving the disk to another position in the
chain to see if it's too long, and to the other scsi controller to see
if the errors follow the same disk. thanks to Pierre Wendling and
Kurt Watkins for your quick responses.
- dave
>From wendling_at_everest.ebc.vbe.dec.com Tue Jan 30 08:59:25 1996
> Hi,
> carter_at_mailhost.lanl.gov said:
> >> ----- UNIT INFORMATION -----
> >> CLASS x0000 DISK
> >> SUBSYSTEM x0000 DISK
> >> BUS # x0001
> >> x0050 LUN x0
> >> TARGET x2
> This part shows you that the faulting device is a disk on SCSI bus
> 1, at target 2, lun 0. From your boot messages, this is your rz10
> disk.
-------------
>From watkins_at_picard.swmed.edu Tue Jan 30 08:48:31 1996
> On Tue, 30 Jan 1996, Dave Carter wrote:
> Sounds vaguely familiar. We had a similar problem with some OpenVMS
> 3000/800's. I'm attaching an exchange between myself and my
> reseller. Since the firmware fix, everything's been happy.
____________________________________________________________________
>Some time ago (maybe about 6 months or so) I talked with you about errors
>we were seeing on our Micropolis 1991 drives attached to an OpenVMS 6.1
>box. As I recall, you suspected a SCSI bus length problem. (We are in
>fact still under 3m I think.) At the time they weren't severe (usually RMS
>read errors) so I never really followed up.
>
>We recently purchased another drive and after watching it for a bit I
>realized it wasn't having the same problem. (It's on the same box, same
>bus, same workload, etc.) This was made more obvious by the increasing
>frequency and severity of the failures on the other disks (where free
>space was becoming increasingly fragmented.) Reinitializing these disks
>and restoring data left us back where we started with tolerable errors.
>
>I can send more details but first I'll ask what the difference is between
>the following drives:
>
> MICROP 1991-27MZ 1020S (3 drives on 2 systems have problems)
> MICROP 1991-27Q4D (the new drive, works nicely)
>
>I'm guessing some type of firmware upgrade or similar is required here.
> Hi Kurt,
> Yep, the only difference that I can see between the 2 types of
> drives is firmware - 'Q4D' is current, the other is older. There's
> a good chance that it's what's causing your problem....
> I can upgrade the firmware of your drives, it only takes a few
> minutes, but they would have to come in here. You won't loose any
> data in process, either. Let me know if you'd like to try this
> (maybe on one of them first?), and what our serial numbers are on
> the units, and I can give you an RMA# and instructions for sending
> them (it) in. Please also include a return address that we can use
> to send them back to you with.
Received on Tue Jan 30 1996 - 17:45:53 NZDT