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

(I am hoping this question squeaks into the accepted set because it's about using Solaris) ---- I'm trying to get hold of ISOs for the Solaris 11 11/11 (ie. 11.0), in particular the Live installation ISO (x86) and the (two part) Repository ISO. I'm also interested in the Automatic Installation (ai) ISO, but that one isn't so important... I already have the text-installation ISO (ol-11-1111-text-x86.iso). It's unfortunately not available on Oracle's Solaris sites (unlike later version), nor have I been able to find these particular ISOs elsewhere (closest I got was defunct FTP-server in Poland). So if anybody know a still working URL or still have them archived somewhere, that would be greatly appreciated. The ISOs I'm after are: * sol-11-1111-live-x86.iso * repo: sol-11-1111-repo-full.iso-a * repo: sol-11-1111-repo-full.iso-b Or alternatively, the fully assembled version of the repo: * repo: sol-11-1111-repo-full.iso I'm also somewhat interested in the automatic install image: * sol-11-1111-ai-x86.iso Why? First I have the other versions of Solaris 11 - I'm just missing this one. Second, my decrepit old computer chocked on the last two versions. Third I like to see if this was before or after Solaris retired their "Primary Administrator" profile. By the way, was a repo-ISO like this ever released for OpenSolaris? (I know there is one for Solaris Express).

i have created linux from scratch which has / in /sdb2 and /boot in /sdb1 and swap in /sdb3 , now i want to create a iso , how do i do it? size of 1. / = 25 GB 2. /boot = 100 MB 3. /swap = 2 GB

Generating an ISO image with genisoimage, but it's not preserving the ownership. I am using the following command: genisoimage -r -v -o -R -J However, when I mount the ISO, it changes the ownership of the files to root.

I want to create a bootable USB and to put drivers folder beside my .iso image. Firstly, I wrote zeroes on my USB drive using this command:

dd if=/dev/zero of=/dev/sda bs=4096 conv=fsync oflag=direct status=progress

, got this output:

1907201+0 records in

1907200+0 records out

7811891200 bytes (7.8 GB, 7.3 GiB) copied, 2188.11 s, 3.6 MB/s

then I unmounted and formatted it:

sudo umount /dev/sda

sudo mkfs.vfat /dev/sda

Then I created a partition on it using

, and got this output in

:

NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS

sda 8:0 1 7.3G 0 disk

└─sda1 8:1 1 7.3G 0 part

Then I wrote an .iso file into my USB using

dd bs=4M if=/home/alex/Downloads/Win10_22H2_EnglishInternational_x64v1.iso of=/dev/sda conv=fsync oflag=direct status=progress

command and got this output:

1462+1 records in

1462+1 records out

6135633920 bytes (6.1 GB, 5.7 GiB) copied, 1396.19 s, 4.4 MB/s

As I understood later,

command overwrites partition table, so now my partition is gone. I'm still need to put a folder with drivers on to my USB drive beside

.iso

image. I don't know how to do it, because I can't copy my folder into USB drive, or create a new folder inside it. My partition

is disappeared, and when I try to mount

itself, it says

"source write-protected, mounted read-only"

. I heard I can use

for this kind of things, but is there any other way? I don't know what to do now and where is the problem. Would be thankful for your help.

I need to write a windows7 iso file on my usb stick. I had been used to this task. I usually either use the dd tool, or unetbootin. Surprisingly both don't work today. With dd I did the following : dd bs=4m if='windows7.iso' of=/dev/sdb My new supposedly bootable usb stick wont boot. Ok so I used unetbootin. This time, I get the unetbootin bootloader screen, but windows7 is not listed. Only the default choice is left. In either way, I failed at creating my bootable stick. Few months ago, I could make this same USB stick boot with the very same ISO file. I also did the same tasks after formatting my stick withh this command: mkfs.vfat -F 32 -I /dev/sdb There were no difference as expected. I am probably doing something wrong here, but I can't see where my mistake is. Any idea on what is going on?

On the old YUMI tool for Legacy systems, there was a distribution option of "unlisted ISO" for using the iso rescue disk image from TrueCrypt. On YUMI 0.0.1.6 (UEFI), there is nothing like that in the drop down list of options. It's all just specific distros of linux, or specific tools like DBAN, Clonezilla, etc etc etc. There's no plain unlisted ISO option. What do I select in YUMI 0.0.1.6 to burn the ISO of a Veracrypt rescue disk?

I want to create a single bootable Debian ISO by merging **DVD1**, **DVD2**, and **DVD3** of Debian 10.13.0. My goal is to install Debian **offline**, using one ISO, and have access to all packages from all three DVDs **without being prompted to insert other discs** during installation. --- ### What I did: I'm on macOS. Here's my full procedure:

brew install p7zip xorriso dpkg

mkdir -p ~/Desktop/operation/combined/{dvd1,dvd2,dvd3,merged}
cd ~/Desktop/operation

7z x debian-10.13.0-amd64-DVD-1.iso -ocombined/dvd1
7z x debian-10.13.0-amd64-DVD-2.iso -ocombined/dvd2
7z x debian-10.13.0-amd64-DVD-3.iso -ocombined/dvd3

cp -a combined/dvd1/.             combined/merged/
cp -a combined/dvd2/pool/.        combined/merged/pool/
cp -a combined/dvd3/pool/.        combined/merged/pool/

cd combined/merged
mkdir -p dists/stable/main/binary-amd64
dpkg-scanpackages pool /dev/null > dists/stable/main/binary-amd64/Packages
gzip -k -f dists/stable/main/binary-amd64/Packages

cp -a ../dvd1/isolinux ./
cp -a ../dvd1/install ./
cp -a ../dvd1/.disk ./
cp -a ../dvd1/boot ./
cp -a ../dvd1/md5sum.txt ./

xorriso -as mkisofs \
  -r -J -joliet-long -iso-level 3 \
  -V "Debian Combined" \
  -o ~/Desktop/debian-combined.iso \
  -b isolinux/isolinux.bin \
  -c isolinux/boot.cat \
  -no-emul-boot -boot-load-size 4 -boot-info-table \
  -eltorito-alt-boot \
  -e boot/grub/efi.img \
  -no-emul-boot \
  .

### The problem: During installation, I still get prompted to insert other DVD, If I say "No", installation proceeds but only ~218 packages are installed (from DVD1). Packages from DVD2 and DVD3 are not used. ### Question : What am I missing to properly merge Debian DVDs into a single ISO that contains all packages and metadata, without the installer asking for additional DVDs?

I have a an original Windows 7 Professional x86 iso file, straight from Microsoft. I want to make a bootable USB from this ISO. Some sources suggest that I simply dd the iso to the USB, but I don't see how that should work. The ISO's first 32768 bytes (reserved as System Area on ISO 9660 media, to be used fx for MBR) are all zeroes, so there is no MBR or anything for the BIOS to read. So as far as I can understand, one way is to add a MBR in this System Area, so that the ISO can be both dd'ed to a USB or written to an optical media, and be bootable from both. I think the tool isohybrid should do that trick. I don't know how it works, so I can't figure out if it should just work for all bootable (ie bootable if written to optical media) ISO 9660 files. Or does it only work for some specific/familiar iso files? At least I can't make it work with my Windows 7 iso. I get the following error: $ isohybrid win7.iso isohybrid: win7.iso: unexpected boot catalogue parameters

For operating system installation images, is there a major difference between DVD and USB images? Can I write an image such as debian-12.11.0-amd64-DVD-1.iso onto a USB and utilize it as I would any other live USB installer? Or are they *somehow* intrinsically different, and I should never utilize a DVD ISO on a USB or vice versa? _________ **Example Usage**:

$ sudo dd if=debian-12.11.0-amd64-DVD-1.iso of=/dev/sda bs=4M status=progress

I created a multi-boot USB stick to load various ISO files, which can either be live systems or used to install different Linux distributions.

sda
 -sda1     1M      | BIOS Boot partition to store MBR
 -sda2     64M     | ESP for UEFI boot
 -sda3     100G    | EXT4 for ISO & IMAGE

I can easily start ISO files such as Debian, Ubuntu, Kali or other distributions from it, using the corresponding menuentry in the /efi/boot/grub/grub.cfg Now I have an disk-image created with dd from a whole USB stick where Debian is installed. However, it's not a true ISO or image but rather a disk-image (snapshot/backup) of the USB stick with all its partitions, with the named example debian1.iso or debian2.img I've now copied this file to the partition sda3 with the other correct ISO's. I created the following menuentry with chainloader, but on the first attempt, GRUB simply restarts the boot process, and on the second attempt, I get an 'invalid signature' error.

menuentry "Chainload GRUB from USB Image debian1.iso" {
    loopback loop (hd0,3)/debian1.iso
    set root=(loop,1)
    chainloader +1
}

menuentry "Boot Debian from ISO on USB (UEFI)" {
    set root=(hd0,3)
    loopback loop /debian2.img
    set root=(loop,1)
    chainloader /EFI/debian/grubx64.efi
}

How can I start this disk-image from GRUB and what does the menu entry look like? It might be possible if the disk-image is written to a separate partition, but I don’t want that. Here are entries I found, but they mostly deal with ISO files. - GRUB2: boot to a second (another) hard disk - Using a bootable live cd disk image mounted on the hard drive - Booting an EXT4 image file from GRUB2 - how to chainload from image file which contain multiple partitions? - install grub on disk image - How to boot Linux from image on disk or "Poor Man's Install"? - GRUB Boot ISO/disk image from NTFS partition - MEMDISK can boot floppy images, hard disk images and some ISO images. At first, I found that it wasn’t possible, but then I discovered that it might be possible with memdisk or GRUB2 using loopback and overlayfs. So, it is indeed possible. **Memdisk** > Memdisk is primarily intended for temporary boot environments, > such as starting installation programs or diagnostic tools where > permanent storage is not required or desired. It is very useful if you just want to test the disk image. **loopback and overlayfs** > You can boot a disk image with GRUB’s loopback function and make the > filesystem writable by combining it with overlayfs. An overlay layer > is placed on top of the read-only image, writing changes to a separate > partition or file. This way, the original image remains unchanged, and > you can save modifications. I need to figure out how to handle the changes if it works. My GRUB is installed on a USB stick without an operating system, so I can't use grub-mkconfig. So I have to make all the changes manually. Is it possible to boot a disk-image via GRUB that is writable, make changes, and have those changes written directly to the image and how? Is there another way besides memdisk to boot where I can make changes? If it works with loopback and overlayfs, what do I need to consider, how do I set it up, and what does the menuentry looks like? Is there some kind of small hack, or should I load additional files onto the GRUB stick to make this work and how? The disk image itself also has GRUB, and the operating system on it is encrypted with LUKS. Is it maybe possible to unpack the image into memory with GRUB, call GRUB from the disk image, unlock LUKS, boot the OS, make the changes, and save the whole thing as a new disk image to some partition?

I'm facing an issue while booting a custom RHEL 8.10 ISO. During the boot process, I encounter the following error:

initqueue: /usr/sbin/fetch-kickstart-disk: line 24: rmdir: command not found

I extracted initrd.img, modified /usr/sbin/fetch-kickstart-disk, and then rebuilt the ISO. However, the problem persists. Has anyone encountered this issue before? Any suggestions on how to properly modify initrd.img or ensure rmdir is available during boot? Thanks This is what I tried: * Extract the image:

-sh
    xzcat initrd.img | cpio -idmv

* Modify line 24 to remove rmdir command:

-sh
    vi usr/sbin/fetch-kickstart-disk

* Recreate the image file

-sh
    find . | cpio -o -H newc | xz --check=crc32 -9 > /WORK/isolinux/initrd.img

* Build the ISO file

-sh
    xorriso -as mkisofs -o /RHEL-8-10-0-BaseOS-x86_64.iso -b isolinux/isolinux.bin -c isolinux/boot.cat -no-emul-boot -boot-load-size 4 -boot-info-table  /WORK/

I try to convert a .bin CD image file (with no .cue-file) of less than 800 MB with iat (Iso9660 Analyzer Tool v0.1.7) to an .iso-file on FreeBSD. With an AMD FX-8370 after 30 minutes iat still has not finished yet (iat uses one core with nearly 100% load). Is this normal? Is there any way to make iat work faster? Or what other better alternative is there to convert .bin-files into .iso-files? I have multiple images to convert and I've never seen such a bad performance when handling large files. Decompression of an encrypted 20 GB archive takes less time.

I am trying to achieve unattended Alpine Linux installation. I went through the Alpine automatic installation guide but many manual interventions are still needed during the installation! For example providing the root user name, creating the answer file (setup-alpine -c answerfileName), editing the answer file, calling the actual installation command (setup-alpine -f answerfileName) and resetting the root password. Is there any way to include the answer file inside the ISO image, select the root user by default before starting the installation and set its password after the installation is done. In CentOS we can provide kickstart file in isolinux.cfg: label MyMENU2 menu label ^Deploy Manager Node kernel vmlinuz append initrd=initrd.img inst.stage2=hd:LABEL=MYISO inst.ks=hd:LABEL=MYISO:/ks/ks1.cfg quiet Is there something similar in Alpine Linux ?

Currently I'm mounting an ISO to a (readonly) directory (using mount -o loop command) and then copying the contents to another normal directory. This takes lot of time as the ISO is large. Is this the only way to do so, or is there some alternative?

Say I have an .iso file from this dd command:

dd if=/dev/sda of=./image.iso

In the case where the drive contained multiple partitions, how could I say, only mount the second one?

I am using Ubuntu. I have a Windows 10 consumer ISO image and I want to modify the ISO to remove all editions from it but keep the Pro edition and that will be in index 4, and need to do all that work just using CLI. How to do that?

I need to mount an ISO as non-root. File names inside the mounted ISO matter. Since I'm "non-root", fuseiso is the most logical choice, but it doesn't produce "correct filenames", while mount does. With fuseiso, spaces are replaced with underscores, and capital letters are uncapitalized. Is there a way to change fuseiso's behavior to copy that of mount ? Correct content of the ISO with mount: [me@pc stalkersoup]$ sudo mount 'STALKERSOUP Game Install.iso' mnt [me@pc stalkersoup]$ ls mnt 'STALKERSOUP game setup-10.bin' 'STALKERSOUP game setup-4.bin' 'STALKERSOUP game setup-8.bin' 'STALKERSOUP game setup-1.bin' 'STALKERSOUP game setup-5.bin' 'STALKERSOUP game setup-9.bin' 'STALKERSOUP game setup-2.bin' 'STALKERSOUP game setup-6.bin' 'STALKERSOUP game setup.exe' 'STALKERSOUP game setup-3.bin' 'STALKERSOUP game setup-7.bin' Incorrect content of the ISO with fuseiso: [me@pc stalkersoup]$ fuseiso 'STALKERSOUP Game Install.iso' mnt/ [me@pc stalkersoup]$ ls mnt/ stalkersoup_game_setup_10.bin stalkersoup_game_setup_4.bin stalkersoup_game_setup_8.bin stalkersoup_game_setup_1.bin stalkersoup_game_setup_5.bin stalkersoup_game_setup_9.bin stalkersoup_game_setup_2.bin stalkersoup_game_setup_6.bin stalkersoup_game_setup.exe stalkersoup_game_setup_3.bin stalkersoup_game_setup_7.bin Context, to avoid a XYZ problem situation: * File name matters, because I want to extract the content of setup.exe with innoextract, and all the bin files contain data required for extraction, and their path is hard-coded * I do this because I'm writing a PKGBUILD (a bash script for building packages for arch). This is a bash script that must run as non-root. Therefore, I'm restricted to CLI tools as non-root * I do this for my personal usage, and this is legal as the game is freely distributed * Renaming is not an option, since mounted ISO is read-only * I can extract the content of the ISO with p7zip for instance, which is what I'm currently doing * This is not a good solution though, because it wastes time and storage * I can't modify the archive, as I must use it "as published by the author" Thanks in advance for your help and expertise :)

I made a custom UEFI only bootable ISO file and loaded it to UTM VM. The rootfs is directly stored in the ISO, and I'm using grub2 as boot loader. After I configured the linux, initrd and boot the image, the vm seems stuck forever, why?