Ubuntu

Ubuntu 13.04 Boot stuck at the changing Orange & White Dots, how can I get it to work?

Asked by Indian Art

I had done a fresh install of Ubuntu 13.04 a few days ago as a dual boot with Windows. Last night since the PC was behaving a bit sluggish I tried to restart Ubuntu. The bootup reached the GRUB loader and stopped because there was no 10 seconds countdown.

I used an Ubuntu 13.04 LiveUSB and got access of root & recovered my files. I repaired the boot-loader with this LiveUSB.

Now the PC boots Windows & even has the 10 seconds countdown. However, when booting into Ubuntu 13.04 the boot gets stuck at the moving Orange & White Dots. These Orange dots turn to white & white to Orange endlessly. It does not boot further. I need to get to the Desktop to use the computer. Please help. Thanks.

P.S. I read similar questions but do not have any problems with the graphics card, which is an integrated Intel.

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Solved by:
Indian Art
Solved:
Last query:
Last reply:
Revision history for this message
Hamish McIntyre-Bhatty (hamishmb) said : 		#1

First, you could try booting into the recovery mode, and then select "Fix broken Packages". Please let me know if that helps.
Also, please give the make and model of you computer and the output of : lsb_release -a

Thanks

Revision history for this message
Indian Art (goldfish-aol) said : 		#2

Hi Hamish, Thanks for your help, it has solved the issue.

As per your instructions I booted into the recovery mode, and then selected "Repair broken Packages". I did not get a place where I could type: lsb_release -a

However, there was an option to select "system_summary System summary". That is 2 pages of text I wrote down.

I also ran fsck twice. It is a long message which in part said "Inode that were part of a corrupted orphan linked list found". It also stated in part "UNEXPECTED INCONSISTENCY; RUN fsck manually ... status 4" & "mountall: Filesystem has errors:/"

I got an option which I don't completely recollect that said it could repair the errors. I accepted it & it solved the problem.

I am very grateful for your help. Thanks again.

Revision history for this message
Hamish McIntyre-Bhatty (hamishmb) said : 		#3

You're welcome, for future reference, if someone asks for the output of lsb_release -a, open a terminal (CRTL + ALT + T), and run it from there.