No GUI with Freenas latest update

[avalon60]

I have just updated FreeNAS 9.10-1-U2 to the latest update, U4, and part way through downloading or installing the update, FreeNAS rebooted. On completion of the reboot, there was no assigned network interfaces , as I watched the boot up on the IPMI KVM console screen.

I tried to assign a network interface and IPv4 address, but one time after selecting item 1 Freenas went into a loop, and kept asking for select an interface. Then a 2nd time after I assigned the IPv4 address and netmask for the interface, FreeNAS said it was invalid, so I repeated the same IPv4 and netmask: 192.168.0.22, and 255.255.255.0 /24, but FreeNAS just said it was invalid.

I am not sure if the update completed the download and or installation, as when the download started, it just seemed too quick to reboot, unless there was some kind of problem during the process.

In the end I reverted back to a previous boot environment

 

[dlavigne]

Paste the output of ifconfig.

 

[avalon60]

I'm not sure this is the first line or not , as that is where started the copy, and the scrollbar was at the top of the window:

ifconfig from FreeNAS-9.10.1-U2 (f045a8b)

ether 0c:c4:7a:0c:1e:ef
inet 192.168.0.22 netmask 0xffffff00 broadcast 192.168.0.255
nd6 options=9<PERFORMNUD,IFDISABLED>
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
em1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=4219b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_MAGIC,VLAN_HWTSO>
ether 0c:c4:7a:0c:1e:ee
nd6 options=9<PERFORMNUD,IFDISABLED>
media: Ethernet autoselect
status: no carrier
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3
inet 127.0.0.1 netmask 0xff000000
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
bridge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
ether 02:77:f9:17:40:00
nd6 options=1<PERFORMNUD>
id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
member: epair2a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
ifmaxaddr 0 port 7 priority 128 path cost 2000
member: epair1a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
ifmaxaddr 0 port 6 priority 128 path cost 2000
member: epair0a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
ifmaxaddr 0 port 5 priority 128 path cost 2000
member: em0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
ifmaxaddr 0 port 1 priority 128 path cost 20000
epair0a: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=8<VLAN_MTU>
ether 02:ff:20:00:05:0a
nd6 options=1<PERFORMNUD>
media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
status: active
epair1a: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=8<VLAN_MTU>
ether 02:ff:20:00:06:0a
nd6 options=1<PERFORMNUD>
media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
status: active
epair2a: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=8<VLAN_MTU>
ether 02:ff:20:00:07:0a
nd6 options=1<PERFORMNUD>
media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
status: active

 

[dlavigne]

Next time please use code tags as it makes the output much easier to read.

Check your cabling as there is "no carrier" on the interface.

 

[avalon60]

I have just googled code tags for FreeNAS, and I think I know what you mean, but I copied and pasted directly from a shell window, and that is how it came out as I used the largest wind there was.
Now I have used a smaller window and it comes out a little different, but without a scroll bar:
It looks ok when I am in the edit window, but when it is posted then it isn't.

ether 0c:c4:7a:0c:1e:ee
nd6 options=9<PERFORMNUD,IFDISABLED>
media: Ethernet autoselect
status: no carrier

I see where it says 'no carrier' but yet I have access to FreeNAS GUI , and the home network is working fine.
Also, I have the IPv4 address of 192.168.0.22 set as a reserved IP address in my router.

I see in my FreeNAS setup that there was no network interface showing, so I just added the existing em0 interface, and hope that is ok.

 

[pirateghost]

I have just googled code tags for FreeNAS,

Not code tags for FreeNAS, code tags IN THE FORUMS.

I think I know what you mean, but I copied and pasted directly from a shell window, and that is how it came out as I used the largest wind there was.
Now I have used a smaller window and it comes out a little different, but without a scroll bar:
It looks ok when I am in the edit window, but when it is posted then it isn't.

Use a proper SSH client to connect. The webGUI shell is piss

 

[avalon60]

After setting the network interface as above , on reboot it now does not show in FreeNAS GUI

 

[avalon60]

I managed now to configure a network interface in the IPMI bootup window or screen, and this time it worked ok. Then I rebooted FreeNAS and it booted from the latest U4 update boot environment. This time there was the IPv4 address 192.168.0.22 showing, but in FreeNAS Interfaces window, there is no entry.

 

[avalon60]

I gave the em0 network interface a proper name and now it shows up in the interface listing