After System Hang, Can no longer access shares/web gui or ping freenas server

[britishknight]

My freenas system hung up today. After rebooting I am unable to access the web gui or the shares.

Also pinging the Freenas server from a windows 10 machine returns request timed out.

From the box in Shell, I'm not able to ping the windows machine or my router. when I try it just says "ping: sendto: Host is down"

Lights are lit on the NIC and on the switch.

I have the freenas server set to a static ip of 192.168.1.195.

I have checked in router and nothing has taken that ip address.

Could it be something with the routes?

Running arp-a returns:

Code:

? (192.168.1.1) at (incomplete) on re0 expired [ethernet]
? (192.168.1.195) at {{the mac address of freenas}} on re0 permanent [ethernet]

Show : See My freeNAS system

System details list

 

[JohnDigital]

Im not saying its the issue, but Realtek NICs are suspect. You can get Intel NICs for dirt cheap on eBay.

Can you get to the terminal on the host? If theres a monitor on the server. You could do some looking around that way if you cant ssh in.

 

[britishknight]

Yes I have access to the terminal on the host. The Freenas CLI, and option 9 to goto shell.

 

[Alecmascot]

What is the boot device ?
Has the boot device failed ?

 

[JohnDigital]

Do some scouting around in there and see what's happening. Try to ping out, check in ifconfig, dmesg, lspci and see if there's any squawking in the terminal about connections or lack thereof. I see this is a realtek family 8111 we are talking about, I had one in a gigabyte board that sucked in Freenas, many moons ago. Intel server grade nics is all I'll use now. If you still can't get anywhere see about an additional and or different nic card.

 

[britishknight]

In dmesg I see a line saying re0 is at device 0.0...could that be a problem?

Here is ifconfig:

and netstat -rn

I order a intel NIC that will be here in a few days.

 

[britishknight]

And Im back up. Intel NIC installed.