Iso created is not bootable

Podesta,

What tool did you use "burn" your iso to USB?

Do you still have all the Cubic Project Folder and Files inside it (so we can take a look at some of the files, if we need to)?

I used dd. Something like "sudo dd bs=4M if=/image/to/iso of/dev/sdX oflag=sync status=progress". Burning the original iso the same way had no issues.

I still have the project folders. In fact I have three of them, since I initially thought I was editing something that was causing problems, so I made a few different tests, and even without any changes, it gives the same problem.

I managed to edit a ubuntu 18 image and boot into the live desktop without any problems.

1. Would you please share the contents of...

   (A) <Cubic Project Folder>/custom-live-iso/boot/grub/grub.cfg

   (B) <Cubic Project Folder>/custom-live-iso/boot/grub/loopback.cfg

You might also want to try...

2. Instead of dd, try using mkusb (https://help.ubuntu.com/community/mkusb) to create the USB image.

3. Have you tried to boot your customized iso directly from your hard drive into Virtual Box (instead of creating a bootable USB)?

If you prefer other sort of pastebin, or me to paste the contents directly here let me know.

1(A). grub.cfg https://privatebin.net/?ad42f4b84b1692c7#TQfmU7jxmkEvjsNiynVsQBuCnA+G2lcBGO8MTefGCsc=

1(B). loopback.cfg https://privatebin.net/?a710f4be91981be7#kzMKOaUoCVjqeCaFlIYltPSPqrrBSxD/OIWazRWyJ20=

2. Burning the image to the USB with mkusb, the problem still happened.

3. Just tried booting from virtualbox, and same problem persists. The original iso booted fine.

Thanks.

What is output of...

$ ls -l <Cubic Project Folder>/custom-live-iso/casper

total 764136
-rw-r--r-- 1 root root 26885 feb 6 13:16 filesystem.manifest
-rw-r--r-- 1 root root 10 feb 6 13:17 filesystem.size
-rw-r--r-- 1 root root 735285248 feb 6 13:17 filesystem.squashfs
-rw-r--r-- 1 root root 40260426 mar 21 2018 initrd.gz
-rw-r--r-- 1 root root 6886336 mar 21 2018 vmlinuz

Thanks.
This is the information I needed.

I'll get back to you in a few days...

I will download ESET SysRescue and use Cubic to customize it, so I can recreate this issue and move the bug to "Confirmed" state.

I will also see if I can suggest a work-around for you, for the short term, while I work on this.

Thanks! That's very much appreciated.

Don't worry about a short term solution for me. I created a ubuntu removable media with their antivirus solution already installed, which is ok for a stoppgap solution.

If you need any other info from me, let me know.

Good morning,

I also have this problem while I used rufus.ie .
Same issue with several Ubuntu ISOs(16.04, 18.04, 18.10) and with several USB keys.

Tested on HP Zbook G3 15 , Lenovo Ideapad Z710 and on VMware 15.

Bensuperpc,

I'm surprised you are having this issue with standard Ubuntu ISOs, since I've tested all three of these Ubuntu releases (16.04, 18.04, 18.10).

Are you using an Ubuntu derivative (as Pddesta was doing with Eset SysRescue)?

Would you please share, for each ISO you are customizing:

   (A) Download location URL of the ISO you are customizing

   (B) Output of ls -l <Cubic Project Folder>/custom-live-iso/casper

   (C) Contents of <Cubic Project Folder>/custom-live-iso/boot/grub/grub.cfg

   (D) Contents of <Cubic Project Folder>/custom-live-iso/boot/grub/loopback.cfg

Bensuperpc,

If you have some time, would you try using mkusb, instead of rufus, and let me know if the ISO is still not bootable?

Also, please confirm you are receive the same error message as in this Bug Report:
  busybox screen, reporting "(initramfs) Unable to find a medium containing a live file system"
?

Customized eset_sysrescue_live_enu files from Comment # 4

(https://bugs.launchpad.net/cubic/+bug/1814598/comments/4)

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

grub.cfg

if loadfont /boot/grub/font.pf2; then
    insmod efi_gop
    insmod efi_uga
fi

set menu_color_normal=white/black
set menu_color_highlight=black/light-gray
set default=0
set timeout=60

menuentry "Run ESET SysRescue" {
    linux /casper/vmlinuz boot=casper live-media=/dev/disk/by-label/eSysRescueLiveCD quiet splash
    initrd /casper/initrd.lz
}

menuentry "Boot from hard disk" {
    exit
}

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

loopback.cfg

menuentry "Run ESET SysRescue" {
 linux /casper/vmlinuz boot=casper iso-scan/filename=${iso_path} quiet splash ---
 initrd /casper/initrd.gz
}
menuentry "Check disc for defects" {
 linux /casper/vmlinuz boot=casper integrity-check iso-scan/filename=${iso_path} quiet splash ---
 initrd /casper/initrd.gz
}
menuentry "Test memory" {
 linux16 /install/mt86plus
}

Podesta,

ESET SysRescue
==============

I discovered that the initrd file on the original ISO (eset_sysrescue_live_enu.iso) has the wrong extension. The file name should be "initrd.gz" because it uses "gz" compression, not "lz" compression. I recommend opening a bug with ESET SysRescue to correct this on their live ISO.

The output of the "file" command shows that "initrd.lz" is "gzip compressed data"...
    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

    ~/Custom_2/custom-live-iso/casper $ ls -1
    initrd.lz
    vmlinuz

    ~/Custom_2/custom-live-iso/casper $ file initrd.lz
    initrd.lz: gzip compressed data, last modified: Mon May 21 12:55:24 2018, from Unix, original size 94081536

    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

(For more information, see https://catchchallenger.first-world.info/wiki/Quick_Benchmark:_Gzip_vs_Bzip2_vs_LZMA_vs_XZ_vs_LZ4_vs_LZO)

Cubic
==============

Cubic ~does~ correct the file extension based on the compression type.
However Cubic overlooks updating the filename in grub.cfg, and this is what needs to be fixed.

Your customized ISO is not booting because ESET SysRescue expects the Volume ID in the "live-media=" boot parameter.

WHAT TO DO
==========

You must to manually remove the "live-media=" boot parameter each time you boot into your customized ISO.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

  1. Select "Run EST SysRescue"

  2. Press F4 key. (Then press ESC to dismiss the pop-up, if you get one).

  3. Press Tab key to edit boot parameters
     You will see the following line:
     "boot=casper live-media=/dev/disk/by-label/eSysRescueLiveCD initrd=/casper/initrd.gz quiet splash ---"

  4. Delete the following part:
     "live-media=/dev/disk/by-label/eSysRescueLiveCD"

     ...so the line reads:
     "boot=casper initrd=/casper/initrd.gz quiet splash ---"

  5. Press enter to boot.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

EXPLANATION
===========

The new volume id that Cubic creates is something like "eSysRescueLiveCD YYYY.MM.DD".

The ESET SysRescue boot loader expects the volume id to be exactly "eSysRescueLiveCD", as you can see from the boot parameters above.

Ubuntu doesn't use the

Because Ubuntu uses more complex volume ids, such as "Ubuntu-Server 14.04.5 LTS amd64", for example, I can not change Cubic to use the format required by ESET SysRescue.

NEXT STEPS
==========

(1)
I will keep this bug open to fix the issue in comment # 13 (https://bugs.launchpad.net/cubic/+bug/1814598/comments/13). The issue in comment # 13 could affect other Ubuntu distributions or some of the other ESET SysRescue boot choices (like "Check disk for defects" or "Test memory"). (Of course, you still need to manually remove "live-media=/dev/disk/by-label/eSysRescueLiveCD").

(2)
In the future, I will be adding a page to Cubic where the user can manually edit the boot parameters before generating the customized iso. Then, you will be able to permanently remove "live-media=/dev/disk/by-label/eSysRescueLiveCD" (and will no longer need not use F4 each time to boot your custom live iso).

I LEFT OUT THE SIMPLEST SOLUTION....

Open your existing Cubic project.

On Project Page, edit the Volume ID text field in the "Custom ISO..." section. (See attached screen shot).

  Change:
    eSysRescueLiveCD 2019.XX.XX

  To:
    eSysRescueLiveCD

(You can leave the "Create a disk image from the existing project" radio button checked if you don't need to go into the chroot environment to make changes).

Then generate your customized iso, and it should work!

Fix released in trunk revision 181.
Fix released in release revision 46.

Note, even with this fix, you still need to edit the Volume ID on Cubic's Project Page. (See https://answers.launchpad.net/cubic/+question/678489)

I'm sorry, all notifications after my last message ended up going to my spam folder. Thanks a bunch for taking a look into it and not only the detailed explanation of the problem but also providing various solutions. Really, really appreciated. Thanks!