Error reading block "x" (Attempt to read block from.......

pvandyk2005 · 07-05-2008, 04:45 PM

Hello guys

I've got following output as a result of using e2fsck

Error reading block "x" (Attempt to read block from file system resulted in short read) white getting next Inode from scan.
Ignore Error?
Force rewrite?

Could someone help me with this.... if someone knows exactly what's the meaning for this.

thank you!

Mr. C. · 07-05-2008, 05:30 PM

Was this fsck run while the file system was mounted, and hence active ?

pvandyk2005 · 07-05-2008, 07:54 PM

no. partition was unmounted

Mr. C. · 07-05-2008, 08:01 PM

Any disk related error messages in /var/log/messages ?

Its hard to know immediately where the problem is. Fsck tried to read from the disk, requesting a certain amount of data, but it did not get all the data expected.

This may be a corrupted FS, bad HD, bad HD controller.

Run disk diagnostics on the disk, to rule out hardware issues. No sense trying to fix an FS if the disk hardware is troubled. Your drive or HW vendor probably has diagnostic software you can download and use.

pvandyk2005 · 07-06-2008, 03:43 AM

i didn't found nothing in log. as a additional information... and i know if this is related to that error or not but anyway

I'm using as a torrent client ktorrent and as soon as ktorrent is started my HDD led is constant red and of course my system is slower. I've check cpu and memory utilizations and are ok.

This problems with ktorrent started just few days before. Until then it worked without any problem.

pvandyk2005 · 07-06-2008, 03:49 AM

ahhh and something else. I can't kill ktorrent process.

Quote:

root@andrei:/home#ps ax | grep ktorrent
13016 pts/1 D 0:01 ktorrent
13093 pts/0 S+ 0:00 grep ktorrent
root@andrei:/home#kill 13016
root@andrei:/home#ps ax | grep ktorrent
13016 pts/1 D 0:01 ktorrent
13093 pts/0 S+ 0:00 grep ktorrent

Mr. C. · 07-06-2008, 05:25 AM

I'd still take the disk offline, and 1) run a full diagnostic on the disk, and 2) run fsck -y repeatedly until no problems remain. A final good step would be to runnie a stress benchmark on the disk (bonnie++).