Cannot access UI interface

[colinshen]

After a fresh install with 11.2 U6(I mean I have installed other version which means the hardware are good with freenas ). The ip address I had is 0.0.0.0. And I could not find the ip address in the router devices list. I think it not connected with my router. So I tried to set a ip address and still cannot access.

 

[colinshen]

another error when install

 

[Newfoundland.Republic]

Without more info, I'd say that you do not have a network connection.

• Do you have link lights on the server NIC and the switch/router port that FreeNAS is connected?
  • [Edit - add this] Have you tried replacing the network cable?
• Is the switch/router configured to hand out DHCP addresses? If so, are there any available addresses?
• You noted that you are manually assigning an IP - have you verified that the IP address you selected is not already in use?

 

[colinshen]

Without more info, I'd say that you do not have a network connection.

• Do you have link lights on the server NIC and the switch/router port that FreeNAS is connected?
  • [Edit - add this] Have you tried replacing the network cable?
• Is the switch/router configured to hand out DHCP addresses? If so, are there any available addresses?
• You noted that you are manually assigning an IP - have you verified that the IP address you selected is not already in use?

1. The lights on NIC is on, but not when reset to default. I tried to reset to default several times.
2. The router is configured to hand out DHCP.
3. I checked the list also. After setting the ip driess. I ping the router. You can see it in the second picture

 

[Newfoundland.Republic]

Hmmm... First, I'd try reducing the DHCP range a little. Maybe only from 192.168.3.2 to 192.168.3.200; that will give you 54 "free" addresses. Then manually set the FreeNAS IP to something like 192.168.3.201.

Check to make sure the FreeNAS gateway is set to that of your router (192.168.3.1).

To make sure everything is "clean", I would reboot the router, switches and FreeNAS. (Likely not necessary but I have seen ARP caches cause issues in the past...)

 

[colinshen]

Hmmm... First, I'd try reducing the DHCP range a little. Maybe only from 192.168.3.2 to 192.168.3.200; that will give you 54 "free" addresses. Then manually set the FreeNAS IP to something like 192.168.3.201.

Check to make sure the FreeNAS gateway is set to that of your router (192.168.3.1).

To make sure everything is "clean", I would reboot the router, switches and FreeNAS. (Likely not necessary but I have seen ARP caches cause issues in the past...)

I tried what you said...it doesn't work.
My NIC is Killer E2205 since it is integrated. But I had succeed installed FreeNas. So, I think it should no problem.

 

[melloa]

Let's start from the beginning:

- Hardware info please
- What does the server report as network card? Is it detected?
- Check your logs for error messages related with your network card, dhcp, etc. You can get that from the shell typing dmesg. You can filter the output using a pipe and the word to filter by (i.e. dmesg | intel).
- You can save the output for anything using a >, so if you want to browse the message during boot and look for the problem, use dmesg > logs.txt. That will create a file called logs.txt on the same directory you are. Use nano to read it.
Simple steps like those will help you to identify problems.
- When finding an error, google it. 99.999% of the time, someone else had the same problem before.

For instance my NIC is a Chelsio, so:

Code:

oot@nas:~ # dmesg | grep Chelsio
cxgbc0: <Chelsio T320, 2 ports> mem 0xfb781000-0xfb781fff,0xfb780000-0xfb780fff irq 32 at device 0.0 on pci2

Looking for the string cxgb to see what happened with it during boot:

Code:

root@nas:~ # dmesg | grep cxgb
cxgbc0: <Chelsio T320, 2 ports> mem 0xfb781000-0xfb781fff,0xfb780000-0xfb780fff irq 32 at device 0.0 on pci2
cxgbc0: using MSI-X interrupts (9 vectors)
cxgb0: <Port 0 10GBASE-R> on cxgbc0
cxgb0: Using defaults for TSO: 65518/35/2048
cxgb0: Ethernet address: 00:07:43:06:b5:0d
cxgb1: <Port 1 10GBASE-R> on cxgbc0
cxgb1: Using defaults for TSO: 65518/35/2048
cxgb1: Ethernet address: 00:07:43:06:b5:0e
cxgbc0: Firmware Version 7.12.0
cxgb0: link state changed to DOWN
cxgb0: link state changed to UP
cxgb1: link state changed to DOWN

If you can't find your way on the shell, boot the server and look and the messages as they appear. During boot you will see the server bringing the interfaces up and down, looking for the dhcp server, getting the IP, etc.

Good luck!

 

[melloa]

Killer E2205

Check this: https://www.ixsystems.com/community/threads/killer-e2205-nic-help.21900/

 

[colinshen]

Let's start from the beginning:

- Hardware info please
- What does the server report as network card? Is it detected?
- Check your logs for error messages related with your network card, dhcp, etc. You can get that from the shell typing dmesg. You can filter the output using a pipe and the word to filter by (i.e. dmesg | intel).
- You can save the output for anything using a >, so if you want to browse the message during boot and look for the problem, use dmesg > logs.txt. That will create a file called logs.txt on the same directory you are. Use nano to read it.
Simple steps like those will help you to identify problems.
- When finding an error, google it. 99.999% of the time, someone else had the same problem before.

For instance my NIC is a Chelsio, so:

Code:

oot@nas:~ # dmesg | grep Chelsio
cxgbc0: <Chelsio T320, 2 ports> mem 0xfb781000-0xfb781fff,0xfb780000-0xfb780fff irq 32 at device 0.0 on pci2

Looking for the string cxgb to see what happened with it during boot:

Code:

root@nas:~ # dmesg | grep cxgb
cxgbc0: <Chelsio T320, 2 ports> mem 0xfb781000-0xfb781fff,0xfb780000-0xfb780fff irq 32 at device 0.0 on pci2
cxgbc0: using MSI-X interrupts (9 vectors)
cxgb0: <Port 0 10GBASE-R> on cxgbc0
cxgb0: Using defaults for TSO: 65518/35/2048
cxgb0: Ethernet address: 00:07:43:06:b5:0d
cxgb1: <Port 1 10GBASE-R> on cxgbc0
cxgb1: Using defaults for TSO: 65518/35/2048
cxgb1: Ethernet address: 00:07:43:06:b5:0e
cxgbc0: Firmware Version 7.12.0
cxgb0: link state changed to DOWN
cxgb0: link state changed to UP
cxgb1: link state changed to DOWN

If you can't find your way on the shell, boot the server and look and the messages as they appear. During boot you will see the server bringing the interfaces up and down, looking for the dhcp server, getting the IP, etc.

Good luck![/Q

Let's start from the beginning:

- Hardware info please
- What does the server report as network card? Is it detected?
- Check your logs for error messages related with your network card, dhcp, etc. You can get that from the shell typing dmesg. You can filter the output using a pipe and the word to filter by (i.e. dmesg | intel).
- You can save the output for anything using a >, so if you want to browse the message during boot and look for the problem, use dmesg > logs.txt. That will create a file called logs.txt on the same directory you are. Use nano to read it.
Simple steps like those will help you to identify problems.
- When finding an error, google it. 99.999% of the time, someone else had the same problem before.

For instance my NIC is a Chelsio, so:

Code:

oot@nas:~ # dmesg | grep Chelsio
cxgbc0: <Chelsio T320, 2 ports> mem 0xfb781000-0xfb781fff,0xfb780000-0xfb780fff irq 32 at device 0.0 on pci2

Looking for the string cxgb to see what happened with it during boot:

Code:

root@nas:~ # dmesg | grep cxgb
cxgbc0: <Chelsio T320, 2 ports> mem 0xfb781000-0xfb781fff,0xfb780000-0xfb780fff irq 32 at device 0.0 on pci2
cxgbc0: using MSI-X interrupts (9 vectors)
cxgb0: <Port 0 10GBASE-R> on cxgbc0
cxgb0: Using defaults for TSO: 65518/35/2048
cxgb0: Ethernet address: 00:07:43:06:b5:0d
cxgb1: <Port 1 10GBASE-R> on cxgbc0
cxgb1: Using defaults for TSO: 65518/35/2048
cxgb1: Ethernet address: 00:07:43:06:b5:0e
cxgbc0: Firmware Version 7.12.0
cxgb0: link state changed to DOWN
cxgb0: link state changed to UP
cxgb1: link state changed to DOWN

If you can't find your way on the shell, boot the server and look and the messages as they appear. During boot you will see the server bringing the interfaces up and down, looking for the dhcp server, getting the IP, etc.

Good luck!

I posted an image that showed unable to pass dns Server.

 

[melloa]

Did you check compatibility, as per discussion here: https://www.ixsystems.com/community/threads/killer-e2205-nic-help.21900/

 

[colinshen]

Did you check compatibility, as per discussion here: https://www.ixsystems.com/community/threads/killer-e2205-nic-help.21900/

yes. I did. But I had succeed install freenas last week.

 

[Newfoundland.Republic]

I hate writing this but effectively FreeNAS, while free, is an enterprise platform. The compatibility list is what is known to work. You may be able to get other configurations to work but they may not be stable and/or you may have issues. While I am really a FreeNAS novice, I have over 25 years in enterprise IT and my experience is that hardware compatibility lists are there for a reason. You may get it to "work" but it may return and bite you in the ass.

I assume that you will be placing files on FreeNAS that you would rather keep and have available to you in a timely manner. Keep that in mind....

 

[danb35]

But I had succeed install freenas last week.

You've mentioned this a couple of times--why do you think it matters? FreeNAS does not do extensive checks for hardware compatibility on installation--I don't believe it checks anything other than the amount of RAM and (maybe) 64-bit support. Your onboard NIC is a POS. It's "supported" in that there's a driver for it, but it's an extremely poor choice--and your problem is most definitely in your network connection (the ping times you posted, as well as it earlier failing to obtain an IP address, are proof). It's possible that something simple like a new cable (or making sure it's plugged in securely) will help, but in any event you need a new NIC.

 

[melloa]

yes. I did. But I had succeed install freenas last week.

Seems that the consensus point to a new NIC. If going 1Gb, I'd say Intel won't give you any issues.

 

[colinshen]

I bought a new NIC. fixed.

 

[melloa]

I bought a new NIC. fixed.

Excellent. If possible, please mark this post as solved.