This is also my advice. I learned this the hard way when wicd on Ubuntu just stopped working, and I got caught in a snafu of needing to be online to reinstall it, and not being able to get online due to it not working.
So my advice is to go live cd, back up what you need to a usb disk, then nuke the system, and put a dedicated /home partition up instead of leaving home on the root partition when you reinstall ubuntu.
I don't remember having that problem when upgrading to maverick though, but I THINK I just did a fresh install vs. using update manager.
That would also be part of my advice as well, is when you upgrade to new versions of ubuntu, do a fresh install from a cd. I have never had a network update for ubuntu versions go right. Only time I did was on a fresh install of gutsy, and updated straight to hardy. Its a PITA with having to reinstall programs, but saves you the frustration when things are broken. And having the dedicated /home partition will make that easier too.
On Apr 15, 2011 1:12 PM, "Tim Hart" <codermsu@gmail.com> wrote:
> Have you tried loading a previous kernel from the grub menu? Ubuntu hides
> the grub menu on boot, by default. You may have to hold or press shift or
> some other key when the grub prompt appears.
>
> This sounds like a kernel issue from a botched upgrade or something. If its
> 10.10, I've seen some grub-> grub2 migration problems that are in this same
> ball park.
>
> In the future, you may want to create a separate partition for your /home
> directory and automate some backups of that home directory to an external
> drive or remote backup service. Then, you can safely nuke your install if
> it ever comes to that.
>
> tim
>
> On Fri, Apr 15, 2011 at 5:17 AM, Robert Citek <robert.citek@gmail.com>wrote:
>
>> What version of Ubuntu are you using? You might also want to run
>> "check disk for defects" at the boot screen.
>>
>> Although, this issue is likely a different issue from the OPs.
>>
>> Regards,
>> - Robert
>>
>> On Fri, Apr 15, 2011 at 12:50 AM, Daniel <dascamel@gmail.com> wrote:
>> > I just got the same error when trying to install on a new, new to us,
>> > computer with my daughter. I downloaded the current stable, burned to cd
>> > then rebooted twice, tried twice, and got the same error. I am
>> > re-downloading to see if it was just a bad download.
>> > Daniel
>> >
>> > On Thu, Apr 14, 2011 at 9:53 PM, Robert Citek <robert.citek@gmail.com>
>> > wrote:
>> >>
>> >> It seems odd that the machine would stop working like that without any
>> >> underlying reason, e.g. a failing disk, an upgrade, deleted file.
>> >>
>> >> The first step you might want to consider it to create a backup of the
>> >> disk. You can do so by booting with an Ubuntu desktop CD, mounting
>> >> the internal drive, and copying the important data (e.g. Chemistry,
>> >> English, etc.) to an external USB drive.
>> >>
>> >> Once you have done that, open a shell terminal and run this collection
>> >> of commands:
>> >>
>> >> sudo true && (
>> >> set -x
>> >> sudo fdisk -l
>> >> blkid -o list
>> >> ls -la /dev/disk/by-uuid/
>> >> ) >& output.txt
>> >>
>> >> Post the contents of the output.txt file here as that will give us
>> >> some clues as what to do next.
>> >>
>> >> Regards,
>> >> - Robert
>> >>
>> >> On Thu, Apr 14, 2011 at 10:17 PM, Craig Ziegel
>> >> <mwtransport@wisperhome.com> wrote:
>> >> > My son uses Ubuntu Studio. He turned his computer on the other day and
>> >> > this is what he got. His system wouldn't boot this system has his
>> >> > Chemistry stuff, English and what ever else. So I can't nuke it and do
>> >> > a fresh install. Can anyone tell me some scripts to run to possibly
>> get
>> >> > this system up and running again. I tried the help option and still
>> the
>> >> > same issue. Please help
>> >>
>> >> -
>> >> To unsubscribe, send email to majordomo@silug.org with
>> >> "unsubscribe silug-discuss" in the body.
>> >
>> >
>> >
>> > --
>> > We cannot solve our problems with the same thinking we used when we
>> created
>> > them. -Einstein
>> >
>>
>>
>> -
>> To unsubscribe, send email to majordomo@silug.org with
>> "unsubscribe silug-discuss" in the body.
>>