File System with errors

nardz · 11-27-2007, 07:22 PM

Hi.

My linux system won't successfully boot as of today (kubuntu)

Code:

* Checking root file system... 
fsck 1.40-WIP (14-Nov-2006)
/dev/sdb6 contains a file system with errors, check forced. 
/dev/sdb6: |=========================

/dev/sdb6: 
Duplicate or bad block in use!
/dev/sdb6: Multiply-claimed block(s) in inode 4000172: 24873687
/dev/sdb6: Multiply-claimed block(s) in inode 4145260: 25071693
/dev/sdb6: Multiply-claimed block(s) in inode 4279660: 25349626
/dev/sdb6: Multiply-claimed block(s) in inode 4376460: 25546288

/dev/sdb6: UNEXPECTED INCONSISTENCY: RUN fsck MANUALLY.
        (i.e., without -a or -p options
fsck died with exit status 4

* An automatic file system check (fsck) of the root file system failed.
A manual fsck must be performed, then the system restarted.
The fsck should be performed in maintenance mode with the
root filesystem mounted in read-only mode.
* The root filesystem is currently mounted in read-only mode. 
A maintenance shell will now be started
After performing system maintenance, perss Control-D to terminate the maintenance shell and erstart the system
bash: no job control in this shell
bash: groups: command not found
bash: lesspipe: command not found
bash: The: command not found
The program 'apt-get' is currently not installed. You can install it by typing: apt-get install apt
bash: apt-get: command not found
bash: dircolors: command not found
bash: The: command not found
The program 'apt-get' is currently not installed. You can install it by typing: apt-get install apt
bash: apt-get: command not found
root@desktop:~#

help!

nardz · 11-27-2007, 08:21 PM

i ran fsck, and corrected all the errors, now i get this as a window prompt when i try to log in to kde:

Code:

Could not start kdeinit. Check your installation.

nardz · 11-27-2007, 09:15 PM

seems ive fixed my own problem.

apt-get update
apt-get install
apt-get check
apt-get build-dep

in case anyone ever comes accross this trying to fix a similar problem, i ran all of the above commands, at least one of them was the solution

nardz · 11-28-2007, 12:17 AM

i'm not having the same problem again (regarding kdeinit).. cant fix it this time...

Anvil · 11-29-2007, 05:57 AM

If you have freshly rebooted, been dropped into filesystem repair; you've run an fsck or two that kicked out errors and then finally run a clean fsck; and your files have been toasted, then I'm afraid you are probably looking at a restore or even a reinstall.

There is a know problem with some 64bit mobos where under conditions of high network and disk activity, they just wig out and start scribbling over the hard drive. When in this state the damage doesn't correlate with recent writes, it just seems to spray the disk. It seems to be something to do with IOMMU and/or ACPI. The more recent the kernel version, the less likely it seems to be to happen.

Would you please reply with your setup .. mobo, cpu, OS etc

Cheers

Andy M