SCSI2SD Issues

[maceffects]

Okay, good. And, to confirm, both of these ribbon cables are _known working_? They are known to work with normal hard drives?

Yes, they both work with standard spinning disk hard drives.  I just updated the firmware and repeated the testing and still have the same result.  It can't find the drive.

@jessenator thanks!  Thanks nearly exactly what I have.  The only difference I can tell would be that I wrote 1.99 since I wasn't sure if the 2gb cap meant to have less size.  I just tried with 2gb and the same result I'm afraid. 

 

[jessenator]

well b*gger  

 

[aperezbios]

Can you record a video of your SCSI2SD, while you attempt to poll for it from Lido? what is your SCSI2SD mounted on, or sitting on?

 

[maceffects]

@aperezbios the SCSI2SD is mounted on a 3d printed bracket I bought designed for the SCSI2SD.  Unfortunately, all the playing with the floppy disk with Lido on it, now the disk isn't working.  But I did run TattleTech (which at least shows it), SCSI Probe which shows but fails to mount, and Apples updated hard drive application which fails to recognize it.  Videos of those 3 linked below:

https://youtu.be/RwPvJh_lOQE

https://youtu.be/g43B6SBvxW8

https://youtu.be/SwaLT-BXgfw

 

[aperezbios]

When I said "video of your SCSI2SD" I meant _of the SCSI2SD_ not of your Mac/monitor. Apparently I wasn't clear enough. The fact that SCSIProbe sees the device means it's working, and you've got a configuration error of some sort.

 

[aperezbios]

In the SCSIProbe screenshot you provided, the "product" string appears empty. This needs to be set to something, and the default string is SCSI2SD. I suspect this may be the issue. Please double check your configuration has something set in the product string. Frankly, I am not convinced you're saving your configuration to the board properly. Simply changing the values in SCSI2SD, without also subsequently saving the configuration to the board, via "File.. Save to device", is insufficient to commit the changes to the board. If you were truly using the values from the XML file  I attached, as claimed,  you would see that string in SCSIProbe

 

[maceffects]

The only thing the SCSI2SD will do during the SCSI Probe or Lido is one faint illumination of the LED.  Nothing else of any diagnostic value.  I'm certain it is saved properly.  I can record that if needed to prove.  However, for now I'm going to take a break for messing with it.  I'll try more things tomorrow and put it under a scope to see if there are any board defects. 

 

[LaPorta]

I know such things sound absurd, but have you tried something ridiculous, like attaching it to the external SCSI port while running off the internal drive? Making it something other than ID 0? I know none of these suggestions make logical sense, but sometimes I've had to do ridiculous crap (attach multiple drives, supplying power via USB or molex, etc). just to get the damn thing working before I place it inside on it's own. Don't ask me, it must be gremlins. When intuitive solutions don't work, I try crazy things. I also have had success formatting/partitioning the SD card up front with OS X 10.4, for example, and leaving the tail end of the SD card as "free space", then setting the total number of GB on the SCSI2SD config drive size as larger than the real partitions, leading it into the free space (so I don't accidentally tell it to end in the middle of a partition).

Sorry if any of this sounds nuts; I've just had prior success.

 

[dochilli]

Did you ever read the setting from the SCSI2SD? If they where saved right, then you should see the settings as you set it. Perhaps the saving of the settings did not work.

 

[pcamen]

Blaming SCSI2SD for "issues" when _you_ have configured termination on your SCSI bus incorrectly is absurd. You have to have termination configured properly, regardless of the type/manufacturer of SCSI devices you choose to use.  SCSI termination is _simple_ You must have termination at the END(s) of your SCSI chains, period. Not in the middle, not double-terminated. If you do anything but that, you can and SHOULD expect problems, as it's electrically incorrect, per the SCSI specification.

I DID have things terminated correctly.  One was on the internal SCSI cable and had termination on and the other was through a SCSI cable attached to the external port, also with termination enabled.  But in this configuration I had issues.  With a power source applied to the external one they would not work reliably and one of the SCSI utilities complained that there was a termination issue.  Take the power off the external one and the problem goes away.

 

[aperezbios]

The only thing the SCSI2SD will do during the SCSI Probe or Lido is one faint illumination of the LED.  Nothing else of any diagnostic value.  I'm certain it is saved properly.  I can record that if needed to prove.  However, for now I'm going to take a break for messing with it.  I'll try more things tomorrow and put it under a scope to see if there are any board defects. 

Yes, we should verify this is correct. All you need to do is attach your scsi2sd, read the config with File...read from device, then SAVE THE XML FILE (screenshots are insufficient, as if there is corrupted string data, it may not be displayed properly by the GUI), and share that here.