Right then folks, I need some help here... had a problem during the upgrade and now my system seems completely borked...
Need to explain a little detail.
I had a fully working 9.04 Kununtu install. Several days ago (a week or so?) I updated it to a 4.3 system using backports - everything was OK, although I lost all my settings etc... Anyway, I finally got it straight, fully updated and stable. No problems. And it looked very nice too - was really looking forward to getting into Karmic with the same eye-candy.
Then I tried to update it to 9.10.
The downloads went fine and the system started to install. I know from the earlier warning at the start of the whole process, that it could be canceled during the downloads but not once the install proper actually started.
Anyway, the install started and then at some point kdesudo crashed on me and threw up an error message. I don't have access to the error message because although I managed to save it as a text file, I couldn't get it off my system. I couldn't mount a usb stick to copy it to (all USB mounts had gone down), I couldn't print it out (CUPS was not responding), and I couldn't send it out by e-mail because I couldn't get either Thunderbird or Firefox to start up. KDE was hanging on and off, plasma was not responding although I could still do a desktop cube spin!!!
Anyway, I couldn't open up a terminal to try and change anything - so I took a massive gamble. Given that my system was up but essentially useless, and I couldn't open a terminal, I rebooted. Plasma unhung long enough for me to press the relevant buttons for a reboot.
The plan was to get it to some sort of command line, and then try again. Gotta be worth a try, right?
Upon rebooting it hung - didn't get to a proper command line. So I'm a little bit stuck.
At the moment, it's currently showing error messages. I'll type in longhand the error that's currently on the screen - please see what you can make of it to give me some guidance.
Pretty bad, huh!! Although, I'm not panicking just yet... I know that all my data is still there but still, it's starting to get a little worrying.
I have not yet tried to CONTROL-D. I am not sure what is the best option here. Should I Ctrl^D out and see if it mounts this time? Is there anything that I should know before I do?
I am pretty sure that if I could get the mounts up and running, then get to a command line etc, then I could rescue the system. I really don't want to go through the whole reinstall - I just wanted to do a simple upgrade this time and reinstall on the next release (LTS?). As a fallback plan, I'm currently downloading a copy of Kubuntu 9.10 CD on the laptop so that I could install from scratch again if I had to... I have a backup of my /home folder anyway, so as a last resort, it can be done - but I'd rather not if it can be rescued...
I need some help here - from someone who knows a lot more about this than I do. How can I get it to a safe command line so that I can try again, and when I do, what are the command line actions I need to take to try it all again.
Many thanks in advance for any help you can give me.
Cheers,
Bag.
Need to explain a little detail.
I had a fully working 9.04 Kununtu install. Several days ago (a week or so?) I updated it to a 4.3 system using backports - everything was OK, although I lost all my settings etc... Anyway, I finally got it straight, fully updated and stable. No problems. And it looked very nice too - was really looking forward to getting into Karmic with the same eye-candy.
Then I tried to update it to 9.10.
The downloads went fine and the system started to install. I know from the earlier warning at the start of the whole process, that it could be canceled during the downloads but not once the install proper actually started.
Anyway, the install started and then at some point kdesudo crashed on me and threw up an error message. I don't have access to the error message because although I managed to save it as a text file, I couldn't get it off my system. I couldn't mount a usb stick to copy it to (all USB mounts had gone down), I couldn't print it out (CUPS was not responding), and I couldn't send it out by e-mail because I couldn't get either Thunderbird or Firefox to start up. KDE was hanging on and off, plasma was not responding although I could still do a desktop cube spin!!!
Anyway, I couldn't open up a terminal to try and change anything - so I took a massive gamble. Given that my system was up but essentially useless, and I couldn't open a terminal, I rebooted. Plasma unhung long enough for me to press the relevant buttons for a reboot.
The plan was to get it to some sort of command line, and then try again. Gotta be worth a try, right?
Upon rebooting it hung - didn't get to a proper command line. So I'm a little bit stuck.
At the moment, it's currently showing error messages. I'll type in longhand the error that's currently on the screen - please see what you can make of it to give me some guidance.
Code:
One or more of the mounts listed in /etc/fstab cannot yet be mounted: (ESC for recovery shell) /: waiting for /dev/disk/bu-uuid/blad-di-blah-di-blah1 /tmp: waiting for /dev/disk/bu-uuid/blad-di-blah-di-blah2 /boot: waiting for /dev/disk/bu-uuid/blad-di-blah-di-blah3 /distros: waiting for /dev/disk/bu-uuid/blad-di-blah-di-blah4 /home: waiting for /dev/disk/bu-uuid/blad-di-blah-di-blah5 /restore: waiting for /dev/disk/bu-uuid/blad-di-blah-di-blah6 swap: waiting for /dev/disk/bu-uuid/blad-di-blah-di-blah7 /common: waiting for /dev/md1 mountall: Cancelled init: mountall main process (879) terminated with status 1 General error mounting filesystems. A maintenance shell will now be started. CONTROL-D will terminate this shell and re-try. root@(none):~#
I have not yet tried to CONTROL-D. I am not sure what is the best option here. Should I Ctrl^D out and see if it mounts this time? Is there anything that I should know before I do?
I am pretty sure that if I could get the mounts up and running, then get to a command line etc, then I could rescue the system. I really don't want to go through the whole reinstall - I just wanted to do a simple upgrade this time and reinstall on the next release (LTS?). As a fallback plan, I'm currently downloading a copy of Kubuntu 9.10 CD on the laptop so that I could install from scratch again if I had to... I have a backup of my /home folder anyway, so as a last resort, it can be done - but I'd rather not if it can be rescued...
I need some help here - from someone who knows a lot more about this than I do. How can I get it to a safe command line so that I can try again, and when I do, what are the command line actions I need to take to try it all again.
Many thanks in advance for any help you can give me.
Cheers,
Bag.
Comment