FreeNAS-9.10.1-U3

[gearhead]

Is there going to be a FreeNAS-9.10.1-U3 iso release?

 

[Ericloewe]

Is there going to be a FreeNAS-9.10.1-U3 iso release?

All updates have been historically available as standalone releases, but -U3 isn't out yet (as of this morning's automatic update check).

 

[gpsguy]

I gather that it's coming soon. The docs were updated on Nov 2nd, to reflect FreeNAS-9.10.1-U3 and when I checked the bug site this morning, there weren't any open issues for the U3 version.

 

[Ericloewe]

I gather that it's coming soon. The docs were updated on Nov 2nd, to reflect FreeNAS-9.10.1-U3 and when I checked the bug site this morning, there weren't any open issues for the U3 version.

Right, they've been closed for a few days now. If -U2 is any indication, I'd expect it around the middle of this week.

 

[Jailer]

My IPMI went all nutso cookoo with the U2 update so I'll be patiently waiting to see how U3 works for everyone.

 

[Ericloewe]

My IPMI went all nutso cookoo with the U2 update so I'll be patiently waiting to see how U3 works for everyone.

How so? On your X10SL7-F?

 

[Jailer]

Yes. It started with email notifications and the IPMI interface was unresponsive. I reset the BMC and the motherboard showed a BMC heartbeat but it would not respond. Once I rolled back to 9.10.1 it started working again so that's where I stayed and am currently at. If U-3 shows to be stable I try updating again but if it goes sideways I'll probably just stay on 9.10.1.

FreeNAS 10 is dropping jail support so I'll likely just stay where I'm at until FreeBSD 10.3 reaches end of life and then make a decision on what to do at that point.

 

[gpsguy]

Apparently FreeNAS-9.10.1-U3 was released today.

 

[Jailer]

Apparently FreeNAS-9.10.1-U3 was released today.

So whats the verdict?

 

[hervon]

So far so good. No bug on my side. Shares (smb, afp) work. Plugins/jails (transmission/urbackup/miniDLNA) are ok too.

 

[rafadavidc]

Poking this thread since things didn't go so well for me in U1 or U2...

 

[diskdiddler]

Yeah after that last update, I'm somewhat hesitant.
I'll take a crack and see how I go.

EDIT: Well it seems ok, she booted back up, jails seem ok

 

[Jurgen Segaert]

Hmmm.. I'm on the FreeNAS-9.10-STABLE train, and I decided to also roll the dice and update today.
I thought was going to get FreeNAS-9.10.1-U3. All went fine, and the system works like a charm, however, in System>Information the build shows as FreeNAS-9.10.1-U4 (ec9a7d3)

Anybody else noticed this?

 

[hervon]

Hmmm.. I'm on the FreeNAS-9.10-STABLE train, and I decided to also roll the dice and update today.
I thought was going to get FreeNAS-9.10.1-U3. All went fine, and the system works like a charm, however, in System>Information the build shows as FreeNAS-9.10.1-U4 (ec9a7d3)

Anybody else noticed this?

Pal stop drugs. ;-)

Kidding. Just updated too & i'm on U4 too! To issue so far.

 

[SavageAUS]

I've updated to U4 without issue.

 

[rafadavidc]

Yes. I just did this tonight. However, it won't boot to U4. U3 is active, and U4 is selected for boot, but when I reboot, that remains the case.

 

[Jurgen Segaert]

I did found an issue with U3/U4. I updated from FreeNAS-9.10-STABLE-201606270534 (dd17351).
The "online help" (the "Guide"" button in the top toolbar) doesn't behave properly anymore. It presents a landing page ./docs/freenas.html but pretty much all of the links on that page are broken and lead to a "404 page not found".

One of the few links that work is the "index" link in the top right.

That index-link brings me to a much prettier looking page that mostly works, including the Docs-link that brings me back to the previous/broken page.

 

[wtfR6a]

Upgraded my second system, all appears well so far.

 

[MatthewSteinhoff]

I'm going to give U4 another week to percolate. I'm still running 9.10.1 and it's rock solid.

The primary reason we're looking to upgrade is Bug 16630 'Unable to save Adobe Indesign documents to CIFS from OS X'. Occasionally we see InDesign crash when attempting to save a file. We're not using OS X though so we're not sure if it is even related. It started happening around the time we went from CS5 to CC2016.

Cheers,
Matt