Aller au contenu principal

Network card Intel

Thread needs solution
Beginner
Contributions: 2
Commentaires: 1

Hello

The bootable media don t reconize the new Intel I219-lm.

I can t join my Nas with new model HP with this network card.

 

Thx

0 Users found this helpful
Forum Hero
Contributions: 57
Commentaires: 9243

Please provide more information about your NAS, make, model, are you using SMB/Samba shares over CIFS and include what version of Windows you are using.  Windows 10 has some issues with network connectivity so that could be at root of your issue.

Forum Hero
Contributions: 87
Commentaires: 9259

A solution would be to create a WIN-PE based recovery media. It boots a more slowly than the Linux based, it doesn't include wireless networking, but it supportss hardware much better.

Beginner
Contributions: 2
Commentaires: 1

Hi

Like Pat L understand, the fail is not with the Nas Synology.

Acronis bootable media recovery don t detect the network card Intel 219-lm.

My acronis is True image 2016 version 6027.

I ll try to create a Win re media.

Beginner
Contributions: 0
Commentaires: 1

Same here. My Gigabyte Brix is using the Intel i219-LM network adapter. Under Windows10 no issue to backup to my Synology. When using F11 during boot to go to Acronis boot manager the network adapter is nog recognized by Acronis boot and hence I am not able to do restore.

Any update on this?

Legend
Contributions: 109
Commentaires: 27771

Bas, the F11 Acronis Startup Recovery Manager (ASRM) uses the standard Linux OS boot environment and may not have the device drives needed for your Intel network adapter.

I would recommend making sure that you have installed the latest build 6569 version for ATIh 2016 and that you remove the ASRM and then activate it again to ensure that that boot environment has also been updated to the latest code version.

If that doesn't recognise your Intel network adapter still, then you will need to build the Windows PE bootable rescue media and use that from either DVD or USB stick instead of using ASRM.

Forum Hero
Contributions: 87
Commentaires: 9259

On my asus motherboard, i have 2 Intel Ethernet adapters: one I219-V and on is I211-AT. The default Linux based recovery medium can see the latter (older) one, but not the former (newer version). I am personally OK, because the difference in features is minimal in my case, and, at least, I have one that is working.

You will have to take to produce a Win-PE recovery media. With Win-PE, you have to use a command line to connect to a network share, which is a bit of a pain. If you are more advanced, there are some other options that are much more user friendly than WinPE, like WinSE-PE, but that requires fiddling with .wim files and configuration files to incorporate a program like ATI. So production is advanced, but usage is very convenient.

Forum Hero
Contributions: 70
Commentaires: 8346

I also have purchased a USB 3.0 to Gigabit ethernet adapter for situations like this.  Not very expensive and comes in handy for a wide range of uses too.  The drivers are very generic for these, have always been detected for me with default Acronis recovery media and can also be used on tablets like the Surface Pro or other small/cheap tablests that don't have onboard ethernet either.  

Otherwise, creating WinPE is the way to go.  Download and install the Microsoft ADK for Windows 10.  Once installed, run your bootable rescue media builder in Acronis.  Instead of the default, click on WinPE and it will do the rest.  I believe the default Windows ADK already has the drivers needed for this adapter, but don't have one to test on.

 

Beginner
Contributions: 0
Commentaires: 3

Hi All,

Beside getting the USB 3.0 adapter, is there any other way? Have tried using the Windows PE version and booted into menu. But when query using 'ipconfig' at the command prompt, message states initialization error. Btw, have inserted the 1219-LM Windows 7 + Windows 10 drivers during the acronis media creation.

Forum Hero
Contributions: 70
Commentaires: 8346

WinPE will work, but you'll need to add drivers using ADK DISM commands. You do not want to mix and match drivers from Windows 7 and Windows 10 in your WinPE. 

Not sure what version of ADK you have installed, but if you don't have the latest version of Windows 10 ADK (which can be installed on Windows7 - Windows 10), I would remove what you have and install the Windows 10 ADK it instead (looks like there is a new 1607ADK for the annual release of Windows 10 that just came out this week, so grab that if you have it, or grab 1511 if you don't yet have the annual release).  Then, create the WinPE with Acronis.  Once created (assuming a USB flash drive), then add the Windows 10 drivers Intel Nic drivers into your WinPE.

Below is an example using Windows 10 ADK commands from command prompt (change folders to match yours).  You can copy the boot.wim from your usb drive root/sources/boot.wim.  Then update drivers and replace on the USB drive. 

 

Dism /Mount-WIM /WimFile:"C:\boot.wim" /index:1 /MountDir:"C:\MOUNT"

Dism /Image:C:\MOUNT /Add-Driver /Driver:C:\Drivers\PROWinx64 /Recurse /ForceUnsigned

Dism /Unmount-wim /mountdir:"C:\MOUNT" /commit

 

 

Beginner
Contributions: 0
Commentaires: 3

Hi Bobbo,

Thanks for the quick feedback. 
Woud like the clarify the difference between usingt the ADK commands and the Add Driver feature inside Acronis BootMedia Builder. Is this not similar? 

Forum Hero
Contributions: 70
Commentaires: 8346

Hi TheArties,

I'm guessing you're using the media creator from universal restore and not the one in the Acronis application >>> tools?  I suppose the universal restore method should work - I have only used it to embed drivers for Universal Restore.  Give it a shot and let us know how it goes.  That might be an easier way to do this.  I've been advocating that this similar functionality be brought into the Acronis media builder as well. 

Beginner
Contributions: 0
Commentaires: 2

I am using Snap Deploy 5 for teh company I work for.  I am unable to pxe boot on a new HP Laptop that has an Intel I219-LM NIC .  I am updated already to 1660 version.  The agent does not recognize the nic.  Can you please provide a fix for this ASAP?

Forum Hero
Contributions: 70
Commentaires: 8346

Rey, there's a SD5 forum (FYI).  SD5 1666 beta bring driver support for the latest intel NICs and PCIE NVME drives.  It's been beta for close to 6 months now and I've been providing it to others and using itmyself without issue - it's bascially the same as 1660 with the newer drivers.  I will send it to you via PM.

Regular Poster
Contributions: 14
Commentaires: 111

I found this thread with a Google search.

 

I am using Acronis Backup Cloud and had the same issue with a new dedicated server from OVH.

 

Acronis is not detecting the Intel ethernet x710 and so I cannot use Acronis Web Console or usual boot media to restore data.

 

Going the WinPE route is very complex/tedious.

Rey, there's a SD5 forum (FYI).  SD5 1666 beta bring driver support for the latest intel NICs and PCIE NVME drives.  It's been beta for close to 6 months now and I've been providing it to others and using itmyself without issue - it's bascially the same as 1660 with the newer drivers.  I will send it to you via PM.

 

I agree. Still an issue from 2016 under 6 years later!?

 

I am using Acronis Backup Cloud

Forum Star
Contributions: 199
Commentaires: 4795

Please advice what Acronis product you are using; this forum is for discussion of ATI (Acronis True Image) 2016. I cannot find any reference to a product called Acronis Backup Cloud. If are using ATI 2021/ACPHO then you should be able to use the MVP tool to create recovery media with the necessary drivers. If you are using Linux recovery media, licensing restrictions prevent the inclusion of some proprietary drivers.

Ian