It won't work if the SE/30 booted from a floppy before. But my HD is a bit peculiar as I said in many posts now. Getting your internal HD out and SCSI2SD in is indeed a good idea. I don't have to worry about all that termination nonsense. The 5.0a version is the latest version of the scsi2sd, and it is self terminated. The HD20SC is my ONLY SCSI device as of now. Took a few tries but finally got there! (What's the problem with firmware 5.0?) HDD into the ext drive 80SC as ID1 and put the SD card in the SE/30 as default ID0, with some success)įrom your comments I lean towards SCSI ID or termination issues - note that I even managed to boot my SD drive once when it was in the ext drive which was turned off! Seems enough power came down the SCSI cable to power the SCSI2SD HDD! Hence even though it's 'off' it still gets enough power to report back a clashing ID 0 no! finally, I might have also tried swapping the SE/30 int. lastly, swapped a few SCSI cables around in case it was the problem, though I think no difference. check the Iomega drive switch (sets ID to 5 or 4(?)) if using one, to be sure the switch is properly engaged - check them all! I think I changed my SD to ID 4 or 2 or something, and that helped too for some reason (Iomega is ID5, SC CD was ID3 etc)
Found I had to re-jig the order of my SCSI daisy chaining (ie SE/30 to Iomega to SC CD, to the 80SC w SD drive and THEN a terminator plug (seemed to me that sometimes the order matters - go figure!) check the SCSI2SD utility logging/messages when setting up the SD drive: I recall a few checksum errors the first few times I set up the SD card over micro USB on my Mac, even though it seemed to complete! (Ie your SD may still be set to ID0 and thus, finding 2 x ID0 drives and thus the flashing ?s!)
I had similar issues when I did what you did (though with an earlier version of the SCSI2SD) - ie putting the SCSI2SD into an ext 80SC drive to copy the SE/30 internal HDD data over (after doing a firmware update and resetting it's ID no) Sorry for the inconvenience but maybe someone in the future will have the same problem as me. Do you think I did something wrong when setting the SCSI2SD up? Now, I know a lot of people come here with their problems which could be easily solved with the search tool of the website, but I couldn't find anything to help me with this problem. It did the same when power was off on the HD20SC but the cable still plugged to my SE/30. I initially thought the internal HD was dead. When I tried to plug the "improved" HD20SC on my machine, it gave me a blinking question mark. It gives 5V to the SCSI2SD and it is connected to the SCSI ribbon which in turn is connected to the back of the HD20SC.
So I need to have both the internal HD and the SCSI2SD connected to the machine, hence my decision to change SCSI ID to 1 for the SCSI2SD. Now, I wanted to make a backup of the hard drive in my SE/30. I only changed the SCSI ID to 1 in the "Device 1" tab, and SCSI Target is not enabled on the other devices.īy the way, my board has got those two terminators on it. When Windows finally gave up on the drivers, it worked again so I was able to install version 4.6 of the firmware. It crashed the util every time the board was connected. I had a problem with the firmware, but after much trouble, I fixed the problem which was bloody windows trying to get a driver online. Finally managed to get some time to test those v5.0a boards.