FreeNAS 9.10-RELEASE now available!

[hinghi]

Does this version has new driver for Chelsio card?
Thanks,

 

[Mlovelace]

Does this version has new driver for Chelsio card?
Thanks,

The 9.10 release updated the firmware on my T520-CR

 

[hinghi]

@Mlovelace it's a good news. Thanks.

 

[garfunkel]

I tried to upgrade my HP N40L from 9.3 to 9.10 but I hit a snag :(

https://drive.google.com/file/d/1jPVWuDrm9Jd_D5ZnIYuEtN6dCJO14Lh9mw/view?usp=sharing

Any ideas?

I updated an identical machine (except for a different USB stick - a SanDisk), and it worked with no issues.

So this looks to me like some sort of regression, 9.10 doesn't like some USB sticks.

 

[ThreeDee]

Bug #14193: 9.10 Boot Partitions Cannot Be Deleted from GUI

Fixed (for me anyways) with latest update today .. niiice ..

 

[garfunkel]

OK, it seems like indeed my USB may be toast. I tried to dd the entire device through FreeNAS 9.3 over to a HDD so I could test if 9.10 worked via a SATA HDD. The copy took many hours for a 32GB stick and I cancelled it. Strange though, it copied completely in minutes on Linux...

9.10 now boots for me via a spinny disk.

Now I have more problems though. Sabnzbd reports "no route to host" when testing any servers added. Anyone else have this issue? I bombed the jails dataset completely and installed Sabnzbd from scratch. I'm able to jexec into the jail and ping the outside world fine, but for some reason Sabnzbd itself can't. It doesn't matter what I put in the host/server field, same result.

 

[Darkk]

Anyone had issues with Link Aggregation (lagg) setups? Well, for some reason mine got hosed early this morning. It was working fine after the update and a couple of reboots. Had to get into the console on the server itself to delete the lagg and use standard networking for now. Going to re-create it and see if it'll work ok. Guessing some cron job ran to update the ARP tables?

Also that https certificate issue resurfaced after the reboot since it reverted back to the bad SSL certs that was generated by the WebGUI. So going to manually fix it later.

 

[jgreco]

cron jobs would have no business reconfiguring networking....

 

[Darkk]

cron jobs would have no business reconfiguring networking....

Ok, I'll have to go through the logs and see what happened at around 5am this morning that borked it.

EDIT:

Got these...will look through the other logs. Weird how it happened at exactly 5am this morning.

Mar 26 05:00:43 freenas mDNSResponder: mDNSPlatformSendUDP got error 51 (Network is unreachable) sending packet to 224.0.0.251 on interface 0.0.0.0/lagg0/4
Mar 26 05:00:44 freenas kernel: <118>Mar 26 05:00:43 freenas mDNSResponder: mDNSPlatformSendUDP got error 51 (Network is unreachable) sending packet to 224.0.0.251 on interface 0.0.0.0/lagg0/4
Mar 26 05:00:44 freenas mDNSResponder: mDNSPlatformSendUDP got error 51 (Network is unreachable) sending packet to 224.0.0.251 on interface 0.0.0.0/lagg0/4
Mar 26 05:00:44 freenas kernel: <118>Mar 26 05:00:44 freenas mDNSResponder: mDNSPlatformSendUDP got error 51 (Network is unreachable) sending packet to 224.0.0.251 on interface 0.0.0.0/lagg0/4
Mar 26 05:00:44 freenas mDNSResponder: mDNSPlatformSendUDP got error 51 (Network is unreachable) sending packet to 224.0.0.251 on interface 0.0.0.0/lagg0/4
Mar 26 05:00:44 freenas kernel: <118>Mar 26 05:00:44 freenas mDNSResponder: mDNSPlatformSendUDP got error 51 (Network is unreachable) sending packet to 224.0.0.251 on interface 0.0.0.0/lagg0/4
Mar 26 05:00:44 freenas mDNSResponder: mDNSPlatformSendUDP got error 51 (Network is unreachable) sending packet to 224.0.0.251 on interface 0.0.0.0/lagg0/4
Mar 26 05:00:44 freenas kernel: <118>Mar 26 05:00:44 freenas mDNSResponder: mDNSPlatformSendUDP got error 51 (Network is unreachable) sending packet to 224.0.0.251 on interface 0.0.0.0/lagg0/4
Mar 26 05:00:45 freenas mDNSResponder: mDNSPlatformSendUDP got error 51 (Network is unreachable) sending packet to 224.0.0.251 on interface 0.0.0.0/lagg0/4
Mar 26 05:00:45 freenas kernel: <118>Mar 26 05:00:45 freenas mDNSResponder: mDNSPlatformSendUDP got error 51 (Network is unreachable) sending packet to 224.0.0.251 on interface 0.0.0.0/lagg0/4
Mar 26 05:00:47 freenas mDNSResponder: mDNSPlatformSendUDP got error 51 (Network is unreachable) sending packet to 224.0.0.251 on interface 0.0.0.0/lagg0/4
Mar 26 05:00:47 freenas kernel: <118>Mar 26 05:00:47 freenas mDNSResponder: mDNSPlatformSendUDP got error 51 (Network is unreachable) sending packet to 224.0.0.251 on interface 0.0.0.0/lagg0/4
Mar 26 05:00:51 freenas mDNSResponder: mDNSPlatformSendUDP got error 51 (Network is unreachable) sending packet to 224.0.0.251 on interface 0.0.0.0/lagg0/4
Mar 26 05:00:51 freenas kernel: <118>Mar 26 05:00:51 freenas mDNSResponder: mDNSPlatformSendUDP got error 51 (Network is unreachable) sending packet to 224.0.0.251 on interface 0.0.0.0/lagg0/4

Mar 26 05:01:20 freenas nmbd[2459]: [2016/03/26 05:01:20.462297, 0] ../source3/libsmb/nmblib.c:873(send_udp)
Mar 26 05:01:20 freenas nmbd[2459]: Packet send failed to 10.2.10.255(138) ERRNO=No route to host
Mar 26 05:01:20 freenas nmbd[2459]: [2016/03/26 05:01:20.462678, 0] ../source3/lib/util_sock.c:396(open_socket_in)
Mar 26 05:01:20 freenas nmbd[2459]: bind failed on port 137 socket_addr = 0.255.255.255.
Mar 26 05:01:20 freenas nmbd[2459]: Error = Can't assign requested address
Mar 26 05:01:20 freenas nmbd[2459]: [2016/03/26 05:01:20.462783, 0] ../source3/nmbd/nmbd_subnetdb.c:127(make_subnet)
Mar 26 05:01:20 freenas nmbd[2459]: nmbd_subnetdb:make_subnet()
Mar 26 05:01:20 freenas nmbd[2459]: Failed to open nmb bcast socket on interface 0.255.255.255 for port 137. Error was Can't assign requested address
Mar 26 05:01:20 freenas nmbd[2459]: [2016/03/26 05:01:20.462874, 0] ../source3/nmbd/nmbd.c:362(reload_interfaces)
Mar 26 05:01:20 freenas nmbd[2459]: reload_interfaces: No subnets to listen to. Waiting..
Mar 26 05:01:20 freenas nmbd[2459]: [2016/03/26 05:01:20.463039, 0] ../source3/lib/util_sock.c:396(open_socket_in)
Mar 26 05:01:20 freenas nmbd[2459]: bind failed on port 137 socket_addr = 0.255.255.255.
Mar 26 05:01:20 freenas nmbd[2459]: Error = Can't assign requested address
Mar 26 05:01:20 freenas nmbd[2459]: [2016/03/26 05:01:20.463135, 0] ../source3/nmbd/nmbd_subnetdb.c:127(make_subnet)
Mar 26 05:01:20 freenas nmbd[2459]: nmbd_subnetdb:make_subnet()
Mar 26 05:01:20 freenas nmbd[2459]: Failed to open nmb bcast socket on interface 0.255.255.255 for port 137. Error was Can't assign requested address
Mar 26 05:01:20 freenas nmbd[2459]: [2016/03/26 05:01:20.463300, 0] ../source3/lib/util_sock.c:396(open_socket_in)
Mar 26 05:01:20 freenas nmbd[2459]: bind failed on port 137 socket_addr = 0.255.255.255.
Mar 26 05:01:20 freenas nmbd[2459]: Error = Can't assign requested address


The errors above kept looping forever. Lucky I woke up early this morning and saw it.

 

[ThreeDee]

Code:

Mar 26 00:00:00 freeNADZ syslog-ng[1437]: WARNING: Configuration file format is too old, syslog-ng is running in compatibility mode Please update it to use the syslog-ng 3.6 format at your time of convinience, compatibility mode can operate less efficiently in some cases. To upgrade the configuration, please review the warnings about incompatible changes printed by syslog-ng, and once completed change the @version header at the top of the configuration file.;

How do I update the Configuration file format?

 

[balamit]

Even with the latest nightly, afp still screwed up, read locked to 1gbe, takes over 2m to load plugins page, none of the plugins will start no matter what I do.

 

[Lorem-Ipsum]

Just after a bit of clarification about updating to the new FreeBSD 10.3-RC2 based template for my jails.

I have stopped all jails/plugins and have nuked my Jails dataset (after backing it up)

Currently my plugins Repository URL is:
http://download.freenas.org/plugins/9/x64/pbi-meta/pbi-repo.rpo

and my jails URL is:
http://download.freenas.org/latest/RELEASE/x64/jails

Do I need to make any changes to these or do I need a reboot?

Many thanks

 

[zambanini]

to many different problems/topics in one thread do not make sense...