Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Problem Starting Octane

Status
Not open for further replies.

robmacaire

Technical User
Jun 7, 2003
2
GB
Just switched on Octane and system states:

Boot file not found on device: xio(0)pci(15)scsi(0)disk(1)rdisk(0)partition(8)/sash.
Autoboot failed
Unable to continue;press <enter> to return to the menu:

I'm stuck! If you could drop me an advice I'd be extremely grateful
 
this could be a few things. but the most likely is that the disk in this machine is not a systems disk. if you have a boot/install server you could get the machine up in miniroot and snoop around the disk OR use the irix install disks to do the same. it's also possible that the volume header is corrupt or has been tinkered with by a rookie. if you can get the machine up in miniroot and determine you have a systems disk you could use dvhtool to get sash from the install cd's and put it back in the volume header.
if you have another octane you can stuff that disk in a running octane, issue scsiha -r 0 ; scsiha -p 0 ; ioconfig -f /hw and the disk will show up in hinv and then you can mount it and snoop it that way.
 
Thanks for your advice Crimso.
I think I understand what you're saying. Unfortunately, I bought this Octane with IRIX already installed and with no installation disks, so all I have is the Command Monitor shell and the Start System blue Octane page. I typed hinv and it reads:

System: IP30
Processor: 300MHz, etc,etc...
SCSI Disk: scsi(0)disk(1)
SCSI Disk: scsi(0)disk(2)
SCSI CDROM: scsi(1)disk(3)
Audio: RAD Audi Processor

From then on I'm stuck! I'm don't know how to initiate miniroot, but I was assured by the seller of this system that I would be able to swirch on and boot fine. It could be that a second hard drive was added that has caused this boot problem.

 
Hi,

Is it possible you accidentally (or the original owner accidentally) switched the drives? The OSLoader looks right.

Try this from prom:

boot -f dksc(0,2,8)sash dksc(0,2,0)/unix

If it works, shutdown and exchange the positions of the drives.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top