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
efi(4)							     Kernel Interfaces Manual							    efi(4)

NAME
efi - Extensible Firmware Interface description DESCRIPTION
The EFI (Extensible Firmware Interface) is an interface between HP-UX and the Itanium-based platform firmware. The file system supported by the Extensible Firmware Interface is based on the FAT file system. EFI encompasses the use of FAT-32 for a system partition, and FAT-12 or FAT-16 for removable media. The system partition is required on a bootable disk for the Itanium-based platform. For a hard disk, the system partition is a contiguous grouping of sectors on the disk, where the starting sector and size are defined by the EFI partition table, which resides on the second logical block of the hard disk, and/or by the Master Boot Record (MBR), which resides on the first sector of the hard disk. For a floppy disk, a partition is defined to be the entire disk. The System Partition can contain directories, data files, and EFI Images. The EFI system firmware may search the directory of the EFI sys- tem partition, EFI volume, to find possible EFI Images that can be loaded. The HP-UX bootloader is one example of an EFI Image. HP-UX contains a set of EFI utilities: efi_fsinit(1M) Initialize an EFI volume; that is, create a header and an empty directory. efi_cp(1M) Copy files to and from an EFI volume. efi_mkdir(1M) Create directories in an EFI volume. efi_ls(1M) List the contents of an EFI volume. efi_rm(1M) Remove files from an EFI volume. efi_rmdir(1M) Remove directories from an EFI volume. The EFI utilities are the only utilities in HP-UX where the internal structure of an EFI volume is known. To the rest of HP-UX, an EFI system partition is simply a partition containing unspecified data. The EFI volume cannot be mounted to HP-UX currently. An EFI volume can be created on any HP-UX file (either regular disk file or device special file) that supports random access via lseek(2). Within an EFI volume, individual files and directories are identified by 1- to 255-character file names. File names can consist of any alphanumeric characters (A through Z, a through z, and 0 through 9) and the certain set of special characters (. $ % ' - _ @ ~ ` ! ( ) + , : ; = # & ? ^ [ ] { } space). The first character of an EFI file name can be any valid EFI characters, except the space. When comparing two EFI names, differences in the case of alphabetic characters are not significant. For example, the following file names are considered the same: If one exists, the user will not be able to create the other. The directory may be made up of multiple components, separated by slashes(/). The last directory component must be followed by a slash to separate it from the file name. There are two special directory components, (.) and (..). They represent the current directory and the parent directory as in other file systems. SEE ALSO
efi_cp(1M), efi_fsinit(1M), efi_ls(1M), efi_mkdir(1M), efi_rm(1M), efi_rmdir(1M). Itanium(R)-Based Processor Family Only efi(4)
All times are GMT -4. The time now is 10:34 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy