How to properly make a bootable iso from the contents of a directory

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP








up vote
0
down vote

favorite












I wanted to have a customized Ubuntu Live CD so:



I mounted ubuntu-18.04-desktop-amd64.iso.



Copied its content to a directory in my home folder.



Used unsquashfs filesystem.squashfs to extract the file system.



Used chroot to change the root into the extracted file system.



Uninstalled some packages I didn't need.



Used sudo mksquashfs squashfs-root filesystem.squashfs -b 1048576 -comp xz -Xdict-size 100% to pack the modified file system back into filesystem.squashfs.



Replaced the original filesystem.squashfs I extracted with the modified one.



Used genisoimage -r -V "Ubuntu" -cache-inodes -J -l -b isolinux/isolinux.bin -c isolinux/boot.cat -no-emul-boot -boot-load-size 4 -boot-info-table -o ironpig.iso FC5/ to build a .iso (FC5 being the directory I extracted ubuntu-18.04-desktop-amd64.iso into).



But after burning ironpig.iso into a SD card with Etcher it looks like this:



enter image description here



But I get this by burning the original ubuntu-18.04-desktop-amd64.iso:



enter image description here



How can I make my.iso bootable?







share|improve this question
























    up vote
    0
    down vote

    favorite












    I wanted to have a customized Ubuntu Live CD so:



    I mounted ubuntu-18.04-desktop-amd64.iso.



    Copied its content to a directory in my home folder.



    Used unsquashfs filesystem.squashfs to extract the file system.



    Used chroot to change the root into the extracted file system.



    Uninstalled some packages I didn't need.



    Used sudo mksquashfs squashfs-root filesystem.squashfs -b 1048576 -comp xz -Xdict-size 100% to pack the modified file system back into filesystem.squashfs.



    Replaced the original filesystem.squashfs I extracted with the modified one.



    Used genisoimage -r -V "Ubuntu" -cache-inodes -J -l -b isolinux/isolinux.bin -c isolinux/boot.cat -no-emul-boot -boot-load-size 4 -boot-info-table -o ironpig.iso FC5/ to build a .iso (FC5 being the directory I extracted ubuntu-18.04-desktop-amd64.iso into).



    But after burning ironpig.iso into a SD card with Etcher it looks like this:



    enter image description here



    But I get this by burning the original ubuntu-18.04-desktop-amd64.iso:



    enter image description here



    How can I make my.iso bootable?







    share|improve this question






















      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      I wanted to have a customized Ubuntu Live CD so:



      I mounted ubuntu-18.04-desktop-amd64.iso.



      Copied its content to a directory in my home folder.



      Used unsquashfs filesystem.squashfs to extract the file system.



      Used chroot to change the root into the extracted file system.



      Uninstalled some packages I didn't need.



      Used sudo mksquashfs squashfs-root filesystem.squashfs -b 1048576 -comp xz -Xdict-size 100% to pack the modified file system back into filesystem.squashfs.



      Replaced the original filesystem.squashfs I extracted with the modified one.



      Used genisoimage -r -V "Ubuntu" -cache-inodes -J -l -b isolinux/isolinux.bin -c isolinux/boot.cat -no-emul-boot -boot-load-size 4 -boot-info-table -o ironpig.iso FC5/ to build a .iso (FC5 being the directory I extracted ubuntu-18.04-desktop-amd64.iso into).



      But after burning ironpig.iso into a SD card with Etcher it looks like this:



      enter image description here



      But I get this by burning the original ubuntu-18.04-desktop-amd64.iso:



      enter image description here



      How can I make my.iso bootable?







      share|improve this question












      I wanted to have a customized Ubuntu Live CD so:



      I mounted ubuntu-18.04-desktop-amd64.iso.



      Copied its content to a directory in my home folder.



      Used unsquashfs filesystem.squashfs to extract the file system.



      Used chroot to change the root into the extracted file system.



      Uninstalled some packages I didn't need.



      Used sudo mksquashfs squashfs-root filesystem.squashfs -b 1048576 -comp xz -Xdict-size 100% to pack the modified file system back into filesystem.squashfs.



      Replaced the original filesystem.squashfs I extracted with the modified one.



      Used genisoimage -r -V "Ubuntu" -cache-inodes -J -l -b isolinux/isolinux.bin -c isolinux/boot.cat -no-emul-boot -boot-load-size 4 -boot-info-table -o ironpig.iso FC5/ to build a .iso (FC5 being the directory I extracted ubuntu-18.04-desktop-amd64.iso into).



      But after burning ironpig.iso into a SD card with Etcher it looks like this:



      enter image description here



      But I get this by burning the original ubuntu-18.04-desktop-amd64.iso:



      enter image description here



      How can I make my.iso bootable?









      share|improve this question











      share|improve this question




      share|improve this question










      asked May 13 at 10:04









      IronPig

      382216




      382216




















          1 Answer
          1






          active

          oldest

          votes

















          up vote
          0
          down vote













          A cd typically uses iso9660 on the raw media and through the spec uses El Torito (an emulated floppy drive with a drive image) for booting along with UEFI which requires an EFI executable at /EFI/boot/bootx64.efi. The emulated floppy image is also for UEFI formated FAT32 containing the same /EFI/boot/bootx64.efi but also contains a legacy boot loader at the beginning of the image.






          share|improve this answer




















          • Other arrangements are possible like for example a GPT partitioned CD containing an ESP.
            – jdwolf
            May 13 at 10:46










          Your Answer







          StackExchange.ready(function()
          var channelOptions =
          tags: "".split(" "),
          id: "89"
          ;
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function()
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled)
          StackExchange.using("snippets", function()
          createEditor();
          );

          else
          createEditor();

          );

          function createEditor()
          StackExchange.prepareEditor(
          heartbeatType: 'answer',
          convertImagesToLinks: true,
          noModals: false,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          );



          );








           

          draft saved


          draft discarded


















          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1035645%2fhow-to-properly-make-a-bootable-iso-from-the-contents-of-a-directory%23new-answer', 'question_page');

          );

          Post as a guest






























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          up vote
          0
          down vote













          A cd typically uses iso9660 on the raw media and through the spec uses El Torito (an emulated floppy drive with a drive image) for booting along with UEFI which requires an EFI executable at /EFI/boot/bootx64.efi. The emulated floppy image is also for UEFI formated FAT32 containing the same /EFI/boot/bootx64.efi but also contains a legacy boot loader at the beginning of the image.






          share|improve this answer




















          • Other arrangements are possible like for example a GPT partitioned CD containing an ESP.
            – jdwolf
            May 13 at 10:46














          up vote
          0
          down vote













          A cd typically uses iso9660 on the raw media and through the spec uses El Torito (an emulated floppy drive with a drive image) for booting along with UEFI which requires an EFI executable at /EFI/boot/bootx64.efi. The emulated floppy image is also for UEFI formated FAT32 containing the same /EFI/boot/bootx64.efi but also contains a legacy boot loader at the beginning of the image.






          share|improve this answer




















          • Other arrangements are possible like for example a GPT partitioned CD containing an ESP.
            – jdwolf
            May 13 at 10:46












          up vote
          0
          down vote










          up vote
          0
          down vote









          A cd typically uses iso9660 on the raw media and through the spec uses El Torito (an emulated floppy drive with a drive image) for booting along with UEFI which requires an EFI executable at /EFI/boot/bootx64.efi. The emulated floppy image is also for UEFI formated FAT32 containing the same /EFI/boot/bootx64.efi but also contains a legacy boot loader at the beginning of the image.






          share|improve this answer












          A cd typically uses iso9660 on the raw media and through the spec uses El Torito (an emulated floppy drive with a drive image) for booting along with UEFI which requires an EFI executable at /EFI/boot/bootx64.efi. The emulated floppy image is also for UEFI formated FAT32 containing the same /EFI/boot/bootx64.efi but also contains a legacy boot loader at the beginning of the image.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered May 13 at 10:45









          jdwolf

          676110




          676110











          • Other arrangements are possible like for example a GPT partitioned CD containing an ESP.
            – jdwolf
            May 13 at 10:46
















          • Other arrangements are possible like for example a GPT partitioned CD containing an ESP.
            – jdwolf
            May 13 at 10:46















          Other arrangements are possible like for example a GPT partitioned CD containing an ESP.
          – jdwolf
          May 13 at 10:46




          Other arrangements are possible like for example a GPT partitioned CD containing an ESP.
          – jdwolf
          May 13 at 10:46












           

          draft saved


          draft discarded


























           


          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1035645%2fhow-to-properly-make-a-bootable-iso-from-the-contents-of-a-directory%23new-answer', 'question_page');

          );

          Post as a guest













































































          Popular posts from this blog

          Which professions warranted travel in Medieval times?

          How do so many people here on Academia.SE, and in general, afford lavish higher education programs?

          Trouble downloading packages list due to a “Hash sum mismatch” error