[Anonymoose]

Heyo,
Alas, my lowly Indy seems too slow to run 6.5.22, so I'm sticking with 5.3 for now. Anyways, I've been following THIS link that is very helpful but confusing. First off, the dallas chip is properly holding the netaddr and eaddr in memory (192.168.0.187 and 08:00:69:0a:4f:d5).

First off, I gather all the requirements needed:
IP of Indy (192.168.0.187)
IP Mask (255.255.255.0)
Hostname (I kept it at IRIS)
DomainName (confused by this, my Win 10 computer displays this as blank?)
IP of DNS Server (192.168.0.1)
IP of Default Gateway (192.168.0.1)

I then follow the instructions and.... it crashes after reboot (ERROR in S30network, Syntax error at line 356: "&")
I'll send a photo of my Win 10 cmd ' ipconfig /all' if requested, I didn't know if that was too personal to post.
Any thoughts? Thanks!

[Raion]

Your root shell is not liking the 2>&1. Is this a pre installation or a new install

[Anonymoose]

New install, completely fresh SD card in my ZuluSCSI

[weblacky]

Is your Indy an R5000? Which Install Source are you using? There are several 5.3 installs bases for different machines architectures and patch levels.

[robespierre]

Your root shell is not liking the 2>&1. Is this a pre installation or a new install

This is a syntax supported by the Bourne shell (sh), which csh (or tcsh) does not recognize. The shell used by init.d scripts is supposed to be the one listed in the first line of the file, according to the well-worn shebang convention. So the root user's chosen shell is not supposed to make any difference.

If for some reason the shell named in the script has been linked to another shell, that can cause this type of problem to occur.

[Anonymoose]

It’s an R4600, I was using “IRIX 5.3 for Indy
R4000, R4400, R4600” from JRRA.ZONE (812-0336-002). I haven’t installed any patches yet, those confuse me too… not sure which ones to install, although a few listings down is a recommended 5.3 patch cd from 97 (812-0602-006)

[Anonymoose]

Welp, hate to hijack this post, but I turned on the Indy this morning and! “SCSI controller 0 diagnostic FAILED, Check or replace: CPU base board”. I’m really hoping it isn’t the permanent kind of hardware failure…

[Raion]

No time to panic. These issues happen due to all sorts of things. Sometimes reseating things carefully will work.

[Anonymoose]

I’ll try it once I’m home again. Regarding the SCSI, should I have termination enabled on my Zulu even though there’s one on the internal cable?

[weblacky]

Nearly every SGI I've ever dealt with has answered the termination question the same for internal drives.

There is normally automatic termination at the end of the chain and you do not need or ever should enable termination for an internal drive. Indy is a passive terminator crimped permanently onto the end of the internal ribbon which means it is already terminated for you.

External devices are a totally different story as there is no provided termination. So you would only terminate external devices yourself. On Indy I have placed an additional external terminator right on the rear of the machine with no ill-effects as it's recognized as a device and the internal termination is disabled.

The only time I've seen this rule not hold is on the internal 50 pound narrow SCSI chain for a Fuel. I believe that on Fuels that came with an optical drive you got the long 50-Pin SCSI-2 cable and since the drive is the last on the internal chain the drive's internal termination is utilized as there is no attached terminator on the ribbon cable. This is the only time I've witnessed an internal drive chain on an SGI that didn't automatically terminate.