Error reading block during fsck

Today my Linux Box started a fsck automaticlly during boot.
Suddenly it sttoped with error:

Error reading block 13565971 (Attempt to read block from filesystem resulted in short read) while doing inode scan.

So, I entered maintenance mode in order to running fsck manually.

After fsck gave me the same error for blocks 13565971-83 and 13565985 with a option to ignore error, the one I choose.

My hard disk has a total of 18175539 blocks (80GB IDE Drive).

Is that a hardware (physical HD damage) error?
How can I be sure my data is safe?

I have received the same error before in another Linux Box, with another HD I had. How often do this occurr?
LVL 1
jclobocarAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
owensleftfootConnect With a Mentor Commented:
dumpe2fs -b will do that for you.
0
 
owensleftfootCommented:
You probably have a dead sector on your disk. It could mean your disk is on the way out, but maybe not :) I would take a backup of any important files anyway. You can use e2fsck with the -c option to mark the sectors as bad - otherwise every time fsck is run it will throw up the same error.
0
 
jclobocarAuthor Commented:
How can i check the bad map sector if I need e2fsck -c another time?
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.