eps@toaster.SFSU.EDU (Eric P. Scott) (12/14/89)
Scenario: User has floptical initialized and written on another 1.0 system; when inserted into our machines it spins up, then a few seconds later spins down, and the cycle continues for several minutes. Events are frozen while the drive is spinning up or down, and system performance drops to near-zero. There may be a problem with this disk since it exhibits the same behavior on four machines here; yet he claims it has no problems on the machine it was written on. A "known good" disk subsequently inserted into the machine does the same thing, but this time produces console messages: od0a: read re-spin (invalid or unimplemented command) block 8 phys block 264 (4165:0:8) (repeated three times) od0a: read failed (invalid or unimplemented command) block 8 phys block 264 (4165:0:8) od0?: write re-spin (invalid or unimplemented command) block 0 phys block 0 (4149:0:0) mount: /dev/od0a on /mnt: Device busy mount: giving up on: /mnt % od0?: write re-spin (invalid or unimplemented command) ... (repeated twice) od0?: write failed ... od0?: write re-spin (invalid or unimplemented command) block 246880 phys block 246880 (19579:0:0) (repeated three times) od0?: write failed ... I was able to eject the disk using disk -e The same user had similar problems with disks he wrote under 0.981. Could there be something "different" about the OD on his cube? It's not one of the early ones. -=EPS=-