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
REAR ISO cannot be created as bootable #2668
Comments
Thank you for your response @gdha , I have managed to resolve it using:
Bootable created after converting to hybrid iso and making it bootable using dd is working.
I have a question @jsmeix @gdha : Is there a way to add a customized flash screen on boot at recovery? Because REAR can be used as creating custom Linux ISO images containing installed applications. So adding a custom screen in these cases will be great and helpful. |
@MubbashirAdnan I used to have a simple splash screen with my very old project mkcdrec with isolinux. The howto can be found here: http://frantisek.rysanek.sweb.cz/splash/isolinux-splash-HOWTO.html Create a splash file and add a copy line in script usr/share/rear/output/ISO/Linux-i386/300_create_isolinux.sh to try it out. |
Thank you @gdha. Will try it out and let you know. |
@gdha Can you please guide if i can change the default timeout settings that appear after we boot the ISO? |
@MubbashirAdnan Use the variable USER_INPUT_TIMEOUT=3 in the local.conf file to define 3 seconds for example. |
@MubbashirAdnan |
Hello @gdha @jsmeix, Thank you for the help. Can you please let me know regarding the REAR ISO for migration on different disk sizes. How do i exactly configure manually if i face a disk size mismatch error while installing the generated ISO? I have performed it using the default.conf by increasing the percentage. But i want to know if there is a way to easily change the configuration of disk size while ISO is installing. Please tell the exact lines that i have to write in runtime configuration. Using default.conf disk increase percentage: i created ISO on 500GB drive and I had to install it on 1TB disk size, so i increased the disk size to 100%. What if i have to install it on even bigger disk i.e. 2TB? should i go past 100%? Waiting for the kind response, Thanks :) |
regarding migration to a system with a bit smaller or a bit bigger disk I recommend to not use AUTORESIZE_PARTITIONS="yes" In general regarding system migration with ReaR In general migrating a system onto different hardware In sufficiently simple cases it may "just work" but in general In general ReaR is first and foremost meant to recreate Additionally ReaR supports to migrate a system See also |
In default.conf tell that Using AUTORESIZE_PARTITIONS='true' with 430_autoresize_all_partitions.sh may result badly aligned partitions in particular possibly harmful aligned according to what SSDs actually need, cf. #2668 (comment)
Stale issue message |
Hi,
I have been working around with REAR for a long while. I have created ISO using CentOS7 installed on VM using:
OUTPUT=ISO
OUTPUT_URL=null
BACKUP=NETFS
BACKUP_URL="iso:///backup"
This has successfully created the ISO using "rear mkbackup". Generated ISO can be used on VM and it is booting without an issue.
I am trying to convert this ISO to a Bootable USB (without using OUTPUT=USB) as i have to share these iso's and i want people to use them by creating bootables.
I used Rufus to create bootable usb of the ISO but it is not booting on base system.
Can you please guide on exact configuration for this case? i don't have a requirement to create backup as well, 'mkrescue' can also work in my case as i just require installed binaries to stay inside the ISO.
The text was updated successfully, but these errors were encountered: