[SterlingNOVA]

Yes, the NUMALINK is being utilized. You may be right...could have been an issue originallywith the cable possibly not being fully seated when the panic alert srewed up the drive. I have seen that happen that it caused a panic anddata dump to the drive.I have found the issue. After running the cu command in debug, pointed to the Devices file not having a direct line.Looked in the file and ttyd3 was commented out. How it got that way....have no idea. These are old drives and I don't havea lot of insight of what all scripting that may have been put on these. Looked for possibility maybe a backup file was copiedor wrote over the file, but not finding where that may have been. At this point. Don't care, it's working.Thanks for the input.weblacky

Ok, rereading your initial description...is it at all possible your “sets” are using NumaLink?  Again, I only own desktop Tezros (not rackmount).  But could this all stem from the fact that you’re not powering the “sets” up in the correct order?  Or someone fiddled with the rear cabling?

In my mind, if you boot from another disk that wasn’t NUMALink configured then everything is fine, if you later install software and settings that activate NumaLink functionality, then missing its connected twin would definitely cause an error early on. 

The manual doesn’t say what happens if you leave a NUNAlink pair this way. 

Could you recheck the rear of the installation and ensure your powering either everything up at once or that if you starting in staggered sequence that you are powering the NumaLinked pairs together and not accidentally powering on one of multiple sets?

From what I know, Tezros can only NUMAlink as one pair, so these “sets“ you refer to struck me as odd word choice.  Perhaps this is why and the simple answer to the unexplained behaviors?

[jwhat]

Hi SterlingNova,

it could be that the port you are trying to access has already been allocated by IRIX for some other purpose.

This would explain why it occurs consistently over each of the setup machines, as the allocation is part of OS configuration.

The allocation of ports is described here: https://techpubs.jurassic.nl/manuals/065.../ch01.html

I recall looking at this a while back when I wanted to use serial port on one machine to be connected to "Console" of another machine so I could do L1 diagnostics.

Cheers from Oz,

John.

[Raion]

SterlingNova,

Just had to straighten out your post. Please reply to quotes like this:

it could be that the port you are trying to access has already been allocated by IRIX for some other purpose.

Reply down here.

The raw code is: 

Code:

[quote]
it could be that the port you are trying to access has already been allocated by IRIX for some other purpose.
[/quote]

Reply down here.

[hamei]

In my mind, if you boot from another disk that wasn’t NUMALink configured then everything is fine, if you later install software and settings that activate NumaLink functionality, then missing its connected twin would definitely cause an error early on. 

It doesn't work that way. The base brick has the operating system on it, and that's what controls everything. Even if you use a compute or storage module for additional software, it won't matter to the boot operation or bringing up the machine. You can't boot from a disk in the wrong brick.

If a numalink cable or something is wrong with a compute brick, you just end up with the base brick running by itself. It's not going to affect anything in the o.s. startup.

There's no numalink configuring to be done, that's all in the prom before you even get to booting.