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 ---"
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).
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 /dev/disk/ by-label/ eSysRescueLiveC D initrd= /casper/ initrd. gz quiet splash ---"
You will see the following line:
"boot=casper live-media=
4. Delete the following part: media=/ dev/disk/ by-label/ eSysRescueLiveC D"
"live-
...so the line reads: /casper/ initrd. gz quiet splash ---"
"boot=casper initrd=
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) /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/ eSysRescueLiveC D").
I will keep this bug open to fix the issue in comment # 13 (https:/
(2) /dev/disk/ by-label/ eSysRescueLiveC D" (and will no longer need not use F4 each time to boot your custom live iso).
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=