GNOME session not starting after filesystem corruption

user3215

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.

EDIT:1

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

machine1 login: root

password:

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
user3215

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.

Collected from the Internet

Please contact [email protected] to delete if infringement.

edited at
0

Comments

0 comments
Login to comment

Related

Ubuntu 18.10 Cosmic not starting GNOME session on bootup

Consistent filesystem corruption

XBMC starting after login insted of gnome

How to fix session not starting after unsetting a variable

Unable to login after killing gnome-session

Failed to load session "gnome" after system crash

sddm not starting after upgrade to 16.04, gnome and kde both installed

Flask-Session (filesystem): session files are not deleted after PERMANENT_SESSION_LIFETIME

Starting a bash script after gnome-keyring-daemon but before gnome-encfs?

Will a backup and restore with dd solve filesystem corruption?

Gnome Shell: Running shell script after session starts?

Postgres database corruption [solved - not corruption after all]

Gnome terminal 3.22 not starting

Patch corruption or loss after rebase

Cassandra session data corruption from multithreaded read

Corruption-proof SD card filesystem for embedded Linux?

How can I simulate ext3 filesystem corruption?

How can I simulate ext3 filesystem corruption?

ext4 corruption found in superblock, but filesystem can be mounted

Starting session in Appium

Starting a session from a function

Starting and keeping a session in IVR

session not starting in php

php session not starting

Session Start not 'starting'

why no gnome session?

Starting a new session causes Error - Cannot set headers after they are sent to the client

After formatting and installing Ubuntu 15.10, and gnome-session-flashback, cannot view desktop icons or drag anything to the desktop

After upgrading to 20.04 my GNOME session dies constantly. How do I troubleshoot?