Ethernet Lost after upgrade from freenas 2.x to recent V3 builds

[nasnice]

Hello all,

Last december I did a clean upgrade from V2 to V3 of the freenas software which worked without problems! About 2 weeks ago I upgraded over the webinterface to the latest stable build and that is when the problem started.

After a reboot the connectivity is lost Freenas reports on the console that it cannot find a valid interface please configure manually; when I renew the DNS setting through the console and renew the em0 ethernet the connectivity is restored. I tried to save these changes through the web interface but to na avail. Everytime the server is rebooted or recovering from power outage (Unfortunately we experience frequent outages due to construction work nearby) the net connectivity is lost. The UPS signals the server in time so sofar no ZFS problems.

I have an Intel Asrock B85M Pro4 motherboard with intel 1 Gig nic and 16 Gig of Ram. I read that there are more persons experiencing difficulties with Intel Nics and V3 software.

Also somewhere in the startup messages Freenas asks me to report something but being new @ freenas and freebsd I have no idea what to report or where to find a log where errors may be logged. The message disappears too fast to even read properly. Would it be viable to have the script either wait for user input or create a report and make it accessible through the status button on the web interface?

In short if anyone can tell me wat file to report and where I can find it that would really help.
Using IPv4 with DHCP

Freenas is on a 8 GB USB disk.

Thanks in advance

 

[Jailer]

If you're on 9.3 boot from a previous working boot environment from the menu in the console during startup.

 

[nasnice]

Tried a lot of things to get this working properly and finally decided to start from a new build so I destroyed the properly working V3 build and just have the latest build from the 24th on the USB stick at the moment.

After the startup and manually adding the NIC the Nas is working fine it is just annoying that is is not automatic anymore..

 

[nasnice]

After leaving Freenas running for some time I noticed the following entries in the log:

"
Feb 9 11:40:41 Nas smbd[3512]: [2015/02/09 11:40:41.202970, 0] ../source3/lib/util_sock.c:1199(get_remote_hostname)
Feb 9 11:40:41 Nas smbd[3512]: matchname failed on 192.168.1.10
Feb 9 11:40:41 Nas smbd[3513]: STATUS=daemon 'smbd' finished starting up and ready to serve connectionsmatchname: host name/name mismatch: 192.168.1.85 != (NULL)
Feb 9 11:40:41 Nas smbd[3513]: [2015/02/09 11:40:41.210040, 0] ../source3/lib/util_sock.c:1199(get_remote_hostname)
Feb 9 11:40:41 Nas smbd[3513]: matchname failed on 192.168.1.85

This may be a result of tests I made with 2 new routers; the Freenas machine is now on 192.168.1.19 which works after I do a manual dhcp assignment. During startup Freenas also complains about the "Old" adresses.

Any input how I may correct this?

TIA
Fred

 

[Rilo Ravestein]

Maybe this can be helpful.

 

[nasnice]

Thanks Rilo, that killed those messages!

However my original problem still persists... At the end of the startup sequence the menu is presented with the message that no configured interfaces are found; try to do it manually...

Then I choose option 6 DNS refresh and push enter 3 times an whoppa Freenas is up and running...

Never had to do that on the 2.X builds...
Anyone?

 

[Rilo Ravestein]

I217V NIC. More people having issues with that, but i also read that should have been fixed. Sorry, can't help you with that one, maybe one of the experts can shed some light.

 

[cyberjock]

My expert opinion is to not attempt to use the I217V. I wasn't aware that it was going to be fixed, as this isn't a problem that the community can fix (Intel has to release an updated driver for FreeBSD 9).

 

[Ericloewe]

Fixed? Doesn't sound likely. Intel specifically states that only the i217LM has support for OSes other than Windows and Linux. The i217V is the consumer version without ECC with gratuitous incompatibilities to make companies pay more for the real deal.

 

[Rilo Ravestein]

Searched for this card on the forums, people reported it 'fixed'. Don't know the details.

Besides that, the OP reported that his card did work on previous version(s). So why not anymore on the newer version? What happened?

 

[cyberjock]

I don't know. I've bought and recommend hardware that would never include an i217V, so I can't say much as I have no personal experience with it.

It could be that it was "working" with the old driver, but was deliberately excluded because it had problems (edge cases?) that were a mess to deal with and Intel was never planning to support a desktop NIC on a server OS.

It's all guesses as to the history and the future, but last I heard it wasn't working and I had serious doubts back when this first came up and still do that it will ever truly be supported.