Public bug reported: Binary package hint: update-manager
This is an attempted upgrade of Kubuntu from Dapper to Edgy on an AMD64 system with NVIDIA drivers installed. The upgrade was launched using the cdromupgrade script on the DVD. Error 1: # /media/cdrom/cdromupgrade su: /media/cdrom0/cdromupgrade: Permission denied So I put a trace on the script to see where the failure was # sh -x /media/cdrom/cdromupgrade + CODENAME=edgy + UPGRADER_DIR=dists/stable/main/dist-upgrader/binary-all/ + cddirname=/media/cdrom0 + fullpath=/media/cdrom0/dists/stable/main/dist-upgrader/binary-all/ + '[' '!' -f /media/cdrom0/dists/stable/main/dist-upgrader/binary-all//edgy.tar.gz ']' ++ mktemp -d + TMPDIR=/tmp/tmp.TcCxlE + cd /tmp/tmp.TcCxlE + tar xzf /media/cdrom0/dists/stable/main/dist-upgrader/binary-all//edgy.tar.gz + '[' '!' -x /tmp/tmp.TcCxlE/edgy ']' + gksu -- /tmp/tmp.TcCxlE/edgy --cdrom /media/cdrom0 /media/cdrom0/cdromupgrade: line 33: gksu: command not found Installed gksu and tried again: # /media/cdrom/cdromupgrade su: /media/cdrom0/cdromupgrade: Permission denied I then ran it with sh -x /media/cdrom/cdromupgrade and unaccountably it then ran on apparently OK. Why this won't run without explicit sh -x before it is a mystery to me. the sh binary is in the default location (/bin/sh) which is at the head of the script. ------------------------------------------------------------------------------------------------------- Error 2: Failed to install evms: The upgrade aborts now. Please report this bug against the 'update-manager' package and include the files in /var/log/dist-upgrade/ in the bugreport. subprocess post-installation script returned error exit status 1 (I assume I will be able to attach the file later) >From the term.log file: Setting up evms (2.5.5-15) ... Installing new version of config file /etc/evms.conf ... update-initramfs: Generating /boot/initrd.img-2.6.17.11 Cannot find /lib/modules/2.6.17.11 dpkg: error processing evms (--configure): subprocess post-installation script returned error exit status 1 ------------------------------------------------------------------------------------------------------- Error 3: initramfs-tools install failed The upgrade aborts now. Please report this bug against the 'update-manager' package and include the files in /var/log/dist-upgrade/ in the bugreport. subprocess post-installation script returned error exit status 1 >From the term.log: Setting up initramfs-tools (0.69ubuntu20) ... update-initramfs: Generating /boot/initrd.img-2.6.17.11 Cannot find /lib/modules/2.6.17.11 dpkg: error processing initramfs-tools (--configure): subprocess post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of volumeid: volumeid depends on initramfs-tools (>= 0.40ubuntu30); however: Package initramfs-tools is not configured yet. dpkg: error processing volumeid (--configure): dependency problems - leaving unconfigured ------------------------------------------------------------------------------------------------------ >From here on it went downhill fast, especially with: dpkg: dependency problems prevent configuration of volumeid: volumeid depends on initramfs-tools (>= 0.40ubuntu30); however: Package initramfs-tools is not configured yet. dpkg: error processing volumeid (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-image-2.6.17-10-generic: linux-image-2.6.17-10-generic depends on initramfs-tools (>= 0.36ubuntu6); however: Package initramfs-tools is not configured yet. dpkg: error processing linux-image-2.6.17-10-generic (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-restricted-modules-2.6.17-10-generic: linux-restricted-modules-2.6.17-10-generic depends on linux-image-2.6.17-10-generic; however: Package linux-image-2.6.17-10-generic is not configured yet. dpkg: error processing linux-restricted-modules-2.6.17-10-generic (--configure): dependency problems - leaving unconfigured ...and so many pop-up failure messages after this, that I couldn't keep a list (despite claiming it was aborting, the installation kept going to the bitter end.) End result, not surprisingly was a system that wouldn't boot the new kernel it had attempted to install and in such a mess that even by selecting the old kernel at the Grub menu the system was unusable. During the boot process, it displayed what looked like some sort of test screen, which had a progress bar in the middle. However it never got to a point where anything could be done. Fortunately I have good backups, so I've been able to restore a working system, but this upgrade has been a disaster for me. I had previously tried a network upgrade using the instructions on the Kubuntu page (http://kubuntu.org/announcements/6.10-release.php) which left the machine in a similar mess and I've tried installing from the DVD on a wiped filesystem, with no more success. ** Affects: update-manager (Ubuntu) Importance: Undecided Status: Unconfirmed -- Multiple failures trying to upgrade Dapper-Edgy https://launchpad.net/bugs/70736 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
