Re: Debugging I/O errors further?

Only idea I have is to unmount the drive ( or remount r/o ) and repeatedly md5sum the block device and see if it ever fails to correctly read the data, and if you get any errors in your syslog. If you get no error messages in your syslog and md5sum completes without error but does not get the same hash each time, then there is definitely something very fubar with the hardware or deep in the kernel.

Roy Sigurd Karlsbakk wrote:

Hi all

Sorry for stressing this, but is there a way I can debug this further? it's a seagate drive connected to a sata_sil controller. I only get ext3 errors, and it fails after a while whatever I do

thanks

roy

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: Debugging I/O errors further?
    • From: Roy Sigurd Karlsbakk <[email protected]>

• References:
  • Debugging I/O errors?
    • From: Roy Sigurd Karlsbakk <[email protected]>
  • Re: Debugging I/O errors?
    • From: Tejun Heo <[email protected]>
  • Re: Debugging I/O errors?
    • From: Roy Sigurd Karlsbakk <[email protected]>
  • Debugging I/O errors further?
    • From: Roy Sigurd Karlsbakk <[email protected]>

• Prev by Date: Re: [PATCH v2] Re: Battery class driver.
• Next by Date: Re: [PATCH] handle ext3 directory corruption better
• Previous by thread: Debugging I/O errors further?
• Next by thread: Re: Debugging I/O errors further?
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]