RHEL 6.2 install image with 2 ISO images

Latest response

There is a "deadly embrace" that occurs during install of RHEL 6.2. One ISO image /dev/sdb is only
the boot image and get's the install started. Then you tell the install about ISO #2 the burned Install
image, but the silly install program can no longer find vmliniz.img once it has found ISO #2, which is
Read Only so you can't just copy the kernel image onto it. No choice in the menue, that we could find
would successfully complete the install, each one crashes the entire install and you have to start over.

Can anyone explain how to make this work please?

Thank You!!!

Responses

The issue here is the HP DL-380 server. When I install RHEL 6/2 in VMware or
on my notebook it sees the boot media as /dev/sda and the install media as /dev/sdb1. On the DL-380 they are /dev/sdb and /dev/sdb1, I imagine the
kernel does a chroot when you chose the Instalation media, which doesn't contain the required vmliniz image.

Hi Damon,
Have you considered an HTTP or NFS based install? I know this doesn't address your question and I apologize. A few other options I can think of, boot-floppy or bootable-USB.

Depending on how many builds you will need to perform, I feel that a HTTP installation would be worth the effort of setting up. Best yet would be a PXE environment, but that's a bit of a commitment there.

James, Thanks for the suggestion. No apology necessary! Always grateful
for another option.

I have been doing CentOS and Fedora, but am new to RHEL subscriptions. I
imagine it is because we are having to redo the install over a few times,
we got the error, "you are oversubscribed"... BUT we bought 2 PREMIUM
subscriptions, and there is only one server, same hostname, Presumably new hostid each install.

If we fully delete the old registrations, and subscriptions will we get back my two PREMIUM registration capabilities?

Thanks

The installation is independent of the number of subscriptions you have. I.e. you could build EVERY system in your data center with RHEL, you just can't update them ;-)

To answer your question: I believe you need to remove the consumed entitlement if you rebuild the system (or fully delete ;-)

You are correct though, every time that you register your system to RHN it will consume an entitlement. (I personally am still a bit new to subscriptions and use RHN classic mostly). I have come across an entitlement option for Satellite (under Kickstart Profile | System Details | Details), which may apply to RHN as well:

RHN Satellite Profile:  If a RHN Satellite system profile already exists for a re-provisioned system outside of the RHN Satellite UI:
* Re-connect to the existing system profile. Do not create a new system profile.
* Delete the existing system profile and create a new system profile.
* Leave the existing system profile in place, but do not re-connect to it. Instead, create a new system profile. 

So - hopefully I understood the question correctly. There probably is an API call to remove the existing entitlement at RHN when you rebuild your system (I too spent time rebuilding systems and had to do everything manually).

In my home lab, I download the ISO to a system running DHCP/PXE/DNS/HTTP.
I mount the ISO to a directory in a web accessible location (/var/www/html/OS/RHEL-6.4-x86_64)
I upload a kickstart file to the web server (with url pointing to the web dir where the ISO is shared).
You don't even need PXE/DHCP. You can boot from the install DVD and hit tab when the menu appears, then use the following:

 vmlinuz initrd=initrd.img hostname=hostname.blah ip=192.168.0.100 netmask=255.255.255.0 gateway=192.168.0.100 dns=192.168.0.2 ks=http://ip.of.webserver/hostname.ks
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.