Ubuntu-12.04 [SOLVED]: VM Player Ubuntu upgrade from 12.04 to 16.04 failed – entering into emergency mode

Ubuntu-12.04 [SOLVED]: VM Player Ubuntu upgrade from 12.04 to 16.04 failed – entering into emergency mode

Home Forums Ubuntu 12.04 Ubuntu-12.04 [SOLVED]: VM Player Ubuntu upgrade from 12.04 to 16.04 failed – entering into emergency mode

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #17534

    Anonymous

    QuestionQuestion

    I’m upgrading Ubuntu from 12.04 to 16.04 in VM Ware Player version 5.0.4.

    When using Ubuntu 12.04, i increased Hard disk size from 150GB to 300GB manually in VM player by mistake.(VM ware located in D:/ drive, which is 232GB in size).

    However, I couldn’t see 300GB replicated in Ubuntu(was not knowing that i should use Gparted to increase partition from 150GB to 300GB).

    After installation Ubuntu is entering into Emergency mode as shown:
    Emergency mode

    Someone, please point out where am i going wrong?

    1). I cannot install successfully because hard disk wrong increment to 300GB out of 232GB?

    2). If I remove old 12.04 files and install 16.04, is it still possible to access data from 12.04’s DSU.vmdk file?

    3). Is it possible to reduce 300GB to 150GB using Gparted in VMWare player?
    (150GB is still unallocated)

    #17535

    Anonymous

    Accepted AnswerAnswer

    If I get you correctly your trying to upgrade Ubuntu from 12.04 to 16.04 in a virtual machine. I don’t think that’s possible in a Virtual device, only real installs can get upgraded. You have to store those files using a folder in you host system, then install the new version using a newly downloaded Ubuntu 16.04.

    Source: https://askubuntu.com/questions/921112/vm-player-ubuntu-upgrade-from-12-04-to-16-04-failed-entering-into-emergency-mo
    Author: George
    Creative Commons License
    This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.