1

This is not a simple disk space problem. I've started an upgrade of Ubuntu Studio 16.04 to 18.10, though ran into "no space left on disk" and it terminated with an error. I no longer can launch Thunar or Nemo to free up space as I get a "symbol lookup error" for each. df shows my drive has 0% available. Is there a way for me to recover from this and restart or resume the upgrade?

Update: I tried "sudo apt-get install -f" though that resulted in a "relocation error". I ran "dpkg --configure -a" and that mostly ran smoothly, though there were a number of dependencies that could not be resolved and were left unconfigured. The building of the initial module for 4.4.0-142 lowlatency succeeded. However, when attempting to generate /boot/initrd.img-4.4.0-142-lowlatency, "Errors were encountered while processing" and there was a list of about 30 packages that followed.

"sudo apt-get install -f" no longer runs as apt-get is unrecognized

"dpkg --configure -a" quickly resolves to the errors it ended with before.

"apt dist-upgrade" also fails with relocation error

"do-release-upgrade" exits with "Please install all available updates for your release before upgrading"

In the end, started all over, wiped the partitions and loaded Ubuntu Studio 18.04, and pulled in my backed up files with Back in Time.

Will
  • 101
  • 2
  • 1
    This is not a duplication, as it involves an upgrade operation. Thanks to the link above, I have freed up about 51G of files (using sudo du -aBM -d 1 . | sort -nr | head -20, and then rm'ing large file directories that I already have backed up ) and an unused image using sudo dpkg [image name].

    Can I restart the apt dist-upgrade, or do I need to do something else first?

    – Will Feb 20 '19 at 16:41
  • Ubuntu does not recommend apt dist-upgrade. That's Debian. Ubuntu uses do-release-upgrade. – user535733 Feb 20 '19 at 17:10
  • Should I reboot and try do-release-upgrade, or try it from the command line now? – Will Feb 20 '19 at 17:12
  • Does the file manager work now? – user535733 Feb 20 '19 at 17:13
  • No, still the same error – Will Feb 20 '19 at 17:25
  • 1
    See here: https://askubuntu.com/a/346795/167115 and please report any errors or if this does not work. – mchid Feb 20 '19 at 17:35
  • 1
    @Will I would advise against rebooting as the system might not reboot right now. If you need to press CTRL+ALT+F2 and sign in to open a terminal if you can't open a terminal and then try running: sudo screen -D -r and if that doesn't restart the upgrade then run: sudo apt dist-upgrade and, if you get an error, you may need to run sudo apt -f install and or sudo dpkg --configure -a as well and you may need to run some of these commands more than once to fix things. – mchid Feb 20 '19 at 18:07
  • 2
  • I tried "sudo apt-get install -f" though that resulted in a "relocation error".

    I ran "dpkg --configure -a" and that mostly ran smoothly, though there were a number of dependencies that could not be resolved and were left unconfigured.

    The building of the initial module for 4.4.0-142 lowlatency succeeded.

    However, when attempting to generate /boot/initrd.img-4.4.0-142-lowlatency, "Errors were encountered while processing" and there was a list of about 30 packages that followed.

    – Will Feb 20 '19 at 21:25
  • "sudo apt-get install -f" no longer runs, apt-get is unrecognized

    "dpkg --configure -a" quickly resolves to the errors it ended with before.

    "apt dist-upgrade" also fails with relocation error

    "do-release-upgrade" exits with "Please install all available updates for your release before upgrading"

    Any other avenues I can take?

    – Will Feb 20 '19 at 21:26
  • 1
    @user535733 dist-upgrade and do-release-upgrade are different things entirely. dist-upgrade (or the better named, newer equivalent full-upgrade) updates packages. do-release-upgrade upgrades the system version (e.g. 18.04 to 18.10). You will need to run a dist-upgrade occasionally to keep your system up to date. Please see man apt and man do-release-upgrade. – Seth Feb 21 '19 at 21:15
  • 1
    @Will If you could [edit] your question to include the exact results of the commands you ran that would be helpful. It's hard to find in the comments. Copy the exact text if possible, although a picture will do if you can't copy the text. Thanks! – Seth Feb 21 '19 at 21:18
  • Threw in the towel and rebuilt the machine from the ground up, with the help of the Back in Time backup, transitioning to US 18.04. – Will Feb 21 '19 at 22:28

0 Answers0