I've updated all Intel NIC drivers to the most recent ones from present FreeBSD stable/10. They should be included into the next nightly build. Please try it.
I've updated all Intel NIC drivers to the most recent ones from present FreeBSD stable/10. They should be included into the next nightly build. Please try it.
ix0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 description: connected to switch02 (te2/1) options=407bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,LRO,VLAN_HWTSO> ether 00:25:90:5d:23:ed inet 192.168.2.4 netmask 0xffffff00 broadcast 192.168.2.255 nd6 options=9<PERFORMNUD,IFDISABLED> media: Ethernet autoselect (10Gbase-T <full-duplex,rxpause,txpause>) status: active ix1: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=407bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,LRO,VLAN_HWTSO> ether 00:25:90:5d:23:ec nd6 options=9<PERFORMNUD,IFDISABLED> media: Ethernet autoselect status: no carrier
Feb 8 20:38:32 nas02 manage.py: [reporting.rrd:161] Failed to generate graph: ERROR: opening '/var/db/collectd/rrd/localhost/load/load.rrd': No such file or directory Feb 8 20:38:32 nas02 manage.py: [reporting.rrd:161] Failed to generate graph: ERROR: opening '/var/db/collectd/rrd/localhost/aggregation-cpu-sum/cpu-idle.rrd': No such file or directory Feb 8 20:38:43 nas02 manage.py: [reporting.rrd:161] Failed to generate graph: ERROR: opening '/var/db/collectd/rrd/localhost/aggregation-cpu-sum/cpu-idle.rrd': No such file or directory Feb 8 20:38:44 nas02 manage.py: [reporting.rrd:161] Failed to generate graph: ERROR: opening '/var/db/collectd/rrd/localhost/load/load.rrd': No such file or directory Feb 8 20:39:09 nas02 manage.py: [reporting.rrd:161] Failed to generate graph: ERROR: opening '/var/db/collectd/rrd/localhost/aggregation-cpu-sum/cpu-idle.rrd': No such file or directory Feb 8 20:39:09 nas02 manage.py: [reporting.rrd:161] Failed to generate graph: ERROR: opening '/var/db/collectd/rrd/localhost/load/load.rrd': No such file or directory Feb 8 20:39:15 nas02 manage.py: [reporting.rrd:161] Failed to generate graph: ERROR: opening '/var/db/collectd/rrd/localhost/load/load.rrd': No such file or directory Feb 9 08:36:57 nas02 manage.py: [reporting.rrd:161] Failed to generate graph: ERROR: opening '/var/db/collectd/rrd/localhost/load/load.rrd': No such file or directory Feb 9 08:36:57 nas02 manage.py: [reporting.rrd:161] Failed to generate graph: ERROR: opening '/var/db/collectd/rrd/localhost/aggregation-cpu-sum/cpu-idle.rrd': No such file or directory Feb 9 08:37:07 nas02 manage.py: [reporting.rrd:161] Failed to generate graph: ERROR: opening '/var/db/collectd/rrd/localhost/memory/memory-free.rrd': No such file or directory Feb 9 08:37:07 nas02 manage.py: [reporting.rrd:161] Failed to generate graph: ERROR: opening '/var/db/collectd/rrd/localhost/swap/swap-free.rrd': No such file or directory Feb 9 08:37:56 nas02 manage.py: [reporting.rrd:161] Failed to generate graph: ERROR: opening '/var/db/collectd/rrd/localhost/load/load.rrd': No such file or directory Feb 9 08:37:56 nas02 manage.py: [reporting.rrd:161] Failed to generate graph: ERROR: opening '/var/db/collectd/rrd/localhost/aggregation-cpu-sum/cpu-idle.rrd': No such file or directory Feb 9 08:38:00 nas02 manage.py: [reporting.rrd:161] Failed to generate graph: ERROR: opening '/var/db/collectd/rrd/localhost/aggregation-cpu-sum/cpu-idle.rrd': No such file or directory Feb 9 08:38:00 nas02 manage.py: [reporting.rrd:161] Failed to generate graph: ERROR: opening '/var/db/collectd/rrd/localhost/load/load.rrd': No such file or directory Feb 9 08:38:15 nas02 manage.py: [reporting.rrd:161] Failed to generate graph: ERROR: opening '/var/db/collectd/rrd/localhost/aggregation-cpu-sum/cpu-idle.rrd': No such file or directory Feb 9 08:39:11 nas02 manage.py: [reporting.rrd:161] Failed to generate graph: ERROR: opening '/var/db/collectd/rrd/localhost/aggregation-cpu-sum/cpu-idle.rrd': No such file or directory Feb 9 08:39:11 nas02 manage.py: [reporting.rrd:161] Failed to generate graph: ERROR: opening '/var/db/collectd/rrd/localhost/load/load.rrd': No such file or directory
Heh, one sentence has managed to totally confuse me... ;-)
There can be irreversible database schema changes within the stable 9.3 branch, and that wouldn't imply a bump to 9.4? I thought I was just getting a few stable series fixes, that, although untested, were relatively minor. What have I gone dun installed :-(
So, is this saying I might have problems if I just switch from the nightly train back to the stable train in the Web GUI and install the updates as prompted? Or will I probably be OK?
Does "revert to the latest stable branch boot environment" mean I should do a fresh install and restore my previous config? Disassembling my computer shelf to get my NAS box physically accessible, unpacking the monitor/keyboard for it, install, config, etc - I'd really rather not go through all that if I don't absolutely have to :-(
What's the best way to know when there's a stable release containing the new drivers? Will it be marked in the bug?
$ sysctl -a |egrep -E "cpu\.[0-9]+\.temp" dev.cpu.7.temperature: 64.0C dev.cpu.6.temperature: 64.0C dev.cpu.5.temperature: 64.0C dev.cpu.4.temperature: 64.0C dev.cpu.3.temperature: 64.0C dev.cpu.2.temperature: 63.0C dev.cpu.1.temperature: 63.0C dev.cpu.0.temperature: 63.0C
Love to know the same question as the guy above. Anyone still rocking this board for FreeNAS?