• Updated 2023-07-12: Hello, Guest! Welcome back, and be sure to check out this follow-up post about our outage a week or so ago.

SCSI Voodoo and an error code, too

MrFahrenheit

Well-known member
That's a lot of things to change, so I wonder which one 'fixed' it?

I believe something with the logic board and/or RAM corrupted the hard drive.

I did try the 128MB EDO in the replaced board, and I started getting some glitches happening (Finder complaining about running out of memory, when nothing was running).

So, I think it was a combination of the logic board corrupted the disk driver on the drive, together with a corrupt OS (due to disk read/write corruption), and Mac OS 8.1 not having enough RAM for what I was trying to do.

I started with Steps 1-4 above one at a time, until the issues were resolved. The 1-4 are the order I went through, while testing in-between.
 

MrFahrenheit

Well-known member
After a successful afternoon of copying files over the disks that were causing issues before, I think I can confirm I fixed the issue.

Just to see I shut it down and installed the same 128MB EDO SIMM I had before and it seems to be working just fine now.

So the issue is something to do with the prior logic board. Either it’s bad or the overclock is causing it to be unstable when copying between external and internal SCSI disks.

I’ll try and troubleshoot more later. I have a few OC’d 475 boards I can stress test later on.
 

Attachments

  • 57579D8F-9A81-4A25-B5C3-2CC96B278CD3.jpeg
    57579D8F-9A81-4A25-B5C3-2CC96B278CD3.jpeg
    7.5 MB · Views: 1
  • 6CB486AA-4605-4BE8-BBE0-B604529A5686.jpeg
    6CB486AA-4605-4BE8-BBE0-B604529A5686.jpeg
    6.2 MB · Views: 1

jeremywork

Well-known member
They come up on eBay now and again. They give you an indication as to what is actually happening on the SCSI bus. I haven't used mine yet but that's my understanding.

View attachment 52996
I have a couple like this (but passthrough.) Mine are branded 'SCSI Rx' and 'AST-ST Plugged-In.'
They're only good for "there is scsi" and "there isn't scsi".
Typically yes, but I find them very useful to identify the normal probing patterns of a healthy SCSI chain and work out what's going wrong. When working with (basically undocumented) PDS SCSI cards I could see device activity lights coincide with the visual sequence of probing each ID. In my experience with those when it hardly pauses a device has responded, a quarter-second delay is normal for no device on an ID, and a long delay is helpful in indicating that the probe has found a device on an ID which failed to respond properly (termination failure, ID conflict, etc.)

Edit: also useful to see when the system has locked up due to a hung SCSI device on the bus. In these cases a power-down can be required instead of a soft-reboot.
(but yeah beyond this, essentially just blinkenlights...)
 
Last edited:
Top