Error reading block ... resulted in short read

shadowrise · 12-28-2006, 01:48 PM

Hello,

O/S = Suse Linux

Every time I try to run fsck on my /dev/sdb1 raid array running ext3, I get these errors:

-------------------------------------------------------------------------------------------

Error reading block 13137026 (Attempt to read block from filesystem resulted in short read) while reading indirect blocks of inode 6554248. Ignore error<y>? yes

Force rewrite<y>? yes

Error reading block 13145561 (Attempt to read block from filesystem resulted in short read) while reading indirect blocks of inode 6554425. Ignore error<y>? yes

Force rewrite<y>? yes

Error reading block 13162652 (Attempt to read block from filesystem resulted in short read) while reading indirect blocks of inode 6554803. Ignore error<y>? yes

Force rewrite<y>? yes

Error reading block 13205308 (Attempt to read block from filesystem resulted in short read) while reading indirect blocks of inode 6555707. Ignore error<y>? yes

Force rewrite<y>? yes

Error reading block 13222601 (Attempt to read block from filesystem resulted in short read) while reading indirect blocks of inode 6556120. Ignore error<y>? yes

Force rewrite<y>? yes

-------------------------------------------------------------------------------------------

Could anyone explain exactly what a "short read" is, why fsck can't fix it, and what else I could do to resolve the problem short of scratching the volume and rebuilding it?

I have looked at the partition table for this device in fdisk, and it appears normal.

farslayer · 12-29-2006, 08:15 AM

At this point I would install SMART on the system and check the drive, looks to me like there is a possibility the drive may be failing..

Quote:

http://tldp.org/HOWTO/text/Software-RAID-0.4x-HOWTO

12.
Q: I've set up /etc/mdtab using mdcreate, I've mdadd'ed, mdrun and
fsck'ed my two /dev/mdX partitions. Everything looks okay before a
reboot. As soon as I reboot, I get an fsck error on both
partitions: fsck.ext2: Attempt to read block from filesystem
resulted in short read while trying too open /dev/md0. Why?! How
do I fix it?!

A: During the boot process, the RAID partitions must be
started before they can be fsck'ed. This must be done in
one of the boot scripts. For some distributions, fsck is
called from /etc/rc.d/rc.S, for others, it is called from
/etc/rc.d/rc.sysinit. Change this file to mdadd -ar *before*
fsck -A is executed. Better yet, it is suggested that
ckraid be run if mdadd returns with an error. How do do
this is discussed in greater detail in question 14 of the
section ''Error Recovery''.

Those are the only references I have found regarding that error..

Please let us know what you find out..