Cookbook: Recovering Boot Options on IPF. Created by Sal Omar UKRCE. Version 3.

4 9/7/2010 page 1 of 72

Recovering Boot Options on IPF Servers

Note on intended use: This cookbook is for those folks who were unable to run the EFI shell utility
‘NVRAMBKP’ to save the boot configuration information on non cell based servers or the EFI>Variable
command on cell based servers.

Topics Covered:

1) EFI Shell Boot Option Recovery

2.1) HELP!! I CAN'T SEE ANY DISKS!!! With the shell> map -r command (they are SCSI attached).
2.2) HELP!! I CAN'T SEE ANY DISKS!!! With the shell> map -r command (they are Fibre attached).
3) HPUX Boot Option Recovery, manually using the 'bcfg' command or via the Boot Maintenance Menu.
4) LINUX Boot Option Recovery, manually using the 'bcfg' command or via the Boot Maintenance Menu.
5) Windows 2003 Boot Option Recovery, manually using '/MSUtil/nvrboot.efi' utility.
6) Windows 2008 Boot Option Recovery, using \EFI\Microsoft\Boot\bootmgfw.efi
7) OpenVMS Boot Option Recovery TBA
8) ODE Boot Option Recovery, manually using the 'bcfg' command or via the Boot Maintenance Menu.
9) Changing the Boot order with the 'u' and 'd' characters in 'Change Boot Order Menu'
10) ACPICONFIG (For Cell Based Systems) HPUX, LINUX, WINDOWS

Note: EFI menu navigation is achieved by using the up and down arrow keys on the keyboard.
Note: To see the navigation bar use Hyper term vt100 mode (if using a laptop). Set to ANSIW
(File>Properties>Settings>Emulation tab within Hyper term) or use PuTTY

1. EFI SHELL Boot Option Recovery.

1.1) Power the Sever ON and get to the Boot Manager Menu. As you can see we have no EFI Shell Boot
option to get us to a shell prompt, let’s add it in. Let’s go into the Boot Option Maintenance Menu:
Cookbook: Recovering Boot Options on IPF. Created by Sal Omar UKRCE. Version 3.4 9/7/2010 page 2 of 72

1.2) Choose ‘Add a Boot Option'

1.3) Choose 'Load EFI Shell Built-in'

Cookbook: Recovering Boot Options on IPF. Created by Sal Omar UKRCE. Version 3.4 9/7/2010 page 3 of 72

1.4) Type "EFI Shell' for the description, and take the defaults for the rest of the prompts by pressing
[ENTER] until you get the 'Save changes to NVRAM' prompt. Type Y to save settings and return to
previous screen.

1.5) Exit 'Boot Maintenance Manager>Add a Boot Option' submenu.

Cookbook: Recovering Boot Options on IPF. Created by Sal Omar UKRCE. Version 3.4 9/7/2010 page 4 of 72

1.6) Exit 'Boot Maintenance Manager' menu.

1.7) You should now be able to choose the 'EFI Shell' boot option and access the EFI Shell.
Cookbook: Recovering Boot Options on IPF. Created by Sal Omar UKRCE. Version 3.4 9/7/2010 page 5 of 72

So we've recovered our 'EFI Shell' Boot option to get us to a Shell Prompt.

Return to Top of EFI Shell Boot Recovery Section

Return to Top of Boot Recovery Cookbook

Cookbook: Recovering Boot Options on IPF. Created by Sal Omar UKRCE. Version 3.4 9/7/2010 page 6 of 72

2. Help! I Can't see any attached disks at efi shell with a 'map -r'.
Well the first thing to check is to make sure your disks are present and connected to the controllers (also
see note at bottom of this section). If your boot disk is Fibre Channel attached then go to section 2.2 to get
your FC attached disks recognized when you run map -r.

Now if all is well with the hardware then the next thing to do is to rescan the controllers for attached
devices using shell> reconnect -r. You could just do a shell> reset and get the same results, through a
reset of the server.

2.1 Help! I Can't see any SCSI attached disks at efi shell with a 'map -r'

2.1.1) Lets run the reconnect -r command at EFI Shell, and save ourselves a reboot (if you don't see the
EFI shell in your Boot Manager List then you might want to read section 1 of this document).

2.1.2). As you can see the SCSI bus is being rescanned and we have found a disk. If disks are RAIDED
through a Smart Array controller you'll see the SA Setup banner from ORCA here also.
Cookbook: Recovering Boot Options on IPF. Created by Sal Omar UKRCE. Version 3.4 9/7/2010 page 7 of 72

2.1.3) After a subsequent shell> map -r we can see our Disk (Pun2) with file systems represented by fs0
and fs1.

So if you can't see attached devices and you're sure they're connected and powered on you can either
reset the server (efi> reset) or rescan the controllers (efi> reconnect -r).

Notes:

On Cell Based systems, to allow faster booting, system firmware does not auto-scan PCI devices with an Option ROM. In order to
boot from a PCI-connected device with an Option ROM, it must be added to the table of boot devices as follows:

Step 1.Install the I/O card into the chassis.

Step 2.Boot the server to the EFI shell.
Step 3.Execute the EFI search command.
To add a single card:
search <cell> <pci_slot #>
To add all cards:
search all
Step 4.Execute the following EFI command:
map –r
Step 5.Enter the Boot Manager by executing the following command:
exit
Step 6.From the EFI Boot Manager Menu, select “Boot Option Maintenance Menu” and then from the Main Menu, select “Add a Boot
Option”. Now add the device as a new boot device.

Return to Top of This Section

Return to Top of Boot Recovery Cookbook

Cookbook: Recovering Boot Options on IPF. Created by Sal Omar UKRCE. Version 3.4 9/7/2010 page 8 of 72

2.2 Help! I Can't see any Fibre Channel Attached Disks at efi shell with a 'map -r'.

Before we start, a few notes:

For fibre channel attached disks the method used for SCSI in section 2.1 is not usually enough to display
your FC boot devices, if you've lost your boot options. This is because the driver for the FC card can be
configured to mask all FC devices but those that are in the boot options list in system NVRAM. The FC
driver setting, in our example using an A6795A HBA, is known as 'enumeration policy 0: Enumerate all
Fibre Channel boot devices in the boot option list ' (you'll have a similar configurable parameter for the
other available FC HBA's see Appendix A for further details). The driver is set this way to prevent a whole
SAN scan during self test or when running map -r, as this can take a significant amount of time.

In our case, as we have lost our boot options from NVRAM, the FC driver (set to enumeration policy 0)
returns no data of attached devices when we run a map -r or a reconnect -r. All we see in the capture
below is the built in IDE DVD drive as blk0.

Shell> reconnect -r and subsequent Shell> map -r aren't displaying any results either.
Cookbook: Recovering Boot Options on IPF. Created by Sal Omar UKRCE. Version 3.4 9/7/2010 page 9 of 72

NOTE: Normally FC attached disks should show up something similar to:

fs0 : Acpi(HWP0002,200)/Pci(1|0)/Fibre(WWN21000004CF270543,Lun0)/HD(Part1,Sig C6BE6E04-FA28-11D9-8002-

D6217B60E588) see below:

If you're seeing an output similar to this already then you can just go and recover your boot options as
normal.

If you're not seeing any FC attached devices and the hardware is connected fine, link lights on , zoning (if
used) setup correctly, WWN (if used) registered on the FC switch, etc. then read on:

To allow us to see fc attached devices and recover boot options from these we must first change the
enumeration (scanning) policy of the FC card driver, using the EFI command shell>drvcfg -s.

The two policies available to us for an A6795A fc card are:

0 : Enumerate all Fibre Channel boot devices in the boot option list
1 : Enumerate all Fibre Channel devices

Critical Notes:

i) Ensure the FC HBA is seated correctly in the PCI slot, storage hardware is connected fine, link lights on,
zoning (if used) setup correctly, WWN (if used) registered on the FC switch, etc.

ii) Ensure the EFI firmware for the card is loaded, especially important if you have just replaced the FC
card. For the A6795A FC HBA the firmware revision when writing this document was V1.09. Check
www.hp.com for firmware for your card.

In the case of the A6795A the firmware is loaded using FCFUPDATE from ODE (Offline Diagnostics CD,
available at http://www.hp.com download is free) or from ODE within ECU CD/DVD 5 . There's a 'catch 22',
you can't use ODE from the ODE partition on the FC attached hard disk as you have lost your boot
options!! and can't get to the disk.

iii) See additional notes in section 2.1.

iv) If you change the enumeration policy for a driver, you change that policy for all cards in the system that
use that driver.

v) Once you’ve changed the policy from 0 (Enumerate all Fibre Channel boot devices in the boot option
list) to 1: Enumerate all Fibre Channel devices and recovered your boot options ensure you set the
policy back to 0 : Enumerate all Fibre Channel boot devices in the boot option list to prevent
unnecessary scanning of the SAN each time the system restarts or when a map -r is run, as this can take
a significant amount of time.
Cookbook: Recovering Boot Options on IPF. Created by Sal Omar UKRCE. Version 3.4 9/7/2010 page 10 of 72

Enough said! Let’s get on and run through the example and get our FC disks displayed so we can
recover boot options.
2.2.1) If we have FC cards in our server first thing you'll notice is the driver reports in during server self
tests, before we get to loading core EFI and to the shell prompt:

In this case the driver is v1.09 for our A6895A FC HBA and that’s fine, see critical notes (i), (ii) & (iii) on the
previous page if your FC card driver is not reporting in.

2.2.2) Highlight the 'EFI Shell' selection from boot manager and get to an EFI shell prompt (if you don't see
the EFI shell in your Boot Manager List then you might want to read Section 1 of this document).

As you can see below we cannot get any disks listed apart from the DVD (blk0) because all our disks
happen to be attached via Fibre Channel in this case, including our boot disk. Even a rescan with shell>
map -r or a rescan with shell> reconnect -r does not help.
Cookbook: Recovering Boot Options on IPF. Created by Sal Omar UKRCE. Version 3.4 9/7/2010 page 11 of 72

2.2.3) Notice the reconnect -r does cause the FC controller to do a bus scan but we get nothing back
when we do a shell> map -r. This is because the enumeration policy on the A6795a FC controller is set to
0 (Enumerate all Fibre Channel boot devices in the boot option list) i.e., only those disks that are in the
boot options list in system NVRAM will be displayed. As we have lost our boot options list in system
NVRAM we get no disks presented here.

2.2.4) We need to go and set the A6795A FC card to policy 1 (Enumerate all Fibre Channel devices) i.e.,
display all FC attached devices. This is done using the command shell> drvcfg -s <driver#> <ctlr #>. In
order to run the command we need to first ascertain the FC HBA driver handle '<driver#>' and the FC HBA
controller handle <ctlr #>. We use the EFI shell command shell> drivers to find the driver handle
'<driver#>' , the -b option allows the output to display one page at a time.
Cookbook: Recovering Boot Options on IPF. Created by Sal Omar UKRCE. Version 3.4 9/7/2010 page 12 of 72

2.2.5) In our case the required driver handle under the 'DRV' column of the capture below is '1C' (notice
the firmware version is also displayed here under the 'VERSION' column as 00000109 ie,V1.09).

2.2.6) We now need to locate the controller handle associated with driver 1C. We do this using the
command shell> drvcfg. In our case our controller handle turns out to be '1D' (see below).
Cookbook: Recovering Boot Options on IPF. Created by Sal Omar UKRCE. Version 3.4 9/7/2010 page 13 of 72

2.2.7) We can now configure the driver using shell> drvcfg -s <driver#> <ctlr #> command to set the
enumeration policy to '1: Enumerate all Fibre Channel Devices'. Our command will be:

Shell> drvcfg -s 1C 1D

2.2.8) Select enumeration policy 1 enumerate all FC devices by typing 1 . Once you have selected the
required policy it will be used for ALL FC HBA's that use this driver (driver 1D).
Cookbook: Recovering Boot Options on IPF. Created by Sal Omar UKRCE. Version 3.4 9/7/2010 page 14 of 72

Note: This is the only configurable for the A6795a FC card. The A6826a dual port FC card in Appendix A1
has more configurables, and you may need to set the ‘luns per target’ parameter to the maximum, to see
all your luns after setting the enumeration policy, for the a6826a dual port card. See Appendix A2 for more
details.

2.2.9) After you type your selection you immediately exit to the following screen:

Note: You may need to repeat steps 2.2.4 to 2.2.9 if you have more than one FC HBA driver to
configure.
Cookbook: Recovering Boot Options on IPF. Created by Sal Omar UKRCE. Version 3.4 9/7/2010 page 15 of 72

2.2.10) Now that we have configured the FC driver to scan for all FC devices lets see if we can locate our
FC disks, using shell> reconnect -r to get the controller to do a scan.

2.2.11) Now lets do a shell> map -r to display the results of our work.
Cookbook: Recovering Boot Options on IPF. Created by Sal Omar UKRCE. Version 3.4 9/7/2010 page 16 of 72

Now that we can see our FC attached disks we can go and recover boot options in the normal way.

Now, Return the Enumeration Policy Back to the Correct State:

As we don't want to do a complete scan of the FC environment each time we boot the server or do a map -
r, as this can take a significant amount of time in a large SAN:

When you have recovered your boot options, don't forget to change the enumeration (scanning) policy
back to '0 : Enumerate all Fibre Channel boot devices in the boot option list' (in our case for the A6795A
FC card), i.e., use commands from step 2.2.4 to 2.2.8 above but select enumeration policy 0.

Return to top of this section

Return to Top of Boot Recovery Cookbook

Cookbook: Recovering Boot Options on IPF. Created by Sal Omar UKRCE. Version 3.4 9/7/2010 page 17 of 72

3. Recovering a HPUX Boot Option With Command Line (bcfg Command) or

Using Boot Option Maintenance Menu
3.1. Using Command Line (BCFG) Command:

3.11) Boot the server and get to EFI Shell prompt (if you don't see the EFI shell in your Boot Manager List
then you might want to read Section 1 of this document).

3.1.2) Run a shell>map -r . Here we have a device mapping table displayed by map -r command. Here 'fs'
numbers represent fat 32 formatted partitions on a hard disk (Pun 2), where we hope to find our boot
loader for HPUX. Note: If you don't see any devices displayed Pun's, Luns' etc. with the map -r command
then you might want to read Section 2 of this document.
Cookbook: Recovering Boot Options on IPF. Created by Sal Omar UKRCE. Version 3.4 9/7/2010 page 18 of 72

3.1.3) Lets go and interrogate each file system to see what we have on this disk.

So fs0: has an EFI directory and a STARTUP.NSH (script file). I know this structure this is the HPUX boot
partition. Let’s check by going into the EFI directory and see what's in there.

3.1.4) Type shell> cd efi to get to the efi directory and shell> dir to display the contents.

There's a HPUX directory where the boot loader will be. Let’s look in there.
Cookbook: Recovering Boot Options on IPF. Created by Sal Omar UKRCE. Version 3.4 9/7/2010 page 19 of 72

3.1.5) Type shell> cd hpux to get to the hpux directory and shell> dir to display the contents. Here we see
HPUX.EFI the HPUX Boot Loader that we wish to recover.

3.1.6) Now we can manually add the Boot Loader pointer in to the Boot Manager list with the following
command from this directory location:
\EFI\HPUX> bcfg boot add 1 hpux.efi "HPUX primary boot"

(where 1= location in boot menu where you'd like to see this entry, in this case at the top of the list, "HPUX primary boot" being the
name you wish displayed in the Boot Manager list).

Exit the EFI Shell shell>exit

Cookbook: Recovering Boot Options on IPF. Created by Sal Omar UKRCE. Version 3.4 9/7/2010 page 20 of 72

3.1.7) You'll see the HPUX boot entry at the top of the Boot Manager list.

3.1.8) The HPUX should now be bootable. Repeat these steps if you have more than one HPUX install to
recover or you have an alternate boot path to recover (mirrored disk). For cell based systems ensure you
run the command shell> acpiconfig default followed by a shell> reset BEFORE BOOTING HPUX.

Note: If your disks were fibre channel attached and you changed the enumeration policy in order to see
you’re FC attached disks and recover this boot option please make sure you return the policy it to its
correct state see section 2.2

Note: In a similar way to the way we recovered the HPUX boot Option we could now go and recover the
Offline Diagnostics (ODE) Boot Option using the shell> bcfg command.

Return to Top of HPUX Boot Recovery Section

Return to Top of Boot Recovery Cookbook
Cookbook: Recovering Boot Options on IPF. Created by Sal Omar UKRCE. Version 3.4 9/7/2010 page 21 of 72

3.2 Recovering a HPUX Boot Option Using the Boot Option Maintenance Menu.

3.2.1) Boot the server and get to EFI Shell prompt (if you don't see the EFI shell in your Boot Manager List
then you might want to read Section 1 of this document).

3.2.2) Run a shell>map -r . Here we have a device mapping table displayed by map -r command. Here 'fs'
numbers represent fat 32 formatted partitions on a hard disk (Pun 2), where we hope to find our boot
loader for HPUX. Note: If you don't see any devices displayed Pun's, Luns' etc. with the map -r command
then you might want to read Section 2 of this document.
Cookbook: Recovering Boot Options on IPF. Created by Sal Omar UKRCE. Version 3.4 9/7/2010 page 22 of 72

3.2.3) Exit EFI Shell shell> exit and get to the Boot Manager Menu. Enter Boot Options Maintenance
Menu.

3.2.4) Enter add a boot option Menu

Cookbook: Recovering Boot Options on IPF. Created by Sal Omar UKRCE. Version 3.4 9/7/2010 page 23 of 72

3.2.5) Choose the file system to look into. Hint: look for 'Part1' (in screen shot below) this means partition
1, i.e., the FAT32 file system where HPUX.EFI resides on Pun 2.Lun 0.

3.2.6) Select the EFI directory

Cookbook: Recovering Boot Options on IPF. Created by Sal Omar UKRCE. Version 3.4 9/7/2010 page 24 of 72

3.2.7) Select the HPUX directory.

3.2.8) Select the boot loader HPUX.EFI to add to the boot list.
Cookbook: Recovering Boot Options on IPF. Created by Sal Omar UKRCE. Version 3.4 9/7/2010 page 25 of 72

3.2.9) Type "HPUX Primary boot" for the description, and take the defaults for the rest of the prompts by
pressing [ENTER] until you get the save settings to NVRAM prompt. Type Y to save settings and return to
previous screen.

3.2.10) Exit 'Boot Maintenance Manager>Add a Boot Option' submenu.

Cookbook: Recovering Boot Options on IPF. Created by Sal Omar UKRCE. Version 3.4 9/7/2010 page 26 of 72

3.2.11) Exit 'Boot Maintenance Manager' menu.

3.2.12) HPUX will now be bootable however each time the machine restarts it will stop at EFI shell as this
is at the top of the current boot order list. We need to go back into the Boot Option Maintenance Menu and
change the boot order to place HPUX at the top of the list so that each time the system restarts it attempts
first to load hpux before exiting on boot failure to EFI Shell.
Cookbook: Recovering Boot Options on IPF. Created by Sal Omar UKRCE. Version 3.4 9/7/2010 page 27 of 72

3.2.13) Select Change Boot Order

3.2.14) Select the HPUX Primary Boot option and move it up to the top of the boot list with the 'u' and 'd'
characters on your keyboard.
Cookbook: Recovering Boot Options on IPF. Created by Sal Omar UKRCE. Version 3.4 9/7/2010 page 28 of 72

3.2.15) Save settings to NVRAM and EXIT

Cookbook: Recovering Boot Options on IPF. Created by Sal Omar UKRCE. Version 3.4 9/7/2010 page 29 of 72

3.2.16) You'll see the HPUX boot entry at the top of the Boot Manager list.

3.2.17 The HPUX should now be bootable. Repeat these steps if you have more than one HPUX install to
recover or you have an alternate boot path to recover (mirrored disk). For cell based systems ensure you
run the command shell> acpiconfig default followed by a shell> reset BEFORE BOOTING HPUX.

Note: If your disks were fibre channel attached and you changed the enumeration policy in order to see
you’re FC attached disks and recover this boot option please make sure you return the policy it to its
correct state see section 2.2

Note: In a similar way to the way we recovered the HPUX boot Option we could now go and recover the
Offline Diagnostics (ODE) Boot Option using the Boot Option Maintenance Menu.

Return to Top of HPUX Boot Recovery Section

Return to Top of Boot Recovery Cookbook
Cookbook: Recovering Boot Options on IPF. Created by Sal Omar UKRCE. Version 3.4 9/7/2010 page 30 of 72

4.Recovering LINUX Boot Option With Command Line (bcfg Command)

& Using Boot Option Maintenance Menu

4.1. Using Command Line (BCFG) Command:

4.1.1) Boot the server and get to EFI Shell prompt (if you don't see the EFI shell in your Boot Manager List
then you might want to read Section 1 of this document).

4.1.2) Run a shell>map -r . Here we have a device mapping table displayed by map -r command. Here 'fs'
numbers represent fat 32 formatted partitions on a hard disk (Pun 2), where we hope to find our boot
loader for LINUX. Note: If you don't see any devices displayed Pun's, Luns' etc. with the map -r command
then you might want to read Section 2 of this document.
Cookbook: Recovering Boot Options on IPF. Created by Sal Omar UKRCE. Version 3.4 9/7/2010 page 31 of 72

4.1.3) Interrogate each file system to see what we have on this disk. Hint: in our case fs0. is the one most
likely to be the EFI System Partition on the hard drive where the LINUX boot loader resides.

4.1.4) We have a 'redhat' directory. Let’s go in there. We can see the LINUX boot loader here 'elilo.efi'.
Cookbook: Recovering Boot Options on IPF. Created by Sal Omar UKRCE. Version 3.4 9/7/2010 page 32 of 72

4.1.5) Now we can manually add the Boot Loader pointer in to the Boot Manager list with the following
command from this directory location:
Shell> bcfg boot add 1 elilo.efi "Linux Boot"

(where 1= location in boot menu where you'd like to see this boot entry, in this case at the top of the list, " Linux Boot " being the
name you wish displayed in the Boot Manager list).

Exit the EFI Shell (shell>exit )

4.1.6) LINUX should now be bootable. Note: For Cell based systems ensure that for REDHAT LINUX the
acpiconfig is set to single-pci-domain with the command shell > acpiconfig single-pci-domain followed by
a reset (shell> reset ), for other LINUX versions see associated software install documentation.
Cookbook: Recovering Boot Options on IPF. Created by Sal Omar UKRCE. Version 3.4 9/7/2010 page 33 of 72

4.1.7) LINUX booting…….

Note: If your disks were fibre channel attached and you changed the enumeration policy in order to see
you’re FC attached disks and recover this boot option, please make sure you return the policy it to its
correct state see section 2.2

Note: In a similar way to the way we recovered the LINUX Boot Option we could now go and recover the
Offline Diagnostics (ODE) Boot Option using the shell> bcfg command.

Return to Top of Linux Boot Recovery Section

Return to Top of Document

Cookbook: Recovering Boot Options on IPF. Created by Sal Omar UKRCE. Version 3.4 9/7/2010 page 34 of 72

4.2 Recovering LINUX Boot Option using the Boot Option Maintenance Menu

4.2.1 Boot the server and get to EFI Shell prompt (if you don't see the EFI Shell in your Boot Manager
List then you might want to read Section 1 of this document).

4.2.2) Run a shell>map -r . Here we have a device mapping table displayed by map -r command. Here 'fs'
numbers represent fat 32 formatted partitions on a hard disk (Pun 1), where we hope to find our boot
loader for LINUX. Note: If you don't see any devices displayed Pun's, Luns' etc. with the map -r command
then you might want to read Section 2 of this document.
Cookbook: Recovering Boot Options on IPF. Created by Sal Omar UKRCE. Version 3.4 9/7/2010 page 35 of 72

4.2.3) Exit EFI Shell (shell> exit ) and get to the Boot Manager Menu. Select 'Boot Options Maintenance
Menu'.

4.2.4) Select 'Add a Boot Option' Menu

Cookbook: Recovering Boot Options on IPF. Created by Sal Omar UKRCE. Version 3.4 9/7/2010 page 36 of 72

4.2.5) Select the file system to look into. Hint: look for 'Part1' (this means partition 1 i.e., the FAT32 file
system on the hard drive (Pun 1, Lun0) where elilo.efi resides.

4.2.6) Select the EFI directory and press [ENTER]

Cookbook: Recovering Boot Options on IPF. Created by Sal Omar UKRCE. Version 3.4 9/7/2010 page 37 of 72

4.2.7) Select the redhat directory and press [ENTER]

4.2.8) Select the Linux boot loader elilo.efi and press [ENTER]
Cookbook: Recovering Boot Options on IPF. Created by Sal Omar UKRCE. Version 3.4 9/7/2010 page 38 of 72

4.2.9) Type "Linux Boot" for the description, and take the defaults for the rest of the prompts by pressing
[ENTER] until you get the 'Save Settings to NVRAM' prompt. Type Y to save settings and return to
previous screen.

4.2.10 Exit 'Add a Boot Option'

Cookbook: Recovering Boot Options on IPF. Created by Sal Omar UKRCE. Version 3.4 9/7/2010 page 39 of 72

4.2.11) Exit 'Boot Maintenance Manager' menu.

4.2.12) LINUX will now be bootable. However each time the machine restarts it will stop at EFI shell as this
is at the top of the current boot order list. We need to go back into the Boot Option Maintenance Menu and
change the boot order to place LINUX at the top of the list so that each time the system restarts it attempts
first to load LINUX before exiting, on boot failure, to EFI Shell. Highlight 'Boot Option Maintenance Menu'.
Cookbook: Recovering Boot Options on IPF. Created by Sal Omar UKRCE. Version 3.4 9/7/2010 page 40 of 72

4.2.13) Select Change Boot Order

4.2.14) Select the LINUX Boot option and move it up to the top of the boot list with the 'u' and 'd' characters
on your keyboard.
Cookbook: Recovering Boot Options on IPF. Created by Sal Omar UKRCE. Version 3.4 9/7/2010 page 41 of 72

4.2.15) Save settings to NVRAM and EXIT.

Cookbook: Recovering Boot Options on IPF. Created by Sal Omar UKRCE. Version 3.4 9/7/2010 page 42 of 72

4.1.6) LINUX should now be bootable. Note: For Cell based systems ensure that for REDHAT LINUX the
acpiconfig is set to single-pci-domain with the command shell > acpiconfig single-pci-domain followed by
a reset (shell> reset )

4.1.7) LINUX booting…….

Note: If your disks were fibre channel attached and you changed the enumeration policy in order to see
you’re FC attached disks and recover this boot option, please make sure you return the policy it to its
correct state see section 2.2

Note: In a similar way to the way we recovered the LINUX Boot Option we could now go and recover the
Offline Diagnostics Boot Option using the Boot Option Maintenance Menu.

Return to Top of Linux Boot Recovery Section

Return to Top of Boot Recovery Cookbook

Cookbook: Recovering Boot Options on IPF. Created by Sal Omar UKRCE. Version 3.4 9/7/2010 page 43 of 72

5. Recovering the Windows 2003 Boot Option with nvrboot.efi

(NOTE: For Windows 2008 see Appendix A5).
Windows Boot Options cannot be recovered in the same way as HPUX, ODE & LINUX. We have to use a
utility /MSUtil/nvrboot.efi to recover boot options from the directory /EFI/Microsoft/WINNT50.x/Bootyyyy
(where x and y = integers that vary depending on the number of O/S installs you have.

5.1 Lets locate the /MSUtil/nvrboot.efi utility & the /EFI/Microsoft/WINNT50.x/Bootyyyy files on our hard
disk where the O/S resides. Boot the server and get to EFI Shell prompt (if you don't see the EFI shell in
your Boot Manager List then you might want to read Section 1 of this document).

5.2) Run a shell>map -r . Here we have a device mapping table displayed by map -r command. Here 'fs'
numbers represent fat 32 formatted partitions on a hard disk (Pun 2), where we hope to find our boot
loader for WINDOWS. Note: If you don't see any devices displayed Pun's, Luns' etc. with the map -r
command then you might want to read Section 2 of this document. Let’s go and interrogate each file
system to see what we have on this disk.
Cookbook: Recovering Boot Options on IPF. Created by Sal Omar UKRCE. Version 3.4 9/7/2010 page 44 of 72

5.3) So Under fs1: we have the EFI directory and the MSUtil directory. Within the EFI directory we have
the Microsoft Directory.

5.4) Changing to the Microsoft directory we find WINNT50 directory. Note: If you have multiple directories
here of the type WINNT50.x (where x= and integer) see the notes at bottom of this section.
Cookbook: Recovering Boot Options on IPF. Created by Sal Omar UKRCE. Version 3.4 9/7/2010 page 45 of 72

5.5) Within there we have 'Boot0001' the Windows boot loader we wish to import with MSUtil/nvrboot.efi.
Make a note of this path from the root directory to the Boot loader. In our case the path is
\EFI\Microsoft\WINNT50\Boot0001. Note: If you DO NOT have Bootyyyy (y= an integer) then you will
have to ring your local response center for assistance recovering the boot loader or RELOAD the O/S.

5.6 ) Let’s change directory back to the root directory of fs1: and go into the MSUtil subdirectory, where
we'll find the utility nvrboot.efi used to import \EFI\Microsoft\WINNT50\Boot0001.
Cookbook: Recovering Boot Options on IPF. Created by Sal Omar UKRCE. Version 3.4 9/7/2010 page 46 of 72

5.7) Within the MSUtil subdirectory we find the nvrboot.efi utility

5.8) Run nvrboot.efi by typing nvrboot.efi at the shell.

Cookbook: Recovering Boot Options on IPF. Created by Sal Omar UKRCE. Version 3.4 9/7/2010 page 47 of 72

5.9) At the next screen choose I to import and put in the path to the Windows boot loader you made a note
of in step 5.5) above and press [enter] and then [enter] again to continue.

5.10) The Windows Boot Loader as now been brought into the Boot Loader menu. Type Q to quit.
Cookbook: Recovering Boot Options on IPF. Created by Sal Omar UKRCE. Version 3.4 9/7/2010 page 48 of 72

5.11) Exit back to the Boot Manager Menu

5.12) Note that our newly imported Windows boot option does not appear at the top of our boot list. If we
now restart the server we would end up at EFI shell by default instead of booting the Windows O/S. We
need to change the boot order, and place the O/S boot Loader at the top of the Boot list. Lets do that next.
Cookbook: Recovering Boot Options on IPF. Created by Sal Omar UKRCE. Version 3.4 9/7/2010 page 49 of 72

5.13) Select the 'Boot Option Maintenance Menu'.

5.14) Select 'Change Boot Order'.

Cookbook: Recovering Boot Options on IPF. Created by Sal Omar UKRCE. Version 3.4 9/7/2010 page 50 of 72

5.15) Select the boot option for Windows and use the 'u' and 'd' keys on your keyboard to move the option
to the top of the boot list.
Cookbook: Recovering Boot Options on IPF. Created by Sal Omar UKRCE. Version 3.4 9/7/2010 page 51 of 72

5.16) Select 'Save Settings to NVRAM ' & 'Exit'.

5.17) The Windows Boot Loader will now be at the top of the boot list and should be bootable. Note: On
Cell Base systems ensure you run shell>acpiconfig windows and then shell> reset BEFORE booting
the Windows O/S.
Cookbook: Recovering Boot Options on IPF. Created by Sal Omar UKRCE. Version 3.4 9/7/2010 page 52 of 72

5.18) Windows Booting….

Notes:

You may wish to repeat the above exercise to recover further Windows boot loaders. If you have multiple
directories here of the type:

\EFI\Microsoft\WINNT50\
\EFI\Microsoft\WINNT50.1\
\EFI\Microsoft\WINNT50.2\

This is indicative of more than one installation of Windows on the hard disk. You will have to go into each
one of these WINNT50.x directories. Repeat step 5.4 (above) onwards for each WINNT50.x directory.

If your disks were fibre channel attached and you changed the enumeration policy in order to see you’re
FC attached disks and recover this boot option, please make sure you return the policy it to its correct state
see section 2.2

Offline Diagnostics on the Windows Hard Disk:

You may wish to interrogate other file systems (fs numbers) on the hard drive for OFFLINE DIAGNOSTICS
(ODE) and recover the Offline Diagnostics boot loader either using the manual method using the shell>
bcfg command OR via the Boot Option Maintenance Menu.

Return to Top of Windows Boot Recovery Section

Return to Top of Boot Recovery Cookbook

Cookbook: Recovering Boot Options on IPF. Created by Sal Omar UKRCE. Version 3.4 9/7/2010 page 53 of 72

6. Recovering Windows 2008 boot option using bootmgfw.efi

The Windows 2008 boot option recovery process is totally different to that used to recover the Windows
2003 boot option detailed in section 5 above.

For Windows 2008:

The Windows 2008 EFI boot loader will automatically recreate the 'Windows Boot Manager' entry upon
execution of the Windows EFI loader file. This loader file must be launched from the EFI boot menu and
not directly from the EFI system partition. The procedure is as follows:

From EFI Boot Menu got through to the following EFI menu structure

-> Boot Configuration

-> Boot From File

Drill down the file system structures on each disk in the server until you locate the ‘bootmgfw.efi’
Normally down the following path:

-> \EFI\Microsoft\Boot\bootmgfw.efi

Once the above is highlighted and you press enter bootmgfw.efi will be executed. bootmgfw.efi will
recreate the Windows Boot Manager entry and will attempt to launch Windows. The Windows Boot
Manager entry will not be the default (top-most) boot order entry. If necessary, the boot order can be
modified by again using the Boot Configuration menu when the system is next restarted.

Return to Top of Boot Recovery Cookbook

Cookbook: Recovering Boot Options on IPF. Created by Sal Omar UKRCE. Version 3.4 9/7/2010 page 54 of 72

8. Offline Diagnostics (ODE) Boot Option Recovery

8.1) Offline Diagnostics (ODE) Boot Option Recovery Using Command Line ('bcfg'
command)

Offline diagnostics is O/S independent and can be recovered using this method for all IPF O/S installs.

8.1.1) Locate the file system on the hard drive where the offline diagnostics reside. If you do not have a file
system for Offline Diagnostics then you can't recover ODE as it doesn't exist on the hard drive. ODE is not
normally partition 1 (Part 1) on a hard disk as Part 1 is more likely to be the EFI System Partition where the
O/S loader resides. ODE is more likely to be on partition 2 (Part 2) or partition 3 (Part 3). Let’s look inside
fs1: (here, pun2, Lun0/HD Part3).

8.1.2) This looks like it has our ODE on it. Let’s look in the directory 'BOOT'. If these directories are not
present or if you just see a 'Readme ' in here then see the notes at the bottom of this section.
Cookbook: Recovering Boot Options on IPF. Created by Sal Omar UKRCE. Version 3.4 9/7/2010 page 55 of 72

8.1.3) In our case we can see the boot loader here, it's called 'LaunchMenu.efi' so let’s bring this into the
boot list:

8.1.4) Now we can manually add the boot loader to the Boot Manager list with the following command from
this directory location:
\EFI\BOOT> bcfg boot add 3 launchmenu.efi "Offline Diagnostics"

(where 3= location in Boot Manager menu where you'd like to see this entry, in this case at the third entry, "Offline Diagnostics"
being the name you wish displayed in the Boot Manager menu).

Exit the EFI Shell shell>exit

Cookbook: Recovering Boot Options on IPF. Created by Sal Omar UKRCE. Version 3.4 9/7/2010 page 56 of 72

8.1.5) Offline Diagnostics should now be bootable.

Notes: If at step 7.1.2 above you do not see any directory structures, then the Offline Diagnostics have not
yet been loaded into the HPSP (HP Service Partition). You'll need an IPF ODE CD to install ODE into the
HPSP( available at http://www.hp.com download is free). Don't use ECU CD/DVD 5 to install ODE onto the
HPSP as this copies other tools into this partition as well as the ODE image. See notes before booting &
running ODE

8.1.6) Offline Diagnostics Booted….

Return to Top of Diagnostics (ODE) Boot Recovery Section

Return to Top of Boot Recovery Cookbook

Cookbook: Recovering Boot Options on IPF. Created by Sal Omar UKRCE. Version 3.4 9/7/2010 page 57 of 72

8.2 ) Offline Diagnostics (ODE) Boot Option Recovery Using the Boot Option
Maintenance Menu

8.2.1) First verify that we have an ODE Boot Option to recover by navigating to the directory where
Launchmenu.efi resides on the HPSP (HP Service Partition) see steps 7.1.1 to 7.1.3 above. If the HPSP
exists and is populated then: Exit EFI Shell shell>exit and get to the 'Boot Manager' Menu. Enter 'Boot
Options Maintenance' Menu.

8.2.2) Enter add a boot option Menu

Cookbook: Recovering Boot Options on IPF. Created by Sal Omar UKRCE. Version 3.4 9/7/2010 page 58 of 72

8.2.3) Select the partition holding the ODE Boot loader: (Hint: look for Part 2 or Part 3 on the same hard
disk, Pun, Lun number as the O/S ). In our case it's Pun2, Lun0 Part 3.

8.2.4) Navigate to the EFI/Boot/ directory

Cookbook: Recovering Boot Options on IPF. Created by Sal Omar UKRCE. Version 3.4 9/7/2010 page 59 of 72

8.2.5) Highlight LaunchMenu.efi and press [ENTER].

Cookbook: Recovering Boot Options on IPF. Created by Sal Omar UKRCE. Version 3.4 9/7/2010 page 60 of 72

8.2.6) Enter a description in this case 'Offline Diagnostics' and take the defaults for the rest of the prompts
by pressing [ENTER] until you get the save settings to NVRAM prompt. Type Y to save settings and return
to previous screen.

8.2.7) Exit 'Add a Boot Option' Menu

Cookbook: Recovering Boot Options on IPF. Created by Sal Omar UKRCE. Version 3.4 9/7/2010 page 61 of 72

8.2.8) Exit 'Boot Option Maintenance Menu'

8.2.9) Boot Manager should now show the Offline Diagnostics entry in the boot list. This should now be
bootable. See notes before booting and running ODE.
Cookbook: Recovering Boot Options on IPF. Created by Sal Omar UKRCE. Version 3.4 9/7/2010 page 62 of 72

8.2.10) Offline Diagnostics Booted….

See notes on next page.

Notes :

For Cell based servers:

On CELL based systems set ACPICONFIG to default shell>acpiconfig default and then shell> reset
BEFORE running ODE. Ensure after you have completed your ODE run, that you return the ACPICONFIG
to its correct value for the operating system, see 3.1.8 for HPUX, 4.1.6 for LINUX, section 5.1.7 for
Windows.

For all Integrity servers:

After you have finished running ODE, ALWAYS reset the server shell> reset before booting the O/S.

Return to Top of Diagnostics (ODE) Boot Recovery Section

Return to Top of Boot Recovery Cookbook

Cookbook: Recovering Boot Options on IPF. Created by Sal Omar UKRCE. Version 3.4 9/7/2010 page 63 of 72

Appendix A
A1. Configuration Screen Shots for Setting Enumeration Policy of an A6826a Dual Port FC HBA.

Various FC HBA's are available. I have managed to get hold of a A6826a HBA where locating
the enumeration policy settings was a little more difficult. I had to read the documentation that came down
with the firmware & EFI driver from http://www.hp.com in order to figure out which parameter to change:

A.1.1 Example of output of devices command for the A6826a to locate the controller Id for our
shell> drvcfg -s [driver#] [controller#] command.

In our Case the controller id is 1E.

A1.1.2 Lets run the drvcfg command to get the associated driver handle. In our case the driver handle
associated with controller 1E above is 1C (see below).
Cookbook: Recovering Boot Options on IPF. Created by Sal Omar UKRCE. Version 3.4 9/7/2010 page 64 of 72

A1.1.3 Lets run shell> drvcfg -s 1C 1E and take at look at the controller configuration for this A6826a
FC card.
Cookbook: Recovering Boot Options on IPF. Created by Sal Omar UKRCE. Version 3.4 9/7/2010 page 65 of 72

A1.1.4 Here is the menu from the controller.

A1.1.5 As you can see it’s not very intuitive. I had to read the documentation for the card to find out were
the enumeration (scanning) policy settings are kept. It turns out to be option 4 'Edit Boot Settings' from
the main menu on the controller.
Cookbook: Recovering Boot Options on IPF. Created by Sal Omar UKRCE. Version 3.4 9/7/2010 page 66 of 72

A1.1.6 Then option 4 again 'EFI Variable EFIFCSanLevel'. Setting this parameter to 1 enables me to scan
all devices on the SAN not just those in my system NVRAM boot options list.

You can now go and search for devices with map -r etc. See section 2.2
Return to Top of Boot Recovery Cookbook or go to Appendix A2 setting ‘LUNS per TARGET’.
Cookbook: Recovering Boot Options on IPF. Created by Sal Omar UKRCE. Version 3.4 9/7/2010 page 67 of 72

A2. Setting Luns per target to see more than the default 128 luns on an A6826A FC card, by Holger
Goetker GRC.

Note: The FW on the adapter was EFI 1.30 & ROM 3.2.168.
Latest available FW is EFI 1.47 / RISC 3.3.154 (19 Oct 2005).

EFI fibre channel configuration parameter “Luns Per Target”

After setting our EFIFCScanLevel to 1 enumerate all devices (Appendix A1), we only see 128 luns. This is
because there is an additional parameter ‘luns per target’ that needs to be set to see all the luns (256) off
this port.

So with EFIFCScanLevel [1] and Luns Per Target (dec) [128]:

Shell> map
Device mapping table
blk0 : Acpi(HWP0002,22A)/Pci(1|0)/Pci(4|0)/Fibre(WWN500060E802C6E701,Lun4000)
...
blk65 : Acpi(HWP0002,22A)/Pci(1|0)/Pci(4|0)/Fibre(WWN500060E802C6E701,Lun4073)
blk66 : Acpi(HWP0002,2A8)/Pci(1|0)/Pci(4|0)/Fibre(WWN500060E802C6E711,Lun4000)
...
blkCB : Acpi(HWP0002,2A8)/Pci(1|0)/Pci(4|0)/Fibre(WWN500060E802C6E711,Lun4073)
blkCC : Acpi(HWP0002,2BE)/Pci(1|0)/Pci(4|0)/Scsi(Pun1,Lun0)

 Note: We see only 102 (0-65h) block devices and no file systems on the adapter
22A.

Shell> drivers

T D
D Y C I E
R P F A B
V VERSION E G G C #D #C DRIVER NAME IMAGE NAME
== ======== = = = = == == ============================== ===================
.
.
33 0007000A B X X - 6 6 Broadcom Gigabit Ethernet Driv BRM5701_LAN
34 00000001 D - - - 9 - Simple Network Protocol Driver Snp3264
35 00000010 D - - - 9 - PXE Base Code Driver PxeBc
36 00000010 D - - - 9 - PXE DHCPv4 Driver PxeDhcp4
39 0000011E B X X X 6 204 HP 2 Gb Fibre Channel Driver S=02 B=16 D=4 F=0 I=0
3A 01040200 B X X - 2 1 LSI Logic Fusion MPT Driver S=02 B=BF D=4 F=0 I=0
3B 00002160 B - - - 2 2 Intel(R) PRO/1000 v2.16 EFI-64 S=02 B=BF D=6 F=0 I=0

Shell> drvcfg
Configurable Components
Drv[33] Ctrl[88] Lang[eng]
Drv[33] Ctrl[8C] Lang[eng]
Drv[33] Ctrl[FB] Lang[eng]
Drv[33] Ctrl[104] Lang[eng]
Drv[33] Ctrl[108] Lang[eng]
Drv[33] Ctrl[178] Lang[eng]
Drv[39] Ctrl[87] Lang[eng]
Drv[39] Ctrl[8B] Lang[eng] ---- gives us our driver & ctlr handle for ‘drvcfg -s’
Drv[39] Ctrl[FA] Lang[eng]
Drv[39] Ctrl[103] Lang[eng]
Drv[39] Ctrl[107] Lang[eng]
Drv[39] Ctrl[177] Lang[eng]
Drv[3A] Ctrl[170] Lang[eng]
Drv[3A] Ctrl[171] Lang[eng]

Shell> drvcfg -s 39 8b
Set Configuration Options
NOTE: Redirecting console output may cause test failures and is not recommended
Cookbook: Recovering Boot Options on IPF. Created by Sal Omar UKRCE. Version 3.4 9/7/2010 page 68 of 72

Adapter Path: Acpi(PNP0002,022A)/Pci(01|00)/Pci(04|00)

eficfg> help

EFI Configuration Utility Commands

NVRAM Parameters
edit_adapter_settings
edit_advanced_settings
edit_database
edit_efi

Information
show_database
show_translation
show_buffer
info
help

Operation
abandon
write
quit

eficfg> edit_efi
EFI parameters:
Enable Alternate Boot Device [y]?
Enable EFI Boot Order List [y]?
Enable Selective Login [n]?
Enable Selective Lun logins [n]?
EFI Variable EFIFCScanLevel [1]?

eficfg> edit_advanced_settings
Advanced Settings:
Operation Mode:
0 - Interrupt for every I/O completion
5 - Interrupt when Interrupt Delay Timer expires
6 - Interrupt when Interrupt Delay Timer expires or no activity
Connection Option [0]?
Interrupt Delay Timer (dec) [0]?
Execution Throttle (dec) [16]?
Login Retry Count (dec) [8]?
Port Down Retry Count (dec) [16]?
Link Down Timeout (dec) [8]?
Luns Per Target (dec) [128]? - This poses a problem if you have more than 128 luns!
Enable Extended Logging [n]?
Enable LIP Reset [n]?
Enable LIP full login [y]?
Enable target reset [y]?

eficfg>

So we changed the "Luns Per Target" to 256:

eficfg> edit_advanced_settings

Advanced Settings:

Operation Mode:
0 - Interrupt for every I/O completion
5 - Interrupt when Interrupt Delay Timer expires
6 - Interrupt when Interrupt Delay Timer expires or no activity

Connection Option [0]?

Interrupt Delay Timer (dec) [0]?
Execution Throttle (dec) [16]?
Login Retry Count (dec) [8]?
Port Down Retry Count (dec) [16]?
Link Down Timeout (dec) [8]?
Luns Per Target (dec) [128]? 256 -- changed to 256
Cookbook: Recovering Boot Options on IPF. Created by Sal Omar UKRCE. Version 3.4 9/7/2010 page 69 of 72

Enable Extended Logging [n]?

Enable LIP Reset [n]?
Enable LIP full login [y]?
Enable target reset [y]?

eficfg> write

Writing (saving changes)...

................
Done.

eficfg> quit

Exiting...
Drv[39] Ctrl[8B] Lang[eng] - Options set. Action Required is None

Shell> reconnect -r
dec2114x found MAC address 00:0F:20:3C:E2:2B Name = sni0
HP 2Gb Fibre Channel Combo Adapter (driver 1.30, firmware 3.02.168)
Broadcom NetXtreme Gigabit Ethernet (BCM5703) is detected (PCI-X)
HP 2Gb Fibre Channel Combo Adapter (driver 1.30, firmware 3.02.168)
Broadcom NetXtreme Gigabit Ethernet (BCM5703) is detected (PCI-X)
HP 2Gb Fibre Channel Combo Adapter (driver 1.30, firmware 3.02.168)
Broadcom NetXtreme Gigabit Ethernet (BCM5703) is detected (PCI-X)
HP 2Gb Fibre Channel Combo Adapter (driver 1.30, firmware 3.02.168)
Broadcom NetXtreme Gigabit Ethernet (BCM5703) is detected (PCI-X)
HP 2Gb Fibre Channel Combo Adapter (driver 1.30, firmware 3.02.168)
Broadcom NetXtreme Gigabit Ethernet (BCM5703) is detected (PCI-X)
Scsi(Pun1,Lun0) _NEC DVD+RW ND-2100AD1.28 ( 80 MBytes/sec)
HP 2Gb Fibre Channel Combo Adapter (driver 1.30, firmware 3.02.168)
Broadcom NetXtreme Gigabit Ethernet (BCM5703) is detected (PCI-X)
ReconnectController(0,0,0) : Status = Success

Now we can see the other luns on the target and see the file systems within.

Shell> map -r
Device mapping table
fs0 : Acpi(HWP0002,22A)/Pci(1|0)/Pci(4|0)/Fibre(WWN500060E802C6E701,Lun40B)
fs1 : Acpi(HWP0002,22A)/Pci(1|0)/Pci(4|0)/Fibre(WWN500060E802C6E701,Lun40B)
fs2 : Acpi(HWP0002,22A)/Pci(1|0)/Pci(4|0)/Fibre(WWN500060E802C6E701,Lun40B)
fs3 : Acpi(HWP0002,22A)/Pci(1|0)/Pci(4|0)/Fibre(WWN500060E802C6E701,Lun40B)
blk0 : Acpi(HWP0002,22A)/Pci(1|0)/Pci(4|0)/Fibre(WWN500060E802C6E701,Lun400)
blk1 : Acpi(HWP0002,22A)/Pci(1|0)/Pci(4|0)/Fibre(WWN500060E802C6E701,Lun400)
blk2 : Acpi(HWP0002,22A)/Pci(1|0)/Pci(4|0)/Fibre(WWN500060E802C6E701,Lun400)
...
blk9A : Acpi(HWP0002,22A)/Pci(1|0)/Pci(4|0)/Fibre(WWN500060E802C6E701,Lun40B)
blk9B : Acpi(HWP0002,22A)/Pci(1|0)/Pci(4|0)/Fibre(WWN500060E802C6E701,Lun40B)
blk9C : Acpi(HWP0002,2A8)/Pci(1|0)/Pci(4|0)/Fibre(WWN500060E802C6E711,Lun400)
blk9D : Acpi(HWP0002,2A8)/Pci(1|0)/Pci(4|0)/Fibre(WWN500060E802C6E711,Lun400)
...
blk101 : Acpi(HWP0002,2A8)/Pci(1|0)/Pci(4|0)/Fibre(WWN500060E802C6E711,Lun407)
blk102 : Acpi(HWP0002,2BE)/Pci(1|0)/Pci(4|0)/Scsi(Pun1,Lun0)

Shell>

 We now see all 156 (0-9Bh) block devices (LUNs) and the file systems on the fc
adapter 22A.
 The “Luns Per Target” parameter can be set to a different value for each adapter.
It’s NOT a driver wide setting like the EFIFCScanLevel, where you change the
parameter on one adapter and it will affect all adapters that use the same driver.

NOTE: When you have recovered your boot options, don't forget to change the enumeration (scanning)
policy back to '0 : Enumerate all Fibre Channel boot devices in the boot option list' (in our case for the
A6795A FC card), i.e., use commands from step 2.2.4 to 2.2.8 above but select enumeration policy 0.

Return to Top of Boot Recovery Cookbook

Cookbook: Recovering Boot Options on IPF. Created by Sal Omar UKRCE. Version 3.4 9/7/2010 page 70 of 72

A3. NVRAMBKP Utility on non cell based servers:

Nvrambkp.efi from hp.com can be used to save the current Non Volatile RAM configuration of non cell
based servers onto an available FAT 32 formatted file system.

The following is extracted from the README that comes with the ‘HP Integrity Non-Volatile RAM
Configuration Back-up Utility’ (nvrambkp.efi).

1. At the shell prompt, type "fs0:", replacing "fs0:" with each "fs" entry in the table until you find the volume
containing the "nvrambkp.efi" file that was copied to the EFI partition in the previous instructions. We
will assume this volume is labeled fs0 for the remainder of these instructions.
2. Type "fs0:", then press ENTER.
3. Locate the file "nvrambkp.efi" on the file system and enter one of the following commands, where
<archivedb> is the name of the NVRAM archive database and <log> is the name of the log file created:

Archive:
"nvrambkp -a <archivedb> -l <log>"

Restore All:
"nvrambkp -r <archivedb> -l <log>"

Restore Boot-Options Only:

"nvrambkp -o -r <archivedb> -l <log>"

Validate Restore Database on the current server:

"nvrambkp -v -r <archivedb> -l <log>"

Information about the Restore Database:

"nvrambkp -i -r <archivedb> -l <log>"

For more information on the available options, view the help text by entering the following command:
"nvrambkp.efi -h".

Return to Top of Boot Recovery Cookbook

Cookbook: Recovering Boot Options on IPF. Created by Sal Omar UKRCE. Version 3.4 9/7/2010 page 71 of 72

A4. EFI> variable command on cell based systems:

The EFI shell ‘variable’ command is built into the firmware of Itanium Cell based servers and is used to
save the Non Volatile RAM configuration information to an available FAT32 formatted file system. The
following is an extract from the HP intarnet WTEC site related to the use of the efi ‘Variable’ command.

Use of the "variable" command is recommended BEFORE replacing a cell board or BEFORE performing a
firmware upgrade.

Special note: If this is a SX2000 server with SFW 9.048, the variable command has been
enhanced to also save the ILM and CLM values required for Virtual partitions.

Usage:

Shell> help variable

VARIABLE -s|-save [filename]

VARIABLE -r|-restore [filename]

VARIABLE -d|-dump [filename]

-s or -save : Specifies save variables mode

-r or -restore : Specifies restore variables mode

-d or -dump : Specified dump variables mode

filename : Specifies the filename to save to or restore from

Note:

1. If no filename is given, the file 'efi.save' in the current directory will be used

Examples:

* To save variables to the file 'variable.save':

fs0:\> variable -s variable.save

* To restore variables from the file 'efi.save':

fs0:\> variable -r

* To restore variables from the file 'variable.save':

fs0:\> variable -r variable.save

* To dump variables from memory:

fs0:\> variable -d

* To dump variables from the file 'variable.save':

fs0:\> variable -d variable.save

Cookbook: Recovering Boot Options on IPF. Created by Sal Omar UKRCE. Version 3.4 9/7/2010 page 72 of 72

Document History:

Version 1 initial release 27/6/05

Version 2 included detection of fc disks released 22/7/05
Version 3 included Appendix A for setting scan level on an A6826a Dual Port FC card.
Version 3.1 included ODE notes & modified ACPI for LINUX 5/9/05
Version 3.2 included ‘Luns Per Target’ on A6826a card, from Holger Goetker GRC 30/3/06.
Version 3.3 included Windows 2008 boot options recovery 06/09/10.
Version 3.4 included comments on NVRAMBKP and Variable commands 06/09/10.

Return to Top of Boot Recovery Cookbook