Ubuntu 10.10 Suddenly Won't Boot

I've had the similar problem with 10.04 the last couple of months.
Might have to wait until they come out with a new kernel. They haven't issued an updated one for awhile.

I just reboot a few times and it boots up properly after a while. It's kinda like a crap shoot. You win some, you lose some.

So far I've rebooted about 35 times but no luck.

hmmm....try re-installing grub. that didn't work for me, but you might have better luck.

https://help.ubuntu.com/community/Grub2#Reinstalling%20from%20LiveCD could work.

Thanks for the suggestion, delance...

I tried following those instructions to reinstall GRUB2 and I was able to boot into the Live CD, however, there appears to be a problem when trying to mount the Linux partition (listed as /dev/sdb1 when I run sudo fdisk -l in a terminal screen)

When I try to mount it (using sudo mount /dev/sdb1 /mnt) I press enter but then the cursor below that line just sits there and blinks and it doesn't appear to do anything...

I can see the drive listed in Places as "988GB Filesystem"... I tried to mount it by clicking on that (and then right clicking and clicking "mount") but I am getting the following error message...

Error: Unable to mount 988GB filesystem
DBus error org.gtk.Private.RemoteVolumeMonitor.Failed: An operation is already pending

I also tried running the sudo fsck /dev/sdb1 command in the terminal screen but am getting the following error:
fsck.ext4: Device or resource busy while trying to open /dev/sdb1
Filesystem mounted or opened exclusively by another program?

Am I correct as in the sample instructions in that link attempting to mount the Linux partition? Or should I be trying to mount and reinstall it to the partition that Windows Vista is currently loaded onto (showing an asterisk under "boot" for the windows partition when I run fdisk -l)??

Thanks

"When I try to mount it (using sudo mount /dev/sdb1 /mnt) I press enter but then the cursor below that line just sits there and blinks and it doesn't appear to do anything..." => you have to enter your password
"sudo fsck /dev/sdb1" => You will have to launch from Ubuntu CD.
It's late in France. I will have a look tomorrow evening.

I have already launched from the Ubuntu CD...at which point do I enter my password? It doesn't appear to prompt me for it at any point...

In live CD, you don't have to enter password for commands requesting to be administrator.
"Device or resource busy while trying to open /dev/sdb1" from Live CD means your partition is marked as being locked by another program or was hibernated.
Did you hibernate the system ? Was the screen saver programed to hibernate the PC ?
If partition is locked, it means you can't mount it, as it is presumed inconsistent (some writing operations are presumed pending in RAM or in swap partition).
This issue occurred many times, but I have yet any solution.
Try other forums as ubuntuforums.org.

Ok...yes, my system had gone into hibernation mode just before the problem started, so it looks like that is likely the issue and the reason I can't mount it...

I will continue to look at other forums I guess, I did find several people on other forums who were getting the same error as me and it looks like several of them fixed the problem by running the command:

e2fsck -f -y -v /dev/sdb1

However, it's not working for me since I can't access the partition (when I try that command I am getting the same "Device or resource busy while trying to open /dev/sdb1" error message...)

I guess I will keep looking for a solution!

I have solved the issue after reviewing unbuntuforums.org (thank you delance for the suggestion)...

Many people there had the same issue and resolved it with the "e2fsck -f -y -v /dev/sdxx" command.

As with my issue where it still said the partition was being used someone else had that same problem and the way they worked around it was to download the SLAX Linux dist. (www.slax.org), burn it to a CD, boot from that LiveCD, and run the above command from a terminal window...

As soon as I ran the e2fsck command and rebooted the issue was resolved and my Ubuntu 10.10 is working just fine now.

If anyone else has the same problem they should try that as well.

Thank you for reporting solution.

mike can you give link from ubuntuforums.org
cause i have problem like yours

thanks

sorry my bad english