terry@spcvxb.spc.edu (Terry Kennedy, Operations Mgr) (11/09/90)
In article <JTKOHL.90Nov9083139@quicksilver.MIT.EDU>, jtkohl@MIT.EDU (John T Kohl) writes: > Two days ago I hooked up an external SCSI TK50 drive, at SCSI #5. After > doing so, my root partition was immediately trashed. Removing the tape > drive allowed me to reconstruct the partition; I then put the tape drive > back on the system, and the drive was trashed again. I read somewhere (possibly in the V5.4 release notes) that the SCSI TK50 is _different_ for an MV2000 vs. a 3100, and that customers wanting to use such a drive on a 3100 should contact Field Service. It also mentioned that the change makes it incompatible with the 2000. I don't know any more de- tails than that, as I don't have any of that hardware. Terry Kennedy Operations Manager, Academic Computing terry@spcvxa.bitnet St. Peter's College, US terry@spcvxa.spc.edu (201) 915-9381
jtkohl@MIT.EDU (John T Kohl) (11/10/90)
I have a DS3100 on my desk, with the following normal configuration: Ultrix/RISC 3.1 16M memory SCSI #0: external RZ55 SCSI #3: internal RZ23 (root partition) SCSI #4: external RZ55 Two days ago I hooked up an external SCSI TK50 drive, at SCSI #5. After doing so, my root partition was immediately trashed. Removing the tape drive allowed me to reconstruct the partition; I then put the tape drive back on the system, and the drive was trashed again. This is with the "new" roms (i.e. the ones that don't give you the full text description of the test command & arguments). One co-worker here reports similar problems with an Exabyte drive interfering with his internal RZ23, and that when he accessed said RZ23, the Exabyte would occasionally make noises as if it were being accessed. Anybody else heard of such a problem/know a solution? -- John Kohl <jtkohl@ATHENA.MIT.EDU> or <jtkohl@MIT.EDU> Digital Equipment Corporation/Project Athena (The above opinions are MINE. Don't put my words in somebody else's mouth!)
alan@shodha.enet.dec.com ( Alan's Home for Wayward Notes File.) (11/10/90)
In article <JTKOHL.90Nov9083139@quicksilver.MIT.EDU>, jtkohl@MIT.EDU (John T Kohl) writes: > I have a DS3100 on my desk, with the following normal configuration: > Ultrix/RISC 3.1 > 16M memory > SCSI #0: external RZ55 > SCSI #3: internal RZ23 (root partition) > SCSI #4: external RZ55 > > Two days ago I hooked up an external SCSI TK50 drive, at SCSI #5. After > doing so, my root partition was immediately trashed. Removing the tape > drive allowed me to reconstruct the partition; I then put the tape drive > back on the system, and the drive was trashed again. I had this problem a long time ago. It turned out it was broken SCSI electronics in the TK50. I got the TK50 and haven't had a problem since. Check the error log to see if any hardware errors are getting logged. I tended to get SCSI parity errors. > > One co-worker here reports similar problems with an Exabyte drive > interfering with his internal RZ23, and that when he accessed said > RZ23, the Exabyte would occasionally make noises as if it were being > accessed. Trouble shooting this sort of thing is easy. Back up everything to wherever you can (network for example). Then use the disk exerciser in /usr/field to put a load on the system. You can run it readonly if you don't have any partitions to scribble on. Depending where you start add or remove devices to/from the bus until you find the one that causes the other to die. That is probably the broken one. up > > Anybody else heard of such a problem/know a solution? Yup. > -- > John Kohl <jtkohl@ATHENA.MIT.EDU> or <jtkohl@MIT.EDU> > Digital Equipment Corporation/Project Athena -- Alan Rollow alan@nabeth.enet.dec.com
avolio@decuac.DEC.COM (Frederick M. Avolio) (11/10/90)
Ihad a similar problem. We actually traced it to a bad RZ23. Field Service replaced just about everything except the skin on my box... We still never found out what the real problem was but replacing the RZ23 with a working one (no noise, etc) seemed to fix things... Fred