[comp.sys.next] is my optical drive crapping out?

pbiron@weber.ucsd.edu (Paul Biron) (03/25/91)

For the past few days I've been getting these error messages, often
resulting the need to reboot (and even a few times pulling the plug!!).

This is on an '030 cube running 2.0:

Mar 24 14:23:51 garp mach: od0a: write failed (busy timeout #1) block 63512 phys
 block 64408 (8174:0:8)
Mar 24 14:23:51 garp mach: od0a: write re-spin (invalid or unimplemented command
) block 63608 phys block 65042 (8214:0:2)

Mar 24 15:02:39 garp mach: od0a: read recover (ECC) block 229216 phys block 2317
94 (18636:0:2)
Mar 24 15:02:41 garp last message repeated 15 times
Mar 24 15:02:41 garp mach: od0a: read failed (ECC) block 229216 phys block 23179
4 (18636:0:2)
Mar 24 16:10:47 garp mach: od0a: read failed (busy timeout #1) block 123080 phys
 block 124584 (11935:0:8)
Mar 24 16:10:47 garp mach: od0?: read failed (busy timeout #1) block 32 phys blo
ck -66384 (0:0:0)
Mar 24 16:10:55 garp mach: od0a: read failed (invalid or unimplemented command)
block 0 phys block -66384 (0:0:0)

The block reported is not always the same.

At first I thought it may be the disk itself, so I ran with another
optical disk for a while and the same kind of messages.

Can anyone tell me what is wrong?  Is the drive itself crapping out?

Please respond to the net or to garp!pbiron@keynes.ucsd.edu.

-- 
Paul Biron      pbiron@ucsd.edu        (619) 534-5758
Central University Library, Mail Code C-075-R
Social Sciences DataBase Project
University of California, San Diego, La Jolla, Ca. 92093