Sponsored Content
Operating Systems HP-UX Map EFI Internal Bootable DVD Post 302721595 by rwuerth on Thursday 25th of October 2012 02:49:04 PM
Old 10-25-2012
I have old information on this, but supposedly the EFI boot manager should automatically scan for bootable devices prior to presenting you with the boot menu. Assuming you used the same DVD on both systems and one lists the DVD at bootable and one does not, I would surmise that the problem may lie with the DVD player itself of the system that does not list the DVD as bootable when the Installation DVD is installed.

Last edited by rwuerth; 10-25-2012 at 03:51 PM.. Reason: clarified where I meant DVD player.
 

8 More Discussions You Might Find Interesting

1. Solaris

iso files to make bootable dvd image

Hey all, I'm a newbie to iso files and I just downloaded the 2 iso files for *cough* ms2003 R2 *cough* trial software. After I downloaded the iso files I just dragged them to my burn software gui and sure enough it burned to dvd 2 iso files. When I attempted to boot the image using VMware... (0 Replies)
Discussion started by: bdsffl
0 Replies

2. Solaris

Getting NFSv4 prompt when installing bootable DVD

Hi, I've created a bootable DVD which works fine for earlier versions of Solaris 10 (6/06) and Solaris 9. But now i've moved to Solaris 10 8/07 and I am getting the NFSv4 prompt at login. Initially i thought i could surpress this by adding the line nfs4_domain=dynamic to my... (0 Replies)
Discussion started by: declanryan
0 Replies

3. AIX

How to burn a bootable DVD on aix 5.3?

I have a mksysb backup image need burn to a DVD, then it can be used to restore OS in other machine. How to do this? (5 Replies)
Discussion started by: rainbow_bean
5 Replies

4. Solaris

bootable X86 dvd and flash archives

I have created a bootable DVD for X86 using a flash archive, the problem is that I have to specify the location at the beginning of the install. I have edited the any_machine profile under ./jumpstart_sample to contain the following install_type flash_install archive_location ... (4 Replies)
Discussion started by: eeisken
4 Replies

5. Solaris

Help me, please! Solaris 10 hands-off installation from a bootable DVD

Hello, I have a problem with installing the Solaris 10 using a bootable DVD with a flar archive. I want this installation to be totally hands-off, but unfortunately after I run this boot command at the ok prompt: ok boot cdrom - install ... the system is rebooted and the interactive... (5 Replies)
Discussion started by: Przemek
5 Replies

6. Linux

Creating a bootable dvd/cd disk

Hi all, thanks for so many helps in many problems! Can anyone guide, how to create a bootable cd/dvd from downloaded iso images of CentOS 5? I have collected all the iso in a dvd but it is not booting the system. Any response will be appreciable... (2 Replies)
Discussion started by: naw_deepak
2 Replies

7. AIX

Using mkdvd to create bootable mksysb on dvd reports success but nothing on dvd?

Hello, Running AIX 7.1 7100-00-03-1115, trying to make a mksysb image to a dvd drive using mkdvd. My final command looks like this.. mkdvd -e -V rootvg -R -C /usr1/AIXADMIN/mkcd/cd_fs -I /usr1/AIXADMIN/mkcd/cd_images -M /usr1/AIXADMIN/mkcd/mksysbimage -d /dev/cd0 -Y When i run this... (3 Replies)
Discussion started by: c3rb3rus
3 Replies

8. AIX

Can I use mkdvd to create bootable DVD from mksysb on tape

Hi, Is it possible to use mkdvd to create a bootable DVD using a mksysb on tape as the source image? On the system concerned, we don't have enough free space to create the mksysb to file first, so would like to use the existing tape mksysb backup. The DVD disk/s will then be used to boot a... (4 Replies)
Discussion started by: alanp36
4 Replies
vparefiutil(1M) 														   vparefiutil(1M)

NAME
vparefiutil - display, update, or delete HP-UX hardware path to EFI path mappings of bootable disks in the virtual partition database SYNOPSIS
db_file] hw_path] DESCRIPTION
The command displays the HP-UX hardware path to EFI path mappings that are stored in the virtual partition database. Legacy and agile hardware paths will be displayed, if available, as provided by HP-UX. If the virtual partition database is not specified, then the live database or by default is used. It can also be used to update the hw_path to EFI_path mappings from to the database. The behavior without any options is to display the HP-UX hardware path to EFI path mappings. This command is not supported on PA-RISC systems. Options and Arguments recognizes the following command line options and arguments: Specifies the alternate database from which the HP-UX hardware path to EFI path mappings need to be displayed, updated, or deleted. or live is default if this is not specified. Updates the database from the info available (from Displays the HP-UX hardware path to EFI path mapping in machine readable format. Each mapping is displayed in a separate line as follows: Deletes the HP-UX hardware path to EFI path mappings in the database. Note: In live database, this deletes only the HP-UX hardware paths owned by the vpar on which this command is executed. If this is specified, only the HP-UX hardware paths at or below the given hw_path are displayed, updated, or deleted. SECURITY RESTRICTIONS
This command is restricted to processes owned by superuser. RETURN VALUE
returns the following values: Successful completion. Error condition occurred. EXAMPLES
Display the hw_path to EFI_path mappings from the live database. # vparefiutil Hardware path - EFI path mapping ================================ Hardware path : 2.0.0.2.0.6.0 : 2.0.0.2.0.6.0 EFI path : Acpi(HWP0002,200)/Pci(2|0)/Scsi(Pun6,Lun0)/EFIHPUXHPUX.EFI Hardware path : 2.0.0.3.0.6.0 : 2.0.0.3.0.6.0 EFI path : Acpi(HWP0002,200)/Pci(3|0)/Scsi(Pun6,Lun0)/ HD(Part1,Sig471031FC-6A12-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI Hardware path : 2.0.0.3.1.2.0 : 2.0.0.3.1.2.0 EFI path : Acpi(HWP0002,200)/Pci(3|1)/Scsi(Pun2,Lun0)/EFIHPUXHPUX.EFI Hardware path : 2.0.8.1.0.3.4.0.0.1.6 : 2.0.8.1.0.0x50001fe1500339ed.0x1000000000000 EFI path : Acpi(HWP0002,28C)/Pci(1|0)/Pci(4|0)/ Fibre(WWN50001FE1500339ED,Lun1000000000000)/ HD(Part1,Sig9FEF4B40-6AC7-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI Hardware path : 2.0.12.1.0.4.1.8.0 : EFI path : Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/Scsi(Pun8,Lun0)/ HD(Part1,Sig00F95EE2-66C4-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI Hardware path : 2.0.12.1.0.4.1.10.0 : EFI path : Acpi(HWP0002,2C6)/Pci(1kk0)/EFIHPUXHPUX.EFI Hardware path : 2.0.12.1.0.4.1.12.0 : EFI path : Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/Scsi(PunC,Lun0)/ HD(Part1,Sig4D70B9D6-6AD5-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI # vparefiutil Hardware path - EFI path mapping ================================ Hardware path : 2.0.0.2.0.6.0 : EFI path : Acpi(HWP0002,200)/Pci(2|0)/Scsi(Pun6,Lun0)/EFIHPUXHPUX.EFI Hardware path : 2.0.0.3.0.6.0 : EFI path : Acpi(HWP0002,200)/Pci(3|0)/Scsi(Pun6,Lun0)/ HD(Part1,Sig471031FC-6A12-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI Hardware path : 2.0.0.3.1.2.0 : EFI path : Acpi(HWP0002,200)/Pci(3|1)/Scsi(Pun2,Lun0)/EFIHPUXHPUX.EFI Hardware path : 2.0.8.1.0.3.4.0.0.1.6 : 2.0.8.1.0.0x50001fe1500339ed.0x1000000000000 EFI path : Acpi(HWP0002,28C)/Pci(1|0)/Pci(4|0)/ Fibre(WWN50001FE1500339ED,Lun1000000000000)/ HD(Part1,Sig9FEF4B40-6AC7-11D9-8002-D6217B60E588)/ EFIHPUXHPUX.EFI Hardware path : 2.0.12.1.0.4.1.8.0 : EFI path : Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/Scsi(Pun8,Lun0)/ HD(Part1,Sig00F95EE2-66C4-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI Hardware path : 2.0.12.1.0.4.1.10.0 : EFI path : Acpi(HWP0002,2C6)/Pci(1kk0)/EFIHPUXHPUX.EFI Hardware path : 2.0.12.1.0.4.1.12.0 : EFI path : Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/Scsi(PunC,Lun0)/ HD(Part1,Sig4D70B9D6-6AD5-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI Display the hw_path to EFI_path mappings from the alternate database in machine readable format. # vparefiutil -M -D vpdb_foo 2.0.0.2.0.6.0:Acpi(HWP0002,200)/Pci(2|0)/Scsi(Pun6,Lun0)/EFIHPUXHPUX.EFI::2.0.0.2.0.6.0 2.0.0.3.0.6.0:Acpi(HWP0002,200)/Pci(3|0)/ Scsi(Pun6,Lkk6A12-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI::2.0.0.3.0.6.0 2.0.0.3.1.2.0:Acpi(HWP0002,200)/Pci(3|1)/Scsi(Pun2,Lun0)/EFIHPUXHPUX.EFI::2.0.0.3.1.2.0 2.0.8.1.0.3.4.0.0.1.6:Acpi(HWP0002,28C)/Pci(1|0)/Pci(4|0)/ Fibre(WWN50001FE1500339ED,Lun1000000000000)/ HD(Part1,Sig9FEF4B40-6AC7-11D9-8002-D6217B60E588)/ EFIHPUXHPUX.EFI::2.0.8.1.0.0x50001fe1500339ed.0x1000000000000 2.0.12.1.0.4.1.8.0:Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/Scsi(Pun8,Lun0)/ HD(Part1,Sig00F95EE2-66C4-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI:: 2.0.12.1.0.4.1.10.0:Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/Scsi(PunA,Lun0)/ EFIHPUXHPUX.EFI:: 2.0.12.1.0.4.1.12.0:Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/Scsi(PunC,Lun0)/ HD(Part1,Sig4D70B9D6-6AD5-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI:: # vparefiutil -M -D vpdb_foo 2.0.0.2.0.6.0:Acpi(HWP0002,200)/Pci(2|0)/Scsi(Pun6,Lun0)/EFIHPUXHPUX.EFI:: 2.0.0.3.0.6.0:Acpi(HWP0002,200)/Pci(3|0)/ Scsi(Pun6,Lkk6A12-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI:: 2.0.0.3.1.2.0:Acpi(HWP0002,200)/Pci(3|1)/Scsi(Pun2,Lun0)/EFIHPUXHPUX.EFI:: 2.0.8.1.0.3.4.0.0.1.6:Acpi(HWP0002,28C)/Pci(1|0)/Pci(4|0)/ Fibre(WWN50001FE1500339ED,Lun1000000000000)/ HD(Part1,Sig9FEF4B40-6AC7-11D9-8002-D6217B60E588)/ EFIHPUXHPUX.EFI::2.0.8.1.0.0x50001fe1500339ed.0x1000000000000 2.0.12.1.0.4.1.8.0:Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/Scsi(Pun8,Lun0)/ HD(Part1,Sig00F95EE2-66C4-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI:: 2.0.12.1.0.4.1.10.0:Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/ Scsi(PunA,Lun0)/EFIHPUXHPUX.EFI:: 2.0.12.1.0.4.1.12.0:Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/Scsi(PunC,Lun0)/ HD(Part1,Sig4D70B9D6-6AD5-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI:: Delete the HP-UX hardware-path paths to EFI path mappings at or below the HP-UX hardware path 2/0/0/3 of the current vpar. # vparefiutil -d -H 2/0/0/3 # vparefiutil Hardware path - EFI path mapping ================================ Hardware path : 2.0.0.2.0.6.0 : EFI path : Acpi(HWP0002,200)/Pci(2|0)/Scsi(Pun6,Lun0)/EFIHPUXHPUX.EFI Hardware path : 2.0.8.1.0.3.4.0.0.1.6 : 2.0.8.1.0.0x50001fe1500339ed.0x1000000000000 EFI path : Acpi(HWP0002,28C)/Pci(1|0)/Pci(4|0)/ Fibre(WWN50001FE1500339ED,Lun1000000000000)/ HD(Part1,Sig9FEF4B40-6AC7-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI Hardware path : 2.0.12.1.0.4.1.8.0 : EFI path : Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/Scsi(Pun8,Lun0)/ HD(Part1,Sig00F95EE2-66C4-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI Hardware path : 2.0.12.1.0.4.1.10.0 : EFI path : Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/Scsi(PunA,Lun0)/ EFIHPUXHPUX.EFI Hardware path : 2.0.12.1.0.4.1.12.0 : EFI path pdb|0)/Pci(4|1)/Scsi(PunC,Lun0)/ HD(Part1,Sig4D70B9D6-6AD5-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI # vparefiutil -d -H 2/0/0/3 # vparefiutil Hardware path - EFI path mapping ================================ Hardware path : 2.0.0.2.0.6.0 : EFI path : Acpi(HWP0002,200)/Pci(2|0)/Scsi(Pun6,Lun0)/EFIHPUXHPUX.EFI Hardware path : 2.0.8.1.0.3.4.0.0.1.6 : 2.0.8.1.0.0x50001fe1500339ed.0x1000000000000 EFI path : Acpi(HWP0002,28C)/Pci(1|0)/Pci(4|0)/ Fibre(WWN50001FE1500339ED,Lun1000000000000)/ HD(Part1,Sig9FEF4B40-6AC7-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI Hardware path : 2.0.12.1.0.4.1.8.0 : EFI path : Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/Scsi(Pun8,Lun0)/ HD(Part1,Sig00F95EE2-66C4-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI Hardware path : 2.0.12.1.0.4.1.10.0 : EFI path : Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/ Scsi(PunA,Lun0)/EFIHPUXHPUX.EFI Hardware path : 2.0.12.1.0.4.1.12.0 : EFI path pdb|0)/Pci(4|1)/Scsi(PunC,Lun0)/ HD(Part1,Sig4D70B9D6-6AD5-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI For Serial Attach SCSI (SAS) devices, the SAS address is displayed along with the hardware path and the EFI path. Hardware path : 0.0.14.0.0.0.0.0.0.2.0 EFI path : Acpi(HPQ0002,PNP0A08,E)/Pci(0|0)/Pci(0|0)/ VenMsg(D487DDB4-008B-11D9-AFDC-001083FFCA4D)/ HD(Part1,SigC6B41C20-01BE-11DC-8000-D6217B60E588)/EFIHPUXHPUX.EFI SAS Address : 0x500000e01200d3f2 The SAS hardware path can potentially change from one OS instance to another, but the SAS address will remain the same. To locate SAS devices in different OS instances (for example, an nPar OS instance and a vPar OS instance), use the SAS address instead of the hardware path. WARNING
The option is provided only to remove the stale HP-UX hardware path to EFI path mappings. If you remove the valid HP-UX hardware path to EFI path mappings, you may not be able to load vpars. It is always better to follow the operation with a operation to update the database with the valid HP-UX hardware path to EFI path mappings available from AUTHOR
was developed by the Hewlett-Packard Company. SEE ALSO
vparadmin(1M), vparboot(1M), vparconfig(1M), vparcreate(1M), vpardump(1M), vparenv(1M), vparextract(1M), vparmodify(1M), vparreloc(1M), vparremove(1M), vparreset(1M), vparstatus(1M), vparutil(1M), privileges(5), vparresources(5), vpartition(5), vpmon(5). Itanium(R)-Based Systems vparefiutil(1M)
All times are GMT -4. The time now is 07:58 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy