your situation is very similar to my SE30 restore. i also replaced UE8 and the rest of the chips in that row. over the course of months i saw my video get progressively worse until i had black “jailhouse” columns AND simasimac. UE8 was the culprit, but i also had a poorly seated ROM simm...
Thanks for the update. I posted some comments on that issue just now. Write cacheing is almost certainly what is going on here. i also just finished recapping my analog board and PSU, so that will add more confidence in the results.
Fixed! It would appear that the edge component inside the PSU that requires the hold down clip and thermal pad was slightly off the pad and conducting 12v to the case. After more careful adjustment, the 12v is isolated from the metal case and everything is now reassembled. With that corrected...
After replacing R19 and deslodering L2, I carefully turned the core all the way back to the middle. I cleaned up the joints with solder wick to soak up old solder and resoldered. After putting it back together somewhat, it’s working! Wow. Another example of sticking to it pays off.
However, I...
Reading some of the symptoms and diagnosis again, I decided to inspect and resolder L2. I noticed my L2 core was almost completely adjusted out of the center. Perhaps this is normal for only the very end of it inside the core. Maybe someone can tell me what their L2 core looks like. Thankfully...
I did a little reading of past forum posts related to the L2 inductor. It seems that most accounts describe a stuck ferrite core, and in at least one example, a crumbled core, once removed, results in a picture that is too wide—the opposite of what I have here. Besides my L2 core is intact and...
Hmm. Reading the notes added by @chillin I guess I missed L2, which is certainly part of the circuit—it is where you can adjust the horizontal size. Is it possible new caps have put this so far out of adjustment that it is compressed into a single vertical line? I wondered that and attempted to...
Thanks for jumping in. . . Yes, I hated to make my bloated post even bigger, but it is a good call about P1. Have completely soaked out the existing solder and replaced with fresh, strong joints. I can trace continuity from the back of the analog board all the way to the yoke when connected...
I am restoring an SE/30 and had a booting logic board and functional display. Work to date includes logic board recap and cleanup, replaced UE8 chip, removed and cleaned and resoldered ASC chip, troubleshooting SCSI—everything with overall successful outcomes. However, I came to the conclusion...
I am starting to think I still have a hardware issue with the SE30 I have been restoring. I know I took voltage measurements before, but this system has been evolving over the past year as I have worked on different parts.
SO, I setup BlueSCSI. It worked fine, but now at shutdown I am getting a...
Had another thought on this, @cheesestraws. When an SE/30 shuts down, it actually doesn’t do a soft power down. It goes to the black-background “RESTART” dialog with power still keeping the HDD etc. alive. I would expect any pending writes to be handled by then, no?
I did a test last night. First, I was easily able to “corrupt” two system 7.5.3 boot disk images by turning off the power while the images were attached. One was the boot drive, another was simply attached. This happens at the “RESTART” screen, to be clear. I am not arbitrarily hitting the power...
I wondered that myself. Tonight, I did an experiment. I detached my 2gig that will no longer boot, attached the RaSCSI 7.5.3 boot image. Let it boot up. Then, re-attached the 2gig and the bootstrap drive. Ran Lido from the bootstrap and did an UPDATE of the disk driver. Shutdown, then detached...
To be fair, used as an external drive, you would be running your own power cable to it, so maybe people are not seeing this happen in those situations—mac turns off but the RaSCSI is still on.
Another observation—even though the Mac cannot boot from the image once this happens, it CAN still mount that image, transfer files from it and so on. It just doesn’t boot from it anymore.
Getting a BlueSCSI in the mean time. The odd part to me is the longstanding risk of SD card corruption without proper pi shutdown is NOT what I am observing. If it were that well-documented issue, I would have a non-bootable Pi. That is not the case here. It is merely corrupting the drive image...
My setup: Mac SE/30, 8mb. RaSCSI setup internally using RPi Zero W, only physical device on SCSI cable. Powered using molex 5v to USB connected to RaSCSI board.
I am curious if others are running into this problem:
Using the November release image on a 16gb SD card, I am successfully booting...