Re: Promise ATA/133 Errors With 2.6.10+

[Erik Slagter <erik@slagter.name>]

On Mon, 2005-06-27 at 13:33 +0200, Vojtech Pavlik wrote:
> On Mon, Jun 27, 2005 at 12:11:36PM +0200, Erik Slagter wrote:
> 
> > On Sun, 2005-06-26 at 18:59 +0100, Alan Cox wrote:
> > > On Sad, 2005-06-25 at 09:35, Justin Piszcz wrote:
> > > > > BTW2 could it be that somewhere a timeout has been lowered in recent
> > > > > kernels? That must have been pre-2.6.11 then.
> > > 
> > > Timeouts have not changed or have increased in fact.
> > 
> > Never mind, the offending harddisk has ceased to be yesterday, it is no
> > more.
> > 
> > What really bothers me, though, is that until the very last moment it
> > was alive, it didn't report any smart error, nor did any self test fail.
> > I guess IBM is to blame here :-(
>  
> Most drives report no SMART problems until they die. I've seen several
> drives who weren't able to read/write or at least remap bad sectors, and
> still their SMART statistics were almost perfect. The SMART event log
> included the errors, though.

In this case NONE of the smartctl -a output revealed any problem, not
the attribute values, not the event log, and not the selftest log
(performed nightly).

I guess it's a problem like a minimal bad contact on the pcb, because
when the drive has properly cooled down, it does function for a while,
then at a certain point (smartctl reports ~35 C) it stops spinning and
hangs the complete bus.

I'm done with it, it is going to be replaced asap.