How To Upgrade to Ubuntu 16.04 LTS from Ubuntu 14.04 LTS

If You Appreciate What We Do Here On TecMint, You Should Consider:

  1. Stay Connected to: Twitter | Facebook | Google Plus
  2. Subscribe to our email updates: Sign Up Now
  3. Use our Linode referral link if you plan to buy VPS (it starts at only $10/month).
  4. Support us via PayPal donate - Make a Donation
  5. Support us by purchasing our premium books in PDF format.
  6. Support us by taking our online Linux courses

We are thankful for your never ending support.

Aaron Kili

Aaron Kili is a Linux and F.O.S.S enthusiast, an upcoming Linux SysAdmin, web developer, and currently a content creator for TecMint who loves working with computers and strongly believes in sharing knowledge.

Your name can also be listed here. Got a tip? Submit it here to become an TecMint author.

RedHat RHCE and RHCSA Certification Book
Linux Foundation LFCS and LFCE Certification Preparation Guide

You may also like...

18 Responses

  1. arokia says:

    I getting the following error at the end of the upgrade.

    Hit:1 http://us.archive.ubuntu.com/ubuntu xenial InRelease
    Get:2 http://security.ubuntu.com/ubuntu xenial-security InRelease [102 kB]
    Get:3 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease [102 kB]
    Get:4 http://us.archive.ubuntu.com/ubuntu xenial-backports InRelease [102 kB]
    Fetched 306 kB in 1s (165 kB/s)
    Reading package lists… Done
    Reading package lists… Done
    Building dependency tree
    Reading state information… Done
    Calculating upgrade… Done
    The following packages were automatically installed and are no longer required:
    apt-xapian-index aptitude-common gcc-4.8-base gcc-4.9-base libapt-inst1.5
    libarchive-extract-perl libbind9-90 libboost-iostreams1.54.0
    libboost-iostreams1.58.0 libcgi-fast-perl libcgi-pm-perl libck-connector0
    libclass-accessor-perl libcwidget3 libdns100 libencode-locale-perl
    libept1.4.12 libfcgi-perl libgck-1-0 libgcr-3-common libgcr-base-3-1
    libhtml-parser-perl libhtml-tagset-perl libhttp-date-perl
    libhttp-message-perl libio-html-perl libio-string-perl libisc95 libisccc90
    libisccfg90 libjson0 liblinear1 liblog-message-perl
    liblog-message-simple-perl liblwp-mediatypes-perl liblwres90
    libmodule-pluggable-perl libmodule-runtime-perl libparams-classify-perl
    libparse-debianchangelog-perl libpod-latex-perl libprocps3
    libsigc++-2.0-0c2a libsub-name-perl libsystemd-daemon0 libsystemd-login0
    libterm-ui-perl libtext-soundex-perl libtimedate-perl liburi-perl
    libxapian-1.3-5 libxapian22v5 libxtables10 linux-generic
    linux-headers-3.13.0-83 linux-headers-3.13.0-83-generic
    linux-headers-3.13.0-86 linux-headers-3.13.0-86-generic
    linux-headers-3.13.0-93 linux-headers-3.13.0-93-generic
    linux-headers-generic linux-image-3.13.0-86-generic
    linux-image-3.13.0-93-generic linux-image-extra-3.13.0-86-generic
    linux-image-extra-3.13.0-93-generic linux-image-generic
    python-ndg-httpsclient python-requests python-urllib3 python-xapian
    python3-xapian1.3 thermald watershed
    Use ‘sudo apt autoremove’ to remove them.
    0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
    4 not fully installed or removed.
    After this operation, 0 B of additional disk space will be used.
    Do you want to continue? [Y/n] Y
    Setting up initramfs-tools (0.122ubuntu8.8) …
    update-initramfs: deferring update (trigger activated)
    Setting up linux-image-extra-4.4.0-59-generic (4.4.0-59.80) …
    run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.0-59-generic /b oot/vmlinuz-4.4.0-59-generic
    run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.4.0-59-generic /bo ot/vmlinuz-4.4.0-59-generic
    update-initramfs: Generating /boot/initrd.img-4.4.0-59-generic

    gzip: stdout: No space left on device
    E: mkinitramfs failure cpio 141 gzip 1
    update-initramfs: failed for /boot/initrd.img-4.4.0-59-generic with 1.
    run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
    dpkg: error processing package linux-image-extra-4.4.0-59-generic (–configure):
    subprocess installed post-installation script returned error exit status 1
    dpkg: dependency problems prevent configuration of linux-image-generic:
    linux-image-generic depends on linux-image-extra-4.4.0-59-generic; however:
    Package linux-image-extra-4.4.0-59-generic is not configured yet.

    dpkg: error processing package linux-image-generic (–configure):
    dependency problems – leaving unconfigured
    dpkg: dependency problems prevent configuration of linux-generic:
    linux-generic depends on linux-image-generic (= 4.4.0.59.62); however:
    Package linux-image-generic is not configured yet.

    dpkg: error processing package linux-generic (–configure):
    dependency problems – leaving unconfigured
    Processing triggers for initramfs-tools (0.122ubuntu8.8) …
    No apport report written because the error message indicates its a followup erro r from a previous failure.
    No apport report written because the error message ind icates its a followup error from a previous failure.
    update-initramfs: Generating /boot/initrd.img-4.4.0-59-generic

    gzip: stdout: No space left on device
    E: mkinitramfs failure cpio 141 gzip 1
    update-initramfs: failed for /boot/initrd.img-4.4.0-59-generic with 1.
    dpkg: error processing package initramfs-tools (–configure):
    subprocess installed post-installation script returned error exit status 1
    No apport report written because MaxReports is reached already
    Errors were encoun tered while processing:
    linux-image-extra-4.4.0-59-generic
    linux-image-generic
    linux-generic
    initramfs-tools
    E: Sub-process /usr/bin/dpkg returned an error code (1)

  2. John deBoer says:

    Instead of interweaving desktop and server upgrades and showing confusion, why couldn’t you have done the LOGICAL “click here for server, here for desktop instructions”?
    I’ll now go elsewhere for more coherent advice!

  3. Grant Hood says:

    What Is the difference from regular upgrade and server upgrade?

  4. Sylvester Rac says:

    A very helpful article. I’d had enough of GUI frontend wrappers failing and never knowing what the error was so I used the CLI method you described to upgrade my Mythbuntu installation. It worked flawlessly, thanks to you!

    • Aaron Kili K says:

      @Sylvester Rac

      You are welcome and thanks so much for the feedback, always remember to stay connected to Tecmint and access more of similar content in other areas of Linux.

  5. Nick Els says:

    A bit of scare after the whole upgrade finished the installation, prompts and messages I did not understand, left it alone without answering anything and waited for it complete. Restarted my server and working like a charm without any problems. Big relief.

    • Aaron Kili K says:

      @Nick Els

      Could you please share the prompts and messages that you did not understand, they could prove useful to another user who may get similar output in the future.

      • N J Els says:

        Unfortunately, not being terribly IT savvy, it did not occur to me to make a note of the prompts. My server is still working without any problems. Next time, I promise.

        • Aaron Kili K says:

          @N JEls

          Okay, no problem, next time you can take note of the prompts because another user some where might encounter similar prompts and you would be the one to help, by explaining to them that output.

  6. Imani Mwalumbwe says:

    Thank you, the post was very useful. I managed to upgrade server from 14.04 to 16.04 without any problem using this guide.

    • Ravi Saive says:

      @Imani,

      Thanks for finding this post useful and we’re glad that you upgraded your Ubuntu 14.04 to 16.04 without any trouble…

  7. Michael Dutcher says:

    I tried updating my FOG server today, and lost the fog db. I ended up rolling back to a previous checkpoint.

  8. Steven Chow says:

    Which ever route you go for you should backup first. So you could backup, upgrade and if it works great. If it doesn’t do a fresh install and restore your data from backup.

  9. Dennis Gutowski says:

    From what I have read this is a bad bad idea. There are so many differences that upgrading from 1404 to 1604 is bound to be “very buggy” at best. The best option is a clean install, I am afraid.

    • Vitor Correia says:

      “…many differences…”

      Such as, LAMP-wise?

    • Aaron Kili K says:

      You can always choose what you think is best for you, direct upgrade is not always 100% good, sometimes when their is poor Internet connectivity, it may go wrong. I once broke my system when an upgrade failed due to poor Internet connectivity, so you have to decide what you think is safe for you.

Got something to say? Join the discussion.

Your email address will not be published. Required fields are marked *

Join Over 300K+ Linux Users
  1. 202,035
  2. 9,267
  3. 38,621

Are you subscribed?