System Report under the bootable media.If the steps above have been executed and the issue still persists, collect the following information and contact Acronis Support. Check the asamba log in /tmp/asamba.log for errors.And try to obtain DHCP lease once more:.If specifying the network manually did not help, enable asamba logs as described in Acronis Linux Products: Collecting Asamba Verbose Logs in Linux.If DHCP is not detected, you can specify the network settings manually (Actions -> Exit ->Configure Network):.

If DHCP is not detected the output will be the following: If DHCP is detected the output will be similar to this:

Check that DHCP server is really active in the subnet where the machine is booted by issuing this command in the shell:.

Issue #ifconfig -aand see which network cards are listed in the output if any.

Switch to shell: navigate to Actions -> Start shell or hit Ctrl+Shift+F2 (Alt+F1 to return back to GUI).

Check the most recent media availableįirst, try to check device work with the latest build of the Linux-based bootable media, most probably it contains more drivers and problem may be already solved.

So here is the situation: You booted machine from Linux-based Bootable Media and your NIC doesn't acquire DHCP address or isn't listed as device Solutionįollow step-by-step instructions below to troubleshoot the issue. In some rare cases there can be some issues with network cards.

Troubleshooting Acronis Backup and Recovery NIC detection issues Introduction

Acronis true image linux