-
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
ReaR PXE setup for SLES11 to boot HP ProLiant with UEFI #1335
Comments
Hi, Maybe you can take a look at DRLM (www.drlm.org) to manage your PXE rear setup with central managent of rear configs, scheduling and more... ;) Regards, |
@didacog you was the first thing on my mind when I've read subject of this issue :-) |
@suneeload I've found this. Maybe it helps. V. |
@gozora: thanks for sharing, that helped in creating rescue image on PXE server. But I still can not see rescue image in pxe boot options. Here is local.conf: OUTPUT=PXE |
@suneeload You should check the PXE config files at http://10.48.187.202/tftpboot/pxelinux.cfg location. |
@gdha PXE config files were not uploading at http://x.x.x.x/tftpboot/pxelinux.cfg, although in logs it says "Created pxelinux config 'rear-xxxx' and symlinks for IP adresses in http://x.x.x.x/tftpboot/pxelinux.cfg". |
Maybe I got it all wrong (I never used ReaR with PXE), but is "rescue image" created with PXE at all? V. |
@gozora you are right, PXE is just providing initrd and kernel for client booting. |
I am able to boot from PXE, now rear recover is failing with following error: |
Again just a guess, 'ifconfig <dev_name> inet <ipaddress> netmask 255.0.0.0 |
Thanks @gozora that didnt help. |
Do you see some network interfaces in |
yes, it say UP. But i cannot even ping to gateway. |
Can you paste output here? |
Ok try, ifconfig eth6 inet <ipaddress> netmask 255.0.0.0; rear recover |
Thinking of it, you might really have drivers missing when migrating... |
I would be surprised at a driver problem as you actually see a NIC in the VM. Do you use DHCP on the physical server? If so then maybe there was an issue picking that up. To check try to add I would also expect the rescue system to take you through the network reconfiguration where you would have to choose the network card. |
@gozora "ifconfig eth6 inet netmask 255.0.0.0; rear recover" solved network issue and recover is successfully finished, but after reboot system is not booting up (error: OS not found). I checked BIOS setting and changed it local disk, even that didnt solve the issue. Any suggestion, anyone please? pasting error below: |
See issue #214 on this. SLES has a patched version of mkisofs and causes issues with uefo. The current solution is located at this link: http://www.it3.be/2015/10/27/uefi-iso-boot-with-ebiso/ |
@suneeload Are your questions answered? |
@gdha nope, still trying to solve the issue :( |
@suneeload you can also try with installing xorriso and run rear mkbackup -v and see if it is throwing the flag USING_EFI_BOOTLOADER=1. if it is, it is creating a efi compatible disk. if it is not, you can set it manually in the config. |
Hello @suneeload, 2 things ...
V. |
Hi @gozora:
Thanks |
Does REAR work with PXE ( HP proliant running sles 11.x) , anyone tried? |
tried to restore on same server but still getting same error while rear recover, as above : "Error: could not find elilo executables". Pasting local.conf again: OUTPUT=PXE Any help! |
@suneeload I wouldn't know why PXE booting wouldn't work on HPE Proliant systems. The rear config looks OK to me, and I guess that PXE booting works? Or am I wrong? Could you paste the output of You could run once |
you may need more information. |
@gozora |
@jsmeix, Yes stupid me did not read message after
Thanks! V. |
Thank you all for your help, I can now restore and server is working fine after restore :) only change i made was to download rear packages from http://download.opensuse.org/repositories/Archiving:/Backup:/Rear/SLE_12_SP1/x86_64/ , rather than using git clone. |
@suneeload Under Regarding P2P and V2V works while P2V does not work: |
@jsmeix Thanks |
I just successfully finished test recovery of my SLES11 SP3 with latest upstream commit 8ce891f . Following configuration was used:
During your P2V recovery, are your source and destination servers using SAME boot method (UEFI/Legacy boot) ? V. |
@gozora no both are different boot methods, i.e. physical uses UEFI and VM is grub. Thanks, |
Changing the bootloader is another "migration" thing This means - as far as I can imagine - changing the bootloader I think this can be done basically in the same way For example after adapting the restored bootloader config files target_system_filesystem_root="/mnt/local" bootloader_install_device="/dev/sdXn" # Make /proc /sys /dev from the installation system # or from the ReaR recovery system # available in the target system: for mountpoint_directory in proc sys dev do mkdir $target_system_filesystem_root/$mountpoint_directory done mount -t proc none $target_system_filesystem_root/proc mount -t sysfs sys $target_system_filesystem_root/sys mount -o bind /dev $target_system_filesystem_root/dev # Make initrd verbosely in the target system: chroot $target_system_filesystem_root /bin/bash --login -c "/sbin/mkinitrd -v" # Install bootloader in the target system: # Make bootloader configuration in the target system: chroot $target_system_filesystem_root /bin/bash --login -c "/usr/sbin/grub2-mkconfig -o /boot/grub2/grub.cfg" # Install bootloader in the target system: chroot $target_system_filesystem_root /usr/sbin/grub2-install --force $bootloader_install_device That has worked for me on SLES12 on a simple virtual machine. As far as I know the only part of a system migration where But I think one cannot expect that e.g. migrating from |
I tested my above chroot $target_system_filesystem_root /bin/bash --login -c "..." cf. #862 Furthermore I tried to avoid that "rear recover" installs NOBOOTLOADER=1 and also in the recovery system # mv /var/lib/rear/recovery/bootloader /var/lib/rear/recovery/bootloader.orig did not avoid that "rear recover" installs a bootloader |
@sko341 is your question answered sufficiently or do you still have other concerns at this point in time? |
lets close it for now |
Relax-and-Recover (ReaR) Issue
Can someone please help me configure rear for DR with PXE. Idea is to store rear rescue image to PXE server, and in event of disaster, recover via pxe boot. Sharing of local.conf configuration for this setup will be highly appreciated.
Relax-and-Recover 2.00 / Git
SLES 11 SP4
Thanks
The text was updated successfully, but these errors were encountered: