Network Driver Issue?

[Jath]

Hey guys,

I'm trying to figure out the best way to fix an issue I'm having - it doesn't seem to be a network issue, but I can't figure out why the configuration won't work in general.

I tried to update FreeNAS to the next stable version today and I couldn't get any network connectivity at all. I looked up the issue from a previous FreeNAS post and they mentioned the driver for the LAN card isn't there. It's builtin with no issues before, and I'm not sure if it's necessarily a driver issue. I DID try to manually configure the network interface and it comes up saying "Try to connect with this IP: XXX.XXX.XXX.XXX" but it doesn't let me. At all. I can't get the network connectivity to work on this updated build.

I had to boot to an older FreeNAS environment, as shown below. It's the only one that I could get working it seems. Anyone have an idea on what step I should take? I can't reupgrade. I'm wondering if I save the config and reinstall? If I DO need to reinstall, how do I make sure I don't lose the data on my hard drives that are in a RAID through FreeNAS? Just readd the drives and it should be good?

Bottom boot image is the updated one. "Now" and top one is the one I can boot to.

Error message on root of server:

Shell:

 

[BigDave]

"I can't reupgrade"

I am not sure I understand this when you have the ability to roll back to a environment
that once again is stable. You should be able to "upgrade" manually.

 

[Sakuru]

Please post the full specs of your box. From the 3rd screenshot it looks like you are virtualized.

 

[Jath]

"I can't reupgrade"

I am not sure I understand this when you have the ability to roll back to a environment
that once again is stable. You should be able to "upgrade" manually.

When I booted to the old boot environment (as you see in the screenshot where it says "Now"), I've tried to go back to the upgrade menu and it continuously says that it cannot unmount the newer environment (the one that says "At Reboot" in the screenshot). Because of that, it is continuously not allowing for the upgrade. I will admit I am not familiar with FreeNAS and having to do this, so I don't want to mess anything up any further. Do you mean Activating this environment as a "permanent"?

Please post the full specs of your box. From the 3rd screenshot it looks like you are virtualized.

No, not virtualizing. This is the console from IPMI with Supermicro motherboards. I'm connected via the IPMI port and the console that allows me to monitor the computer that way, all remotely - like I've always done.

https://www.amazon.com/gp/product/B004WKRDA4/?tag=ozlp-20

 

[BigDave]

When I booted to the old boot environment (as you see in the screenshot where it says "Now"), I've tried to go back to the upgrade menu and it continuously says that it cannot unmount the newer environment (the one that says "At Reboot" in the screenshot). Because of that, it is continuously not allowing for the upgrade. I will admit I am not familiar with FreeNAS and having to do this, so I don't want to mess anything up any further. Do you mean Activating this environment as a "permanent"?

After activating the earlier one (20151128xxxx) did you reboot the server afterwards?

 

[BigDave]

Well first off let me tell you that at this stage your data can not be affected due to the fact
that you are dealing only with the boot drive which is totally removed from your pool.
If you can get your server to reboot into the Nov. 28th 2015 version, you could then delete
your "failed" update of Jan. 18th 2016 from that list. Reboot again and after coming back
online you should be able to update to the latest stable version.

 

[Jath]

Okay that's the piece that it was. I'm sorry for asking such a stupid question, I just wanted to make sure I didn't mess anything up. I didn't think I could delete that data, but I didn't want to take the chance, if you know what I mean.

I couldn't access the December 24th version either, which was weird. The one that I was on - The Nov 28th, I activated as you mentioned and then updated. Worked fine. Not really sure why the Dec 24 one had an issue updating, but it happens, I know that.

Glad it was something as easy as that, and again, sorry for a stupid question.

 

[BigDave]

In this case it was easier because you asked for help FIRST, that's what made it the smart thing to do.
I saw nothing stupid about your question and I'm glad you got things straight.
@Jath
So, a question if you dont mind? Were you able to update to the latest stable version without
having the connection issues?

 

[Jath]

Thank you. The help was greatly appreciate it.

Simple answer, yes. I was.

Long answer, basically, I was on the last stable version I was aware of that I updated to on December 24th, as shown by the build environment. I didn't have any noticeable issues at all with that build. I then today decided to update to the latest stable build, and after it restarted, I couldn't connect to the web GUI. Because of that, I loaded up the console through IPMI, and saw the error messages. Tried restarting, manually configuring the NIC, nothing. So when I restarted, I saw I could boot to another environment build, and tried the December 24th one. That one had the exact same issue as today's build even though it was working absolutely fine. So I tried the November 28th one, and that one worked. I was able to get to the web GUI and load everything. Went back to today's, nothing. Seems like upgrading from the 24th one to the latest caused some kind of issue for me. But I updated from the November 28th build to the latest stable and it works with only one issue..

The only issue I have now is my Plex plugin won't update, complaining about "An error occurred while unserializing from http://192.168.1.2/plugins/plexmediaserver/1/_s/treemenu: No JSON object could be decoded". No idea, but I'm not worried about it greatly. It works, and the server works, which is what I'm happy about.

Thanks again, sir.

Edit: Added a line.

 

[BigDave]

I would move over to the Plug Ins section and try and formulate a new question.
It seems the issue might be connected, so make sure and tell them about this.

 

[Jath]

I actually did create a new thread there since it was a different piece. I didn't mention this though. I'll make sure to mention it.

Thank you sir!