BlueSCSI and PiSCSI coexistence issues
Closed this issue · 1 comments
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.
PiSCSI Info for reference
- 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
Crosslinking the PiSCSI issue since I'm not sure which device is the cause: PiSCSI/piscsi#1202
Closing as piscsi ticket has the resolution (termination issue)