[Discussion] Did the 9.10.2 update work for you?

[reloaded]

I left the thing and took off to run some errands.

Thanks for the full picture, do you think the modification to grub had an effect on the outcome or is going out the recommended policy. I ask because I am getting some sort of check sum error in the grub area when I run Verification and any excuse to go to the pub seems better than none.

 

[MatthewSteinhoff]

We're worried about upgrading to 9.10.2 and this poll confirms our plan to wait.

Half of those who upgraded rolled back? Ouch!

Cheers,
Matt

 

[reloaded]

FreeNAS seems to have a history of this sort of problem, my first searches came back with stuck updates from years ago, perhaps a way of turning off "Alerts" would be beneficial. I also read something here about Jails going, that seems a bit retrograde, I had better do some more reading. Don't worry, it's not good for you.

 

[reloaded]

And another thing, I was just wondering if there is any relationship between problems and file systems, my file system was upgrade by the idiot who took over admin of the FreeNAS box for six months so I think I'm running the most recent zpool, I will have to check.

 

[Quebecman]

Had a first unsuccessful install, then a second install that booted but got into a Python script loop (thread here; might get moved and I might file a bug report : https://forums.freenas.org/index.ph...de-fail-python-script-errors-on-reboot.49272/)

 

[m0nkey_]

OK, so about a week ago I went ahead with the update. Albeit having an issue with snapshots not running at the time expected and what appeared to be odd ARC statistics (which weren't odd at all, FreeNAS has been lying to us for a very long time), it's been pretty solid so far.

I've noticed that if your boot device is USB, then the update may take a little bit of time to complete. Some people have reported upwards of an hour for completion. Having switched to an SSD for booting, the update only took a few minutes.

Overall, the update worked for me.

When a new update is released, give it a week or two before applying :)

 

[Jailer]

Ok your update success gives me the push to try 9.10.2. Will report back as soon as it's done downloading and updating........

 

[JohnDigital]

I did update without any issues. I have not run into anything lately other than the Virtualbox issue. I think that started with U4.

 

[Jailer]

Will report back as soon as it's done downloading and updating........

Well it's been up for a day and a half and all seems well.

 

[GreyMatters]

Where is the "what's new" of the last version?
The updated smb is good news but what else is updated?

I can't find this information with my poor google-fu :(

 

[MrToddsFriends]

Where is the "what's new" of the last version?

http://doc.freenas.org/9.10/intro.html#what-is-new-in-version
http://download.freenas.org/9.10/STABLE/9.10.2/ChangeLog

 

[drumer93]

So I recently upgraded my system to a Intel Confidential E3-1240L v5 chip (a very late in the testing process sample, its 4 digit code stars with a Q) and the update has not worked for me. It installs fine via the GUI but after restarting it hangs during boot while loading a kernel module after loading the ZFS Pool. I noticed that when loading 9.10.1 it recognizes the CPU there as 'Unknown Intel CPU' but then continues and the GUI recognizes it appropriately as a E3-1240L v5. I realize that since it is an Intel Confidential CPU its not officially supported by anyone or anything, and me even having it is questionable. I just don't understand why it worked flawlessly under 9.10.1 without any issue whatsoever and fails miserably on 9.10.2. Not necessarily looking for help, just thought it would be nice if something could be changed back to support unidentified CPU's.

 

[Jailer]

Felt froggy so I updated to 9.10.2-U1 today. All seems well so far.

 

[Ericloewe]

So I recently upgraded my system to a Intel Confidential E3-1240L v5 chip (a very late in the testing process sample, its 4 digit code stars with a Q) and the update has not worked for me. It installs fine via the GUI but after restarting it hangs during boot while loading a kernel module after loading the ZFS Pool. I noticed that when loading 9.10.1 it recognizes the CPU there as 'Unknown Intel CPU' but then continues and the GUI recognizes it appropriately as a E3-1240L v5. I realize that since it is an Intel Confidential CPU its not officially supported by anyone or anything, and me even having it is questionable. I just don't understand why it worked flawlessly under 9.10.1 without any issue whatsoever and fails miserably on 9.10.2. Not necessarily looking for help, just thought it would be nice if something could be changed back to support unidentified CPU's.

I dunno, what's being loaded?

 

[drumer93]

I dunno, what's being loaded?

idk, I don't really know what 'kernel modules' are, but I know this CPU doesn't report a serial number and a few other things that CPU's do normally report. I'm guessing FreeNAS is asking for something and the CPU doesn't have a value to return so it just gets stuck in a loop so it hangs there indefinitely. Here's a list of my other components: https://pcpartpicker.com/list/RpxP7h

 

[Fraoch]

The 9.10.2 update worked fine for me. The U1 update yesterday resulted in an abnormally long boot and some odd errors on startup I've never seen before:

Code:

> warning: KLD '/boot/kernel/dtraceall.ko' is newer than the linker.hints file
> warning: KLD '/boot/kernel/dtrace.ko' is newer than the linker.hints file
> warning: KLD '/boot/kernel/dtmalloc.ko' is newer than the linker.hints file
> warning: KLD '/boot/kernel/dtnfscl.ko' is newer than the linker.hints file
> warning: KLD '/boot/kernel/fbt.ko' is newer than the linker.hints file
> warning: KLD '/boot/kernel/fasttrap.ko' is newer than the linker.hints file
> warning: KLD '/boot/kernel/lockstat.ko' is newer than the linker.hints file
> warning: KLD '/boot/kernel/sdt.ko' is newer than the linker.hints file
> warning: KLD '/boot/kernel/systrace.ko' is newer than the linker.hints file
> warning: KLD '/boot/kernel/systrace_freebsd32.ko' is newer than the linker.hints file
> warning: KLD '/boot/kernel/profile.ko' is newer than the linker.hints file
> warning: KLD '/boot/kernel/smbus.ko' is newer than the linker.hints file
> warning: KLD '/boot/kernel/t3_tom.ko' is newer than the linker.hints file
> warning: KLD '/boot/kernel/toecore.ko' is newer than the linker.hints file
> warning: KLD '/boot/kernel/t4_tom.ko' is newer than the linker.hints file
> warning: KLD '/boot/kernel/ums.ko' is newer than the linker.hints file
> warning: KLD '/boot/kernel/ng_ether.ko' is newer than the linker.hints file

Not sure if that's what caused the long reboot.

Anything to be concerned about?

 

[m0nkey_]

The 9.10.2 update worked fine for me. The U1 update yesterday resulted in an abnormally long boot and some odd errors on startup I've never seen before:

Code:

> warning: KLD '/boot/kernel/dtraceall.ko' is newer than the linker.hints file
> warning: KLD '/boot/kernel/dtrace.ko' is newer than the linker.hints file
> warning: KLD '/boot/kernel/dtmalloc.ko' is newer than the linker.hints file
> warning: KLD '/boot/kernel/dtnfscl.ko' is newer than the linker.hints file
> warning: KLD '/boot/kernel/fbt.ko' is newer than the linker.hints file
> warning: KLD '/boot/kernel/fasttrap.ko' is newer than the linker.hints file
> warning: KLD '/boot/kernel/lockstat.ko' is newer than the linker.hints file
> warning: KLD '/boot/kernel/sdt.ko' is newer than the linker.hints file
> warning: KLD '/boot/kernel/systrace.ko' is newer than the linker.hints file
> warning: KLD '/boot/kernel/systrace_freebsd32.ko' is newer than the linker.hints file
> warning: KLD '/boot/kernel/profile.ko' is newer than the linker.hints file
> warning: KLD '/boot/kernel/smbus.ko' is newer than the linker.hints file
> warning: KLD '/boot/kernel/t3_tom.ko' is newer than the linker.hints file
> warning: KLD '/boot/kernel/toecore.ko' is newer than the linker.hints file
> warning: KLD '/boot/kernel/t4_tom.ko' is newer than the linker.hints file
> warning: KLD '/boot/kernel/ums.ko' is newer than the linker.hints file
> warning: KLD '/boot/kernel/ng_ether.ko' is newer than the linker.hints file

Not sure if that's what caused the long reboot.

Anything to be concerned about?

I opened a bug ticket to make sure this wasn't going to be a problem. Performed another reboot and the messages did not appear.

 

[Fraoch]

I see the bug:

https://bugs.freenas.org/issues/20237#change-105747

Doesn't look like too much of an issue. I haven't rebooted to see if these messages would clear though.

Thanks.

 

[IceBoosteR]

Hi,

I could upgrade without a problem to 9.10.2 and 9.10.2-U1. I am happy not to face any problems :)
IceBoosteR

 

[nonvtec]

I just updated. I have 2 x mirrored 64gb USB OS drives and the install took about 2-3 mins and the subsequent reboot maybe 5-7 mins. All good!