Sign in with
Sign up | Sign in
Your question

Recover Windows with iSCSI

Tags:
  • Windows
  • Windows Server 2008
  • iSCSI
  • Business Computing
  • Servers
Last response: in Business Computing
Share
August 27, 2013 3:09:58 AM

Hello,

I have been trying to test a recovery of Windows Server 2008 x64 using windows back up. I wanted to prove I would be able to restore the entire system if the server died, although Windows haven't made this easy. I followed the instructions on how to perform an entire system restore, which took me into the Window Server installation CD, 'repair this computer' and into the recover tool available there. The problem with this, is there is no way to connect iSCSI. So after some research into this, luckily this guide exists:

http://glennmatthys.wordpress.com/2012/01/07/add-iscsi-...

Following this instructions I added the iSCSI components into the Windows Installation CD, started the service and opened the iSCSI indicator. Problem I have now is I can't get the NIC card to pick up a IP address, which I can only assume is a driver issue. It is a Boardcom NetXtreme II 5716, I need to get the driver installed using command prompt on the Windows CD. I think the correct command is 'drvload' but this only works with .INF driver files, which I am unable to find for this NIC.

Anyone know where I can find the relevant driver files, or another way of getting the network card working during Windows Preinstallation Environment?

Kind regards,
Niall

More about : recover windows iscsi

August 27, 2013 3:30:47 AM

MC_K7 said:
A quick Google search gave me this:

http://www.broadcom.com/support/ethernet_nic/netxtremei...

I downloaded the .zip file for Win Svr 2008 x64 and there's another .cab file inside which contains .inf files.


I did see this .CAB file but the files within it didn't look very friendly:

bxdiag.inf1.7B96F30D_6291_4960_8264_0CA3B968E204

I was not sure what all the numbers after file extension were, I will extract them and give them a shot anyway and let you know.
m
0
l
Related resources
August 27, 2013 3:38:36 AM

NiallA said:
I did see this .CAB file but the files within it didn't look very friendly:

bxdiag.inf1.7B96F30D_6291_4960_8264_0CA3B968E204

I was not sure what all the numbers after file extension were, I will extract them and give them a shot anyway and let you know.


I am not sure either if you can simply rename the file by removing the numbers at the end. Or maybe you need another tool to extract .CAB file content properly. But there are definitely many .inf files inside there.
m
0
l
August 27, 2013 4:17:41 AM

MC_K7 said:
NiallA said:
I did see this .CAB file but the files within it didn't look very friendly:

bxdiag.inf1.7B96F30D_6291_4960_8264_0CA3B968E204

I was not sure what all the numbers after file extension were, I will extract them and give them a shot anyway and let you know.


I am not sure either if you can simply rename the file by removing the numbers at the end. Or maybe you need another tool to extract .CAB file content properly. But there are definitely many .inf files inside there.


No joy, I renamed all the files and injected all the .INF's using the 'drvload' command. Tried a ipconfig, no IP. Tried /renew and got the following error:

'An error occurred while releasing interface loopback Pseudo-Interface 1 : The system cannot find the file specified.
The operation failed as no adapter is in the state permissible for this operation'.

I will continue investigating this error but it may not be driver related after all.
m
0
l
!