[po6labs]

I'm having some trouble installing IRIX from the FTP on my O2. I'm using https://github.com/halfmanhalftaco/irixboot to make network installation. Everything seems to be working fine, the installation completes, quickrestaring ELF files completes and then I'm asked to reboot. 

So I enter (y) to reboot but on boot I get the following:

Cannot load pci(0)scsi(0)disk(1)rdisk(0)partition(0).
Illegal f_magic number 0x5846, expected MISPELMAGIC or MIPSEBMAGIC.

Did I miss something during the installation or might this be a hardware problem?

[mamorim01]

The system is looking for the boot partition on disk 1, have you by any chance installed a new drive with a different SCSI ID setting before the OS installation? This could be a remnant from a previous installation and could possibly be cleared by running 'resetenv' from the command monitor (F5) in PROM.

If you have not made any chances to the disk ID, it could be a damaged partition or something similar. Have you run fx before the installation and made a new XFS filesystem? If you run out of options and plan to reinstall it may be worth to run an auto check from within fx to check consistency of the drive. This was advised by others for other disk related issues.

Maybe others can chime in with other suggestions. Hope this helps.

[jan-jaap]

Regarding resetenv: this will always set up the system to boot from SCSI disk ID #1.

But in an R10K/R12K O2 system, the CPU module is wider and takes up the space of the left hard disk slot. Which corresponded to disk ID #1... So in an R10K/R12K O2 the system disk is always SCSI ID #2, and you need to change the PROM settings to reflect this.

[po6labs]

Yes, it's a brand new harddisk that I've just plugged in before installation. I basically went along the instructions from http://www.sgidepot.co.uk/6.5inst.html starting at "Erasing the Disk Within the Inst Program".  Do have to do some partitioning beforehand? I though since the installation process was working that the disk is correctly formatted.

hinv says:
...
SCSI Disk: scsi(0)disk(1)
...

and printenv says:

...
SystemPartition=pci(0)scsi(0)disk(1)rdisk(0)partition(8)
OSLoadPartition=pci(0)scsi(0)disk(1)rdisk(0)partition(0)
OSLoadFilename=
OSLoader=sash
...

I can repeat the installation process without a problem if I have to. Could you point me to a document that explains how to correctly format the disk if that is the issue?

[mamorim01]

Regarding resetenv: this will always set up the system to boot from SCSI disk ID #1.

But in an R10K/R12K O2 system, the CPU module is wider and takes up the space of the left hard disk slot. Which corresponded to disk ID #1... So in an R10K/R12K O2 the system disk is always SCSI ID #2, and you need to change the PROM settings to reflect this.

I was not aware that resetenv would default to disk ID 1, I agree this would achieve nothing on this particular case as there is consistency. I ran into problems myself once, entirely my fault, where I plugged in a disk set to ID 2 where PROM parameters were still considering the bootfile at ID 1. I could install IRIX but this discrepancy would not allow the system to boot. It was a silly mistake but it took me a while to figure it out. This does not seem to be the case, though.

Yes, it's a brand new harddisk that I've just plugged in before installation. I basically went along the instructions from http://www.sgidepot.co.uk/6.5inst.html starting at "Erasing the Disk Within the Inst Program".  Do have to do some partitioning beforehand? I though since the installation process was working that the disk is correctly formatted.

hinv says:
...
SCSI Disk: scsi(0)disk(1)
...

and printenv says:

...
SystemPartition=pci(0)scsi(0)disk(1)rdisk(0)partition(8)
OSLoadPartition=pci(0)scsi(0)disk(1)rdisk(0)partition(0)
OSLoadFilename=
OSLoader=sash
...

I can repeat the installation process without a problem if I have to. Could you point me to a document that explains how to correctly format the disk if that is the issue?

That looks okay. I am not in front of my SGI systems but shouldn't the OSLoadFilename parameter be?:

OSLoadFilename=/unix

I have followed the procedure which you used to initialize the disk with success, so that would probably not be an issue. Still, from within the fx program and before you repartition you may wish to carry out an [auto] initialization or an [exer]cise to check the integrity of the disk. See, for instance:

https://software.majix.org/irix/install-fx.shtml

This would provide insight in case there were problems with the drive. I would rule out other possibilities before attempting a reinstall, though.

[Unxmaal]

If you decide to reinstall, try this:

https://github.com/unxmaal/irixboot

It's a lot easier.

[po6labs]

All I had to do was: setenv OSLoadFilename /unix

Thanks for your help, I would have never found that on my own...

[mamorim01]

Great, enjoy your O2!