Skip Navigation Links | |
Exit Print View | |
Oracle Hardware Installation Assistant 2.5 User's Guide for x86 Servers |
Overview of the Oracle Hardware Installation Assistant User's Guide
Getting Started With Oracle Hardware Installation Assistant
What is Oracle Hardware Installation Assistant?
Supported Provisioning Tasks List
Launching the Application and Performing Provisioning Tasks
Local and Remote Media Launch Options for Sun Fire and Sun Blade Servers
How to Perform Provisioning Tasks
How to Install Windows Using Local or Remote Media
How to Install Linux Using Local or Remote Media
Updating System and Component Firmware
How to Update the System BIOS and Oracle ILOM Firmware
How to Update Expander Firmware
Recovering a Service Processor
How to Recover a Service Processor
Configuring Service Processor Settings
How to Configure Service Processor Identification Information Settings
How to Configure Network Information Settings
How to Manage Oracle ILOM User Accounts
Configuring BIOS Boot Device Settings
How to Set the Boot Device Order
How to Set the Boot Device for the Next Boot
Setting Up PXE-Based Oracle Hardware Installation Assistant
How to Set Up the PXE Infrastructure
Preparing the Oracle Hardware Installation Assistant PXE Image Files
Launching an Attended PXE-Based Session
Attended PXE-Based Session Overview
How to Create the Image for a PXE-Based Session
How to Launch an Attended Installation From a PXE Server
Performing Unattended PXE-Based Provisioning Tasks
Unattended PXE-Based Provisioning Tasks Requirements
Creating a State File for Unattended Installation
How to Prepare for an Unattended Installation of Linux
How to Prepare for an Unattended Installation of Windows Server
How to Prepare for an Unattended Firmware Update
How to Create the Application Image and Prepare for a PXE-Based Launch
How to Launch an Unattended Session From a PXE-Based Server
Observing Unattended PXE-Based Provisioning Tasks
Establishing a Viewing Connection Using a Virtual Console or Secure Shell (SSH) Connection
How to Set Up Root and VNC Passwords
How to Establish a Connection Using a VNC Viewer
How to Establish a Connection Using a Serial Console
Troubleshooting Oracle Hardware Installation Assistant
No Driver Found Message Appears During Oracle VM 2.2.1 Server Installation
Oracle Hardware Installation Assistant Can Go Into a Loop at Last OS Install Screen
Oracle Hardware Installation Assistant Error Messages
How to View the Application Log File
How to Debug a PXE Image That Does Not Boot
Launching Oracle Hardware Installation Assistant Using a USB Flash Drive
How to Get the Syslinux and Oracle Hardware Installation Assistant Software
Creating an Oracle Hardware Installation Assistant USB Flash Drive
How to Prepare an Oracle Hardware Installation Assistant USB Flash Drive With Windows Autorun
How to Boot the USB Flash Drive and Launch Oracle Hardware Installation Assistant
How to Install Service Tags in Linux
Before You Begin
This procedure requires the use of parted utility version 1.8.6 or later. Do not use earlier versions of parted.
You should have already downloaded the Syslinux and Oracle Hardware Installation Assistant archive files. See How to Get the Syslinux and Oracle Hardware Installation Assistant Software.
# tar -zxvf /path/syslinux-version.tar.gz
where path is the path to the directory that contains the Syslinux archive file and version is the Syslinux version number.
# tail /var/log/messages
You should see the device name (such as, sda or sdb). Example output is shown below:
Nov 12 13:19:29 server kernel: scsi 4:0:0:0: Lexar, Inc. USBdisk PQ: 0 ANSI: 0 CCS Nov 12 13:19:29 server kernel: sd 4:0:0:0: [sdb] 1030750208 512-byte hardware sectors (1030 MB) Nov 12 13:19:29 server kernel: sd 4:0:0:0: [sdb] Write Protect is off Nov 12 13:19:29 server kernel: sd 4:0:0:0: [sdb] Assuming drive cache: write through Nov 12 13:19:29 server kernel: sdb: Nov 12 13:19:29 server kernel: sd 4:0:0:0: [sdb] Attached SCSI removable disk Nov 12 13:19:29 server kernel: sd 4:0:0:0: Attached scsi generic sg2 type 0
Caution - Possible unintentional data loss. Be sure to confirm and make a note of the device name of the USB flash drive (/dev/sda, /dev/sdb). The instructions listed here require you to delete existing partition(s) on the USB flash disk. Making a mistake in identifying the device might cause you to erase a hard disk. |
Note - This procedure requires the use of parted utility version 1.8.6 or later. Do not use earlier versions of parted.
Note - These steps require superuser (su - root) access.
# umount /dev/sdX1
where X is the drive letter for the USB flash drive (for example, /dev/sda or /dev/sdb), and 1 indicates the first partition.
# /sbin/parted /dev/sdX
where X is the drive letter for the USB flash drive (for example, /dev/sda or /dev/sdb).
The parted command prompt appears.
(parted): mklabel
You are prompted to create a disk label type. If msdos is not listed as the default, you need to enter msdos at the appropriate prompt, as shown in the example below:
Warning: The existing label on sdx will be destroyed and all data on this disk will be lost. Do you want to continue? Yes/No: yes New disk label type? msdos
(parted): mkpartfs
Creates a new partition on the disk. Answer the prompts to confirm that this is the primary partition, fat32 format, spanning the entire disk minus the last megabyte (starting at 1, and ending at -1). Example output is shown below:
Partition type? primary/extended? primary File system type? [ext2] fat32 Start? 1 End? -1
(parted): set 1 boot on
Sets the boot flag for this partition.
(parted): set 1 lba on
Sets the lba (Linear Block Addressing) flag for this partition.
(parted): print
Displays the current settings for the new partition. Example output is shown below:
Model: Lexar, Inc. USBdisk (scsi) Disk /dev/sdb: 1031MB Sector size (logical/physical): 512B/512B Partition Table: msdos Minor Start End Size Type Filesystem Flags 1 16.4kB 931MB 1031MB primary fat32 boot, lba (parted)
(parted): quit
Quits the parted utility.
# cd path/mbr
where path is the directory to which you extracted Syslinux.
# cat mbr.bin > /dev/sdX
where X is the drive letter for the USB flash drive (for example, /dev/sda or /dev/sdb).
# mkfs.vfat -n OHIA /dev/sdX1
where X is the USB device identifier (for example, /dev/sda or /dev/sdb) and 1 indicates the first partition.
# cd path/unix
where path is the directory to which you extracted Syslinux.
Note - For later versions of Syslinux, the unix directory might be replaced with a linux directory. If so, replace the unix directory name with linux.
# ./syslinux /dev/sdX1
where X is the drive letter for the USB flash drive (for example, /dev/sda or /dev/sdb), and 1 indicates the first partition.
Note - In the next step you need to specify the mount point. If autofs is running, it might have auto–mounted the drive partition to some other mount point. If this happens, unmount it by entering the command:
umount /dev/sdX1
# mount -t vfat /dev/sdX1 /mnt
where X is the drive letter for the USB flash drive (for example, /dev/sda or /dev/sdb), and 1 indicates the first partition. For this example, the mount point is /mnt.
# unzip -q -d /mnt ~/path/HIA-version-usb.zip -x “source/*”
where path represents the path to the directory where the .zip file is located, and version represents the Oracle Hardware Installation Assistant version number. The “source/*” parameter excludes the any source files from the extraction to save time and disk space.
# umount /mnt
The USB flash drive is now ready to boot the Oracle Hardware Installation Assistant application.
Next Steps
How to Boot the USB Flash Drive and Launch Oracle Hardware Installation Assistant