BlueSCSI v2 on SGI Indy fails with error cmd=0x12 Unexpected info phase 20, state 4e on SCSI-2 Mode
#307
Unanswered
Cyanoxygen
asked this question in
Help
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
We have an SGI Indy with R5000 CPU. I connected the BlueSCSI to its internal SCSI bus and fired up the machine. The machine does not pass the power on diagnostics, stating the following errors:
It continued booting despite the error, and
hinvcommand showed the presense of the BlueSCSI drive. However thefxutility was not able to read from or write to the drive with the same error:I found a similar issue in the BlueSCSI (v1?) repository: erichelgeson/BlueSCSI#107, however no followup is being posted.
After some fiddling around the settings, I managed to make it work by disabling SCSI-2 mode:
The SCSI controller used by this Indy (WDC 33C93B) supports SCSI-2 features. The SCSI cable has a terminator at its end, both BlueSCSI and CDROM drive have their termination disabled.
After the workaround everything worked perfectly fine along with a physical CDROM drive.
I didn't find any related information about this workaround, and since the SCSI controller does support SCSI-2 features, is there anything wrong with the BlueSCSI?
Edit: I can provide any help and debugging.
Information Table
HD20_512.hda, 20GBDebug Log
Click to expand/collapse
Beta Was this translation helpful? Give feedback.
All reactions