Video Screencast Help
Give us your opinion and win with Symantec! Please help us by taking this survey to tell us about your experience with Symantec Connect, so that we can continue to grow and improve.  Take the survey.

Could not get network adaptor. - error

Created: 30 Nov 2008 • Updated: 21 May 2010 | 4 comments

When booting to the Recovery CD in a Hyper-V VM I am getting the error "Could not get a network adaptor".  I have a known working network adaptor attached to the VM.  I have tried it a few times with other adaptors attached to that VM but I can not get that VM with the restore CD booting to get on the network to read my backup images.

 

Has anyone else tried this?

 

Thanks,

 

JohnnyF

Comments 4 CommentsJump to latest comment

AJT's picture

Have you tired by adding a "Legacy Network Adapter"?

JohnnyF's picture

Can't see the forest for the trees!!!  To busy verifying I had all my other ducks in a row.

 

The restore process is working.  I will post my results and see if it works better than the P2V I tried.

 

Thanks,

 

JohnnyF

JohnnyF's picture

The Legacy Network Adapter allowed me to get the process started.  However, once it was finished and the VM was rebooted I had a black screen with a flasing curser and nothing else.

 

Have to do some more research and see what else I can try.

 

The fact that I can not get any of these processes to works makes me leary of relying on BESR to make a working backup of the system.  If it can't restore the backup to a VM or other hardware, it doesn't do me much good.

 

If anyone else out there has gotten it to restore a system to a VM I would really like to hear about it.

 

Thanks,

 

JohnnyF

David F's picture

If it is an option for you, open a support ticket and re-perform the restore opting not to reboot when it finishes. When the restore completes, while still in the recovery environment choose Utilities | Run support tool | Gather technical support information. Send in the restore logs that this generates to be reviewed.

Are you converting first and injecting into a Hyper-V guest OS or are you creating a blank guest OS and booting off the disk and mapping to a share to perform the restore; sounds like the latter. What is the emulation of your mass-storage controller that you are choosing?