file system, kernel or hardware raid failure?

[Vegard Svanberg]

* Eric Sandeen <sandeen at redhat.com> [2009-03-04 18:26]:

> > [   38.907730] end_request: I/O error, dev sda, sector 284688831
> 
> Drive hardware on sda failing; I'd run smart tools or vendor
> diagnostics, to be sure.

Late answer, but...

After posting this, we figured this had to be due to a power failure
occuring some weeks before. But yesterday, we suddenly had one other,
identical, machine failing with exactly the same error messages:

[2834866.071770] sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK
[2834866.071778] sd 0:0:0:0: [sda] Sense Key : Hardware Error [current] 
[2834866.071782] sd 0:0:0:0: [sda] Add. Sense: Internal target failure
[2834866.071787] end_request: I/O error, dev sda, sector 302515639
[2834866.071823] EXT3-fs error (device dm-0): ext3_get_inode_loc: unable to read inode block - inode=9455580, block=37814399

Any ideas? Fsck will fix the errors, but report short reads while
fixing, and on reboot/remount, the problems are back.

As this probably isn't relevant to ext3 list anymore (I guess it's more
relevant for kernel/SCSI subsystem developers), I'll find some other
lists.

-- 
Vegard Svanberg <vegard at svanberg.no> [*Takapa at IRC (EFnet)]