[Bug 559582] Re: Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall
** Changed in: apt (Ubuntu) Status: In Progress = Triaged ** Changed in: apt (Ubuntu Lucid) Status: In Progress = Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/559582 Title: Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/559582/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 559582] Re: Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall
Jeez, really? You've abandoned apt-get as a valid upgrade path? That constitutes a major change to ubuntu, if not a complete detachment from Debian. It fundamentally alters the path that Ubuntu sysadmins can plan around. This needs to be VERY clear to people, like a big red box above any discussion of lucid. Sticking it in release notes is not enough. -- Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall https://bugs.launchpad.net/bugs/559582 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 559582] Re: Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall
The do-release-upgrade script is not an option for us (and hence a number of our clients) running high availability clusters - since pacemaker-openais has been removed in favour of pacemaker/cluster-glue, the do-release-upgrade kills the node in the cluster by removing pacemaker-openais, making subsequent upgrades that rely on shared storage brought online via the crm fail painfully. Perhaps this is a bug against pacemaker, however it illustrates a point. The path to achieving a successful upgrade for us and our clients would be: - shift apt sources to lucid - install pacemaker (fail due to this bug, and needs explicit upgrade of libxslt1.1) - dist-upgrade Also, the disabling by do-release-upgrade of custom repositories that we use to override official packages creates all sorts of headaches putting the pieces back together post-upgrade. The 'dist-upgrade' was created for a reason, and whilst I don't necessarily agree with the manor in which sam.watkins proposes it, I do agree with the sentiment that correct dependency chains are critical to a quality distribution, a core-value if you will. So, we hack around this force-installing dependencies, etc... -- Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall https://bugs.launchpad.net/bugs/559582 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 559582] Re: Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall
One of the other workarounds would have been a lot better. This bug bit me with the released version of lucid, and I don't really appreciate having to spend however many hours hacking around it to fix package dependencies. It bit me because instead of doing a dist-upgrade, I just did apt-get install ubuntu-desktop. Please make sure that package dependencies are actually correct and solve the problem, rather than hacks that do not work for everyone. I'm seriously considering switching back to plain old debian for my desktop, because every time I upgrade my ubuntu + kubuntu + xubuntu system something breaks, and it never did break this badly with Debian. -- Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall https://bugs.launchpad.net/bugs/559582 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 559582] Re: Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall
Sam, I am sorry to tell you that for Ubuntu the upgrade process as documented at http://www.ubuntu.com/getubuntu/releasenotes/1004overview#Upgrading%20from%20Ubuntu%209.10%20or%20Ubuntu%208.04%20LTS is to use do-release-upgrade or update-manager, using apt-get install or dist-upgrade is not one of the supported methods. -- Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall https://bugs.launchpad.net/bugs/559582 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 559582] Re: Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall
that's ok for dumb users but not for people like me - so I will switch back to Debian. I'm sorry to leave ubuntu, because I thought it was a really good distro, but if you don't get the package dependencies right, there's not much point trying to make a distro at all. -- Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall https://bugs.launchpad.net/bugs/559582 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 559582] Re: Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall
I feel a bit sad about people which classifies others which read and respect the instructions as dumb. Next time please try to be more constructive and read the actual bug report before adding uninformed comments, if you read Michael's comments you will notice that the problem is related to a bug on apt and not to a wrong dependency being set. Thanks -- Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall https://bugs.launchpad.net/bugs/559582 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 559582] Re: Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall
I've tried do-release-upgrade -d from jaunty lucid it failed and now gives a Segmentation fault for every command I try to use. I have tried to access the system with a rescue disk but via the terminal I get the mountall error when trying to apt-get install -f. I cant seem to do anything. I cant edit/view any log files, nor can I install with apt-get, dkpg - it just sends the Segmentation fault error. Any ideas would be great, thanks Brett -- Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall https://bugs.launchpad.net/bugs/559582 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 559582] Re: Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall
Thanks, just tested on virtualized server at linode with kernel 2.6.32 paravirt, do-release-upgrade -d worked great, Andrea -- Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall https://bugs.launchpad.net/bugs/559582 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 559582] Re: Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall
Thanks Michael, I can confirm on an identical setup, bare metal virtual server image, upgrading from karmic to lucid, do-release-upgrade -d worked perfectly this time. Tom. -- Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall https://bugs.launchpad.net/bugs/559582 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 559582] Re: Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall
I can reproduce the problem and it is caused by a feature in apt that tries to ensure that all important packages gets ocnfigured immediately to minimize the risks if somethng goes wrong (pkg failure, power loss etc) ** Changed in: mountall (Ubuntu) Status: Confirmed = In Progress ** Changed in: mountall (Ubuntu) Importance: Undecided = Medium -- Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall https://bugs.launchpad.net/bugs/559582 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 559582] Re: Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall
** Also affects: mountall (Ubuntu Lucid) Importance: Medium Status: In Progress -- Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall https://bugs.launchpad.net/bugs/559582 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 559582] Re: Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall
** Attachment added: apt debug log of the failure http://launchpadlibrarian.net/44414325/apt-debug.log -- Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall https://bugs.launchpad.net/bugs/559582 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 559582] Re: Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall
So the problem is that libpng12-0 requires libc6 (= 2.11) and at the point apt tries to configure it its not ready yet and the pre-configure code fails. That is a bug in this code. I would not want to change this code at this point of the release though but instead add a workaround to help apt to get it right. A fix is to add a stricter libc6 dependency (libc6 (= 2.11)) to any of the packages before mountall, i.e.: ... Conf libnih1 (1.0.1-1 Ubuntu:10.04/lucid) Conf libnih-dbus1 (1.0.1-1 Ubuntu:10.04/lucid) Conf ifupdown (0.6.8ubuntu29 Ubuntu:10.04/lucid) Conf upstart (0.6.5-6 Ubuntu:10.04/lucid) Inst libc6-dev [2.10.1-0ubuntu16] (2.11.1-0ubuntu5 Ubuntu:10.04/lucid) [] Inst libc-dev-bin [2.10.1-0ubuntu16] (2.11.1-0ubuntu5 Ubuntu:10.04/lucid) [] Inst libdrm2 (2.4.18-1ubuntu3 Ubuntu:10.04/lucid) [] Inst libdrm-intel1 (2.4.18-1ubuntu3 Ubuntu:10.04/lucid) [] Inst libdrm-nouveau1 (2.4.18-1ubuntu3 Ubuntu:10.04/lucid) [] Inst libdrm-radeon1 (2.4.18-1ubuntu3 Ubuntu:10.04/lucid) [] Inst libpng12-0 (1.2.42-1ubuntu2 Ubuntu:10.04/lucid) [] Inst initramfs-tools-bin (0.92bubuntu73 Ubuntu:10.04/lucid) [] Inst initramfs-tools [0.92bubuntu53] (0.92bubuntu73 Ubuntu:10.04/lucid) [initramfs-tools on mountall] [] Inst udev [147~-6.1] (151-10 Ubuntu:10.04/lucid) [initramfs-tools on mountall] [] Inst plymouth (0.8.2-1 Ubuntu:10.04/lucid) [initramfs-tools on mountall] [] Inst libplymouth2 (0.8.2-1 Ubuntu:10.04/lucid) [initramfs-tools on mountall] [libplymouth2 on mountall] [] -- Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall https://bugs.launchpad.net/bugs/559582 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 559582] Re: Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall
A alternative workaround is to build libpng12-0 so that it works with libc6 2.10, it appears that the only used symbol from 2.11 is __longjmp_chk -- Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall https://bugs.launchpad.net/bugs/559582 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 559582] Re: Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall
Next option is to try to make mountall not part of the immediate- configure set or to run with -o Apt::Immediate-Configure=false -- Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall https://bugs.launchpad.net/bugs/559582 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 559582] Re: Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall
** Package changed: mountall (Ubuntu Lucid) = apt (Ubuntu Lucid) ** Also affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Changed in: initramfs-tools (Ubuntu Lucid) Status: New = Fix Committed -- Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall https://bugs.launchpad.net/bugs/559582 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 559582] Re: Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall
Probably too late to debug the apt issue for lucid, but with the files it should be possible to fix early in maverick. -- Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall https://bugs.launchpad.net/bugs/559582 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 559582] Re: Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall
To reproduce, unpack in a chroot and run: # apt-get dist-upgrade or # apt-get dist-upgrade --simulate ** Attachment added: tarball of the required files to reproduce the failure http://launchpadlibrarian.net/44421820/apt-configure-error-state.tar.gz -- Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall https://bugs.launchpad.net/bugs/559582 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 559582] Re: Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall
This bug was fixed in the package initramfs-tools - 0.92bubuntu74 --- initramfs-tools (0.92bubuntu74) lucid; urgency=low * debian/control, debian/rules: - force libc6 dependency to = 2.11 (and libc6.1 on ia64, the libc6 has a different packages name on this architecture) to workaround a bug in libapt when it orders the install for essential packages (LP: #559582) This can be removed after lucid -- Michael Vogt michael.v...@ubuntu.com Fri, 16 Apr 2010 13:13:50 +0200 ** Changed in: initramfs-tools (Ubuntu Lucid) Status: Fix Committed = Fix Released -- Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall https://bugs.launchpad.net/bugs/559582 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 559582] Re: Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall
** Branch linked: lp:ubuntu/initramfs-tools -- Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall https://bugs.launchpad.net/bugs/559582 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 559582] Re: Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall
Added /var/log/dist-upgrade/system_state.tar.gz from an affected system as per request of mvo from #ubuntu+1 =) ** Attachment added: system_state.tar.gz http://launchpadlibrarian.net/44273097/system_state.tar.gz -- Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall https://bugs.launchpad.net/bugs/559582 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 559582] Re: Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall
Me too. Upgrade from karmic-lucid on bare metal. $ sudo do-release-upgrade -d Checking for a new ubuntu release Done Upgrade tool signature Done Upgrade tool Done downloading extracting 'lucid.tar.gz' authenticate 'lucid.tar.gz' against 'lucid.tar.gz.gpg' tar: Removing leading `/' from member names tar: /etc/apt/preferences: Cannot stat: No such file or directory tar: Exiting with failure status due to previous errors Reading cache Checking package manager Reading package lists: Done Reading state information: Done Reading state information: Done Reading state information: Done Done downloading Reading package lists: Done Reading state information: Done Reading state information: Done Reading state information: Done Updating repository information WARNING: Failed to read mirror file No valid mirror found While scanning your repository information no mirror entry for the upgrade was found. This can happen if you run a internal mirror or if the mirror information is out of date. Do you want to rewrite your 'sources.list' file anyway? If you choose 'Yes' here it will update all 'karmic' to 'lucid' entries. If you select 'No' the upgrade will cancel. Continue [yN] y WARNING: Failed to read mirror file Done downloading Checking package manager Reading package lists: Donelucid-security/multiverse Packages: 98 Reading state information: Done Reading state information: Done Reading state information: Done Calculating the changes Calculating the changes Support for some applications ended Canonical Ltd. no longer provides support for the following software packages. You can still get support from the community. Demoted: libcompress-bzip2-perl, netcat-traditional Do you want to start the upgrade? 3 packages are going to be removed. 41 new packages are going to be installed. 346 packages are going to be upgraded. Fetching and installing the upgrade can take several hours. Once the download has finished, the process cannot be cancelled. Continue [yN] Details [d]y Fetching Done downloading Upgrading Done downloading Exception during pm.DoInstall(): E:Internal Error, Could not perform immediate configuration (2) on mountall Could not install the upgrades Error during commit 'E:Internal Error, Could not perform immediate configuration (2) on mountall' Restoring original system state Restoring original system state Aborting Reading package lists: Donekarmic-security/multiverse Packages: 98 Reading state information: Done Reading state information: Done Reading state information: Done -- Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall https://bugs.launchpad.net/bugs/559582 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 559582] Re: Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall
i too am affected by this. for my setup its not a virtualized setup but on a physical machine. ** Changed in: mountall (Ubuntu) Status: New = Confirmed -- Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall https://bugs.launchpad.net/bugs/559582 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 559582] Re: Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall
Likewise, this affects me too, karmic-lucid beta on a virtual machine, /etc/fstab: proc/proc procdefaults0 0 /dev/xvda / ext3noatime,errors=remount-ro 0 1 /dev/xvdb noneswapsw 0 0 # mountall swapon: /dev/xvdb: swapon failed: Device or resource busy mountall: swapon /dev/xvdb [11712] terminated with status 255 mountall: Problem activating swap: /dev/xvdb # do-release-upgrade -d . . Upgrading Done downloading Exception during pm.DoInstall(): E:Internal Error, Could not perform immediate configuration (2) on mountall Could not install the upgrades Error during commit 'E:Internal Error, Could not perform immediate configuration (2) on mountall' Restoring original system state -- Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall https://bugs.launchpad.net/bugs/559582 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 559582] Re: Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall
I had this problem too, with Ubuntu Karmic server. I was able to upgrade the desktop version painlessly (with update manager). -- Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall https://bugs.launchpad.net/bugs/559582 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 559582] Re: Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall
I've also upgraded 3 desktops with the update manager to lucid beta with no problems. I have tried downgrading to the mountall karmic 1.0 package with: sudo apt-get install mountall=1.0 and it downgraded fine, however I still get the same error from do-release-upgrade -d -- Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall https://bugs.launchpad.net/bugs/559582 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 559582] Re: Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall
anyone have any ideas for a work around? On Mon, Apr 12, 2010 at 3:58 PM, Tom Worley t...@worley.co.uk wrote: I've also upgraded 3 desktops with the update manager to lucid beta with no problems. I have tried downgrading to the mountall karmic 1.0 package with: sudo apt-get install mountall=1.0 and it downgraded fine, however I still get the same error from do-release-upgrade -d -- Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall https://bugs.launchpad.net/bugs/559582 You received this bug notification because you are a direct subscriber of the bug. -- Jonathan Aquilina -- Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall https://bugs.launchpad.net/bugs/559582 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 559582] Re: Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall
I'm considering replacing karmic with lucid in /etc/apt/sources.list and then apt-get dist-upgrade Is there any more than that that do-release-upgrade actually does? -- Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall https://bugs.launchpad.net/bugs/559582 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 559582] Re: Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall
im not 100% sure. but the error is with mount all i did a query to the bot on irc and thats for filesystem mounting. ill try and do some more digging but i would be apprehensive if that is buggy to upgrade. On Mon, Apr 12, 2010 at 4:29 PM, Tom Worley t...@worley.co.uk wrote: I'm considering replacing karmic with lucid in /etc/apt/sources.list and then apt-get dist-upgrade Is there any more than that that do-release-upgrade actually does? -- Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall https://bugs.launchpad.net/bugs/559582 You received this bug notification because you are a direct subscriber of the bug. -- Jonathan Aquilina -- Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall https://bugs.launchpad.net/bugs/559582 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 559582] Re: Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall
I've managed to around this by doing the following: sudo sed -i 's/karmic/lucid/g' /etc/apt/sources.list sudo apt-get update wget http://mirrors.kernel.org/ubuntu/pool/main/m/mountall/mountall_2.11_amd64.deb sudo dpkg --force-all -i /var/cache/apt/archives/mountall_2.11_amd64.deb sudo apt-get -f install sudo apt-get dist-upgrade Which manually changes to lucid, gets the 64bit version of the latest lucid mountall (change to the i386 if not running 64 bit), forces mountall to install without the dependancies, then fixes the dependancies and does a dist-upgrade to upgrade everything else. On a bare-metal karmic install this worked fine, and the server has returned after remote reboot. -- Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall https://bugs.launchpad.net/bugs/559582 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 559582] Re: Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall
will try this out to confirm On Mon, Apr 12, 2010 at 5:04 PM, Tom Worley t...@worley.co.uk wrote: I've managed to around this by doing the following: sudo sed -i 's/karmic/lucid/g' /etc/apt/sources.list sudo apt-get update wget http://mirrors.kernel.org/ubuntu/pool/main/m/mountall/mountall_2.11_amd64.deb sudo dpkg --force-all -i /var/cache/apt/archives/mountall_2.11_amd64.deb sudo apt-get -f install sudo apt-get dist-upgrade Which manually changes to lucid, gets the 64bit version of the latest lucid mountall (change to the i386 if not running 64 bit), forces mountall to install without the dependancies, then fixes the dependancies and does a dist-upgrade to upgrade everything else. On a bare-metal karmic install this worked fine, and the server has returned after remote reboot. -- Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall https://bugs.launchpad.net/bugs/559582 You received this bug notification because you are a direct subscriber of the bug. -- Jonathan Aquilina -- Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall https://bugs.launchpad.net/bugs/559582 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 559582] Re: Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall
tom can confirm that this method works :) on a physical machine if someone would confirm for those having an issue with upgrading virtual machines. On Mon, Apr 12, 2010 at 5:17 PM, Jonathan Aquilina eagles051...@gmail.comwrote: will try this out to confirm On Mon, Apr 12, 2010 at 5:04 PM, Tom Worley t...@worley.co.uk wrote: I've managed to around this by doing the following: sudo sed -i 's/karmic/lucid/g' /etc/apt/sources.list sudo apt-get update wget http://mirrors.kernel.org/ubuntu/pool/main/m/mountall/mountall_2.11_amd64.deb sudo dpkg --force-all -i /var/cache/apt/archives/mountall_2.11_amd64.deb sudo apt-get -f install sudo apt-get dist-upgrade Which manually changes to lucid, gets the 64bit version of the latest lucid mountall (change to the i386 if not running 64 bit), forces mountall to install without the dependancies, then fixes the dependancies and does a dist-upgrade to upgrade everything else. On a bare-metal karmic install this worked fine, and the server has returned after remote reboot. -- Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall https://bugs.launchpad.net/bugs/559582 You received this bug notification because you are a direct subscriber of the bug. -- Jonathan Aquilina -- Jonathan Aquilina -- Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall https://bugs.launchpad.net/bugs/559582 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 559582] Re: Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall
The above workaround was on a linode virtual server and worked first time. There's a slight amendment to the above instructions, the dpkg line should read: sudo dpkg --force-all -i mountall_2.11_amd64.deb I used the local copy that I got dist-upgrade to download while doing testing -- Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall https://bugs.launchpad.net/bugs/559582 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 559582] Re: Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall
for me your original way worked. On Mon, Apr 12, 2010 at 6:28 PM, Tom Worley t...@worley.co.uk wrote: The above workaround was on a linode virtual server and worked first time. There's a slight amendment to the above instructions, the dpkg line should read: sudo dpkg --force-all -i mountall_2.11_amd64.deb I used the local copy that I got dist-upgrade to download while doing testing -- Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall https://bugs.launchpad.net/bugs/559582 You received this bug notification because you are a direct subscriber of the bug. -- Jonathan Aquilina -- Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall https://bugs.launchpad.net/bugs/559582 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 559582] Re: Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall
Tom's workaround worked for me too - thanks. Bare metal server. -- Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall https://bugs.launchpad.net/bugs/559582 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 559582] Re: Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall
Manually running sudo mountall gives: swapon: /dev/vda2: swapon failed: Device or resource busy mountall: swapon /dev/vda2 [11295] terminated with status 255 mountall: Problem activating swap: /dev/vda2 -- Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall https://bugs.launchpad.net/bugs/559582 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 559582] Re: Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall
Using do-release-upgrade gives the same error (just takes much longer;-) -- Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall https://bugs.launchpad.net/bugs/559582 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 559582] Re: Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall
Using 'swapoff /dev/vda2' allows me to run mountall without an error exactly once. On a further call, it spits out the above error again. It looks like the swap disk doesn't get added to /etc/mtab... -- Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall https://bugs.launchpad.net/bugs/559582 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 559582] Re: Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall
Doing swapoff /dev/vda2 doesn't help with upgrading, same error... -- Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall https://bugs.launchpad.net/bugs/559582 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 559582] Re: Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall
Disabling the swap in /etc/fstab does fix the error on multiple calls to mountall, but upgrading still fails... -- Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall https://bugs.launchpad.net/bugs/559582 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 559582] Re: Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall
Installing mountall 2.10 using dpkg -i gives dependency errors. A succinct apt-get -f install gives the following error: E: Internal Error, Could not perform immediate configuration (2) on plymouth -- Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall https://bugs.launchpad.net/bugs/559582 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 559582] Re: Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall
I somehow did get it to upgrade now:-) From my mind: * Fixed the manual installation of mountall 2.10 by re-installing 1.0 * I did run apt-get upgrade which did seem to work: sudo apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done The following packages have been kept back: apt-utils autofs bash bind9-host busybox-initramfs coreutils dash debianutils diff dpkg e2fslibs e2fsprogs grub-common initramfs-tools iproute libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap libc-bin libc6 libdbi-perl libdigest-sha1-perl libedit2 libgc1c2 libpam-modules libreadline5 libreadline6 libsasl2-2 libsasl2-modules libss2 libsub-name-perl linux-image-virtual mawk mountall munin-node nano nscd ntp openssh-client openssh-server perl perl-base perl-modules php5-cli php5-common puppet python python-minimal python2.6 python2.6-minimal ubuntu-minimal udev upstart util-linux vim-common vim-tiny The following packages will be upgraded: acpid adduser apache2-mpm-worker apache2-utils apache2.2-bin apache2.2-common apt aptitude augeas-lenses base-files base-passwd bash-completion bsd-mailx bsdutils bzip2 console-setup console-terminus cpio cron debconf debconf-i18n dhcp3-client dhcp3-common dmidecode dmsetup eject facter file findutils gawk gcc-4.4-base geoip-database git-core gnupg gpgv grep grub gzip hostname ifupdown initscripts insserv iputils-ping irb1.8 iso-codes javascript-common kbd klibc-utils laptop-detect less libacl1 libapr1 libatm1 libattr1 libaugeas-ruby1.8 libaugeas0 libblkid1 libbsd0 libbz2-1.0 libcap2 libclass-accessor-perl libcomerr2 libcurl3-gnutls libcwidget3 libdb4.7 libdbd-mysql-perl libdbus-1-3 libdevmapper1.02.1 libept0 libevent-1.4-2 libexpat1 libfreetype6 libfribidi0 libgcc1 libgcrypt11 libgdbm3 libgeoip1 libglib2.0-0 libglib2.0-data libgnutls26 libgpg-error0 libgpm2 libgssapi-krb5-2 libgssglue1 libidn11 libjs-jquery libjs-prototype libk5crypto3 libkeyutils1 libklibc libkrb5-3 libkrb5support0 libldap-2.4-2 liblocale-gettext-perl liblockfile1 libmagic1 libmdbtools libmysql-ruby libmysql-ruby1.8 libmysqlclient16 libncurses-ruby1.8 libncurses5 libncursesw5 libnet-snmp-perl libnewt0.52 libnfsidmap2 libnss-ldapd libopenssl-ruby1.8 libpam-ldap libpam-runtime libpam0g libpci3 libpcre3 libpopt0 librack-ruby librack-ruby1.8 libreadline-ruby1.8 librecode0 librpcsecgss3 libruby1.8 libselinux1 libsepol1 libshadow-ruby1.8 libsigc++-2.0-0c2a libslang2 libsqlite3-0 libsqlite3-ruby libsqlite3-ruby1.8 libssl0.9.8 libstdc++6 libtasn1-3 libtext-charwidth-perl libtext-iconv-perl libtimedate-perl libudev0 libusb-0.1-4 libuuid1 libwrap0 libx11-6 libx11-data libxapian15 libxau6 libxcb1 libxdmcp6 libxext6 libxml2 libxmuu1 linux-firmware locales lockfile-progs login logrotate lsb-base lsb-release lzma make makedev mdbtools mime-support module-init-tools mount mysql-client-5.1 mysql-common mysql-server mysql-server-5.1 mysql-server-core-5.1 ncurses-base ncurses-bin net-tools netbase nfs-common nslcd ntpdate nullmailer openssl os-prober passwd patch pciutils portmap procps psmisc python-apt python-central python-gnupginterface python-support rdoc1.8 readline-common recode resolvconf rsync rsyslog ruby1.8 sed shared-mime-info sqlite3 sudo sysv-rc sysvinit-utils tar tasksel tasksel-data tcpd tzdata ubuntu-keyring ucf unattended-upgrades unzip update-manager-core w3m wget whiptail x11-common xauth xkb-data xml-core zlib1g 217 upgraded, 0 newly installed, 0 to remove and 56 not upgraded. Need to get 0B/86.0MB of archives. * Did install redmine (the original goal of this upgrade;-) * Did install man which triggered an upgrade of mountall and others: sudo apt-get install man Reading package lists... Done Building dependency tree Reading state information... Done Note, selecting man-db instead of man The following packages were automatically installed and are no longer required: libmysqlclient15off x11-common Use 'apt-get autoremove' to remove them.
