topic Re: Windows Boot Manager for BL860c in Integrity Servers

Windows Boot Manager for BL860c

marcj — Wed, 25 Feb 2009 01:04:55 GMT

Hi everyone,

I replace a systemboard for Integrity BL860c because of intermittent video problem (green screen). After the replacement, tried to boot the server but it could not find the hard drive. I look at the RAID configuration, the array was inactive. I reactivate the array and go back to EFI boot configuration menu. Add new boot entry and point to the HDD. When I boot the new loaded boot entry, It won't boot because it could not find the windows system file.

The operating system installed on this machine is Windows 2008 for Itanium. When I tried to reinstall the old systemboard, the it boots up to windows.

How do I input the boot load option in adding a new boot entry? Could anyone provide a step by step guide on how would I configure the server with the new system board?

Thanks!

Re: Windows Boot Manager for BL860c

Torsten. — Wed, 25 Feb 2009 04:27:27 GMT

I hope this helps:

http://docs.hp.com/en/13558/win_recovery_2003.pdf

Re: Windows Boot Manager for BL860c

marcj — Wed, 25 Feb 2009 05:37:44 GMT

Is it possible to copy the boot entry of server with old systemboard installed and paste the copied boot entry after the installation of new systemboard?

Re: Windows Boot Manager for BL860c

Torsten. — Wed, 25 Feb 2009 06:10:42 GMT

Have a look at nvrboot utility.

Re: Windows Boot Manager for BL860c

Torsten. — Wed, 25 Feb 2009 06:13:44 GMT

Re: Windows Boot Manager for BL860c

marcj — Wed, 25 Feb 2009 07:20:54 GMT

How would I do it?

Re: Windows Boot Manager for BL860c

Torsten. — Wed, 25 Feb 2009 07:38:10 GMT

http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&prodTypeId=3709945&prodSeriesId=3331044&swItem=ux-65542-1&prodNameId=3331045&swEnvOID=54&swLang=13&taskId=135&mode=4&idx=0

backup the config to a file, swap the board and restore the config to the NVRAM.

Re: Windows Boot Manager for BL860c

marcj — Wed, 25 Feb 2009 07:41:05 GMT

Do I need to run the said utility with the old systemboard installed? How would i backup the nvram database?

Re: Windows Boot Manager for BL860c

marcj — Wed, 25 Feb 2009 07:43:32 GMT

Thanks! I will to do this and feedback you soon.

Re: Windows Boot Manager for BL860c

Torsten. — Wed, 25 Feb 2009 07:44:35 GMT

Did you read the page?

...
OS Independent - Running the Utility from the EFI Shell For general information about using EFI, refer to the "Operation and Maintenance Guide".
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.
Type "fs0:", then press ENTER.
Locate the file "nvrambkp.efi" on the file system and enter one of the following commands, where is the name of the NVRAM archive database and is the name of the log file created:
Archive:
"nvrambkp -a -l "

Restore All:
"nvrambkp -r -l "

Restore Boot-Options Only:
"nvrambkp -o -r -l "

Validate Restore Database on the current server:
"nvrambkp -v -r -l "

Information about the Restore Database:
"nvrambkp -i -r -l "

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

Re: Windows Boot Manager for BL860c

marcj — Thu, 26 Feb 2009 06:04:14 GMT

Correct me if I'm wrong. These are the steps I will do:
---Windows - Loading the Non-Volatile RAM Utility onto the EFI partition

1. Click "Start" on the taskbar, then click "Run..."
2. Type "cmd", then press ENTER. A command prompt window opens
3. Type "mountvol z: /s", then press ENTER. "z" can be replaced with any available drive letter in your system.
4. Download the firmware update package "nvrambkp_010301EFI.tar.gz" and unpack it to obtain the "nvrambkp.efi". Save "nvrambkp.efi" in z:\
5. Reboot the system to "EFI Boot Manager"; see next step.
6. When the "EFI Boot Manager" menu appears, use the arrow keys to highlight the entry "EFI Shell [Built-in]", then press ENTER to select it. The selection must be made within the timeout period displayed on the screen.
7. The "Device mapping table" will be displayed.

---# 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.
# Type "fs0:", then press ENTER.
# Locate the file "nvrambkp.efi" on the file system and enter one of the following commands, where is the name of the NVRAM archive database and is the name of the log file created:

Archive:
"nvrambkp -a -l "

----Shutdown the Server then install the new Systemboard...

----Restore All:
"nvrambkp -r -l "

Restore Boot-Options Only:
"nvrambkp -o -r -l "

Validate Restore Database on the current server:
"nvrambkp -v -r -l "

Information about the Restore Database:
"nvrambkp -i -r -l "

One question again....Where would I save the NVRAM Database during backup?

Re: Windows Boot Manager for BL860c

Torsten. — Thu, 26 Feb 2009 06:12:14 GMT

Steps look good.

You may consider to store the util directly on a usb stick together with the config.

But it will be fine too to store the config on the disk (fs0:), because you keep the disks.

Re: Windows Boot Manager for BL860c

marcj — Thu, 26 Feb 2009 06:15:37 GMT

Ok...Thank you so much. I will just save the nvram configuration file directly to the hdd drive (fs0).

Re: Windows Boot Manager for BL860c

marcj — Mon, 02 Mar 2009 06:37:23 GMT

It works good...Thanks a lot

Re: Windows Boot Manager for BL860c

kris rombauts — Mon, 02 Mar 2009 09:42:00 GMT

Marcj,

to late now but HP has a video controller firmware fix for the "green" screen issue on BL860C.

In case the issue comes back with the newly installed systemboard, pls open a HP support call and let them provide you the video controller BIOS to address this video issue, a systemboard replacement was not needed.
This video BIOS is not available on hp.com, it is provided on a case by case basis after investigation has been made to see if the issue is really the one that is addressed in the special BIOS release since only few board can face this specific issue.

Kris