Announcing FreeNAS 9.2.1.3-RELEASE

[pschatz100]

I tried with Firefox, Google Chrome, and Internet Explorer! Same problem! Solved with the advice of gpsguy!

As of April 5, I downloaded the 64bit version with Firefox v28 (latest version.) No issues...

 

[Charles Elliott]

I updated FreeNAS using FreeNAS-9.2.1.3-RELEASE-x64.iso and a CDROM. I am still seeing three issues:
1. The update wrote an error to data disk 1 of 3, as evidenced by a cksum error from "zpool status." The NAS fixes itself in about 24 hours, but before then, it says it is running in degraded mode.

2. After the install, the disk transfer rate on long files went from a common 340 Mbs (under version 9.1.1) to about 10 Mbs. Several people on the forums said the cause was likely to be the SSD cache device, which previously had always worked well. Nevertheless I removed the SSD. There was no change in performance subsequently. However, I just checked the transfer rate from the NAS to this computer, and I am seeing 80-85 MBs (640- 680 Mbs) depending on the hard disk. Please don't ask, "How did it heal itself?" This morning, the following message appeared on the NAS console:

Code:

Apr  4 08:29:41 freenas kernel: .
Apr  5 06:50:40 freenas kernel: pid 15014 (smbd), uid 0: exited on signal 11 (core dumped)
Apr  5 08:56:40 freenas notifier: Stopping ntpd.

Could the restart of smbd be the cause of the faster transfer rates? It has been years since I worked with an O/S similar to FreeBSD, but if someone posts the commands to make smbd restart itself, I will be happy to reboot FreeNAS and test the transfer rate before and after causing smbd to restart.

3. The following messages are output whenever FreeNAS starts up:

Code:

Apr  4 08:29:37 freenas mDNSResponder:  11: Listening for incoming Unix Domain Socket client requests
Apr  4 08:29:37 freenas mDNSResponder: mDNS_AddDNSServer: Lock not held! mDNS_busy (0) mDNS_reentrancy (0)
Apr  4 08:29:37 freenas last message repeated 2 times
Apr  4 08:29:39 freenas mDNSResponder: mDNS_Register_internal: ERROR!! Tried to register AuthRecord 0000000800C2FD60 freenas.local. (Addr) that's already in the list
Apr  4 08:29:39 freenas mDNSResponder: mDNS_Register_internal: ERROR!! Tried to register AuthRecord 0000000800C30180 1.1.168.192.in-addr.arpa. (PTR) that's already in the list
Apr  4 08:29:39 freenas mDNSResponder: mDNS_Register_internal: ERROR!! Tried to register AuthRecord 0000000800C31D60 freenas.local. (Addr) that's already in the list
Apr  4 08:29:39 freenas mDNSResponder: mDNS_Register_internal: ERROR!! Tried to register AuthRecord 0000000800C32180 1.0.168.192.in-addr.arpa. (PTR) that's already in the list
Apr  4 08:29:39 freenas mDNSResponder: mDNS_Register_internal: ERROR!! Tried to register AuthRecord 0000000800C33D60 freenas.local. (AAAA) that's already in the list
Apr  4 08:29:39 freenas mDNSResponder: mDNS_Register_internal: ERROR!! Tried to register AuthRecord 0000000800C34180 A.A.C.F.4.A.E.F.F.F.0.9.5.2.2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.8.E.F.ip6.arpa. (PTR) that's already in the list
Apr  4 08:29:39 freenas mDNSResponder: mDNS_Register_internal: ERROR!! Tried to register AuthRecord 0000000800C35D60 freenas.local. (AAAA) that's already in the list
Apr  4 08:29:39 freenas mDNSResponder: mDNS_Register_internal: ERROR!! Tried to register AuthRecord 0000000800C36180 B.A.C.F.4.A.E.F.F.F.0.9.5.2.2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.8.E.F.ip6.arpa. (PTR) that's already in the list

 

[warri]

I updated FreeNAS using FreeNAS-9.2.1.3-RELEASE-x64.iso and a CDROM. I am still seeing three issues:
1. The update wrote an error to data disk 1 of 3, as evidenced by a cksum error from "zpool status." The NAS fixes itself in about 24 hours, but before then, it says it is running in degraded mode.

The update itself doesn't even write onto the pool - except for the temporary update file which lands in the .freenas folder. Most likely the update didn't write an error, but one your disk caused it instead. You should verify that your RAM is ok (if you are running non-ECC), check SMART attributes of the disk and scrub the volume.

If a disk is dying this might also explain the unsteady transfer rates. Otherwise I unfortunately cannot help you with point 2.

Point 3 is a known bug with 9.2.1.x (see Bug #4154) which seems to be harmless.

 

[Charles Elliott]

>Most likely the update didn't write an error
I would agree except that it happened with both 9.2.1.2 and 9.2.1.3.

 

[jkh]

>Most likely the update didn't write an error
I would agree except that it happened with both 9.2.1.2 and 9.2.1.3.

Doesn't mean anything. As folks have said, the updates write to your USB stick. You could completely export your pool before the update and still apply it (in fact, a number of scenarios involve installing FreeNAS to a new machine with an exported pool on some collection of external disks, then importing it after the install is completed). I think the problem with your pool was probably latent and this is simply case of confirmation bias in action.

 

[cyberjock]

You believe that fallacy about confirmation bias jkh? Maybe this will restore your faith!

http://www.forbes.com/sites/erikaan...he-lack-of-pirates-is-causing-global-warming/

 

[aufalien]

Wow, now that was hilarious!

 

[jkh]

You believe that fallacy about confirmation bias jkh? Maybe this will restore your faith!

http://www.forbes.com/sites/erikaan...he-lack-of-pirates-is-causing-global-warming/

Gah! That was totally stolen from the church of the flying spaghetti monster!

http://www.venganza.org/about/open-letter/

 

[gpsguy]

Looks like it's okay now. I downloaded the 9.2.1.3 x64 ISO from http://download.freenas.org just a few minutes ago.