We want to upgrade to ALE3.

So, pwr d and then pwr u (at console) and quickly jam the boot CD in. Then wait and wait and wait anyway.

Eventually you get to a menu that looks like this:

EFI Boot Manager ver 1.02 [12.38]

Partition  0:                           Enabled Disabled
    CBricks          6         Nodes         12        0
    RBricks          4         CPUs          24        0
    IOBricks         1         Mem(GB)       64        0

Please select a boot option

    SGI ProPack(TM)                                                 
    Pci(1|1)/Scsi(Pun0,Lun1)/HD(Part1,Sig46A05A69-2E29-4CD4-8C8D-2F3
    Pci(4|0)/Mac(08006913F167)/NicName(tg0)                         
    VenMsg(E443E6B6-8AE5-11D7-84A4-003B000000090C0000000000000279880
    EFI Shell [Built-in]                                            
    Boot option maintenance menu                                    

Choose EFI Shell.

Loading: EFI Shell [Built-in]                                       
EFI Shell version 1.02 [12.38]
Device mapping table
  fs0  : Pci(1|1)/Scsi(Pun0,Lun1)/HD(Part1,Sigg1)
  fs1  : Pci(1|1)/Scsi(Pun0,Lun2)/HD(Part1,Sigg2)
  fs2  : Pci(2|1)/Ata(Primary,Master)/CDROM(Entry1)
  blk0 : Pci(1|1)/Scsi(Pun0,Lun1)
  blk1 : Pci(1|1)/Scsi(Pun0,Lun1)/HD(Part1,Sigg1)
  blk2 : Pci(1|1)/Scsi(Pun0,Lun1)/HD(Part2,Sigg3)
  blk3 : Pci(1|1)/Scsi(Pun0,Lun1)/HD(Part3,Sigg4)
  blk4 : Pci(1|1)/Scsi(Pun0,Lun2)
  blk5 : Pci(1|1)/Scsi(Pun0,Lun2)/HD(Part1,Sigg2)
  blk6 : Pci(1|1)/Scsi(Pun0,Lun2)/HD(Part2,Sigg5)
  blk7 : Pci(1|1)/Scsi(Pun0,Lun2)/HD(Part3,Sigg6)
  blk8 : Pci(2|1)/Ata(Primary,Master)
  blk9 : Pci(2|1)/Ata(Primary,Master)/CDROM(Entry1)
Shell> 

That's the device mapping table the install guide talks about. We see here that the CDROM is fs2.

So:

Shell> fs2:
fs2:\> cd efi\boot
fs2:\efi\boot>

and then boot like it sez in the manual.

We had pre-existing partitions, so we left those unchanged and just told it the vfat partition was /boot/efi, the xfs partition was /, and to format them. I can't give screenshots because flow control was messed up and half the changes were done semi-blind.

For package boot selection, I deselected:

• X11
• GNOME
• graphical internet
• graphics
• printing support

and selected:

• system tools

Then it's a matter of waiting and switching CDs. BEWARE: the CDROM "helpfully" autoejects. So don't close the door for pilatus!

Apparently the all-powerful Redhat team know better than I, and decided to install GNOME and printer stuff anyway without telling me. Thanks, guys.

Post-install, ran redhat-config-security-level to allow ssh. Now to patch it to SP3.

Can't mount /fsys1. It's an XVM filesystem, which... uh oh, apparently is supposed to be installed by SGI personnel. Whoops. Well, it talks about /etc/flexlm/license.dat, so let's put that back.

-- MikePatterson - 24 Jan 2005:

Meantime, accomplish patching. Copied Robyn's SP3 and patches directories to /root/sps.

[root@pilatus ServicePack3]# mkdir /iso
[root@pilatus ServicePack3]# mount -o loop ./propack-3SP3-cd1-open.iso /iso
[root@pilatus iso]# ./INSTALL 
/iso
is you current directory.
you can't start INSTALL script here, please instead type
        cd /; /iso/INSTALL
[root@pilatus iso]# cd
[root@pilatus root]# cd /
[root@pilatus /]# /iso/INSTALL 

Nice, it then unmounts where I had it and remounts it at /mnt/source. Oh well.

It asks if I want to install "Open Source only" or "ALL". I chose ALL, since we have ISOs for everything. Then it asks about customization, I said don't bother, and it told me that a full log will be placed in /root/sgi-install.log. It asked for 3 CD images, then said it was done and suggested a reboot. Hurray, it reboots, and console output shows me that it's at least trying to do XVM:

Loading xvm module:  modprobe: Can't locate module xvm
[FAILED]
Enabling xvm license:  execvp: No such file or directory

Look at the patches Robyn had collected, looks like 10120 doesn't apply. But 10123 does. And probably subsequent ones. Apply with "rpm -Uv".

Hrm, perhaps I should have just installed everything. I'm getting into twisty mazes of dependencies, some of which are development packages that I'm certain somebody, somewhere, will want eventually. sigh. I'll make ISOs out of the ALE3 CDs (probably worth having them anyway). For reference, I did this on my ubuntu system by mounting the CDs at /media/cdrom0 (default location) and doing mkisofs -R -o /home/tmp/ale3-1.iso /media/cdrom0 f'rinstance. I wound up having to install the unpatched versions of some packages in order to patch other packages which depended on them. sigh. Reboot and make sure the machine still boots... yup, no problems there.

XVM

Looking at the XVM adminstrator's guide, it appears that we need /etc/flexlm/license.dat to talk about xvm (check) and the xvm-standalone module to load (bzzt). rpm -qa | grep xvm sez nothing, and locate xvm doesn't give anything that looks like modules. So I guess I need some more stuff.

Ah, I can install xvm-cmnds and xvm-standalone from cd3-prop.iso from SP3. Now modprobe sgi-xvm-standalone works.

[root@pilatus modules]# cat /proc/xscsi/dksc 
pci01.03.0-1/target1/lun0  SGI      ST336753LC        36 GB
pci01.03.0-1/target2/lun0  SGI      ST336753LC        36 GB
pci02.01.0/target2/lun0  SGI      TP9100 F PSEUDO   0 GB
pci03.01.0/target0/lun0  SGI      TP9100 FFX2       586 GB
[root@pilatus modules]# mount /fsys1
mount: /dev/lxvm/array1s0: can't read superblock
[root@pilatus modules]# 

Well, we're farther along now, at least.

Looks like what we have is a physical volume:

xvm:local> show phys/*
phys/array1              1146311680 online,local
xvm:local>

... and now I can mount /fsys1. I tried it in the middle of leaving a voicemail for Scott Wilson and it... just worked.

But now I can't ssh in, I just get "connection closed". Ah, the sshd user doesn't exist, I overwrote /etc/{passwd,shadow,group} with the old ones. Merge the differences and make /home a link to /fsys1/home... perfect.

/usr/local/maple runs, hurrah!

Now let's see if we can still reboot cleanly - yup.

Test things like gcc, icc, maple - all "work" as well as I can tell. So I guess pilatus can be considered to have been upgraded.