update 9.10.1U4 to 9.10.2 no gui

[BillCardiff]

I thought it was down, but all my jails are running great.
All jails started, all jails seem to be running correctly with access to all their data shares.
Nothing on the web gui. Tried https and http --- nada.

My gui is supposed to be present at port 9000 --- so I typically am able to see the page at 192.168.1.5:9000, am instead greeted by "server not found"

Tried Safari, Chrome and Firefox.

I am able to get in via terminal and ssh --- so the brains are running, just the lights are out.
Side note: can I set the boot preference from an ssh session or do I have to go find a spare monitor ?

 

[dlavigne]

Anything related in /var/log/messages? Is port 9000 showing as open if you type
sockstat -4?

 

[BillCardiff]

port 9000 is not shown in the sockstat command now that I am looking, but nothing in /var/log/messages

 

[dlavigne]

That would be why it's not connecting

Why it's not opening it though sounds like a bug (assuming you set the port number using the GUI). Please create a report at bugs.freenas.org and post the issue number here.

 

[BillCardiff]

The port was created using the 9.10.1 GUI all normal like. I am pondering setting the boot back to 9.10.1U4 and removing that specific port and then trying the update. The porting was needed for remote access due to the weird jails and other internal hardware I run.
I will create a report as soon as I try the no port refresh.


Sent from my iPhone using Tapatalk

 

[Ajedi32]

This sounds similar to the problem I'm having: https://forums.freenas.org/index.php?threads/update-from-9-10-1-to-9-10-2-broke-my-install.48863/

Can you confirm whether you get similar results when trying to run `wget` and `freenas-update`, or what information your screen is displaying when you boot?

 

[Sup3rNerdy]

SAme issue here after the last update. I'm unable to run anything as sudo :/

The GUI wont load and the shares dont work either

 

[Arkhen]

SAme issue here after the last update. I'm unable to run anything as sudo :/

The GUI wont load and the shares dont work either

Exact same issue here.

- Motherboard: SuperMicro X11SSH-F
- CPU: Xeon E3-1270 v5
- HDD: 7x WD 4TB Reds
- RAM: Crucial 32GB Kit (2 x 16GB) DDR4 ECC
- USB /w Boots: Corsair Flash Voyager GT 32GB
- Updating from: 9.10.1-U4 (which was working fine)

 

[Wirefree]

I also had a failed update to 9.10.2. Tried a couple of times, sometimes the server would come back up but no GUI (as described above), and once when the machine wouldn't even boot. In all cases I rolled back successfully to U4 and all is well. I have not tried a fresh install, that might work, but not really wanting to go through setting up jails

Given the number of posts of issues, I think this needs to come off the "stable" train until it is better understood.

- System: ASRock Server board, Xeon E3-1241, 16GB ECC, 4 X 3TB WD Red, boot = 2 X 16 GB mirrored Flash drives

 

[ndehmer]

I had an issue with the GUI upgrade as well. I didn't have SSH access setup and the CLI was having an issue that looked like a stuck key or something. So I created another update USB Stick and booted off of that and then re-did the upgrade from the install USB to the existing USB. SO far everything is working as expected.

 

[Ajedi32]

In all cases I rolled back successfully to U4 and all is well.

If you don't mind me asking, how do you do that from the command line? It's pretty obvious how to do it from the Web GUI, but obviously that won't work in this case since the Web GUI is broken for me.

 

[Ericloewe]

If you don't mind me asking, how do you do that from the command line? It's pretty obvious how to do it from the Web GUI, but obviously that won't work in this case since the Web GUI is broken for me.

You don't. Before the system boots, GRUB gives you the option of booting an older environment.

 

[Sup3rNerdy]

I also had a failed update to 9.10.2. Tried a couple of times, sometimes the server would come back up but no GUI (as described above), and once when the machine wouldn't even boot. In all cases I rolled back successfully to U4 and all is well. I have not tried a fresh install, that might work, but not really wanting to go through setting up jails

Given the number of posts of issues, I think this needs to come off the "stable" train until it is better understood.

- System: ASRock Server board, Xeon E3-1241, 16GB ECC, 4 X 3TB WD Red, boot = 2 X 16 GB mirrored Flash drives

Is there a way to rollback through CLI ?

 

[Ajedi32]

Is there a way to rollback through CLI ?

Ericloewe literally just answered that in the post directly above yours.

 

[cyberjock]

If you want to change the boot environment you can do what @Ericloewe recommended or you can do this:

# beadm list

That'll list your boot environments. Find the one you want and do:

# beadm activate <boot environment name>

For most of us, this will likely be:

# beadm activate 9.10.1-U4

Then reboot and you'll be back on your old boot environment.

This changed the boot environment that is the default on bootup. So at least understand this before actually doing this. The way that @Ericloewe mentioned will only last for that bootup sequence. If you reboot the system again you'll be booted from the default boot environment (9.10.2).

 

[Ajedi32]

If you want to change the boot environment you can do what @Ericloewe recommended or you can do this:

# beadm list

That'll list your boot environments. Find the one you want and do:

# beadm activate <boot environment name>

For most of us, this will likely be:

# beadm activate 9.10.1-U4

Then reboot and you'll be back on your old boot environment.

This changed the boot environment that is the default on bootup. So at least understand this before actually doing this. The way that @Ericloewe mentioned will only last for that bootup sequence. If you reboot the system again you'll be booted from the default boot environment (9.10.2).

Thanks. That seemed to work, but I did get a warning message which was a bit concerning:

Code:

[root@freenas] ~# beadm activate 9.10.1-U4
WARNING: Failed to update GRUB configuration
Activated successfully

The old environment is listed as active:

Code:

[root@freenas] ~# beadm list
BE					   Active Mountpoint  Space Created				Nickname
default				  -	  -			3.6M 2016-05-27 21:56	   default
Initial-Install		  -	  -			2.9M 2016-05-27 22:15	   Initial-Install
9.10-STABLE-201605240427 -	  -		  111.0M 2016-05-28 19:52	   9.10-STABLE-201605240427
9.10-STABLE-201606072003 -	  -		  186.2M 2016-06-08 19:03	   9.10-STABLE-201606072003
9.10-STABLE-201606270534 -	  -		  184.8M 2016-07-06 23:52	   9.10-STABLE-201606270534
9.10.1-U1				-	  -		  151.9M 2016-10-01 20:24	   9.10.1-U1
9.10.1-U2				-	  -		  149.7M 2016-10-04 23:10	   9.10.1-U2
9.10.1-U3				-	  -		  149.5M 2016-11-09 21:52	   9.10.1-U3
9.10.1-U4				R	  -			2.2G 2016-11-09 22:05	   9.10.1-U4
9.10.2				   N	  /		   19.9M 2016-12-22 19:16	   9.10.2

However, upon reboot the problem persists, and 9.10.2 is still listed as the currently active environment:

Code:

[root@freenas] ~# beadm list
BE					   Active Mountpoint  Space Created				Nickname
default				  -	  -			3.6M 2016-05-27 21:56	   default
Initial-Install		  -	  -			2.9M 2016-05-27 22:15	   Initial-Install
9.10-STABLE-201605240427 -	  -		  111.0M 2016-05-28 19:52	   9.10-STABLE-201605240427
9.10-STABLE-201606072003 -	  -		  186.2M 2016-06-08 19:03	   9.10-STABLE-201606072003
9.10-STABLE-201606270534 -	  -		  184.8M 2016-07-06 23:52	   9.10-STABLE-201606270534
9.10.1-U1				-	  -		  151.9M 2016-10-01 20:24	   9.10.1-U1
9.10.1-U2				-	  -		  149.7M 2016-10-04 23:10	   9.10.1-U2
9.10.1-U3				-	  -		  149.5M 2016-11-09 21:52	   9.10.1-U3
9.10.1-U4				R	  -			2.2G 2016-11-09 22:05	   9.10.1-U4
9.10.2				   N	  /		   19.9M 2016-12-22 19:16	   9.10.2

I was able to boot into 9.10.1-U4 from grub, and everything (Web GUI, wget, etc) is working fine in this environment.

As you said though, on reboot I'll be back to the broken 9.10.2 install unless I'm able to complete a more permanent fix. Now that the Web GUI is operational, I'm going to see what I can do from there...

 

[Ajedi32]

Okay I fixed it. After booting into 9.10.1-U4 from grub (the menu which pops up on your screen when you first start the machine running Freenas), I SSHd into the machine and ran:

Code:

beadm destroy 9.10.2

Then to update, I ran:

Code:

cd /var/tmp
wget https://download.freenas.org/9.10/STABLE/9.10.2/FreeNAS-9.10.2.tar
freenas-update FreeNAS-9.10.2.tar

And rebooted:

Code:

shutdown -r now

Then everything worked fine:

 

[cyberjock]

The output you gave for beadm list shows that on reboot 9.10.1-U4 is what should boot (the R=reboot under the ACTIVE column), but you were currently on 9.10.2 (the N=now under the ACTIVE column).

 

[cyberjock]

Your steps don't make sense. You cannot do a beadm destroy 9.10.2 if you are running from the 9.10.2 boot environment (which it sounds like you're saying you did above). You'd literally be destroying the filesystem that's mounted, and that's not possible to do. :P

 

[JJT211]

I was able to boot into 9.10.1-U4 from grub, and everything (Web GUI, wget, etc) is working fine in this environment.

As you said though, on reboot I'll be back to the broken 9.10.2 install unless I'm able to complete a more permanent fix. Now that the Web GUI is operational, I'm going to see what I can do from there...

Once you boot into 9.10.1-U4, go to System>Boot, highlight the 9.10.1-U4 file, then select "Activate" it to stay on 9.10.1-U4 after reboot.