Dear Experts,
I'm
very new to the SGI and IRIX Universe, but I did look at the FAQs and did quite a bit of Googling before posting this. However, if I still sound like a newbie, please forgive me for that.
The long story short, I got a
SGI Fuel system (IP35) with 700 MHz R16000 CPU, ODYSSEY Graphic board and a Seagate ST373405LW HDD connected to the
add-on Qlogic 12160 PCI-X card (
not the onboard SCSI connector!). The problem is, the system does not boot to the IRIX and all I can do is to go to the PROM console.
There, typing "hinv" without options shows that
add-on Qlogic 12160 controller as controller
2 and
3 (in addition to the Qlogic controllers 0 and 1 that are built-in). Also, the HDD is shown as
dksc(2,1,0) not the dksc(0,1,0) as specified in "setenv". The "hinv -v" command shows a SCSI interface on Module 001c01, Widget 14, PCI ID 1 (that is
in addition to the similar one on the Widget 15 which is
onboard).
The person whom I got this rig from knows that it
does not boot, but swears that the data on the HDD are good! He also gave me a spare HDD (which
I assume could be a copy of the 1st one).
So, the important question is:
Is it even possible to make a system with an add-on SCSI adapter boot in to the "sash" and beyond (provided that all data on the HDD is alright)?
Unfortunately, I can't just remove the add-on SCSI adapter and connect my HDD to the onboard (HD68) connector, because I
don't have the proper cable! So, I've been trying my best to get the system to at least recognize the HDD somehow.
Additional things that I have tried to achieve the above goal are as follows:
1) I tried to use the "disable" command to disable the onboard Qlogic controller so that the controller on the Add-on card would be re-numbered from 2 and 3 to 0 and 1.
But the PROM replied to me "Cannot disable the Master Baseio". Well, I think I got the correct parameters for the "disable" command because it
did work to disable the add-on SCSI card (on Widget 14). But that was
not what I really needed.
2) I tried to use the "ls" and "boot" commands.
The "ls dksc(2,1,0)/" command replied 'no such device'. And the "boot -f dksc(2,1,8)/sash" command replied "Unable to execute ..." and "Unable to load ..."
3) My last
desperate attempt was to try to modify some PROM variables from their default values as follows and then reboot:
Code:
setenv scsihostid 02
setenv ProbeAllScsi y
setenv root dks2d1s0
setenv SystemPartition dksc(2,1,8)
setenv OSLoadPartition dksc(2,1,0)
... but that did not help at all.
Did you happen to notice anything wrong in my configuration? Or do you have any advice/recommendations for me on what else to try?
Or do you need some additional info before you advise?
Please let me know... One way or another...
Thanks a lot in advance and Best Regards,
AK
