FreeNAS-9.10.1 Upgrade problem

[styno]

Luckily I didn't encounter this yesterday when I did an upgrade on two systems (from the gui). They are both booting from mirrored usb devices.
In my case, the freenas-boot pool was created on FreeNas 9.3 and upgraded ever since.

 

[Blish]

I don't have a mirrored setup either.

 

[LukeD]

Yes same here, upgrading via web gui 9.10.0 (works) to 9.10.1 kills ability to boot. (Gen9 HP 180 server), download and clean install 9.10.1 iso does work but for some reason my display isnt working in this scenario once reboot after install routine completed. (nor in in-band/out-of-band remote screen console)

 

[Nick Dutch]

For me the display also stopped working after doing a clean re-install.

 

[moparbrian]

Our setup at Stanford University is the same with mirrored drives and we also have this same problem. Please warn others not do upgrade to 9.10.1. System is Dell R710 connected to multiple Dell JBODS.

 

[Johannez]

Same problem for me after updating on a mirror set of scandisk cruzer 16gb usb.

From both versions the update failed.
FreeNAS-9.10-STABLE-201606270534 (dd17351)
FreeNAS-9.10-STABLE-201606072003 (696eba7)

 

[eroji]

So it seems like if you download the ISO of 9.10.1 off the website and do an upgrade install, it should leave the settings but recreate the boot volume. Quite the pain but at least that will get you back up and running. Release notes mentioned nothing about GRUB or USB related changes, so I am not exactly sure what caused this problem.

 

[SFoskett]

There are obvious visual differences between the initial boot sequence (GRUB) of 9.10 and 9.10.1. Combine that with the corrupted GRUB people are reporting here and perhaps also with the blank IPMI issue I experienced, and I think it's safe to say that some change to GRUB in 9.10.1 is flaky. It's disappointing that the release notes don't mention this change, since it obviously happened.

As for me, I rolled back to 9.10 Stable and don't plan to risk 9.10.1 for a while. At the very least, these changes should be documented and the flakiness addressed. Even then, this issue has made me nervous about updating in the future.

 

[Cellobita]

Even then, this issue has made me nervous about updating in the future.

Ditto. I usually update my systems remotely (I live an hour away from most of my customers), so this kind of problem is very upsetting. From now on I'll wait for at least a week before upgrading to a newer version.

 

[SFoskett]

https://bugs.freenas.org/issues/16720

What happened to bug 16720? I get "You are not authorized to access this page." Was there some resolution I'm not aware of?

 

[LukeD]

I think the no-display issue is either one of two things (or the combination). eg gen8 microserver, no issues with Freenas 9.10.1 upgrade or clean install.

Could th eissues with the Gen9 DL180 be:
1. UFI Matrox driver
2. UFI in general

I tried the same Gen9 DL180 on centos with ZFS on Linux added, I noted the onscreen centos dmesg log item regarding display driver selection... (see screenshot)

I also tried the working gen8 9.10.1 USB installation disk on the Gen9 DL180 server, same issue of no display so the issues around some servers having no display is a UFI/Driver selection issue somewhere in the new base install (as user Freenas settings will not change during upgrade/clean install)

Up to the FreeNAS team to see logic somewhere in this, regardless it is an issue on many rack servers reading this thread.

 

[LukeD]

Same problem for me after updating on a mirror set of scandisk cruzer 16gb usb.

From both versions the update failed.
FreeNAS-9.10-STABLE-201606270534 (dd17351)
FreeNAS-9.10-STABLE-201606072003 (696eba7)

I tried the CD upgrade vs the webgui upgrade, boots yes, no display output or IPMI display output, definitely in the grub arguments calling drivers/modules or base installation drivers/firmware modules - no issues gen8 HP Microserver, same scenario.

 

[warri]

What happened to bug 16720? I get "You are not authorized to access this page." Was there some resolution I'm not aware of?

Same here, has the bug moved to some kind of non-public area of the bug tracker?

 

[Jacopx]

News for a new release?

 

[acoustician]

What happened to bug 16720? I get "You are not authorized to access this page." Was there some resolution I'm not aware of?

Bug is private now. But I'm not sure that i can provide enough information to solve this problem.

 

[Spearfoot]

Same here, has the bug moved to some kind of non-public area of the bug tracker?

iXsystems flags bug reports 'private' if the submitter includes debug information with the bug report, because the debug fileset contains sensitive information.

 

[Spacemarine]

Still, that doesn't seem to be the ideal procedure...

 

[eroji]

Ditto. I usually update my systems remotely (I live an hour away from most of my customers), so this kind of problem is very upsetting. From now on I'll wait for at least a week before upgrading to a newer version.

Funny the problem actually happened to my friend who I built the server for, but he is in Hong Kong. I had to connect to his IPMI over the web with high latency and mount the ISO remotely and reinstall the boot volume.

 

[Nick Dutch]

Any updates?

 

[SFoskett]

So, on a lark, I installed FreeNAS 9.10 Stable on some random hardware I had sitting around: A Broadwell Intel NUC and some random flash drives. Then I clicked "Check Now" and "Update". Guess what happened...

Yup! Same two issues!

On first reboot, I get the GRUB error. So I reboot with a USB drive made from the 9.10.1 ISO and now I have a running FreeNAS with the blank console issue.

So this happens repeatedly and predictably on totally different hardware with a brand new, fresh install. I imaging it ought to be easy to reproduce and hopefully to debug and fix. And I imagine it would be a good idea to pull that bad update before anyone else clicks Update and has the same experience.

Note, in response to some questions and suggestions I've gotten, that I've tried both UEFI booting and legacy and have tried a number of different flash drives for both install and boot.