rx2620 boot problem after system bd replacement

[alex_971]

Hi,
I've replaced the system board on rx2620, but now on EFI interface I have not the path to boot from hd
configuration:
SA6400
qty 2 hdd raid 1
win2003srv

how can I solve the problem?
this product is new form me, and I don't know it!!!

[Torsten.]

The boot entries are stored on system board.

New board = no entries.

I assume you don't have a backup ...

Select the disk to boot from, e.g.

fs0:

run

\EFI\HPUX\HPUX.EFI

and use "setboot" to configure the pathes.

[kris rombauts]

Hi Alex,

since this is a Windows OS, there should be a copy of the boot file on the EFI partition.
Do this:

- go to EFI partition i.e. fs0:
- cd efi\microsoft\winnt50
- 'ls' or 'dir' command and check for a file called 'boot000x (x= a number like 3 i.e.)

i.e. :

fs0:\EFI\Microsoft\WINNT50> ls
Directory of: fs0:\EFI\Microsoft\WINNT50

01/09/09 04:27p 1,024 .
01/09/09 04:27p 1,024 ..
01/09/09 03:41p 378 Boot0007
1 File(s) 378 bytes
2 Dir(s)




- go to \msutil and run the command nvrboot
- choose I (import) and provide the path to the boot file and the filename i.e.

efi\microsoft\winnt50\boot0007


- exit the nvrboot utility
- exit to the EFI boot menu and all entries should be back and you should be able to boot just fine.


If the boot file is not present you can do this:

- log a call with HP to re-create the boot file of this server. This can be done, it just requires some binary tools and a reload of the file on your system.

- re-install the original sysboard (assuming it still works a bit) and take a copy of the variables and boot menu using the utility you can download here :

http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&prodTypeId=15351&prodSeriesId=88837&prodNameId=346361&swEnvOID=1060&swLang=13&mode=2&taskId=135&swItem=ux-71170-1

http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&prodTypeId=15351&prodSeriesId=88837&prodNameId=346361&swEnvOID=1060&swLang=13&mode=2&taskId=135&swItem=ux-71170-1

Then install the new sysboard and Import the bootfile like in the first scenario.


One of the above options will fix your issue, there is no reason to reinstall the Windows OS i.e. it is just missing a pointer to where it needs to get the OS.


HTH

Kris