Because of the problems I was having with my 9.04 test system, I decided to wipe it clean and start over. I made a copy of my kubuntu-8.10 system onto an SSD card, changed fstab and menu.lst so it would boot, and booted into it. Fine, system as it should be.
I know one -should- upgrade without X running, but my "rescue" menu on this system does not include "root shell with network" (on Ubuntu, it does), so I booted into the whole system, and ran, as instructed, "update-manager -d". After a few steps, it proceeded to download several hours worth of stuff. Then it started the upgrade, and crashed about 2 hours into it. Froze the whole system. Had to do a hard poweroff.
Powered back on and booted into the root shell, figuring everything it needed from the net was already there. Ran "apt-get dist-upgrade"; it said I needed to run "dpkg --configure -a". I did that, it ran for a few minutes, and ended with a list of stuff, and a message, "Too many errors. Processing halted" (or something close to that) Ran "apt-get dist-upgrade" again, it ran for a while, then spit out the same message, Too many errors, and quit. (Sorry but I do not know how to paste from the root shell into another system's browser)
OK, so we are basically stuck at this point. I have over 20gb of software in this system, so starting from scratch is not a realistic option. Is there a way I can do the upgrade? I would, if possible, like to save the hours of downloading I have done. The files are all still there in /var/cache/apt/archives.
Can I run the upgrade chrooted from another system, without risking hosing the system I am running from? Any other ideas?
So many questions, but I am stuck at this point.
Further:
I tried to chroot into the broken system, and did an apt-get update.
After running through the usual Hit stuff, got this error message:
Looks like that isn't going to work, at least not that way.
I know one -should- upgrade without X running, but my "rescue" menu on this system does not include "root shell with network" (on Ubuntu, it does), so I booted into the whole system, and ran, as instructed, "update-manager -d". After a few steps, it proceeded to download several hours worth of stuff. Then it started the upgrade, and crashed about 2 hours into it. Froze the whole system. Had to do a hard poweroff.
Powered back on and booted into the root shell, figuring everything it needed from the net was already there. Ran "apt-get dist-upgrade"; it said I needed to run "dpkg --configure -a". I did that, it ran for a few minutes, and ended with a list of stuff, and a message, "Too many errors. Processing halted" (or something close to that) Ran "apt-get dist-upgrade" again, it ran for a while, then spit out the same message, Too many errors, and quit. (Sorry but I do not know how to paste from the root shell into another system's browser)
OK, so we are basically stuck at this point. I have over 20gb of software in this system, so starting from scratch is not a realistic option. Is there a way I can do the upgrade? I would, if possible, like to save the hours of downloading I have done. The files are all still there in /var/cache/apt/archives.
Can I run the upgrade chrooted from another system, without risking hosing the system I am running from? Any other ideas?
So many questions, but I am stuck at this point.
Further:
I tried to chroot into the broken system, and did an apt-get update.
After running through the usual Hit stuff, got this error message:
Code:
Failed to open connection to "system" message bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory E: Problem executing scripts APT::Update::Post-Invoke-Success '/usr/bin/dbus-send --system --dest=org.freedesktop.PackageKit --type=method_call /org/freedesktop/PackageKit org.freedesktop.PackageKit.StateHasChanged string:'cache-update'' E: Sub-process returned an error code
Comment