Cannot ignore software not registered during RHEL9 installation
Quote from Deleted user on 2022-06-22, 3:50 AMWith brand new made USB flash by Easy2Boot 2.13
Put RHEL9 enterprise iso into the ISO/LINUX folder
Could boot into Easy2Boot and select RHEL9 enterprise iso to install
But it appear software is not registered and unable to ignore it
It won't appear if make this ISO by Rufus 3.18 dd mode
With brand new made USB flash by Easy2Boot 2.13
Put RHEL9 enterprise iso into the ISO/LINUX folder
Could boot into Easy2Boot and select RHEL9 enterprise iso to install
But it appear software is not registered and unable to ignore it
It won't appear if make this ISO by Rufus 3.18 dd mode
Quote from SteveSi on 2022-06-22, 6:14 AMHi
I registered on Redhat site for an account. redhat.com
I signed up for Beta RHEL 9 and downloaded ISO and added to E2B drive and made contiguous.
Then booted to rhel-baseos-9.0-x86_64-dvd.iso on VBOX VM from Easy2Boot USb drive (UEFI64).
I completed install using username and password of my registered account
and installed to virtual hard disk
it said 'Downloading 1174 RPMS' - 'Preparing transaction from installation source'
It seems to be installing OK...
Install completed. I can now boot to Red Hat from virtual hard disk.
P.S. Also works under Ventoy and E2B legacy boot on a real system.
Hi
I registered on Redhat site for an account. redhat.com
I signed up for Beta RHEL 9 and downloaded ISO and added to E2B drive and made contiguous.
Then booted to rhel-baseos-9.0-x86_64-dvd.iso on VBOX VM from Easy2Boot USb drive (UEFI64).
I completed install using username and password of my registered account
and installed to virtual hard disk
it said 'Downloading 1174 RPMS' - 'Preparing transaction from installation source'
It seems to be installing OK...
Install completed. I can now boot to Red Hat from virtual hard disk.
P.S. Also works under Ventoy and E2B legacy boot on a real system.
Quote from Deleted user on 2022-06-22, 10:12 AMWith Rufus 3.18 dd mode, the installation won't be blocked if I don't give redhat account password.
Not sure what's the difference between them
With Rufus 3.18 dd mode, the installation won't be blocked if I don't give redhat account password.
Not sure what's the difference between them
Quote from SteveSi on 2022-06-22, 10:45 AMah yes, if I boot from the ISO as a virtual DVD in a VBOX VM, then I do not have to register.
Perhaps it is looking on a 'real DVD' device for a special trial licence file?
ah yes, if I boot from the ISO as a virtual DVD in a VBOX VM, then I do not have to register.
Perhaps it is looking on a 'real DVD' device for a special trial licence file?
Quote from Deleted user on 2022-06-22, 11:45 AMWondering to know if there's any way to act like Rufus dd mode by using E2B for more flexibility for RHEL9?
Wondering to know if there's any way to act like Rufus dd mode by using E2B for more flexibility for RHEL9?
Quote from SteveSi on 2022-06-22, 11:48 AMYes, in new Beta 2.14e, you can use an extension of _.iso83.iso for E2B Legacy.
This will create a new partition 4 of type 0x83 and you wont need to register.
The only problem is that E2B does checks for empty Ptn 4 on boot - so when you reboot again afterwards you must delete Ptn4.
Is that of any use to you?
Yes, in new Beta 2.14e, you can use an extension of _.iso83.iso for E2B Legacy.
This will create a new partition 4 of type 0x83 and you wont need to register.
The only problem is that E2B does checks for empty Ptn 4 on boot - so when you reboot again afterwards you must delete Ptn4.
Is that of any use to you?
Quote from Deleted user on 2022-06-22, 11:55 AMThanks for prompt solution, I'll try it ans give back here.
Thanks for prompt solution, I'll try it ans give back here.
Quote from SteveSi on 2022-06-22, 11:58 AMOK - its in latest Beta folder v2.14e
I used
\_ISO\LINUX\rhel-baseos-9.0-x86_64-dvd_.iso83.iso
as filename
only works in legacy E2B menu.
https://1drv.ms/u/s!AqlrQcdsFA-K8HPUcEdLcuZAVbTP?e=hBgVfT
OK - its in latest Beta folder v2.14e
I used
\_ISO\LINUX\rhel-baseos-9.0-x86_64-dvd_.iso83.iso
as filename
only works in legacy E2B menu.
Quote from SteveSi on 2022-06-22, 4:48 PMIf you want to get rid of the annoying message to delete partition 4 every time you boot, make sure you have these lines at the top of your \_ISO\MyE2B.cfg file
!BAT
# Always wipe Ptn4
if not exist CD if not "%E2BDEV%"=="" partnew (%E2BDEV%,3) 0 0 0 > nul0 - ZERO not a letter !
If you want to get rid of the annoying message to delete partition 4 every time you boot, make sure you have these lines at the top of your \_ISO\MyE2B.cfg file
!BAT
# Always wipe Ptn4
if not exist CD if not "%E2BDEV%"=="" partnew (%E2BDEV%,3) 0 0 0 > nul
0 - ZERO not a letter !
Quote from Deleted user on 2022-06-28, 9:08 AMNot sure if I miss any detail to prevent this
- make E2B USB by Easy2Boot_v2.14fBeta
- put RHEL-8.5.0-20211013.2-x86_64-dvd1.iso to USB as \_ISO\LINUX\RHEL-8.5.0-20211013.2-x86_64-dvd1.iso83.iso
- Boot physical server as legacy mode from USB device
- choose RHEL-8.5.0-20211013.2-x86_64-dvd1.iso83.iso
- the software not registered wanring still there
screenshot as https://imgur.com/a/VltqjDk
Not sure if I miss any detail to prevent this
- make E2B USB by Easy2Boot_v2.14fBeta
- put RHEL-8.5.0-20211013.2-x86_64-dvd1.iso to USB as \_ISO\LINUX\RHEL-8.5.0-20211013.2-x86_64-dvd1.iso83.iso
- Boot physical server as legacy mode from USB device
- choose RHEL-8.5.0-20211013.2-x86_64-dvd1.iso83.iso
- the software not registered wanring still there
screenshot as https://imgur.com/a/VltqjDk
Quote from Deleted user on 2022-06-28, 9:35 AMOkay I found the root casue is the file extension name MUST end with _.iso83.iso
I ignored the underlineI made it pass the license warning during the installation, thank you!
BTW, will this solution able to implement in UEFI mode?
Okay I found the root casue is the file extension name MUST end with _.iso83.iso
I ignored the underline
I made it pass the license warning during the installation, thank you!
BTW, will this solution able to implement in UEFI mode?
Quote from SteveSi on 2022-08-06, 9:37 AMUnfortunately, the same mechanism cannot be used under UEFI because most UEFI BIOSes will refuse to recognise an MBR-partitioned disk as 'valid' if the partitions are out of order:
Ptn1: contains RHEL ISO
Ptn2: contains agFM files
Ptn3: any
Ptn4: unusedwhen we add in a type 83 Ptn4 table entry, we get:
Ptn1: contains RHEL ISO
Ptn2: contains agFM files
Ptn3: any or unused
Ptn4: Points to start of RHEL ISOSince Ptn4 points to a partition that starts before partition 2, the whole MBR disk is considered invalid and so you cannot easily boot to it using UEFI as it does not 'see' the USB disk! A legacy (BIOS) system does not mind out-of-order partitions.
However, there are two ways to work around this:
agFM - .imgPTNREP3 on Partition 3
- Make a third PRIMARY NTFS partition on the E2B USB drive (not LOGICAL Partition but PRIMARY!)
- Copy the RHEL iso file to it
- Rename the RHEL file to have a .imgptnREP3 file extension
- UEFI64-boot to agFM and use the file manager menu system to select the .imgptnREP3 file on partition 3 - use 0x83 as the partition type when prompted.
- Reboot to agFM - press F3 and boot from Partition 3
- When finished, reboot to agFM and choose 'Restore E2B Partitions' to restore the original partition 3
You could legacy boot to Partition 3 at Step 5, but you would need to make a .cfg file for agFM and a .mnu file for E2B.
Here is a simple \_ISO\LINUX\RHEL_Boot_from_Ptn3.cfg file:
# Boot RHEL in ptn 3
if [ "$CPU" = "64" ] ; then
set root=(${grubfm_disk},3)
linux /isolinux/vmlinuz inst.stage2=hd:LABEL=RHEL-9-0-0-BaseOS-x86_64
initrd /isolinux/initrd.img
boot
else
# return back to 'open' menu
echo Not 64-bit CPU!
sleep 3
grubfm "${grubfm_current_path}"
fiHere is simple \_ISO\LINUX\RHEL_Boot_from_Ptn3.mnu file contents:
iftitle [if exist (hd0,2)/isolinux/vmlinuz if exist (hd0,2)/isolinux/initrd.img] RHEL Boot from Ptn 3\nBoot to RHEL which must be on Partition 3
root (hd0,2)
kernel /isolinux/vmlinuz inst.stage2=hd:LABEL=RHEL-9-0-0-BaseOS-x86_64
initrd /isolinux/initrd.img
errorcheck off
boot
An alternative way
agFM - .imgPTN23 on Partition 1This has the disadvantage that the E2B Partition 1 will be removed and legacy booting to the E2B menu system will be unavailable.
- Rename the RHEL file on Ptn1 (e.g. \_ISO\LINUX) to have a _.iso83.imgptn23 file extension
- UEFI64-boot to agFM and use the file manager menu system to select the .imgptn23 file on partition 3 - use 0x83 as the partition type when prompted.
- Reboot - it should UEFI64-boot to RHEL
- When finished, reboot to agFM on Partition 2 and choose 'Restore E2B Partitions' to restore the original partition 3
Note that this will not work if you try to boot to legacy mode after step 3. The agFM menu will load but booting to RHEL as Partition 1 will not work.
Finally, as a third alternative (and the 'proper' way) you can use the MPI Tool Kit to convert the whole ISO into a RHELxxx.imgptn23 file. This should work in both Legacy and UEFI modes and from both the E2B menu and the agFM menu systems (untested).
Unfortunately, the same mechanism cannot be used under UEFI because most UEFI BIOSes will refuse to recognise an MBR-partitioned disk as 'valid' if the partitions are out of order:
Ptn1: contains RHEL ISO
Ptn2: contains agFM files
Ptn3: any
Ptn4: unused
when we add in a type 83 Ptn4 table entry, we get:
Ptn1: contains RHEL ISO
Ptn2: contains agFM files
Ptn3: any or unused
Ptn4: Points to start of RHEL ISO
Since Ptn4 points to a partition that starts before partition 2, the whole MBR disk is considered invalid and so you cannot easily boot to it using UEFI as it does not 'see' the USB disk! A legacy (BIOS) system does not mind out-of-order partitions.
However, there are two ways to work around this:
agFM - .imgPTNREP3 on Partition 3
- Make a third PRIMARY NTFS partition on the E2B USB drive (not LOGICAL Partition but PRIMARY!)
- Copy the RHEL iso file to it
- Rename the RHEL file to have a .imgptnREP3 file extension
- UEFI64-boot to agFM and use the file manager menu system to select the .imgptnREP3 file on partition 3 - use 0x83 as the partition type when prompted.
- Reboot to agFM - press F3 and boot from Partition 3
- When finished, reboot to agFM and choose 'Restore E2B Partitions' to restore the original partition 3
You could legacy boot to Partition 3 at Step 5, but you would need to make a .cfg file for agFM and a .mnu file for E2B.
Here is a simple \_ISO\LINUX\RHEL_Boot_from_Ptn3.cfg file:
# Boot RHEL in ptn 3
if [ "$CPU" = "64" ] ; then
set root=(${grubfm_disk},3)
linux /isolinux/vmlinuz inst.stage2=hd:LABEL=RHEL-9-0-0-BaseOS-x86_64
initrd /isolinux/initrd.img
boot
else
# return back to 'open' menu
echo Not 64-bit CPU!
sleep 3
grubfm "${grubfm_current_path}"
fi
Here is simple \_ISO\LINUX\RHEL_Boot_from_Ptn3.mnu file contents:
iftitle [if exist (hd0,2)/isolinux/vmlinuz if exist (hd0,2)/isolinux/initrd.img] RHEL Boot from Ptn 3\nBoot to RHEL which must be on Partition 3
root (hd0,2)
kernel /isolinux/vmlinuz inst.stage2=hd:LABEL=RHEL-9-0-0-BaseOS-x86_64
initrd /isolinux/initrd.img
errorcheck off
boot
An alternative way
agFM - .imgPTN23 on Partition 1
This has the disadvantage that the E2B Partition 1 will be removed and legacy booting to the E2B menu system will be unavailable.
- Rename the RHEL file on Ptn1 (e.g. \_ISO\LINUX) to have a _.iso83.imgptn23 file extension
- UEFI64-boot to agFM and use the file manager menu system to select the .imgptn23 file on partition 3 - use 0x83 as the partition type when prompted.
- Reboot - it should UEFI64-boot to RHEL
- When finished, reboot to agFM on Partition 2 and choose 'Restore E2B Partitions' to restore the original partition 3
Note that this will not work if you try to boot to legacy mode after step 3. The agFM menu will load but booting to RHEL as Partition 1 will not work.
Finally, as a third alternative (and the 'proper' way) you can use the MPI Tool Kit to convert the whole ISO into a RHELxxx.imgptn23 file. This should work in both Legacy and UEFI modes and from both the E2B menu and the agFM menu systems (untested).