dewey@sequoia.execu.com (Dewey Henize) (06/09/90)
I've got a system that was just repaired and it appears we've managed to clobber something. I sure don't know what it is, but perhaps the wisdom of others could bail me out... We recently replaced the SCSI controller and a disk on a Sun 3/260 running SunOS 4.1. I had previously installed an Exabyte unit as /dev/nrst1 with SCSI id 5 that was used to back it and a couple related machines up. Since the repair, I can't do anything with the Exabyte! Commands like 'mt -f /dev/nrst1 rew' yield the following: si0: siintr: spurious phase si0: resetting scsi bus csr= 0x1407 bcr= 0 tcr= 0x4 cbsr= 0x68 (COMMAND) cdr= 0x2 mr= 0x0 bsr= 0x0 target= 5, lun= 0 DMA addr= 0x0 count= 0 (0) cdb= 0 0 0 0 0 0 last phase= 0x8 (COMMAND) 5 0 last phase= 0x81 (Arbitration) last phase= 0x8c (Cmd complete MSG) 0 last phase= 0xc (STATUS) 0 last phase= 0x4 (DATA IN) 8192 last phase= 0x82 (Identify MSG) 0 0 last phase= 0x8d (Reselect) 0 last phase= 0x8b (Disconnect MSG) 0 At which time the ready light goes off for a while, the disks (2) and the QIC-24 drive go through a reset and it continues to run. I'm sure it's probably something simple, but I don't know what. The SCSI id hasn't changed, nor has the kernel. I've checked the cables so many times I'm thinking of giving them names like pets. Any ideas? I got the data restored across the network from another Exabyte, but this is quite a blow to our backup capabilities right now. Any and all help, and most especially from anyone that's seen this before, would be extremely appreciated. Thanks in advance Dew