From: Mark Lord <lkml@rtr.ca>
To: "J.A. Magallon" <jamagallon@able.es>
Cc: "Linux-Kernel, " <linux-kernel@vger.kernel.org>
Subject: Re: hdparm almost burned my SATA disk
Date: Mon, 17 Oct 2005 16:48:56 -0400 [thread overview]
Message-ID: <43540E38.9060408@rtr.ca> (raw)
In-Reply-To: <20051016010153.768d29d5@werewolf.able.es>
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
prev parent reply other threads:[~2005-10-17 20:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-15 23:01 hdparm almost burned my SATA disk J.A. Magallon
2005-10-15 23:04 ` J.A. Magallon
2005-10-16 0:05 ` Michal Piotrowski
2005-10-17 20:50 ` Mark Lord
2005-10-17 20:48 ` Mark Lord [this message]
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=43540E38.9060408@rtr.ca \
--to=lkml@rtr.ca \
--cc=jamagallon@able.es \
--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