>
> I was getting these errors in my logs, and I wanted to know if this was
> more likely a disk error or a scsi cable error and what drive it might
> be referring to?
>
> Oct 19 09:47:20 i kernel: scsidisk I/O error: dev 08:01, sector 46
> ext2_write_inode: unable to read inode block - inode=2, block=87
device 08:01 is the major/minor number. Look in /dev. It is
probably /dev/sda1
Block 87 is corrupt.
> Oct 19 09:47:25 i kernel: scsidisk I/O error: dev 08:41, sector 6574
> ext2_write_inode: unable to read inode block - inode=4097, block=164
This is probably /dev/sdc9 (08:41).
Block 164 is corrupt.
> Oct 19 09:47:29 i kernel: scsidisk I/O error: dev 08:21, sector 3310
> ext2_write_inode: unable to read inode block - inode=2049, block=8279
This is probably /dev/sdb5 (08:21).
Block 8279 is corrupt.
> Oct 19 09:47:33 i kernel: scsidisk I/O error: dev 08:01, sector 46
> ext2_write_inode: unable to read inode block - inode=2, block=87
Same as previous. Shows a probable real error.
..etc,..etc,.. With SCSI, bad cables corrupt data, but not the disk
blocks. In other words, a bad cable or improper termination may cause
garbage to be written. However, the garbage can be read back because
the hardware makes the correct CRC even though you wrote junk. In your
case, you have some real CRC errors (bad blocks on the disks).
I suggest you get everything off those disks as soon as possible.
Cheers,
Dick Johnson
**** FILE SYSTEM WAS MODIFIED ****
Penguin : Linux version 2.3.13 on an i686 machine (400.59 BogoMips).
Warning : It's hard to remain at the trailing edge of technology.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/