public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Fabio Coatti <cova@ferrara.linux.it>
To: Robert Hancock <hancockr@shaw.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: SATA problems and fs corruption on recent kernels
Date: Tue, 12 Aug 2008 22:24:39 +0200	[thread overview]
Message-ID: <200808122224.39863.cova@ferrara.linux.it> (raw)
In-Reply-To: <48A0D44D.7010305@shaw.ca>

Alle Tuesday 12 August 2008, Robert Hancock ha scritto:
> Fabio Coatti wrote:
> > Hi all,
> > I'm facing a quite annoying problem with sata disks. Googling a bit I've
> > seen several references to similar issues, but without any hint on how to
> > solve. Short description, details below and on request ;) : on a quite
> > old Pentium IV /IC7G abit mobo, I've started to see sata lockups when
> > moving files of 4~15Mb size. I do this quite often (photo, actually) and
> > prior the 2.6.25.something I can't recall any single problem. On that
> > machine I've 3 sata disks, both maxtor and seagate. The lockup caused XFS
> > corruption, and a simple reset is not enough: I've to turn off the power
> > to have the hd drive responding again, otherwise the machine will stop at
> > POST.
> > It doesn't matter which HD are involved in file transfer, it can happen
> > moving files on different partition of the same disk, between different
> > disks and between sata and usb disks as well.
> > the same configuration worked without a glitch for years, using drivers
> > sata_sil and ata_piix (that mobo has two controllers)
> >
> > Since then, I've changed hardware: new mobo (M3N-HT asus), new processor,
> > kernel and even some disks (I've added a new one). Of course new cables
> > and power supply. So I think that a hw culprit can be excluded.
> > The driver has changed as well, now I use  ahci mode for sata disks.
> > Tried with 2.6.26.2
> > The behaviour is exactly the same: moving files (more or less of the same
> > size as before) causes a HD lockup so bad that it needs a power cycle to
> > recover, otherwise the post will fail ahci detection of the drive (for
> > those used to that controller, it waits  for some seconds with "Port:00"
> > message, then the POST process locks)
> > now even a mount of the damaged xfs partition can trigger the freeze: I
> > can only see a that xfs starts the recovery, then the hd stops blinking
> > (always on) and after that even a "ls" on the drive remains stuck. This
> > happens on a brand new 500Mb sata disk.
> > so it seems that nor the hardware, nor the 64 or 32 bit of cpu/kernel nor
> > the low level drivers can explain this. I've tried only with xfs, but
> > sounds strange that a fs can lockup a drive.
> > the hardware that I'm using is a 9850AMD phenom, m3n-ht mobo, 2.6.26.2
> > kernel, gentoo 2008.0, sata hd from seagate and maxtor, different sizes
> > and models. AHCI sata drivers.
> > working on small size files seems to be fine, as I can compile kernels
> > and I've installed the system without problems.
> > Now I will try several things to get more clues, I can donwngrade kernels
> > to see if the situation changes (dunno if the new mobo is compatible with
> > too old kernels...), but if someone can give me some hints about which
> > tests has to be made and wich information I must provide, it will be most
> > welcome Thanks for any help.
>
> For things to lock up badly enough that even BIOS POST fails to detect
> the drives or locks up really seems like a hardware problem to me.
> You're still using some of the same disks from the old machine?

Yes, and the hardware problem is the first thing I thinked of, but I've 
changed MB and cables, as well as bought a new disk. An I still get some I/O 
errors, even on the new one.
So, or I'm a bit unlucky to find several faulty disks in a row (it can be :) ) 
or something unclear is going on. 
The disk that suffers most lockups, after many tries, is the new one, the only 
SATA-II drive.
I'll keep stressing the HD trying to figure out what's going on, I'll even try 
a new sata-II unit, to see if I've really picked a heap of faulty disks.

Thanks for the answer!


-- 
Fabio Coatti       http://members.ferrara.linux.it/cova     
Ferrara Linux Users Group           http://ferrara.linux.it
GnuPG fp:9765 A5B6 6843 17BC A646  BE8C FA56 373A 5374 C703
Old SysOps never die... they simply forget their password.

  reply	other threads:[~2008-08-12 22:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.PZ8V7KpfqpWoxUeVa4Sv6GFtUN0@ifi.uio.no>
2008-08-12  0:07 ` SATA problems and fs corruption on recent kernels Robert Hancock
2008-08-12 20:24   ` Fabio Coatti [this message]
2008-08-20  8:41     ` Tejun Heo
2008-08-09  9:18 Fabio Coatti

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200808122224.39863.cova@ferrara.linux.it \
    --to=cova@ferrara.linux.it \
    --cc=hancockr@shaw.ca \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox