Jump to content

KDE hangs after login in [solved]


jethro
 Share

Recommended Posts

Hi everybody,

 

I have been running Mandriva 2008.0 for a little while now without any major problems. Today I was working in Eclipse when all of a sudden my screen went black. When it can back on I was logged out of my KDE session. When I try to login it hangs after I supplied my username and password. I see the blue screen which says "LINUX Mandriva" (some kind of default startup screen).

 

I tried to reboot my PC, during the boot process Mandriva tells me is is "Checking Filesystems", it kept hanging on this during a few tries. After these attempts I tried to boot into failsafe mode. Here the "Checking Filesystems" came to 100% but it said there were severe errors and that I should try to run "fsck". I booted into an Ubuntu live CD to see what's going on. I mounted the sda7 drive (which is the problem drive) to /media/disk in Ubuntu and was successfully able to open some files. I tried to run "fsck" from the live CD, but it kept complaining about a corrupt or missing superblock.

 

At this point I was not able to boot Mandriva, not even to the point where I have to supply my username / password. I modified my /etc/fstab file and replaced the 2 at the end of the /dev/sda7 mount point (which is the problem drive) for a 0. This ensures that Mandriva is not going to check the filesystem on sda7. Using this approach I am successfully able to boot into Mandriva and supply my username and password. But after entering these two Mandriva hangs again at the blue screen which says "LINUX Mandriva". If I then hit CTRL-ALT-F1 I get to see what's going on. If I do this thousands of statements like

EXT3-fs error (device sda7): ext3_free_blocks_sb: bit already cleared for block 186396159
keep flying by. I am looking at these things flying by for almost an hour now.

 

Best regards,

Jethro

 

[moved from Installing Mandriva by spinynorman]

Link to comment
Share on other sites

I mounted the sda7 drive (which is the problem drive) to /media/disk in Ubuntu and was successfully able to open some files. I tried to run "fsck" from the live CD

 

Did I read you right there? You ran fsck on a mounted partition? You really shouldn't, in fact I am surprised it allowed you to do so.

 

Anyway you didn't say what options you used with fsck. This is what I would do.

 

I suppose you can use a Ubuntu CD if you want to, but Mandriva 2008 has its own rescue system so why not use that. Boot from your 2008 disc, select 'Rescue this system' followed by 'Go to Console'. When you get there run:

 

e2fsck -p  /dev/sda7

 

and see if that does anything. (the -p option means 'repair')

 

Edit: here is an alternative strategy if that doesn't work.

 

In a console run

dumpe2fs /dev/sda7 | grep -i superblock

. This will tell you the locations of all the backup superblocks that Linux has created, for example on my system it returns:

 

Primary superblock at 0, Group descriptors at 1-1

Backup superblock at 32768, Group descriptors at 32769-32769

Backup superblock at 98304, Group descriptors at 98305-98305

Backup superblock at 163840, Group descriptors at 163841-163841

Backup superblock at 229376, Group descriptors at 229377-229377

Backup superblock at 294912, Group descriptors at 294913-294913

Backup superblock at 819200, Group descriptors at 819201-819201

Backup superblock at 884736, Group descriptors at 884737-884737

Backup superblock at 1605632, Group descriptors at 1605633-1605633

Backup superblock at 2654208, Group descriptors at 2654209-2654209

Backup superblock at 4096000, Group descriptors at 4096001-4096001

 

You can then run

e2fsck -b 32768

for example and see if it can recognise the file system from there.

 

I should say that I have never used this technique so I don't know if it works or not. If you do happen to succeed with it please let me know.

Edited by viking777
Link to comment
Share on other sites

Did I read you right there? You ran fsck on a mounted partition? You really shouldn't, in fact I am surprised it allowed you to do so.

This comment lead me to try running fsck on /dev/sda7 instead of on a mounted partition. I just ran the following command:

sudo fsck /dev/sda7

which results in the following output:

fsck 1.40.2 (12-Jul-2007)

e2fsck 1.40.2 (12-Jul-2007)

/dev/sda7 contains a file system with errors, check forced.

Pass 1: Checking inodes, blocks and sizes

I am looking at this screen for 10 minutes now. I am not sure if this command is supposed to take a long time. The size of the partition with errors is 187GB.

 

I suppose you can use a Ubuntu CD if you want to, but Mandriva 2008 has its own rescue system so why not use that. Boot from your 2008 disc, select 'Rescue this system' followed by 'Go to Console'. When you get there run:

 

e2fsck -p  /dev/sda7

 

and see if that does anything. (the -p option means 'repair')

I had an Ubunta disk nearby, if

sudo fsck /dev/sda7

will not work from Ubuntu I will try

sudo e2fsck -p /dev/sda7

from the Ubuntu disk. If that also does not work I will download a Mandriva disk.

 

Edit: here is an alternative strategy if that doesn't work.

 

In a console run

dumpe2fs /dev/sda7 | grep -i superblock

. This will tell you the locations of all the backup superblocks that Linux has created, for example on my system it returns:

 

Primary superblock at 0, Group descriptors at 1-1

Backup superblock at 32768, Group descriptors at 32769-32769

Backup superblock at 98304, Group descriptors at 98305-98305

Backup superblock at 163840, Group descriptors at 163841-163841

Backup superblock at 229376, Group descriptors at 229377-229377

Backup superblock at 294912, Group descriptors at 294913-294913

Backup superblock at 819200, Group descriptors at 819201-819201

Backup superblock at 884736, Group descriptors at 884737-884737

Backup superblock at 1605632, Group descriptors at 1605633-1605633

Backup superblock at 2654208, Group descriptors at 2654209-2654209

Backup superblock at 4096000, Group descriptors at 4096001-4096001

 

You can then run

e2fsck -b 32768

for example and see if it can recognise the file system from there.

 

I should say that I have never used this technique so I don't know if it works or not. If you do happen to succeed with it please let me know.

If everything else fails I will try this option. Edited by jethro
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...