Upgrading Ubuntu 14 to 16
#1
Has anyone run 'do-release-upgrade' on their Ubuntu 14 installation in order to upgrade it to Ubuntu 16.04.2 LTS?

I have been avoiding doing this since everything is working well with Ubuntu 14 and it is supported until 2019.  But I know that I will have to upgrade eventually.

Has the upgrade process gone smoothly or have there been any issues?

Did ssh still work afterwards?
Did the config for xdm stay intact?
Were there any driver problems, Nivida or AMD?
Reply
#2
FWIW I'm not planning to move to 16.04 for at least another 7 months.

If you're using AMD GPUs, then yes things will be different moving from 14.04, as you would use fglrx on 14.04 but amdgpu-pro on 16.04. For Nvidia things should pretty much be the same.
Reply
#3
(03-18-2017, 11:11 PM)epixoip Wrote: FWIW I'm not planning to move to 16.04 for at least another 7 months.

If you're using AMD GPUs, then yes things will be different moving from 14.04, as you would use fglrx on 14.04 but amdgpu-pro on 16.04. For Nvidia things should pretty much be the same.

Curious - any particular reason? I haven't had an issue thus far but I'm sure you could be running into things I'm not.
Reply
#4
(03-18-2017, 11:00 PM)devilsadvocate Wrote: Has anyone run 'do-release-upgrade' on their Ubuntu 14 installation in order to upgrade it to Ubuntu 16.04.2 LTS?

I have been avoiding doing this since everything is working well with Ubuntu 14 and it is supported until 2019.  But I know that I will have to upgrade eventually.

Has the upgrade process gone smoothly or have there been any issues?

Did ssh still work afterwards?
Did the config for xdm stay intact?
Were there any driver problems, Nivida or AMD?

Today, I decided to do the upgrade from Ubuntu 14 to 16.

I ran this command while connected via ssh:
do-release-upgrade
(This took just under an hour to complete.)
(You will have to watch it since you will be asked some questions as it progresses.  You will have to type a response like 'y' and then press Enter.)

It went smoothly with the exception of a network configuration that I forgot about.

I had been running a VM setup on my hashcat machine and I was using the virbr0 (virtual bridge) interface (/etc/network/interfaces).  After the upgrade had completed, I rebooted and couldn't connect to my machine.  My access point tells me which machines are considered "connected devices" and my Ubuntu hashcat system wasn't listed as a connected device.  From that, I knew that I had a network configuration problem.

I rebooted into recovery mode, enabled networking, connected via ssh, and, as root, removed the entry for virbr0 from /etc/network/interfaces.  After that, I rebooted again and was able to connect via ssh.

This was what the output was from 'ifconfig' before the configuration change.  (MAC addresses have been removed.)
Code:
enp11s0   Link encap:Ethernet  HWaddr 
         UP BROADCAST MULTICAST  MTU:1500  Metric:1
         RX packets:0 errors:0 dropped:0 overruns:0 frame:0
         TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000
         RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
         Interrupt:17

eth0      Link encap:Ethernet  HWaddr 
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:1478 errors:0 dropped:32 overruns:0 frame:0
         TX packets:1051 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000
         RX bytes:141579 (141.5 KB)  TX bytes:186980 (186.9 KB)
         Interrupt:20 Memory:dd100000-dd120000

lo        Link encap:Local Loopback
         inet addr:127.0.0.1  Mask:255.0.0.0
         inet6 addr: ::1/128 Scope:Host
         UP LOOPBACK RUNNING  MTU:65536  Metric:1
         RX packets:21 errors:0 dropped:0 overruns:0 frame:0
         TX packets:21 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1
         RX bytes:1473 (1.4 KB)  TX bytes:1473 (1.4 KB)

virbr0    Link encap:Ethernet  HWaddr 
         inet addr:192.168.1.77  Bcast:192.168.1.255  Mask:255.255.255.0
         inet6 addr: 2605:6000:6b52:db00:1e1b:dff:fe0c:7f9f/64 Scope:Global
         inet6 addr: fe80::1e1b:dff:fe0c:7f9f/64 Scope:Link
         inet6 addr: 2605:6000:6b52:db00:a511:1c31:bdcd:3058/64 Scope:Global
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:1431 errors:0 dropped:0 overruns:0 frame:0
         TX packets:1040 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000
         RX bytes:112813 (112.8 KB)  TX bytes:181764 (181.7 KB)

This was what the output was from 'ifconfig' after the configuration change.  (MAC addresses have been removed.)
Code:
enp11s0   Link encap:Ethernet  HWaddr 
         UP BROADCAST MULTICAST  MTU:1500  Metric:1
         RX packets:0 errors:0 dropped:0 overruns:0 frame:0
         TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000
         RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
         Interrupt:17

eth0      Link encap:Ethernet  HWaddr 
         inet addr:192.168.1.77  Bcast:192.168.1.255  Mask:255.255.255.0
         inet6 addr: 2605:6000:6b52:db00::4/128 Scope:Global
         inet6 addr: fe80::fb51:3fed:3a69:23e/64 Scope:Link
         inet6 addr: 2605:6000:6b52:db00:7cb0:3033:99b4:22d9/64 Scope:Global
         inet6 addr: 2605:6000:6b52:db00:15bd:48fe:6c7f:8791/64 Scope:Global
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:584 errors:0 dropped:0 overruns:0 frame:0
         TX packets:371 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000
         RX bytes:109896 (109.8 KB)  TX bytes:51646 (51.6 KB)
         Interrupt:20 Memory:dd100000-dd120000

lo        Link encap:Local Loopback
         inet addr:127.0.0.1  Mask:255.0.0.0
         inet6 addr: ::1/128 Scope:Host
         UP LOOPBACK RUNNING  MTU:65536  Metric:1
         RX packets:531 errors:0 dropped:0 overruns:0 frame:0
         TX packets:531 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1
         RX bytes:41389 (41.3 KB)  TX bytes:41389 (41.3 KB)

virbr0    Link encap:Ethernet  HWaddr 00:00:00:00:00:00
         inet addr:192.168.122.1  Bcast:192.168.122.255  Mask:255.255.255.0
         UP BROADCAST MULTICAST  MTU:1500  Metric:1
         RX packets:0 errors:0 dropped:0 overruns:0 frame:0
         TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000
         RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

eth0 had the desired ip address, not virbr0.

To be thorough, I decided to properly remove the virbr0 interface altogether.

I executed the following: (you can do this while connected via ssh on your main interface, in my case, eth0)
virsh net-destroy default
virsh net-undefine default
systemctl restart libvirtd (you will have to authenticate as root if you are not running this as root)

output from ifconfig (virbr0 is gone)
Code:
enp11s0   Link encap:Ethernet  HWaddr 
         UP BROADCAST MULTICAST  MTU:1500  Metric:1
         RX packets:0 errors:0 dropped:0 overruns:0 frame:0
         TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000
         RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
         Interrupt:17

eth0      Link encap:Ethernet  HWaddr 
         inet addr:192.168.1.77  Bcast:192.168.1.255  Mask:255.255.255.0
         inet6 addr: 2605:6000:6b52:db00::4/128 Scope:Global
         inet6 addr: fe80::fb51:3fed:3a69:23e/64 Scope:Link
         inet6 addr: 2605:6000:6b52:db00:7cb0:3033:99b4:22d9/64 Scope:Global
         inet6 addr: 2605:6000:6b52:db00:15bd:48fe:6c7f:8791/64 Scope:Global
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:1994 errors:0 dropped:0 overruns:0 frame:0
         TX packets:1388 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000
         RX bytes:251796 (251.7 KB)  TX bytes:241490 (241.4 KB)
         Interrupt:20 Memory:dd100000-dd120000

lo        Link encap:Local Loopback
         inet addr:127.0.0.1  Mask:255.0.0.0
         inet6 addr: ::1/128 Scope:Host
         UP LOOPBACK RUNNING  MTU:65536  Metric:1
         RX packets:754 errors:0 dropped:0 overruns:0 frame:0
         TX packets:754 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1
         RX bytes:60316 (60.3 KB)  TX bytes:60316 (60.3 KB)

Other than this issue, all seems well.  The ssh and xdm configurations were persistent across the upgrade process.
Reply