I am building a custom ISO for CentOS 7 and for now I am just intending for this to be an absolute minimal install (a proof of concept basically). I am re-creating the ISO via using mkisofs. The command I entered is: Mkisofs –o custom.iso –b isolinux.bin –c boot.cat –no-emul-boot –V ‘CentOS’ –boot-load-size 4 –boot-info-table –R –J –v –T isolinux/ This successfully created the iso and allowed me to mount it in the optical drive of VirtualBox. Upon installation I am receiving an error within the rdsosreport.txt that says: > localhost dracut-initqueue: Warning: Could not boot. > > localhost dracut-initqueue: Warning: /dev/root does not exist So far I have: copied .treeinfo, .discinfo into the root directory of where I am making the iso. Created subdirectory /isolinux with all the /isolinux data from the latest CentOS-7-x86_64-Minimal-1503-01 as well as the /images and /LiveOS directories. I have also copied over the repo .xml file into the root directory. I have tried a multitude of kickstart files, but the current version I am using is ultra-minimalistic just to get this to work at some point. install cdrom text keyboard us lang en_US.UTF-8 rootpw --iscrypted $6$XRIetvtFyLXRFVzZ$jX7xRxsN6M.DIqwJ9DQui9ytaqK3IAzauSqB4zeRNvMKJo6xCJQAk90XIaxh.SBn0IBtyZM7ZlHK8eSk55VnG0 timezone America/New_York --isUtc clearpart --none --initlabel %packages @core %end My ks.cfg is located in isolinux/ks/ks.cfg and when I boot into the system I am running is linux inst.ks=cdrom:/dev/cdrom:/ks/ks.cfg I'm a little lost on where to investigate further as all I am trying to do is load a very simple kickstart file to get Linux to do a one-button install. I don't necessarily need to be told, just to be pointed in the right direction as I've tried quite a few different kickstart configurations and have come up with the same error. edit: I have gotten this working by editing the isolinux.cfg file and changing the volume ID to my -V volume ID set in my mkisofs and then selecting this menu option when doing my installation. append initrd=initrd.img inst.stage2=hd:LABEL=CentOS quiet inst.ks=cdrom:/dev/cdrom:/ks/ks.cfg I have other errors within the iso that I'm investigating now due to the fact my kickstart file is so barren.

I am trying to create a bootable ISO for a customised Ubuntu. The ISO I create is not bootable (it won't boot in VirtualBox). To debug I am not modifying Ubuntu, just trying to recreate a bootable ISO from the the original bootable Ubuntu ISO I downloaded from the web (it boots in VirtualBox). The steps are: 1. Mount original ISO 2. Make a read-write copy 3. Use genisoimage to create a new ISO The details are shown below. The new ISO won't boot. The file command indicates it is bootable, but does not contain a "DOS/MBR boot sector" (whereas the original ISO does). I have also shown some of the contents of the mounted disk (in case I am specifying the wrong boot catalog or image). Can anyone tell me what I am doing wrong?
---
Steps 1 and 2. Mount original ISO and make a read/write copy:

> sudo mount -t iso9660 -o loop ubuntu-24.04.iso mntpoint
> mkdir mntpoint_rw
> rsync -a mntpoint/ mntpoint_rw

Step 3. Recreate the ISO:

> sudo genisoimage \,
   -o /tmp/custom.iso \
   -R -J -b EFI/boot/grubx64.efi -c boot.catalog -no-emul-boot -boot-load-size 4 -boot-info-table \
   $(pwd)/mntpoint_rw

I have tried various combinations of -b, -c options with files boot.catalog, EFI/boot/grubx64.efi and boot/grub/grub.cfg. Info about the original ISO (downloaded from web):

> file ubuntu-24.04.iso
ubuntu-24.04.iso: ISO 9660 CD-ROM filesystem data (DOS/MBR boot sector) 'Ubuntu 24.04.2 LTS amd64' (bootable)
>  ls -lh ubuntu-24.04.iso
-rw-r--r-- 1   6.0G Aug  1 13:37 ubuntu-24.04.iso

Info about the new ISO:

> file /tmp/custom.iso
/tmp/custom.iso: ISO 9660 CD-ROM filesystem data 'Custom Ubuntu-24.04' (bootable)
> ls -lh /tmp/custom.iso
-rw-r--r-- 1 root root 6.0G Aug  1 13:56 /tmp/custom.iso

Selected content of the mounted disk:

> ls -l --block-size=K mntpoint_rw
total 84K
dr-xr-xr-x 3    4K Jan 27  2025 EFI
dr-xr-xr-x 3    4K Jan 27  2025 boot
-r--r--r-- 1    2K Feb 15 19:15 boot.catalog
dr-xr-xr-x 2   12K Feb 15 19:15 casper
dr-xr-xr-x 3    4K Feb 15 19:09 dists
dr-xr-xr-x 2    4K Feb 15 19:09 install
-r--r--r-- 1   44K Feb 15 19:15 md5sum.txt
dr-xr-xr-x 4    4K Feb 15 19:09 pool
dr-xr-xr-x 2    4K Feb 15 19:09 preseed
lrwxrwxrwx 1    1K Feb 15 19:09 ubuntu -> .

> find mntpoint_rw/EFI -type f | xargs ls -lh
-r--r--r-- 1   945K Jan 27  2025 mntpoint_rw/EFI/boot/bootx64.efi
-r--r--r-- 1   2.3M Aug  1 13:56 mntpoint_rw/EFI/boot/grubx64.efi
-r--r--r-- 1   837K Jan 27  2025 mntpoint_rw/EFI/boot/mmx64.efi

> find mntpoint_rw/boot ! \( -name '*.mod' -o -name '*.lst' \) -type f | xargs ls -lh
-r--r--r-- 1   2.4M Jan 27  2025 mntpoint_rw/boot/grub/fonts/unicode.pf2
-r--r--r-- 1    583 Feb 15 19:13 mntpoint_rw/boot/grub/grub.cfg
-r--r--r-- 1   7.5K Jan 27  2025 mntpoint_rw/boot/grub/i386-pc/efiemu32.o
-r--r--r-- 1    11K Jan 27  2025 mntpoint_rw/boot/grub/i386-pc/efiemu64.o
-r--r--r-- 1    31K Jan 27  2025 mntpoint_rw/boot/grub/i386-pc/eltorito.img
-r--r--r-- 1    318 Feb 15 19:13 mntpoint_rw/boot/grub/loopback.cfg
-r--r--r-- 1   145K Apr  9  2024 mntpoint_rw/boot/memtest86+x64.bin

We have an old physical machine with *Ubuntu distro 20.04* and that physical machine has a total of

/root partition

and

as swap memory

. We have currently utilized up to 45GB. We want to create a bootable ISO image from that current installation. Also, we tried to create an image using the below packages. While running these packages, we are facing an error -- “filesystem.squashfs size exceeds more than 4GB”. Then we verified that the filesystem file consumes more than 8GB. So that, we cannot able to create an image file. Is there any other package/tool to create an image from the current installation? Thanks! 1.remastersys – respin - https://itectec.com/ubuntu/ubuntu-build-the-own-ubuntu-iso/ 2.distroshare image builder - https://github.com/Distroshare/distroshare-ubuntu-imager

Pseudocode but originally developed for Windows 7 iso file but applied for Windows 8 in the thread How to create bootable Windows 8 iso image in Linux? but it does not work with Windows 10 iso # https://rwmj.wordpress.com/2010/11/04/customizing-a-windows-7-install-iso/ # https://unix.stackexchange.com/a/312477/16920 $ dd if=../en_windows_10_x64_dvd.iso \ of=boot.img bs=2048 count=8 skip=734 $ mkisofs -o ../new-win.iso -b boot.img -no-emul-boot -c BOOT.CAT \ -iso-level 2 -udf \ -J -l -D -N -joliet-long -relaxed-filenames . Unsuccessful output when run on Windows 10 image dd if=/home/masi/Downloads/en_windows_10_multiple_editions_version_1511_x64_dvd.iso of=/home/masi/Downloads/boot.img bs=2048 count=8 skip=734 8+0 records in 8+0 records out 16384 bytes (16 kB) copied, 0.000392973 s, 41.7 MB/s Some of the following fields have changed for the iso file used in dd - bs=2048 - count=8 - skip=734 How can you study which field values you can use for Windows 10 iso? OS: Debian 8.5 64 bit Hardware: Asus Zenbook UX303UA Linux kernel: 4.6 of backports Related threads: How to create bootable Windows 7 iso image in Linux? , Customizing a Windows 7 install ISO Motivation: I need Windows 10 to use Canon P-150 duplex scanner, but when I started my Windows, I got Error *0xC0000428* because Windows update has again broken things there and I use Windows otherwise so rarely; and I have no spare Windows left to make bootable media

In an automated process an iso file is created with mkisofs. Even, as the original data is excactly the same, the resulting iso files are not the same (their md5sum changes). Since I rsync --checksum the result, I dislike that the "same iso" is of course retransferred every time. I expect mostly timestamps to be the main difference. Is there some libfaketime buildin switch to generate an iso via mkisofs that would indeed be the same. I do not know if only timestamps matter? I have compared the resulting iso files with their xxd isofile output like this: diff --side-by-side --suppress-common-lines <(xxd a.iso) <(xxd b.iso ) and there seem to be only 51 lines representing 16 Bytes (so roughly 800 Bytes of difference) in the else exact same file. The command used to generate this iso in question is roughly this: genisoimage -o "file.iso" -b isolinux/isolinux.bin \ -c isolinux/boot.cat -no-emul-boot \ -boot-load-size 4 -boot-info-table \ -J -R -v -T -V 'CDLABEL' "datadir/" BS: Am I missing a command line parameer switch with rsync that does checksumming for ~1MB chunks of big files, as to prevent the retransfer when as in my case only some 800 bytes differ?

When you boot a Windows 10 ISO, you will get this misleading prompt: Why is it misleading? Because this message comes from the Windows ISO itself after you actually already booted from it. This prompt is a feature that is supposed to prevent you from accidentally booting in your Windows image. Now I have a very specific use-case in which this prompt makes it impossible for me to automatically create and install a UEFI-based Windows 10 VM. So I've done some digging and on Windows you can create a Windows ISO without the prompt by specifying a noprompt image on the boot entry like so: $setfsboot="C:\01_TEMP\ISO\etfsboot.com" $sefisys ="C:\01_TEMP\ISO\efisys_noprompt.bin" Oscdimg -bootdata:2#p0,eb$setfsboot#pEF,e,b$sefisys -u1 -udfver102 C:\winpe_amd64\media C:\winpe_amd64\winpeamd64.iso **Quick explanation** -bootdata:2#p0,eb$setfsboot#pEF,e,b$sefisys - 2 means there are 2 boot entries - # separator - p0,eb$setfsboot is the default boot entry (for legacy BIOS boot) - # separator - pEF,e,b$sefisys is the fallback boot entry (for UEFI boot) Documentation for OSCdimg Now I'm trying to achieve the same thing on Linux using mkisofs, which is very tricky because just in order to make a UEFI-bootable Windows ISO, you need the upstream version of mkisofs (see this post by mkey ) (Which can be obtained here .) The versions of mkisofs that come with Linux distributions apparently lack some features and have ancient bugs in them that never got fixed. I've tried removing efi/microsoft/boot/cdboot.efi and then renaming efi/microsoft/boot/cdboot_noprompt.efi to efi/microsoft/boot/cdboot.efi in order to trick the ISO, but that didn't work unfortunately. At the moment I use this code to extract a boot image from the ISO directly: BOOT_LOAD_SEG="$(dumpet -i "${WIN10_IMG}" | grep "Media load segment: " | cut -d ':' -f2 | cut -d ' ' -f2)" BOOT_LOAD_SIZE="$(dumpet -i "${WIN10_IMG}" | grep "Load Sectors: " | grep -o "[^:]*$" | cut -d ' ' -f2 | head -1)" EFI_STARTING_SECTOR="$(dumpet -i "${WIN10_IMG}" | grep "Load LBA: " | grep -o "[^:]*$" | cut -d ' ' -f2 | tail -1)" echo "EFI_STARTING_SECTOR: $EFI_STARTING_SECTOR" sudo dd if="${WIN10_IMG}" of="${TMP}/efi.dmp" bs=2048 count=1 skip="${EFI_STARTING_SECTOR}" EFI_BOOT_LOAD_SIZE="$(file "${TMP}/efi.dmp" | grep -oP 'sectors (\d+)' | cut -d ' ' -f2)" echo "EFI_BOOT_LOAD_SIZE: ${EFI_BOOT_LOAD_SIZE}" sudo dd if="${WIN10_IMG}" of="${ISO_FILES}/efi/win_efi_boot.img" bs=2048 count="${EFI_BOOT_LOAD_SIZE}" skip="${EFI_STARTING_SECTOR}" In the last command above, the extracted image is placed in the folder containing the files extracted from the ISO. Then using the -eltorito-boot "efi/win_efi_boot.img" flag for mkisofs, I tell it to use that for the boot entry. I have written a script that automatically sets up everything you need in order to get to the point where I am right now. If you take a look at STEP 5 in the script you can see my attempt to change the file names, but I think, I may have to change STEP 4 instead, but I just don't know how. #!/usr/bin/env bash #You might have to install a few dependencies for schily tools to compile. #On Fedora this did the trick for me: sudo dnf install e2fsprogs-devel imake gcc-c++ ############ STEP 1 download Windows 10 ISO from Microsoft ############## WIN10_IMG="$(pwd)/windows10.iso" WIN10_IMG_ARCH="x64" if [ ! -f "$WIN10_IMG" ]; then # if the windows10.iso has not been downloaded yet if [[ "$WIN10_IMG_ARCH" == "x86" ]] || [[ "$WIN10_IMG_ARCH" == "i386" ]] ; then echo "Retrieving the x86 Windows 10 iso URL..." WINDOWS_10_ISO_URL=$(curl -LsI -o /dev/null -w %{url_effective} "https://tb.rg-adguard.net/dl.php?go=7e583fea ") # This strange looking URL actually redirects to a legit software-download.microsoft.com URL else echo "Retrieving the x64 Windows 10 iso URL..." WINDOWS_10_ISO_URL=$(curl -LsI -o /dev/null -w %{url_effective} "https://tb.rg-adguard.net/dl.php?go=3dd1ce66 ") # This strange looking URL actually redirects to a legit software-download.microsoft.com URL fi echo "Download URL: $WINDOWS_10_ISO_URL" echo "Making sure the URL comes from a trusted Microsoft domain..." if [[ $WINDOWS_10_ISO_URL == https://software-download.microsoft.com/* ]] ; then echo "Downloading the Windows 10 installation iso..." wget "$WINDOWS_10_ISO_URL" -O "$WIN10_IMG" else echo "URL validation failed. Please download the Windows 10 iso manually." exit 1 fi fi ######################################################################### ############## STEP 2 download and build the schily tools ############### SCHILY_VERSION="2021-06-07" SCHILY_ARCHIVE="schily-${SCHILY_VERSION}.tar.bz2" SCHILY_DIR="./schily-tools" if [ ! -f "${SCHILY_DIR}/mkisofs/OBJ/x86_64-linux-gcc/mkisofs" ]; then # if the mkisofs of Schily Tools has not been built yet sudo rm -rf "${SCHILY_DIR}" wget "https://altushost-swe.dl.sourceforge.net/project/schilytools/${SCHILY_ARCHIVE} " -O "${SCHILY_ARCHIVE}" tar -xf "${SCHILY_ARCHIVE}" rm "${SCHILY_ARCHIVE}" mv "schily-${SCHILY_VERSION}" "${SCHILY_DIR}" cd "${SCHILY_DIR}" ./Gmake.linux cd .. if [ ! -f "${SCHILY_DIR}/mkisofs/OBJ/x86_64-linux-gcc/mkisofs" ]; then echo "Building Schily Tools failed" exit 1 fi fi ######################################################################### ################# STEP 3 Extract the files from the ISO ################# TMP="./tmp" ISO_FILES="${TMP}/iso-files" ISO_MP="${TMP}/iso-mountpoint" if [ ! -f "${ISO_FILES}/setup.exe" ]; then # If the Windows ISO hasn't been extracted yet sudo rm -rf "${TMP}" mkdir -p "${ISO_FILES}" mkdir -p "${ISO_MP}" sudo mount -t udf "${WIN10_IMG}" "${ISO_MP}" sudo cp -Rva ${ISO_MP}/* "${ISO_FILES}" sudo umount "${ISO_MP}" fi ######################################################################### ################## STEP 4 Extract the EFI boot image #################### # Extract boot load segment address and size BOOT_LOAD_SEG="$(dumpet -i "${WIN10_IMG}" | grep "Media load segment: " | cut -d ':' -f2 | cut -d ' ' -f2)" BOOT_LOAD_SIZE="$(dumpet -i "${WIN10_IMG}" | grep "Load Sectors: " | grep -o "[^:]*$" | cut -d ' ' -f2 | head -1)" EFI_STARTING_SECTOR="$(dumpet -i "${WIN10_IMG}" | grep "Load LBA: " | grep -o "[^:]*$" | cut -d ' ' -f2 | tail -1)" echo "EFI_STARTING_SECTOR: $EFI_STARTING_SECTOR" sudo dd if="${WIN10_IMG}" of="${TMP}/efi.dmp" bs=2048 count=1 skip="${EFI_STARTING_SECTOR}" EFI_BOOT_LOAD_SIZE="$(file "${TMP}/efi.dmp" | grep -oP 'sectors (\d+)' | cut -d ' ' -f2)" echo "EFI_BOOT_LOAD_SIZE: ${EFI_BOOT_LOAD_SIZE}" sudo dd if="${WIN10_IMG}" of="${ISO_FILES}/efi/win_efi_boot.img" bs=2048 count="${EFI_BOOT_LOAD_SIZE}" skip="${EFI_STARTING_SECTOR}" ######################################################################### ######## STEP 5 Make changes to the files extracted from the ISO ######## # Make some arbitrary changes to the iso files #sudo rm -rf "${ISO_FILES}/efi/microsoft/boot/cdboot.efi" #sudo mv "${ISO_FILES}/efi/microsoft/boot/cdboot_noprompt.efi" "${ISO_FILES}/efi/microsoft/boot/cdboot.efi" #sudo rm -rf "${ISO_FILES}/efi/microsoft/boot/efisys.bin" #sudo mv "${ISO_FILES}/efi/microsoft/boot/efisys_noprompt.bin" "${ISO_FILES}/efi/microsoft/boot/efisys.bin" ######################################################################### ###### STEP 6 Build a new ISO using the extracted/modified files ######## sudo rm -f "${WIN10_IMG}.tmp.iso" sudo "${SCHILY_DIR}/mkisofs/OBJ/x86_64-linux-gcc/mkisofs" \ -no-emul-boot \ -b boot/etfsboot.com \ -boot-load-seg "${BOOT_LOAD_SEG}" \ -boot-load-size "${BOOT_LOAD_SIZE}" \ -eltorito-alt-boot \ -no-emul-boot \ -eltorito-boot "efi/win_efi_boot.img" \ -boot-load-size 1 \ -iso-level 4 \ -UDF \ -o "${WIN10_IMG}.tmp.iso" \ "${ISO_FILES}" ######################################################################### ############ STEP 7 Remove the files exxtracted from the ISO ############ #sudo rm -f "${TMP}" #########################################################################

I'm using Fedora v32. The only support I could find for Blu-ray burners on Linux is either xfburn or growisofs. I'd like to add files for backup and then burn it. When I tried using xfburn and selecting "Pioneer BDR-XD07B" under "Burning device", after adding the files to be saved, I get: > Failed to unmount 'Blank DS-R Disc'. Drive cannot be used for burning. Couldn't find an example of growisofs adding files to be burned then burning the disc. I assume I'll need to use mkisofs to make an ISO file with the data files in it then burning the Blu-ray disc with that ISO? I looked for Linux drivers for the Pioneer BDR-XD07B but found only Windows and MacOS drivers. Suggestions?

I'm trying to create a bootable ISO using xorriso, but I get this error: xorriso : FAILURE : Cannot find in ISO image: -boot_image ... bin_path='' It's [not just me](https://www.google.com/search?q= "Cannot+find+in+ISO+image") who gas gotten this error. The message doesn't make sense either because I never used -boot_image and xorriso should not be looking for isolinux.bin in any ISO. The path to isolinux.bin that I gave is the root directory of an already-unpacked ISO that I'm modifying.

I'm trying to build an alpine linux and devuan live iso using linux live kit. I followed the instructions and everything seemd to be fine. However, both the resulting iso do not boot from the usb stick. I was able to boot the rootsfs in frugal mode and the iso from the hd using grub. I used dd to copy the iso to the usb, and I used the same process hundreds of times and iso always boot with no problem. This is the gen_mycd_iso.sh which linux live kit uses to produce the iso.

cd /mycd-data-4201 && /usr/bin/mkisofs \
  -o /tmp/mycd-x86_64.iso -v -J -R -D -A mycd -V mycd \
  -no-emul-boot -boot-info-table \
  -boot-load-size 4 -b mycd/boot/isolinux.bin \ 
  -c mycd/boot/isolinux.boot .

My guess is that somehow the script fails to write the correct bootable flag to the usb partition. Any suggestions as to how troubleshoot the issue?

I am trying to add UEFI boot capability to a BIOS only Ubuntu 18.04 based custom iso. All the methods I've found so far require an efi.img file which isn't present in the iso. Can I use the file out of a full install Ubuntu 18.04? If yes, do I need to edit it? If not, how can I construct an efi.img file? The custom iso is designed to run from a USB, not installed. It is also intended for distribution to new Linux users. Adding UEFI capabilities to the USB rather than the iso isn't the solution we're looking for. This is the script that I used to build the fat partition. It is run in the folder containing the extracted iso: #! /bin/sh BOOT_IMG_DATA="$PWD" BOOT_IMG=efi.img #Ensure needed folders exist if [ ! -d "$BOOT_IMG_DATA"/efi/boot ]; then mkdir -p "$BOOT_IMG_DATA"/efi/boot fi if [ ! -d "$BOOT_IMG_DATA"/boot/grub ]; then mkdir -p "$BOOT_IMG_DATA"/boot/grub fi chmod -R +rw "$BOOT_IMG_DATA"/boot/grub chmod -R +rw "$BOOT_IMG_DATA"/efi/boot # Create the 64-bit EFI GRUB binary (bootx64.efi) and the El-Torito boot # image (efiboot.img) that goes in the /isolinux directory for booting on # UEFI systems. # First, build bootx64.efi, which will be installed here in /EFI/BOOT: grub-mkimage --format=x86_64-efi --output=bootx64.efi --config=grub.cfg --compression=xz --prefix=/EFI/BOOT part_gpt part_msdos fat ext2 hfs hfsplus iso9660 udf ufs1 ufs2 zfs chain linux boot appleldr ahci configfile normal regexp minicmd reboot halt search search_fs_file search_fs_uuid search_label gfxterm gfxmenu efi_gop efi_uga all_video loadbios gzio echo true probe loadenv bitmap_scale font cat help ls png jpeg tga test at_keyboard usb_keyboard # Then, create a FAT formatted image that contains bootx64.efi in the # /EFI/BOOT directory. This is used to bootstrap GRUB from the ISO image. dd if=/dev/zero of=efiboot.img bs=1K count=1440 # Format the image as FAT12: mkdosfs -F 12 efiboot.img # Create a temporary mount point: MOUNTPOINT=$(mktemp -d) # Mount the image there: mount -o loop efiboot.img $MOUNTPOINT # Copy the GRUB binary to /EFI/BOOT: mkdir -p $MOUNTPOINT/EFI/BOOT cp -a bootx64.efi -s $MOUNTPOINT/EFI/BOOT # Unmount and clean up: umount $MOUNTPOINT rmdir $MOUNTPOINT # Move the efiboot.img to isolinux: mv efiboot.img isolinux mv bootx64.efi efi/boot echo echo "Done building /EFI/BOOT/bootx64.efi and /isolinux/efiboot.img." This is the script I use to build the iso: #!/bin/bash # The example names get mapped to their roles here orig_iso="$HOME"/foxclone/foxclone025-01.iso new_iso="$HOME"/foxclone/foxclone025-02.iso new_files="$PWD" mbr_template=isohdpfx.bin # Extract MBR template file to disk dd if="$orig_iso" bs=1 count=432 of="$mbr_template" # Create the new ISO image xorriso -as mkisofs \ -U \ -allow-lowercase \ -r -V 'foxclone025-02' \ -o "$new_iso" \ -J -J -joliet-long \ -isohybrid-mbr "$mbr_template" \ -c isolinux/boot.cat \ -b isolinux/isolinux.bin \ -no-emul-boot -boot-load-size 4 -boot-info-table \ -eltorito-alt-boot \ -e isolinux/efiboot.img \ -no-emul-boot \ -isohybrid-gpt-basdat \ "$new_files" Does anyone see a problem in the code? I really appreciate a different set of eyes looking at this as I think I've gotten "too close to the forest to see the trees". TIA, Larry

I'm trying to create a custom Ubuntu 22.04 image using the following link . I'm not having luck on the Producing the CD image. I get all the way to the > sudo mkisofs -D -r -V "$IMAGE_NAME" -cache-inodes -J -l -b isolinux/isolinux.bin -c isolinux/boot.cat -no-emul-boot -boot-load-size 4 -boot-info-table -o ../ubuntu-9.04.1-desktop-i386-custom.iso . The reason this command doesn't work is because Ubuntu 22.04 doesn't have the isolinux/syslinux installed anymore. I've tried finding other ways to get this to write, but they either use isolinux.bin, or a .img that doesn't exist either. I've tried using the .img in boot/grub/i386-pc/eltorito.img, this causes the below error to occur > xorriso: FAILURE: Cannot find in ISO image: -boot_image ... bin_path='boot/grub/i386-pc/eltorito.img I could use some help on getting this Ubuntu 22.04 custom image to write to a bootable image.

I have custom vmlinuz and initrd files that compose a PXE image I use. Is there any way of building an ISO equivalent image given this initram image? I cannot seem anything obvious from genisoimage or mkisofs tools. Am I missing something and maybe what I try to accomplish does not make sense?

I have extracted the iso file "archlinux-2022.06.01-x86_64.iso". And I have made changes in the "airootfs.sfs" file And now I am going to create a "bootable (dos/MBR sector)" iso image again Like the original iso file that I have extracted

sudo xorriso -as  mkisofs -d -l -r  -no-emul-boot 
-o archlinux.iso .
-append_partition 2 0xef ../compile-linux/efi_part.img -e  "--interval:appended_partition_2:all::" -no-emul-boot ../compile-linux/bios_boot.img
-G ../compile-linux/mbr_code.img 
-b syslinux/isolinux.bin 
-c syslinux/boot.cat

output

archlinux.iso

archlinux.iso: ISO 9660 CD-ROM filesystem data (DOS/MBR boot sector) 'ISOIMAGE' (bootable)

output command

-indev archlinux.iso -report-el-torito plain -report-system-area plain

xorriso 1.5.4 : RockRidge filesystem manipulator, libburnia project.

xorriso : NOTE : Loading ISO image tree from LBA 0
xorriso : UPDATE :     114 nodes read in 1 seconds
xorriso : NOTE : Detected El-Torito boot information which currently is set to be discarded
Drive current: -indev 'archlinux.iso'
Media current: stdio file, overwriteable
Media status : is written , is appendable
Boot record  : El Torito , MBR cyl-align-off
Media summary: 1 session, 445804 data blocks,  871m data,  178g free
Volume id    : 'ISOIMAGE'
El Torito catalog  : 42  1
El Torito cat path : /syslinux/boot.cat
El Torito images   :   N  Pltf  B   Emul  Ld_seg  Hdpt  Ldsiz         LBA
El Torito boot img :   1  BIOS  y   none  0x0000  0x00     76          43
El Torito img path :   1  /syslinux/isolinux.bin
System area options: 0x00000a00
System area summary: MBR cyl-align-off
ISO image size/512 : 1783216
Partition offset   : 0
MBR heads per cyl  : 64
MBR secs per head  : 32
MBR partition table:   N Status  Type        Start       Blocks
MBR partition      :   1   0x00  0x83            0      1783216
MBR partition      :   2   0x00  0xef      1783216         1600

The above outputs are for the iso file that I made myself I tried to use my iso file live in virtual machine "Efi option is disabled" but I get these errors. I am a beginner and don't know much about this That's why I tried to find the right way to make the image from the original iso output, but I didn't succeed

xorriso 1.5.4 : RockRidge filesystem manipulator, libburnia project.

xorriso : NOTE : ISO image bears MBR with  -boot_image any partition_offset=16
xorriso : NOTE : Loading ISO image tree from LBA 0
xorriso : UPDATE :     113 nodes read in 1 seconds
libisofs: NOTE : Found hidden El-Torito image for EFI.
libisofs: NOTE : EFI image start and size: 396800 * 2048 , 0 * 512
xorriso : NOTE : Detected El-Torito boot information which currently is set to be discarded
Drive current: -indev '../archlinux-2022.06.01-x86_64.iso'
Media current: stdio file, overwriteable
Media status : is written , is appendable
Boot record  : El Torito , MBR isohybrid cyl-align-all GPT
Media summary: 1 session, 440998 data blocks,  861m data,  178g free
Volume id    : 'ARCH_202206'
El Torito catalog  : 118  1
El Torito cat path : /syslinux/boot.cat
El Torito images   :   N  Pltf  B   Emul  Ld_seg  Hdpt  Ldsiz         LBA
El Torito boot img :   1  BIOS  y   none  0x0000  0x00      4         119
El Torito boot img :   2  UEFI  y   none  0x0000  0x00      0      396800
El Torito img path :   1  /syslinux/isolinux.bin
El Torito img opts :   1  boot-info-table isohybrid-suitable
El Torito img blks :   2  44032
System area options: 0x00000302
System area summary: MBR isohybrid cyl-align-all GPT
ISO image size/512 : 1763992
Partition offset   : 16
MBR heads per cyl  : 64
MBR secs per head  : 32
MBR partition table:   N Status  Type        Start       Blocks
MBR partition      :   1   0x80  0x00           64      1587136
MBR partition      :   2   0x00  0xef      1587200       176128
GPT                :   N  Info
GPT disk GUID      :      3230323230363041b130303533353232
GPT entry array    :      2  248  separated
GPT lba range      :      64  1763928  1763991
GPT partition name :   1  490053004f00480079006200720069006400
GPT partname local :   1  ISOHybrid
GPT partition GUID :   1  3230323230363041b131303533353232
GPT type GUID      :   1  a2a0d0ebe5b9334487c068b6b72699c7
GPT partition flags:   1  0x1000000000000001
GPT start and size :   1  64  1587136
GPT partition name :   2  490053004f004800790062007200690064003100
GPT partname local :   2  ISOHybrid1
GPT partition GUID :   2  3230323230363041b132303533353232
GPT type GUID      :   2  a2a0d0ebe5b9334487c068b6b72699c7
GPT partition flags:   2  0x1000000000000001
GPT start and size :   2  1587200  176128

Where did I go wrong? I am trying to create my ISO image file and use it live Thank you for your help

I am trying to create a custom ISO from a rhel-8 installation disk that can boot on either a BIOS or an EFI server. Everything goes fine until I try to create the iso. If I run the following command:

mkisofs -J -R -T -V "NGS-8.4-0 Server" \
    -o ngs-8.4-0.iso \
    -b isolinux/isolinux.bin \
    -c isolinux/boot.cat \
    --no-emul-boot \
    --boot-load-size 4 \
    --boot-info-table \
    --eltorito-alt-boot \
    -e images/efiboot.img \
    -m TRANS.TBL \
    ngs-dvd

I get the following output:

Creating NGS iso...I: -input-charset not specified, using iso-8859-1 (detected in locale settings)

(bunch of TRANS.TBL output deleted)

Size of boot image is 4 sectors -> No emulation
Size of boot image is 19612 sectors -> genisoimage: Error - boot image '/NGS/ngs-dvd/images/efiboot.img' has not an allowable size.

However, if I delete two options (--eltorito-alt-boot & -e images/efiboot.img), it creates a bootable iso. What am I doing wrong?

Im using Xorriso and running this command : $MKISOFS \ -iso-level 3 \ -J -joliet-long \ -append_partition 2 0xef $UNIONDIR/$EFIIMG \ -partition_cyl_align all \ -add "$UNATTENDED_FILE" 'C:\System32\Sysprep' \ -o "$CFG_ISOPATH" \ "$UNIONDIR/" the command with populated vars is this : /usr/bin/xorriso -as mkisofs -iso-level 3 -J -joliet-long -append_partition 2 0xef /tmp/union.19/boot-efi.img -partition_cyl_align all -add /tmp/wf_script-Xjc2i3/unattended.xml | 'C:\System32\Sysprep' -o 991cc570-10d9-11ec-818a-5d4c9d0ae440.iso /tmp/union.19/ This is the error I'm getting, and it is happening because of the -add option: + /usr/bin/xorriso -as mkisofs -iso-level 3 -J -joliet-long -append_partition 2 0xef /tmp/union.19/boot-efi.img -partition_cyl_align all -add /tmp/wf_script-eZeXEW/unattended.xml 'C:\System32\Sysprep' -o 3d3839e0-10db-11ec-818a-5d4c9d0ae440.iso /tmp/union.19/ xorriso 1.5.0 : RockRidge filesystem manipulator, libburnia project. Drive current: -outdev 'stdio:3d3839e0-10db-11ec-818a-5d4c9d0ae440.iso' Media current: stdio file, overwriteable Media status : is blank Media summary: 0 sessions, 0 data blocks, 0 data, 42.2g free xorriso : FAILURE : -as mkisofs: Unrecognized option '-add' xorriso : aborting : -abort_on 'FAILURE' encountered 'FAILURE' + ok 'Creating new windows ISO' + EXITCODE=5 + '[' 5 = 0 ']' + echo 'FAILURE: Creating new windows ISO' + exit 5 FAILURE: Creating new windows ISO + cleanup + purge /tmp/etfsimg19 /tmp/etfsmnt.19 /tmp/lower.19 /tmp/prop.19 /tmp/union.19 /tmp/union.19 /tmp/upper.19 /tmp/work.19 + cd /tmp + for X in "$@" + '[' -d /tmp/etfsimg19 ']' + for X in "$@" + '[' -d /tmp/etfsmnt.19 ']' + umount /tmp/etfsmnt.19 + for X in "$@" + '[' -d /tmp/lower.19 ']' + umount /tmp/lower.19 + for X in "$@" + '[' -d /tmp/prop.19 ']' + umount /tmp/prop.19 + for X in "$@" + '[' -d /tmp/union.19 ']' + umount /tmp/union.19 + for X in "$@" + '[' -d /tmp/union.19 ']' + umount /tmp/union.19 + for X in "$@" + '[' -d /tmp/upper.19 ']' + umount /tmp/upper.19 + for X in "$@" + '[' -d /tmp/work.19 ']' + umount /tmp/work.19 + rm -rf /tmp/etfsimg19 /tmp/etfsmnt.19 /tmp/lower.19 /tmp/prop.19 /tmp/union.19 /tmp/union.19 /tmp/upper.19 /tmp/work.19 The reason why i need the -add option is because i need to drop the file unattended.xml into the C:\System32\Sysprep folder in the ISO, so when it will run it will be able to execute the installation by itself. Any help is very much appreciated Regards Danilo

As an example I'm trying to extract all the files from the ubuntu live iso **except** the path /casper/filesystem.squashfs. According to the man page:

Normally  xorriso  only writes to disk files which were given as stdio:
       pseudo-drives or as log files.  But its alter ego osirrox  is  able  to
       extract  file  objects  from  ISO  images  and to create, overwrite, or
       delete file objects on disk.
       Disk file exclusions by -not_mgt, -not_leaf, -not_paths apply.

I can extract all paths on the iso fine using:

xorriso -osirrox on -indev ubuntu-21.04-desktop-amd64.iso -extract / extract_dir

But I've been attempting to use the disk file exclusions but to no avail. I've tried different variations or not_leaf and not_paths in different orders both before and after the -extract action. They all extract all paths. Here's a few that I've tried. Using not_leaf:

xorriso -osirrox on -indev ubuntu-21.04-desktop-amd64.iso -not_leaf 'filesystem.squashfs' -extract / extracted_dir
xorriso -osirrox on -indev ubuntu-21.04-desktop-amd64.iso -extract / extracted_dir -not_leaf 'filesystem.squashfs'
xorriso -osirrox on -indev ubuntu-21.04-desktop-amd64.iso -not_mgt on -not_leaf 'filesystem.squashfs' -extract / extracted_dir
xorriso -osirrox on -indev ubuntu-21.04-desktop-amd64.iso -not_mgt on -extract / extracted_dir -not_leaf 'filesystem.squashfs'

Using not_paths with reorderings as above:

xorriso -osirrox on -indev ubuntu-21.04-desktop-amd64.iso -not_mgt on -not_paths 'casper/filesystem.squashfs' -- -extract / extracted_dir
xorriso -osirrox on -indev ubuntu-21.04-desktop-amd64.iso -not_mgt on -not_paths '/casper/filesystem.squashfs' -- -extract / extracted_dir
xorriso -osirrox on -indev ubuntu-21.04-desktop-amd64.iso -not_mgt on -not_paths 'extracted_dir/casper/filesystem.squashfs' -- -extract / extracted_dir

I would accept an answer with not_leaf or not_paths, but would prefer both. And an explanation of the logic behind how this is supposed to work (ie why am I not getting it?) would be nice.

I have to insert the Autounattend.xml file into a Windows 8 iso image to make the iso install automatically. My system need to run on Linux and only could use Linux shell command, so ISO tools on Winodws such as UltraISO can not be used. I have tried several methods, but all the created iso could not be booted, just printed CDBOOT: Cannot boot from CD - Code: 5 A. The first method I tried is: tuto 1. Mount iso to a folder 2. Copy the mounted iso content into a new folder 3. Add my files into the new folder 4. Use mkisofs command to create a new iso image mkisofs -o windows2008_new.iso -b boot/etfsboot.com -no-emul-boot -boot-load-size 8 -boot-info-table -V -J -l -D -N -UDF -relaxed-filenames -V "WINSP" B. The second method I tried: MS cmd tool named "oscdimg" on Windows to create new Windows iso, it works. So I copy the oscdimg into Linux and use Wine to run it, it can not be run normally. Does any one know how to make bootable Windows iso image in Linux using pure shell command?

I am building a custom iso using xorriso in mkisofs mode. The build seems correct, inspecting the iso afterwards shows 2 boot images (1 BIOS, 2 UEFI), yet booting to the ISO from qemu using the OVMF firmware fails to find any bootable media. If I try the exact same boot in qemu but using a clean downloaded ubuntu 16.04 server iso, it boots without a problem. If I use BIOS (not UEFI), both boot just fine. xorriso command: xorriso -as mkisofs \ -l -J -R -V version \ -no-emul-boot -boot-load-size 4 -boot-info-table \ -b boot/isolinux/isolinux.bin -c boot/isolinux/boot.cat \ -isohybrid-mbr isohhdpfx.bin \ -eltorito-alt-boot -e EFI/BOOT/BOOTX64.EFI -no-emul-boot \ -isohybrid-gpt-basdat \ -o testos.iso ./cddir/ The details of examining the 2 iso (ubuntu and my custom built one) with xorriso -report_el_torito plain and cmd are in the following gist https://gist.github.com/deitch/e069268f92402d6a2b1c7e060ddba622

Today, I have built isolinux from source code (git://repo.or.cz/syslinux.git) using command

make bios efi64 installer

During the building, I got some errors. For these errors, I must copy /usr/share/syslinux/{mbr.bin,ldlinux.c32...} to the appropriate directories. Now I am curious how these files such as mbr.bin and ldlinux.c32 are built from scratch？ Any advice will be appreciated!

I am trying to automate CentOS VM on ESXI using a kickstart file. After injecting the KS file I build the Custom iso using mkisofs tool. below is the command I used .\mkisofs.exe -J -R -v -T -o 'D:\myISO1.iso' -b 'isolinux/isolinux.bin' -c 'ISOLINUX\BOOT.CAT' -no-emul-boot -V 'CentOS_7_x86_64' -boot-load-size 4 -boot-info-table 'D:\CustomCentOS' The problem I am facing is: During installation the ISO is failing to find a installation media And when I run media check from boot option, Its throwing below error "Failed to start media check on /dev/sr0'