-
Notifications
You must be signed in to change notification settings - Fork 246
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unknown -e flag with genisoimage under Debian #828
Comments
@erkannt what version of genisoimage are you using? |
I'm also running |
that is really strange, because if I run:
No ambiguous warning ... Do you have |
Very strange indeed. |
All this EFI boot wars drives me nuts, I personally don't see a reason for such big difference despite same version number is used. |
One more thing I just realized ... You are using |
http://trac.mondorescue.org/ticket/782 I manually changed Would it be sensible to include such a workaround in the defaul/Debian.conf? |
That is interesting, however I'm not sure that |
and maybe one more question that I should ask at the very begging. :-) |
I currently am using EFI boot, but have no qualms is switching to BIOS boot. I was able to boot from the created ISO when mounting it as a virtual drive via iDRAC. |
If you really can switch to legacy boot, my humble advice would be DO SO AND NEVER LOOK BACK ;-), you will save lot of trouble to your self ... |
I am afraid my knowledge in general about UEFI From my very limited own experience with UEFI @gozora What exactly do you mean with "ReaR on USB ... rear format ... Shouldn't it work generically to let "rear mkrescue" create Isn't it a different way to use "rear format"? Regarding "rear format": What I found documented about it: create a bootable USB backup doc/rear-release-notes.txt reads (excerpts): External USB booting now uses extlinux instead of syslinux, and therefore, the USB disk must first be formatted with an ext2, ext3, ext4 or btrfs based file system doc/user-guide/04-scenarios.adoc reads (excerpts): To prepare your USB device for use with Relax-and-Recover, do: rear format /dev/sdX This will create a single partition, make it bootable, format it with ext3, label it REAR-000 It seems nothing is documented about BIOS versus UEFI lib/format-workflow.sh reads (excerpts): # Usage: rear -v format -- -h /dev/ # By default 1 partition will be created with ext3 format and label REAR-000 # With the --efi toggle you get 2 partitions (vfat and ext3) so we are able # to make this USB UEFI bootable afterwards It seems with "rear format --efi /dev/sdX" But I never tried that myself. |
@jsmeix From what I've understood UEFI recognizes (by default) only FAT file systems. Means that if you plug in any device that does not contain FAT and trigger information about Thanks for pointing it out! |
I love "git blame" for "assignment of guilt" ;-) $ git blame usr/share/rear/lib/format-workflow.sh ... 9fa2faaf (Gratien D'haese 2015-06-05 16:43:13 +0200 4) # Usage: rear -v format -- -h /dev/ 9fa2faaf (Gratien D'haese 2015-06-05 16:43:13 +0200 5) # By default 1 partition will be created with ext3 format and label REAR-000 9fa2faaf (Gratien D'haese 2015-06-05 16:43:13 +0200 6) # With the --efi toggle you get 2 partitions (vfat and ext3) so we are able 9fa2faaf (Gratien D'haese 2015-06-05 16:43:13 +0200 7) # to make this USB UEFI bootable afterwards ... 9fa2faaf (Gratien D'haese 2015-06-05 16:43:13 +0200 26) (-e|--efi) EFI=y;; $ git log | grep -A7 9fa2faaf commit 9fa2faaf9d59fec679e68645963365ae41598441 Author: Gratien D'haese Date: Fri Jun 5 16:43:13 2015 +0200 Added some clarification on how to use the options in the format workflow. Added an --efi toggle to create an UEFI bootable disk (partitions only for the moment) issue #593 which refers to #593 But the "partitions only for the moment" may indicate that It seems it is @gdha who knows the real details here... |
Hey there, Using Debian 8 and rear-1.17.2. The same issue with option In the mean time, maybe the Debian version should depend on xorriso instead of genisoimage and ship Cheers. |
In general that should not do any harm, considering that xorriso really works fine. |
I am not a Debian or Ubuntu user but in general |
@carragom Don't be afraid to contribute to Relax-and-Recover |
With #962 merged |
It is not fixed for me unfortunately. I am backing up a Debian 9 system installed in UEFI mode. And I also get:
carragom's workaround (#828 (comment)) works for me. But shouldn't the default be sane even for UEFI? genisoimage here is
|
@Signum why not create a dedicated config file for Debian? Use |
Only FYI a general addendum: In ReaR basically all is bash scripts, in particular config files Therefore one can do arbitrary bash scripting in config files as needed
One must consider that etc/rear/local.conf is also used during "rear recover" |
Built and installed deb-package from current master with
make deb OFFICIAL=1.18
.Tried running
rear -v mkrescue
with the following conf:This fails when creating ISO image.
This error has come up previously on OpenSUSE #804. Here it was solved by using ebiso. But this is on Debian where genisoimage should work if I understand this post correctly.
The text was updated successfully, but these errors were encountered: