68kMLA Classic Interface

This is a version of the 68kMLA forums for viewing on your favorite old mac. Visitors on modern platforms may prefer the main site.

Click here to select a new forum.
SE/30 bad SCSI bus?
Posted by: Chuckdubuque on 2024-08-26 04:06:50
Was playing with my SE/30 when I started to get a Sad Mac 0000000F 0000000A. Narrowed it down to my BlueSCSI. If it had a SD card it would go sad Mac. If not I would get the blinking floppy. Tried internal and external BlueSCSI same result.

So it sounds like I have a broken trace or something bad with the SCSI chip? Anything else I should check before tracing it out?
Posted by: Chuckdubuque on 2024-08-26 04:08:22
Was playing with my SE/30 when I started to get a Sad Mac 0000000F 0000000A. Narrowed it down to my BlueSCSI. If it had a SD card it would go sad Mac. If not I would get the blinking floppy. Tried internal and external BlueSCSI same result.

So it sounds like I have a broken trace or something bad with the SCSI chip? Anything else I should check before tracing it out?
Just a quick note, I did recap the board and cleaned cap goo. Did not note any corrosion, but we all know that’s possible.
Posted by: CircuitBored on 2024-08-26 05:51:43
Does the SE/30 operate normally without the BlueSCSI connected?

The BlueSCSI is unfortunately quite incompatible with the SE/30 in my experience. I couldn't get mine to work for love nor money and ended up using a ZuluSCSI instead. The BlueSCSI has certain limiting factors that make it quite unpredictable in some machines.
Posted by: ironborn65 on 2024-08-26 05:55:32
@CircuitBored , can u pls tell which version of BlueSCSI you have been using?
thanks
Posted by: codevonlux on 2024-08-26 06:39:23
How is the HD image in the SD card made? An image with incorrect driver inside will definitely cause this.
Posted by: zigzagjoe on 2024-08-26 06:43:08
May be worth booting from a disk tools floppy just to make sure that comes up OK also.
Posted by: Chuckdubuque on 2024-08-26 07:00:04
It was working with BlueSCSI until it started giving a Sad Mac. If I remove the card from BlueSCSI or remove the BlueSCSI altogether it does boot from ROM Drive, and from Floppy. I will dig up a real-HD sometime tonight, but something bad on the SCSI bus sounds like the culplrit.
Posted by: robin-fo on 2024-08-26 07:09:37
Especially if it‘s an old BlueSCSI, I wouldn‘t trust it. I‘m no longer using mine for similar reasons.
Posted by: Chuckdubuque on 2024-08-26 13:07:36
So, I booted a Snooper rescue disk from a FloppyEMU and ran the SCSI test. Here's what I got IMG_0703.jpg
Posted by: Chuckdubuque on 2024-08-26 13:08:10
Of course there is nothing hooked up to the SCSI bus at the moment.
Posted by: Chuckdubuque on 2024-08-26 13:10:57
Looks like it should say "Empty Address" if it's not populated. So I am still looking at the SCSI chip...
Posted by: Chuckdubuque on 2024-08-26 13:47:01
Ok. So, it worked with the original HD (which I managed to find). So I got to thinking that I have not recapped the PS or the analog board yet, and I have some other goodies (Zigzagjoe's 30 Video GS card and PDS 030 Accelerator card) installed. So I grabbed my molex to floppy power cable and plugged in the BlueSCSI and viola. It seems the BlueSCSI is not quite getting enough power without the extra juice and is messing up the SCSI. Snooper reports normal. Problem solved.

Now I have to add power supply and analog board to my priority list.
Posted by: ironborn65 on 2024-08-26 15:22:41
never trust the termination power, if you can hook an external PS the better ....
1