Ask Ubuntu is a question and answer site for Ubuntu users and developers. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm running Ubuntu 9.10 desktop edition. Suddenly today /home became corrupted and I was prompted to run fsck manually. I ran fsck -y /home and rebooted the system. The system booted but I got no GUI interface (GNOME session) but a black screen with a user prompt instead. Any tricks here to start my system normally? Any help is greatly appreciated.


The error were similar to the the following(may be with some mistakes as I had to type it manually):

machine1 login: root


at login Sun Jan 16 15:30:46 IST 2011 on tty1

EXT3-fs error (devie sda1): ext3_lookup :deleted inode referenced

aborting journal on device sda1

Remounting filesystem read-only

root@machine1:~# startx
ktemp: failed to create file via template `/tmp/serverauth.xxxxxxxxxxx: Read-only file
/usr/bin/startx: line 157: cannot create temp file for here-document: Read-only file
xauth: error in locking authority file /root/.Xauthority
/usr/bin/startx: line 173: cannnot create temp file for here-document: Read-only file
xauth: error in locking authority file /root/.Xauthority
/usr/bin/startx: line 173: cannnot create temp file for here-document: Read-only file
X: cannot stat /tmp/.x11-unix (No such file or directory), aborting giving up.
xinit: No such file or directory (errno 2): unable to connect to xserver
xinit: No such process (errno 3): Server error
xauth: error in locking authority file /root/.Xauthority
share|improve this question
In the prompt,type the following and see if it helps you sudo dpkg-reconfigure xserver-xorg – karthick87 Jan 16 '11 at 10:47
What happens when you press Ctrl+Alt+F7? – dv3500ea Jan 16 '11 at 11:09
I'll try this two options! – user3215 Jan 16 '11 at 13:47
I was not at that system. Running fsck on / fixed the issue and booted gnome. I simply did fsck -y / and I think there would be some better way to do this without corrupting the file system(some times fsck may corrupt on a way to recover). Any one could tell me please? – user3215 Jan 17 '11 at 4:11

Log in and try startx

Is your /home on a separate partition?

share|improve this answer
yes it's on separate partition – user3215 Jan 16 '11 at 13:45
I've updated my question! – user3215 Jan 16 '11 at 14:08
You can't run startx as root. Log in as your normal user. – wojox Jan 17 '11 at 11:53
up vote 0 down vote accepted

Just running fsck -y /, or fsck -y /dev/sda1 fixed the issue and system started gnome as usual. The best way of running fsck would be booting the system from live cd or usb stick. But before running fsck, backing up necessary data is also to be considered mandatory.

share|improve this answer
wow, now my linux mint is constantly rebooting (after fsck -y /). Any ideas how to fix that? – sasha.sochka Apr 5 '15 at 21:52

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.