linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <teheo@suse.de>
To: "Ivan N. Zlatev" <contact@i-nz.net>
Cc: linux-ide@vger.kernel.org
Subject: Re: Seagate HDD Frequent Head Unload - hdparm/dmidecode/smartctl output
Date: Mon, 28 Jul 2008 16:28:28 +0900	[thread overview]
Message-ID: <488D751C.5080302@suse.de> (raw)
In-Reply-To: <488B27CE.5060106@i-nz.net>

[-- Attachment #1: Type: text/plain, Size: 804 bytes --]

Ivan N. Zlatev wrote:
> I am having frequent head unloads on a Dell Vostro 1400 laptop with a
> Seagate HDD. As explained on the Wiki[1] I am attaching for you the
> output of:
> 
>    * hdparm -I
>    * dmidecode
>    * smartctl --all (in addition)
> 
> I hope this information is useful for you.
> 
> I am currently using a workaround to prevent the unloads as described
> here - http://en.opensuse.org/Disk_Power_Management .
> 
> [1]
> http://ata.wiki.kernel.org/index.php/Known_issues#Drives_which_perform_frequent_head_unloads_under_Linux

Can you please test the attached storage-fixup.conf?  If you're on suse,
just do "zypper install storage-fixup" and replace
/etc/storage-fixup.conf with the attached file, remove the manual
workaround and see whether the problem is gone.

Thanks.

-- 
tejun

[-- Attachment #2: storage-fixup.conf --]
[-- Type: text/plain, Size: 1513 bytes --]

#
# /etc/storage-fixup.conf - Configuration file for storage-fixup
#
# Blank lines and lines starting with # are ignored.  Please read
# comment at the top of storage-fixup for more information.
#
# Drive model patterns are generalized to cover drives from the same
# family.  Drive manufacturers usually have datasheets or web pages
# listing all models of the same family.
#
# The DMI part is difficult to generalize as there's no such
# information.  We'll have to generalize as we collect entries.
#
# If you have a harddrive which does crazy unloading but not listed
# here, please write to linux-ide@vger.kernel.org with the outputs of
# "dmidecode" and "hdparm -I DRIVE" attached.  On a laptop the DRIVE
# is usually /dev/sda.
#

# Reported drive model: Hitachi HTS722020K9SA00
rule tp-t60
dmi system-manufacturer		LENOVO
dmi system-product-name		1952W5R
dmi system-version		ThinkPad T60
ata model			Hitachi HTS7220*K9*A*
act hdparm -B 255 $DEV

# Reported drive model: SAMSUNG HM250JI
rule hp-dv6500
dmi system-manufacturer		Hewlett-Packard
dmi system-product-name		HP Pavilion dv6500 Notebook PC
dmi system-version		Rev 1
ata model			SAMSUNG HM*I
act hdparm -B 255 $DEV

# Reported drive model: ST9100824AS
rule dell-e1505
dmi system-manufacturer		Dell Inc.
dmi system-product-name		MM061
ata model			ST9*AS
act hdparm -B 255 $DEV

# Reported drive model: ST9120822AS
rule dell-Vostro-1400
dmi system-manufacturer		Dell Inc.
dmi system-product-name		Vostro 1400
ata model			ST9*AS
act hdparm -B 255 $DEV

  reply	other threads:[~2008-07-28  7:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-26 13:34 Seagate HDD Frequent Head Unload - hdparm/dmidecode/smartctl output Ivan N. Zlatev
2008-07-28  7:28 ` Tejun Heo [this message]
2008-07-28  9:04   ` Ivan N. Zlatev
2008-07-28  9:18     ` Tejun Heo
2008-08-02 13:01       ` Ivan N. Zlatev
2008-08-03  8:23         ` Tejun Heo
2008-08-03 15:29           ` Ivan N. Zlatev
2008-08-03 22:42             ` Tejun Heo

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=488D751C.5080302@suse.de \
    --to=teheo@suse.de \
    --cc=contact@i-nz.net \
    --cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).