PDA

View Full Version : can't boot into ubuntu



libihero
November 29th, 2010, 05:14 PM
my battery was running out, and my computer was trying to hibernate, but i think it powered off before it was done with the process. now i can't boot into my ubuntu partition. i attached a picture of the boot (the first two lines normally come up during boot)

karthick87
November 29th, 2010, 05:53 PM
Are u facing this problem after updating your kernel?

libihero
November 29th, 2010, 06:57 PM
no, it was working fine until it went into hibernate

karthick87
November 29th, 2010, 07:37 PM
I think your boot partition is not getting mounted.

philinux
November 29th, 2010, 07:41 PM
my battery was running out, and my computer was trying to hibernate, but i think it powered off before it was done with the process. now i can't boot into my ubuntu partition. i attached a picture of the boot (the first two lines normally come up during boot)

Might be worth fsck'ing your partition from recovery mode or if that dosn't work then fsck from the livecd.

libihero
November 29th, 2010, 07:47 PM
i dunno how to fsck, or what that even means :(

karthick87
November 29th, 2010, 08:15 PM
FSCK - File System Check.Boot your system using live cd and then open terminal and type
fsck.<filesystem> /dev/<device>
Note:
Before running fsck unmount your partition first.

libihero
November 30th, 2010, 09:41 PM
what should i put into <filesystem>?
i had already looked up previous threads and i put this into the terminal


sudo e2fsck -fvy /dev/sda4

it fixed the problem, but when i restart later it gives me the same error screen

karthick87
November 30th, 2010, 10:25 PM
Can you post the output of df -hT command.


df -hT

libihero
November 30th, 2010, 11:51 PM
wow, right now it wont even let me load a live cd anymore. i get an error:

"cant open dev/sda no medium found"

and i've tried multiple live cds...

libihero
December 1st, 2010, 12:23 AM
finally got it to boot, this is the output


Filesystem Type Size Used Avail Use% Mounted on
aufs aufs 943M 24M 919M 3% /
none devtmpfs 937M 296K 937M 1% /dev
/dev/sr0 iso9660 694M 694M 0 100% /cdrom
/dev/loop0
squashfs 661M 661M 0 100% /rofs
none tmpfs 943M 116K 943M 1% /dev/shm
tmpfs tmpfs 943M 12K 943M 1% /tmp
none tmpfs 943M 88K 943M 1% /var/run
none tmpfs 943M 0 943M 0% /var/lock

libihero
December 1st, 2010, 01:05 AM
ok i found out what filesystem is lol lets hope it works...

libihero
December 3rd, 2010, 03:30 AM
so it happened again even after putting

fsck.ext4 /dev/sda4

doing this did fix it temporarily, but it keeps happening. does it have anything to do with the kernel? i'm using the newest stable one (2.6.36), not the standard ubuntu one

libihero
December 3rd, 2010, 10:37 PM
so in my eternal cycle of fsck'ing from a live cd and trying to boot, i hit a roadblock. now i cant boot, mount my hard drive, or fsck. when i try to fsck i get this error:


fsck.ext4: Device or resource busy while trying to open /dev/sda4
Filesystem mounted or opened exclusively by another program?

and when i try to mount i get this:


DBus error org.gtk.Private.RemoteVolumeMonitor.Failed: An operation is already pending

normally at this point, i would just do a fresh install, but now i cant access my files :(

please help!!!!

libihero
December 4th, 2010, 04:11 AM
solved this with some research. i downloaded the slax distro and made a live cd out of it and fsck'd from there. apparently my file system was broken, but for some reason the live cd wasnt detecting the breaks at all. slax was able to, and now things r dandy :)
thanks for all your guys's help!

libihero
March 1st, 2011, 12:35 AM
ok this happens A LOT to me lately. for both 10.10 and i went down to 10.04 and it still happens.... is there a reason its been happening??? i can fix it with a slax cd, but then later it'll get messed up again and i repeatedly have to bust out the slax cd to fix it.

alegomaster
March 1st, 2011, 12:40 AM
Just reformat the hard drive and reinstall the OS.

libihero
March 1st, 2011, 06:35 AM
i've done that like three times...

libihero
March 4th, 2011, 09:39 PM
bump...