-
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
we have faced a network connectivity issue when the REAR ISO has been booted #1818
Comments
@nirmal21s As a possible workaround in this particular case when manual Such a PRE_RECOVERY_SCRIPT is run during "rear recover" via # rear -s recover Simulation mode activated ... Source conf/Linux-i386.conf Source conf/GNU/Linux.conf Source conf/SUSE_LINUX.conf Source init/default/005_verify_os_conf.sh Source init/default/010_set_drlm_env.sh Source init/default/030_update_recovery_system.sh Source init/default/050_check_rear_recover_mode.sh Source setup/default/005_ssh_agent_start.sh Source setup/default/010_pre_recovery_script.sh ... |
@nirmal21s MODULES_LOAD=( tg3 igb ) might help in your case. In general to debug what happens during recovery system startup: In general regarding debugging issues with the start up scripts Add 'debug' to the ReaR kernel command line In the ReaR recovery/rescue system boot menue select You may found yourself stopped at a blank screen. The further start up scripts are run one by one In 'debug' mode the start up scripts are run with 'set -x' Cf. |
@jsmeix PRE_RECOVERY_SCRIPT=(rmmod tg3 ; mmod igb ; modprobe tg3 ; modprobe igb) I hope the parameter is correct. |
PRE_RECOVERY_SCRIPT and POST_RECOVERY_SCRIPT |
@jsmeix So do i need to remove "USE_STATIC_NETWORKING="y"" and use USE_DHCLIENT=y .. |
@nirmal21s About USE_DHCLIENT: If You have an DHCP server available use it. But I assume not using DHCP is not the issue here. BTW, can You provide the information which kind of server is in use? Thanks. |
@hpannenb |
@nirmal21s I believe the question was "do you have internally a DHCP server you can use to gain an IP address (during a recovery)?" |
@gdha The below mentioned is correct :
|
@nirmal21s You could try the following. Add above commands into a script and saved it as |
@nirmal21s good thinking as on RHEL 7.5 the |
@gdha I will test it and confirm .. |
After removing the below parameters : BACKUP_RESTORE_MOVE_AWAY_FILES=( /lib/udev/rules.d/70-persistent-net.rules ) We tried to crated a new ISO image and tried to boot. But we were able to ping only this servers gateway and not able to ping the backup server IP. |
There were changes made to how linux boots & identifies the Ethernet interfaces. In my case I ALWAYS have to boot my HP servers with "REAR" in "manual mode", since it is impossible for rear to guess my network config. (unless i make manual scripts) "ip addr" gets me I then MUST So how can REAR fail to find the ipaddress on a functioning network, seems foolish ? cat ifcfg-enp3s0f0 cat ifcfg-br-ex Ha Har...... |
FYI Perhaps that could help in this case? |
Yes.. I have added the PRE_RECOVERY_SCRIPT=/usr/share/rear/skel/default/etc/scripts/system-setup.d/77-my-network-setup.sh.. It worked fine.. Thanks a lot for your support. |
@nirmal21s |
Relax-and-Recover (ReaR) Issue Template
Fill in the following items before submitting a new issue
(quick response is not guaranteed with free support):
The problem is in the mapping of the server physical interfces to the ethXX logaical interface names. As you can see in the screenshot (1) the eth names are assigned to the physical interfaces almost in random which is incorrect configuration. When I removed network card kernel modules (rmmod tg3;rmmod igb) and probed than back again (modprobe tg3, modprobe igb) the mapping between the physical interfaces and logical interface names is correct as you can see on screenshot (2). The mapping is configured in the udev conf file located in /lib/udev/rules.d/70-persistent-net.rules This file is present on the REAR iso as well, seems not used by the REAR initramdisk during bootup though.
70-persistent-net_rules.txt
The text was updated successfully, but these errors were encountered: