FreeNAS 9.10-RELEASE now available!

[jagter_freenas]

Simple Question -

Is a reboot of FreeNas required for the upgrade from 9.3 to 9.10?

 

[ThreeDee]

Simple Question -

Is a reboot of FreeNas required for the upgrade from 9.3 to 9.10?

it automatically rebooted my box when I did the update

 

[jgreco]

Simple Question -

Is a reboot of FreeNas required for the upgrade from 9.3 to 9.10?

Absolutely.

 

[diehard]

lol you hosers cant even do a major underlying OS upgrade without a restart? Amateurs.

 

[Ghwomb]

p20 - same version as before. There have been no recent LSI driver updates, even in FreeBSD-current (11).

Well 10.x seems to support m1115 for example. So no more flashing of of m115 cards to m1015 firmware in order to get FreeNAS support. Or am I missing something?
Altough I from what I gather the mfi drivers is something different than p20.

 

[jgreco]

Well 10.x seems to support m1115 for example. So no more flashing of of m115 cards to m1015 firmware in order to get FreeNAS support. Or am I missing something?

No, I'm reasonably certain there's a bunch of people who have had success with the M1115, but the M1015 is easily found so most people still go for that.

Altough I from what I gather the mfi drivers is something different than p20.

Yes, see the LSI sticky for an explanation of the various modes.

 

[diskdiddler]

Should 9.10 bugs be filed for FN9 or FN10? considering the underlying OS?

 

[jkh]

Should 9.10 bugs be filed for FN9 or FN10? considering the underlying OS?

9 please - the version # refers to FreeNAS not FreeBSD.

 

[johnjaylward]

almost all my jails died that did anything complex. I usually use portmaster in my jails to manage the installed packages and portmaster is hosed. Happened only after doing a `portsnap fetch update`.

I get one of 2 errors depending on the jail:

"/usr/ports/Mk/bsd.port.mk", line 1162: UNAME_r (10.3-RC3) and OSVERSION (903000) do not agree on major version number.

"The value of DISTDIR cannot be empty"

Seems my only option is to nuke the entire thing and start over, which as I said initially, is non-trivial.

 

[Alecmascot]

Wow, colour me surprised. Otherwise working fine?

Several people have indicated that it may require slightly more memory, how much is in yours? Mine only has 8.

Working fine but I think maybe CIFS browsing has slowed down.
They both have 8GB

 

[gpsguy]

According to Alecmascot's signature, he's running 4x2TB disks in RAIDz2.

Before the disk failure fiasco, you were running 6x5TB disks in RAIDz2.

Several people have indicated that it may require slightly more memory, how much is in yours? Mine only has 8.

 

[joeschmuck]

I distinctly recall many posts in the FN10 discussion threads, 6 months ago which seemed to indicate BSD10 could / would have all kinds of issues with drivers and hardware for older machines (especially AMD)

I recall some of those discussions but with respect to AMD support and there was some code waiting to become part of FreeBSD Release, it was in FreeBSD Current, or something like that, either way it's no longer an issue as far as I know.

I myself will be holding off upgrading my FreeNAS system to 9.10 but I have a play system now (my old AMD FreeNAS system) and I will play around on that hardware.

 

[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?

 

[SweetAndLow]

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?

Looks like your usb is dead

 

[garfunkel]

I was able to boot back into 9.3 without any issues. It's the same Corsair Voyager USB 3 stick I've been using for a few years, never had any issues.

I even tried the upgrade a second time, with no success.

Is this some regression in FreeBSD?

 

[BRC]

I have an issue updating a couple 9.10 updates through UI.
It was a new install yesterday from img, and system is working fine with 32GB, some mirrored pools, ZIL and iSCSI.

I notice there was some fixes in changelog around update installation, but not sure if this might be one of those fixes. I'll look through relevant bugs but thought someone might be able to save me some time working this out.

I can manual zfs snapshot btw...


Mar 25 22:37:07 freenas-03-01 kernel: <118>Mar 25 22:37:07 freenas-03-01 updated.py: [freenasOS.Update:1204] Unable to create snapshot freenas-boot/ROOT/default@Pre-Uprgade-d1851bb004ead848f18f828f8fd48bae, bailing for now
Mar 25 22:37:09 freenas-03-01 manage.py: [middleware.exceptions:37] [MiddlewareError: Unable to create snapshot freenas-boot/ROOT/default@Pre-Uprgade-d1851bb004ead848f18f828f8fd48bae]
Mar 25 22:38:10 freenas-03-01 updated.py: [freenasOS.Update:1204] Unable to create snapshot freenas-boot/ROOT/default@Pre-Uprgade-d1851bb004ead848f18f828f8fd48bae, bailing for now
Mar 25 22:38:10 freenas-03-01 kernel: <118>Mar 25 22:38:10 freenas-03-01 updated.py: [freenasOS.Update:1204] Unable to create snapshot freenas-boot/ROOT/default@Pre-Uprgade-d1851bb004ead848f18f828f8fd48bae, bailing for now
Mar 25 22:38:12 freenas-03-01 manage.py: [middleware.exceptions:37] [MiddlewareError: Unable to create snapshot freenas-boot/ROOT/default@Pre-Uprgade-d1851bb004ead848f18f828f8fd48bae]
Mar 25 22:48:58 freenas-03-01 updated.py: [freenasOS.Update:1214] Unable to create new boot environment 9.10-RELEASE
Mar 25 22:48:58 freenas-03-01 kernel: <118>Mar 25 22:48:58 freenas-03-01 updated.py: [freenasOS.Update:1214] Unable to create new boot environment 9.10-RELEASE
Mar 25 22:49:19 freenas-03-01 manage.py: [middleware.exceptions:37] [MiddlewareError: Unable to create new boot environment 9.10-RELEASE]

 

[SaskiFX]

The upgrade of the jails and encrypted volume went without issues so far. :)

However, seems my CA certs are giving Chrome and Firefox the fits when connecting to the FreeNAS WebGUI. IE seems to take it just fine with warnings (typical Microsoft).

In Firefox I get this:

An error occurred during a connection to 10.x.x.x You have received an invalid certificate. Please contact the server administrator or email correspondent and give them the following information: Your certificate contains the same serial number as another certificate issued by the certificate authority. Please get a new certificate containing a unique serial number. Error code: SEC_ERROR_REUSED_ISSUER_AND_SERIAL

I get the same thing in Chrome. Both running on my Linux Mint 17.3 workstation.

After quick google something about the Serial Number is set to 01 or Zero?

I tried deleting all the CA certs and re-create them. No go. For now I got the http and https enabled until I sort this out.

Thanks.

How did you get HTTP working? I am unable to get on via HTTP or SSH. I know the box is running because I can see my drives, I just can't do anything. =/

EDIT: Fixed SSH, was a bug in PuTTY on windows. So now I can get to the console easy, but I still can't get to the WebGUI in any way.

EDIT2: Fixed it. Regenerated the certificates via the console and forced nginx to restart. Got back into the WebGUI and set things to HTTP+HTTPS :)

 

[rogerh]

No problems detected yet with an N54L and 9.10 release. Using SSDs as boot devices, though.

 

[zambanini]

what about the easter egg?

 

[Darkk]

How did you get HTTP working? I am unable to get on via HTTP or SSH. I know the box is running because I can see my drives, I just can't do anything. =/

EDIT: Fixed SSH, was a bug in PuTTY on windows. So now I can get to the console easy, but I still can't get to the WebGUI in any way.

EDIT2: Fixed it. Regenerated the certificates via the console and forced nginx to restart. Got back into the WebGUI and set things to HTTP+HTTPS :)

Yep, I had to go into the console and re-generate the SSL cert and key in the /etc/certificates folder and then edit the ngnix.conf in /usr/local/etc/nginx

Doing it manually fixed the SSL cert issue but the drawback is that this won't get updated in the FreeNAS WebGUI's system general tab. I tried re-generating new certs via the WebGUI which reverts back to the same problem as before so I am suspecting might be a bug. For now this works.