Message-ID: <43540E38.9060408@rtr.ca>
Date: Mon, 17 Oct 2005 16:48:56 -0400
From: Mark Lord <lkml@rtr.ca>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050923 Debian/1.7.12-0ubuntu05.04
MIME-Version: 1.0
To: "J.A. Magallon" <jamagallon@able.es>
Cc: "Linux-Kernel, " <linux-kernel@vger.kernel.org>
Subject: Re: hdparm almost burned my SATA disk
References: <20051016010153.768d29d5@werewolf.able.es>
In-Reply-To: <20051016010153.768d29d5@werewolf.able.es>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 962
Lines: 23

J.A. Magallon wrote:
>
> I was trying hdparm -tT on a SATA disk, it did the buffered part OK,
> and hanged my box in the non-buffered measure. After waiting some minutes,
> I did a SysRQ-s-u-b, and the the disk began to give many read errors on
> sectors and could not boot because journal was not present and many other
> errors.
> 
> After some warm and cold boots, finally the box came up correctly.
> I suspect that something that hdparm did left my disk dumb. But what ?

Nope.  hdparm simply does a bunch of read() system calls to fetch
data from the drive, same as any other code might do it.

I think you should use the smartmontools to check the drive error logs
and find out what REALLY happened there.

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