Sponsored Content
Operating Systems Linux Red Hat Trouble creating RHEL 6.5 bootable image with custom kickstart file Post 302982906 by 911Eric on Tuesday 4th of October 2016 01:59:42 PM
Old 10-04-2016
Error Trouble creating RHEL 6.5 bootable image with custom kickstart file

Hi everyone,

I have a custom kickstart file from a software vendor and I'm trying to package that with a RHEL 6.5 and then attach it to a VM and install RHEL with the settings in the kickstarter file. I'm doing this from a windows PC using an app called InfraRecorder.

I've extracted the contents of an original RHEL 6.5 ISO, placed the custom ks.cfg file in the root of the image and then I create my ISO with InfraRecorder and mount it to the VM however when I boot up the VM I keep receiving this error
Code:
ISOLINUX 4.02 2010-07-21 ETCDisolinux: Image checksum error, sorry...

For the boot sector I have placed the files isolinux.bin, boot.cat and efiboot.img.

What am I missing? Hopefully this is the right place to ask this question, I realize I'm using windows to create the image but I figured this has more to do with modifying the Linux ISO and something I'm not doing correctly. I've googled this and searched here in the forums prior to posting this and can't seem to find what I'm looking for. Thanks in advance!

Last edited by rbatte1; 10-05-2016 at 05:53 AM.. Reason: Added CODE tags for error message, removing other font information.
 

10 More Discussions You Might Find Interesting

1. AIX

How do I create a bootable mksysb image file

I have several systems which require software maintenance several times a year. After the software maintenance, it is required that we make two system tapes for DR purposes. The creation of these system tapes takes anywhere from 1-1.5 hours because of the performance of the tape drives. What I... (7 Replies)
Discussion started by: acascianelli
7 Replies

2. Red Hat

Custom package installation using kickstart

Hi there, I've started playing around with Linux a few days back, as part of my intenship. I was wondering if there is anyway I can install custom packages (non RPM packages...say like Oracle) as a part of Kickstart. My machines are running RHEL 4. Thanks a lot :) (1 Reply)
Discussion started by: iman453
1 Replies

3. Red Hat

RHEL Kickstart

Hi, I am trying to install RHEL5.3 using kickstart method. Copied the rhel.iso file from DVD to http location. ks.cfg and rhel.iso files are available on a WINDOWS2008 Server (via HTTP). In ks.cfg file, provided the media path as url --url=http://xx.xx.xx.xx/RHEL53. System understanding the... (3 Replies)
Discussion started by: uday123
3 Replies

4. Red Hat

RHEL Kickstart Pre-Install script

Hey all, I'm not sure if this possible but I had tested it out manually during the installation (placed a sleep in the pre-installation) and it worked. I'm trying to have a pexpect script to log into the mysql and input a new row for the pre-installation, which will end up displaying on a web... (1 Reply)
Discussion started by: karljbaker
1 Replies

5. Red Hat

OpenSUSE installation using RHEL / CentOS Kickstart

Hi guys I have CentOS installed on my server. I have also installed TFTP server, DHCP server. I am able to install CentOS on remote machines using PXE boot and kickstart cfg file. I would like to install OpenSUSE using CentOS kickstart file. How do I do it ? I am also fine with any other... (2 Replies)
Discussion started by: msohail
2 Replies

6. AIX

bootable mksysb image on

i have been given a bootable cd/dvd, that i install a ibm aix 185 workstation with, i want to make a nim mksysb resource from that, the following is a listing for the root file structure of the cd/dvd, seems someone took a mksysb of a built ibm aix machine and did mkcd -L -S -I and setup the... (2 Replies)
Discussion started by: asyed123
2 Replies

7. Fedora

Rhel 6.1 - How to create a kickstart file?

Can anyone tell me how you create a kickstart file for RHEL 6.1 install? I am new to this and wanting to learn Red Hat. I have a training guide that says to create one but it does not give you instructions on how to do so. (3 Replies)
Discussion started by: Saplmb
3 Replies

8. Red Hat

Prevent kickstart to install image on external LUN

on the HP box , when we try to kickstart , the Linux gets installed on external LUN (Storage) .. so we end up unmapping the LUN and rekick , is there a way to disable the kickstart to ignore the external LUN incase we net boot it again (1 Reply)
Discussion started by: skamal4u
1 Replies

9. Red Hat

RHEL Linux 6.2 to 7.3 - Bootable iso

Hi All On one of my sandbox machine, I want to replace RHEL 6.2 to RHEL 7.3. I am using both developer editions. rhel-server-7.3-x86_64-dvd.iso ... This is what I have downloaded from Red Hat Enterprise Linux Download | Red Hat Developers My understanding is this file would work as a... (1 Reply)
Discussion started by: videsh77
1 Replies

10. UNIX for Beginners Questions & Answers

How to perform kickstart installation with virtual floppy image from ILO console?

HI All, I have created a kickstart file and converted into .img with below procedure to mount this as a floppy image file to supply the kickstart file during the installation time. But installation failing with unknown ks file location and other error messages. 1. Build an empty floppy... (3 Replies)
Discussion started by: venumutyalu
3 Replies
Makebootfat Bootable FAT Disk Creation(1)		      General Commands Manual			 Makebootfat Bootable FAT Disk Creation(1)

NAME
makebootfat - Makebootfat Bootable FAT Disk Creation SYNOPSIS
makebootfat [options] IMAGE DESCRIPTION
This utility creates a bootable FAT filesystem and populates it with files and boot tools. It is mainly designed to create bootable USB and Fixed disk for the AdvanceCD project. The official site of AdvanceCD and makebootfat is: http://advancemame.sourceforge.net/ OPTIONS
-o, --output DEVICE Specify the output device. It must be the device where you want to setup the filesystem. You can use the special "usb" value to automatically select the USB Mass Storage device connected at the system. This option is always required. -b, --boot FILE -1, --boot-fat12 FILE -2, --boot-fat16 FILE -3, --boot-fat32 FILE Specify the FAT boot sector images to use. The -b option uses the same sector for all the FAT types. The other options can be used to specify a different sector for different FAT types. The FAT types for which a boot sector is not specified are not used. This option is always required. -m, --mbr FILE Specify the MBR sector image to use. If this option is specified a partition table is created on the disk. Otherwise the disk is filled without a partition table like a floppy disk. -F, --mbrfat Change the MBR image specified with the -m option to pretend to be a FAT filesystem starting from the first sector of the disk. This allows booting from USB-FDD (Floppy Disk Drive) also using a partition table generally required by USB-HDD (Hard Disk Drive). The MBR image specified with the -m option must have executable code positioned like a FAT boot sector. You can use the included 'mbr- fat.bin' file. -c, --copy FILE Copy the specified file in the root directory of the disk. The file is copied using the readonly attribute. -x, --exclude FILE Exclude the specified files and subdirectories in the IMAGE directory to copy. The path must be specified using the same format used in the IMAGE directory specification. -X, --syslinux2 Enforce the syslinux 2.xx FAT limitations. Syslinux 2.xx doesn't support FAT32 at all, and FAT16 with 64 and 128 sectors per cluster formats. This option excludes all the FAT formats not supported by syslinux. Please note that it limits the maximum size of filesystem to 1 GB. -Y, --syslinux3 Enforce the syslinux 3.xx FAT support. Syslinux 3.00 supports all the FAT types and sizes but it requires a special customisation of the boot sector and of the file 'ldlinux.sys'. This option does this customisation without the need to use the syslinux installer if the 'ldlinux.sys' file is copied on disk with the -c option. -Z, --zip If possible force the ZIP-Disk compatibility. It sets a geometry of 32 sectors and 64 heads. It also uses the 4'th partition entry in the partition table. It's required to boot also in USB-ZIP mode. -P, --partition Ensure to operate on a partition and not on a disk. -D, --disk Ensure to operate on a disk and not on a partition. -L, --label LABEL Set the FAT label. The label is a string of 11 chars. -O, --oem OEM Set the FAT OEM name. The OEM name is a string of 11 chars. -S, --serial SERIAL Set the FAT serial number. The serial number is a 32 bit unsigned integer. -E, --drive DRIVE Set the BIOS drive to setup in the FAT boot sector. Generally this value is ignored by boot sectors, with the exception of the FAT12 and FAT16 FreeDOS boot sectors that require the correct value or the value 255 to force auto detection. -v, --verbose Print some information on the device and on the filesystem created. -i, --interactive Show the errors in a message box. Only for Windows. -h, --help Print a short help. -V, --version Print the version number. IMAGE Directory image to copy on the disk. All the files and subdirectories present in this directory are copied on the disk. DISKS AND PARTITIONS NAMES
In Linux disk devices are named /dev/hdX or /dev/sdX where X is a letter. Partition devices are named /dev/hdXN or /dev/sdXN where X is a letter and N a digit. In Windows disk devices are named \.PhysicalDriveN where N is a digit. Partition devices are named \.X: where X is a letter, but some- times \.X: is a disk and not a partition, for example on floppies and on all the USB Mass Storage devices without a partition table. SYSLINUX
To make a bootable FAT using syslinux you must use the -X option for syslinux version 2.xx or the -Y option for syslinux version 3.xx. You must also copy in the root directory of the disk the files: ldlinux.sys The syslinux loader. syslinux.cfg The syslinux configuration file. linux The Linux kernel image (the file name may be different). initrd.img The initrd filesystem (the file name may be different or missing). You must also specify the 'ldlinux.bss' boot sector with the -b option and possibily the 'mbr.bin' MBR sector with the -m option. Both the sector images are present in the syslinux package. For example: makebootfat -o usb -Y -b ldlinux.bss -m mbr.bin -c ldlinux.sys -c syslinux.cfg -c linux -c initrd.img image LOADLIN AND FREEDOS
To make a bootable FAT using loadlin and FreeDOS you must copy in the root directory of the disk the files: kernel.sys The FreeDOS kernel. Remember to use the "32" kernel version to support FAT32. command.com The FreeDOS shell. autoexec.bat Used to start loadlin. loadlin.exe The loadlin executable. linux The Linux kernel image (the file name may be different). initrd.img The initrd filesystem (the file name may be different or missing). You must also specify the FreeDOS boot sectors available on the FreeDOS 'sys' source package with the -1, -2, -3 option. For the MBR you can use the sectors image available on the FreeDOS 'fdisk' source package. For example: makebootfat -o /dev/hda1 -E 255 -1 fat12com.bin -2 fat16com.bin -3 fat32lba.bin -c kernel.sys -c command.com -c autoexec.bat -c loadlin.exe -c linux -c initrd.img image MULTI STANDARD USB BOOTING
The BIOS USB boot support is generally differentiated in three categories: USB-HDD, USB-FDD and USB-ZIP. The USB-HDD (Hard Disk Drive) standard is the preferred choice and it requires the presence of a partition table in the first sector of the disk. You can create this type of disk using the -m option. The USB-FDD (Floppy Disk Drive) standard requires the presence of a filesystem starting from the first sector of the disk without a parti- tion table. You can create this type of disk without using the -m option. The USB-ZIP (ZIP Drive) standard requires the presence of a device with a very specific geometry. Specifically, it requires a geometry with 32 sectors and 64 heads. It also requires the presence of a partition table with only a bootable partition in the fourth entry. You can create this type of disk using the -m and -Z option. Generally these standards are incompatible, but using the -m, -F and -Z options you can create a disk compatible with all of them. To use the -F option, the MBR image specified must follow the constrains: o It must start with a standard FAT 3 bytes jump instruction. o It must have the bytes from address 3 to 89 (included) unused. And example of such image is in the 'mbrfat.bin' file. For example to create a syslinux image: makebootfat -o usb -Y -Z -b ldlinux.bss -m mbrfat.bin -F -c ldlinux.sys -c syslinux.cfg -c linux -c initrd.img image and for a FreeDOS and loadlin image: makebootfat -o usb -E 255 -Z -1 fat12com.bin -2 fat16com.bin -3 fat32chs.bin -m mbrfat.bin -F -c kernel.sys -c command.com -c autoexec.bat -c loadlin.exe -c linux -c initrd.img image Please note that FreeDos has some problems booting from USB. It works only on very few conditions. EXCLUSION
To exclude some files or directories in the image copy, you can use the -x option using the same path specification which are you using for the image directory. For example, if you need to exclude the 'isolinux' and 'syslinux' subdirectories from the 'image' directory you can use the command: makebootfat ... -x image/isolinux -x image/syslinux image COPYRIGHT
This file is Copyright (C) 2004, 2005 Andrea Mazzoleni SEE ALSO
syslinux(1), mkdosfs(1), dosfsck(1) Makebootfat Bootable FAT Disk Creation(1)
All times are GMT -4. The time now is 11:05 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy