SE/30 won't boot from internal SCSI

[CaseyAC]

Hi all,
New at posting here but reading the forum has helped me resolve many issues, so hopefully someone will have an idea what could be causing this problem. I'm working on my first SE/30 repair. So far I've recapped the logic board - which restored sound, recapped the analog board - which resolved an issue where the screen would only display a single, bright vertical line, and re-soldered the analog board solder joints - which resolved a screen flickering issue. This SE/30 came with a working original Quantum 40 MB drive, and it booted to that drive just fine up until I tried to replace the ROM. At that point, booting up would get to the "Welcome to Macintosh" screen, then I would get an error that the system file had corrupted. Thinking perhaps the hard drive was on it's way out, I replaced it with a BlueSCSI that I was going to install anyway. With the BlueSCSI installed, I get the flashing "?" icon.

• The replacement ROM is from Garrett's Workshop - a GW4402B - GW4420B Manual.
• Taking the new ROM out and putting back in the original makes no difference, I still get the flashing "?".
• The BlueSCSI log indicates the hard drive image is being found and loaded with no errors.
• If I boot up using Floppy Emu with "Disk Utilities" loaded, I can see, access, test, update and repair the BlueSCSI, but I still get the flashing "?" when I restart.
• I tried to install System 7.5.3 onto the BlueSCSI manually from the disk images using Floppy Emu. The install completes but I still get the flashing "?" when I restart.
• I replaced the BlueSCSI with the original hard drive again and tried to initialize and clean install System 7.1, and I got the error that the system file is corrupt again.

I posted a video to YouTube showing that I can boot up with Disk Utilities and see/access/repair the BlueSCSI drive, but I continue to get the flashing "?":

.
I took some shots of the logic board showing the SCSI controller area:

and
.
This would seem to be some sort of hardware issue, right? To me, the logic board and traces look like they're in good shape, so I really have no idea what's going on.

 

[robin-fo]

This is very strange… Did you already try some „known working“ BlueSCSI image? Is the BlueSCSI terminated? You could also try to set the startup disk and then restart.

The original HD is no longer connected?

 

[CaseyAC]

This is very strange… Did you already try some „known working“ BlueSCSI image? Is the BlueSCSI terminated? You could also try to set the startup disk and then restart.

The original HD is no longer connected?

Hi - thanks for taking a look! I did try a BlueSCSI pre-made image with the same result. The BlueSCSI is terminated but I did not enable the "BACK_FEED" jumper. I should add this is the BlueSCSI v2 desktop. The original HD is not connected - I've only connected one or the other. I'll try to select a startup disk.

 

[killvore]

I'm having a similar issue, so watching this thread with interest! I suspect I may have done a bad job recapping C8-C9-C10
Mine will happily boot from floppy, but does not seem to recognize a known good drive/image (works in my other two SE/30s) so seems to be a SCSI issue.

 

[jmacz]

Where is the bluescsi getting its power from? is it just relying on termination power (ie. via the scsi connection) or do you have it powered using an internal +5V source like a 4pin molex connector?

Just to help rule things out, can you leave the bluescsi connected to the internal scsi connector on the SE/30 but power it using the usb port to an external usb brick (phone charger, etc)? power up the bluescsi first and then turn your se/30 on. See if it boots then. Given you are seeing issues with both the stock and custom ROMs and also with the original working hard disk, I doubt it’s the bluescsi but nonetheless, try this out.

It’s possible the hard disk was on its last legs and is now having issues. But my guess is something went wrong when you swapped the ROM.

Note in my experience, the custom ROM options use newer PCBs that are slightly thinner than the original part Apple used and don’t make good contact with the original ROM socket. This is why multiple vendors provide 3D printed clips to help improve the contact and/or suggest rubber band tricks, etc. I had unexplained IO errors, corruption, crashes, even with these various hacks. I only resolved it by buying a new ROM socket with metal clips that worked perfectly and no longer required any hacks to improve the contact. That could explain the issue with your new custom ROM.

But it’s strange it wouldn’t work even after going back to the original ROM. The original plastic ROM socket clips are brittle, maybe something broke or went wrong there. Or you should probably reflow the solder joints on the ROM socket as perhaps some joints cracked while you were installing the custom ROM.