BlueSCSI and PiSCSI coexistence issues

[ShadeDream]

Info

• Which version of Pi are you using: 2b
• Which github revision of software: v23.04.01
• Which board version: 2.4a
• Which computer is the PiSCSI connected to: Mac SE, Quadra 700

Describe the issue

Generally when a BlueSCSI (v1 or v2) is connected internally and PiSCSI externally on the same machine I run into issues with behavior of the two together.

Q700 - BlueSCSI v2 + PiSCSI - Bad

Using the two devices together in this configuration and booting from the BlueSCSI results in very slow boot times and corruption of data on the BlueSCSI disk image. This blueSCSI I believe is running the latest firmware (v2023.07.03).

SE - BlueSCSI v1 + PiSCSI - Bad

In this case I was booting from the PiSCSI to install an OS on the BlueSCSI v1 images. The machine boots up fine from the PiSCSI but the BlueSCSI is completely inaccessible and doesn't show up. Running Apple SD HC to see the drives is very slow and only finds the PiSCSI devices. BlueSCSI log file reports it's seeing the images and operating normally. The BlueSCSI v1 is an earlier model and running an older firmware because it requires a programmer to upgrade (which I don't have).

Molar G3 - BlueSCSI v2 + PiSCSI - Fine?

Out of curiosity, I tossed one of the BluSCSI v2s in a gossamer Molar G3 and connected the PiSCSI up. I was booting from my IDE CF card, but I was able to see and interact with both devices in that case for whatever reason.

IIsi - SCSI2SD 5.1 + PiSCSI - Good

No issues in this case, only including to note that I've tested this as well.

Crosslinking the BlueSCSI issue since I'm not sure which device may be the cause: BlueSCSI/BlueSCSI-v2#60

[benjamink]

Performa 475 - External BlueSCSI v1 + Internal PiSCSI - Good

I was able to boot just fine with my Performa with a PiSCSI v2.7 internally (fullsize w/ Raspberry Pi 3B) & a BlueSCSI v1.1 externally. BlueSCSI has the jumpers both on 0 termination DIP switches both set to ON on the PiSCSI.

[erichelgeson]

I'll add to this as I test more machines but this is something I've not come across. My tests are with a 2.4 board and a Pi4 with BlueSCSI v2

• Powerbook 160 - worked fine. PiSCSI external, internal BlueSCSI

[rdmark]

What hasn't worked for me:

• IIsi with BlueSCSI v1.1 internally, and PiSCSI externally
• SE/30 with BlueSCSI v2 internally, and PiSCSI externally

[benjamink]

Testing on my MacSE w/ BlueSCSI v1.1 internally & PiSCSI v2.7 w/ RPi0W externally:

• BlueSCSI term on, PiSCSI term on - fail
• BlueSCSI term off, PiSCSI term on - fail
• BlueSCSI term on, PiSCSI term off - boots from PiSCSI ID0 but no other PiSCSI or BlueSCSI drives visible on desktop (SCSI Tools sees devices on all IDs I'd expect but it won't mount them)

Finally, hooked up USB power to the BlueSCSI & that fixed things. All devices are now showing up on the desktop & I'm also able to boot with either device.

I was also successful when I connected the molex power to the BlueSCSI (instead of USB on the Blue Pill). So it seems the problem is ultimately just lack of sufficient termination power at BOTH ENDS (PiSCSI had it via external USB power but BlueSCSI didn't get enough from the SCSI cable alone).

[uweseimet]

Looks as if a termination issue has been identified as the source of the problem. Can this ticket be closed?