juan@bitnerd (05/14/91)
I have a NeXT cube with an HP 660MB hard disk that was upgraded to a 68040 CPU from the original 68030 CPU. I recently purchased a PLI turbo floppy 2.88, and since I've hooked it up, I've been getting SCSI errors that have caused my hard disk to crash with a LOSS OF DATA. Note that the terminator switch on the PLI drive is set to the on position, and there are no other SCSI devices attached. The PLI drive is set to device 4. In order to verify that the problem is indeed caused by the addition of the PLI floppy, I disconnected the floppy for a period of 4 days and monitored the file: /usr/adm/messages in which SCSI errors are logged. I found no SCSI errors reported for a period of four days. I then reconnected the floppy and found that the errors immediately returned. The following lines were extracted from the /usr/adm/messages file today after reconnecting the PLI floppy. May 13 15:14:24 bitnerd mach: sd0 (1,0): ERROR op:0x2a sd_state:4 scsi status:0x0 May 13 15:14:24 bitnerd mach: sd0 (1,0): sense key:0xb additional sense code:0x47 May 13 15:14:24 bitnerd mach: SCSI Block in error = 0 (front porch) The errors are not that frequent, the seem to occur about once a day, altho not at regular intervals. Note that the problems booting that I mentioned in my earlier posts have been resolved (see summary post entitled: "FIX for problems booting from hard disk when PLI floppy is attached") and should not be a factor in this new problem. Also, in response to my earlier post, I did receive some mail indicating that there may be some problems with the termination switch on the PLI, and that things work better with higher SCSI IDs, but I've not yet gotten a confirmation from PLI on these problems. If your system has experienced the same symptoms, or if you have some information that may help, please reply. When I get resolution on this problem I will post a summary. -- Juan Pineda juan@apple.com -- Juan Pineda
madler@nntp-server.caltech.edu (Mark Adler) (05/14/91)
Looks like the HP 660M vs. PLI floppy problem belongs in the FAQ ... Mark Adler madler@pooh.caltech.edu