NIC Compatibility Issue

[Baligh Bedewi]

Dear All,

I don't know is that the right place to post.. But really I'm in deep serious problem, Shortely..
I have HP Proliant DL380 G7 With 2x dual Broadcom BCM5719 interface card, on the physical host i have windows server 2008 R2, and I installed FreeNAS 9.1 on Hyper-V. However, since my NIC is not compatible with freeBSD it says, network interface card not found... even though i looked at freeBSD blogs and they talking about compiling.. I did tried to add the line in the /usr/...conf.. However it says "directory not found"

I can't install FreeNAS on physical machine because i have shortage on my servers..

I even though that i might install FreeBSD 9.1, configuring the NIC and then compiling the FreeNAS but I couldn't find someone mentioning it.. So it seems that something is wrong..

Could you please help me..

I have another solution which is install Intel NIC but these is plan B

 

[dlavigne]

Plan B is probably your easiest solution.

 

[cyberjock]

FreeNAS does not work with Hyper-V. Hyper-V is not compatible with FreeBSD at all. Your only option as far as I'm aware is to install FreeNAS to bare metal. Well, that or use a different type 1 hypervisor that is compatible with FreeBSD.

I'm assuming you haven't read the threads that say not to virtualize FreeNAS?

http://forums.freenas.org/threads/p...duction-as-a-virtual-machine.12484/#post58364

http://forums.freenas.org/threads/a...ide-to-not-completely-losing-your-data.12714/

Quote from the second link:

Hyper-V is not suitable for the task, as it is incompatible with FreeBSD at this time.

 

[Baligh Bedewi]

FreeNAS does not work with Hyper-V. Hyper-V is not compatible with FreeBSD at all. Your only option as far as I'm aware is to install FreeNAS to bare metal. Well, that or use a different type 1 hypervisor that is compatible with FreeBSD.

I'm assuming you haven't read the threads that say not to virtualize FreeNAS?

http://forums.freenas.org/threads/p...duction-as-a-virtual-machine.12484/#post58364

http://forums.freenas.org/threads/a...ide-to-not-completely-losing-your-data.12714/

Quote from the second link:

Thank you cyberjock for your consideration..

Well I'll try to explain a little bit more, I've Windows Server 2012R2, and I was thinking of Failover Cluster on my File Servers..
First I went to the hardware solutions, however most of the hardware does not support the R2, even the new one like HP, Dell... Starting from 10k$ which is too expensive

So, someone at Microsoft Technet recommended the FreeNAS, and I have that server DL380 G7 with 3 SAS installed and 5 free slot.. Therefore I said why not using 1.2TBx5 SAS on RAID5 and using it as FreeNAS to accomplish that task.. But again, on that server we've customized application hosted on the physical machine which I cannot move and there is no available server on my RACK.

After all.. I tested the FreeNAS on Hyper-V however that NIC issue has come, but I did some searching on that and I found that I was suppose to use Legacy Network Adapter instead of the normal one.. And it did work and obtained from the DHCP and I had to down and up the Ethernet to able to ping/login..

What I faced so far is that when I create UFS drive it says "Error: Volume creation failed: newfs: wtfs: bytes at sector Input/output error"
but on the ZFS it working fine...

So other than that,.. Am I going to face any serious problem in the feature since I'll join it to the domain using DFS and failover cluster on SRV 2012R2?

 

[cyberjock]

So other than that,.. Am I going to face any serious problem in the feature since I'll join it to the domain using DFS and failover cluster on SRV 2012R2?

I'll answer my question with this. If you read those links and you followed them perfectly(aka did PCI passthrough over disk passthrough and all the other stuff without exception you might have a chance of the system working. But I think this is a very ill conceived effort because HyperV support is literally nonexistent for FreeBSD. Those stickies I linked are because we got sick and tired of people complaining about lost data. Many users would shutdown a server(properly) for some mundane reason. Then when they bootup the server their data is gone. No recovery. Just gone. There are zero recovery tools for ZFS. Recovery costs typically start at about $20,000 USD for just 200GB of data.

If I were in a business environment and you came to me with a recommendation of a FreeNAS server with Hyper-V I would probably fire you on the spot. In my opinion what you are doing is not and will not be for the good of the business and the decision to even consider Hyper-V in the face of warnings is a red flag you are not putting the business' interests first.

If you are doing this for home use, have a ball. But you'll get no sympathy if you come to the forum later complaining that your data just disappeared and you have no backup. Someone will link you to the 2 stickies we wrote earlier this year and tell you to do your homework properly next time. Those stickies are well known around here and linked to regularly. I've seen it happen every time and I don't even bother responding to people that won't listen to warnings but want help from a volunteer now that they've made those bad decisions. It's like drinking and driving, then asking the judge to forgive you and help you turn your life around after you hit someone while drunk. It will be too late to ask for forgiveness and too late to recover your data. And most of the other senior posters in this forum feel the same. You lost your data on purpose with bad decisions, you can recover it on your time and not ours.

 

[Baligh Bedewi]

Well, its not in the production, still on the test side... and yes i did not read all the link you provided above since i don't have any solution but the virtual and I just did, And you are right.. I'm totally agree with you.. So what am going to do is to test it in the long term, and once it'll be compatible with MS Hyper-v I'll shifted into the production.. Again thank you for your considerations cyberjock :)