Hard drive failure / system board failure?

[kenbotransy]

I was rearranging some of the SGI O2s in my lab and one of the machines
failed to boot.
The message it gives me is:

Unable to execute ci(0)scsi(0)disk(1)rdisk(0)partition(8)/ash: no such
device
Unable to load bootfile: no such device

Thinking that one of my older harddrives may have finally died, I
pulled one from a
spare O2. Got the same error.

I have tried 4 drives with the same results. Of course, those 4
drives work on other
SGIs. So, I am led to believe that perhaps the system board has gone
to the great
beyond.

Not a problem, I have spares. But, there's one piece of software that
is licensed to that particular system ID. I don't have the money to
have the
software relicensed to a new machine.

Any suggestions? Is there something else that might be causing the
issue?

The machines are O2s, with varying memories and hard drive sizes.
All are running 6.5.XX not that that should make a difference.

Thoughts are appreciated.

Kenny

[Walter Roberson]

Post by kenbotransy
I was rearranging some of the SGI O2s in my lab and one of the machines
failed to boot.
Unable to execute ci(0)scsi(0)disk(1)rdisk(0)partition(8)/ash: no such
device
Unable to load bootfile: no such device

Go into the prom and resetenv

[Atro Tossavainen]

Is this a typo?

It should be executing "sash", not "ash", but the

Post by kenbotransy
no such device
Unable to load bootfile: no such device

message sort of shows that either the SCSI configuration is wrong or
the interface is dead.

What does "hinv" say?

[Walter Roberson]

Post by Atro Tossavainen
Is this a typo?

No.

Post by Atro Tossavainen
It should be executing "sash", not "ash", but the

Post by kenbotransy
no such device
Unable to load bootfile: no such device

message sort of shows that either the SCSI configuration is wrong or
the interface is dead.

No. Notice the string does not start with scsi but with ci
This tells us it is the string that is corrupted. resetenv
will fix the string.

[kenbotransy]

Thanks for the help.

The resetenv fixed the problem---I was going to ask why but your
followup
answered that as well :-)

kenny