mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Mark Lord <liml@rtr.ca>
Cc: Robert Hancock <hancockr@shaw.ca>,
	linux-ide@vger.kernel.org, linux-raid@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: 2.6.27.10: ata1.00: HPA detected: current 293044655, native   293046768
Date: Sat, 3 Jan 2009 08:15:52 -0500 (EST)	[thread overview]
Message-ID: <alpine.DEB.1.10.0901030813410.31871@p34.internal.lan> (raw)
In-Reply-To: <495B9ED3.8050008@rtr.ca>



On Wed, 31 Dec 2008, Mark Lord wrote:

> Robert Hancock wrote:
>> Justin Piszcz wrote:
>>> On one system, two Raptor 150s:
>>> 
>>> [    0.739402] ata1.00: HPA detected: current 293044655, native 293046768
> ..
>> Presumably somebody or something set up a host protected area on one drive 
>> and not the other.. I believe there are some utilities out there that can 
>> be used to disable the HPA and allow the full capacity to be used.
> ..
>
> "hdparm -N" can do this, temporarily or permanently.
> Get the latest version from Sourceforge, and see the manpage for details.
>
> -ml
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

Just incase someone Google's this later on, this is what it looks like,
for my case:

The /dev/sda (first disk) is the one with the problem.

root@Knoppix:~/hpa# hdparm -N /dev/sda

/dev/sda:
  max sectors   = 293044655/293046768, HPA is enabled
root@Knoppix:~/hpa# hdparm -N /dev/sdb

/dev/sdb:
  max sectors   = 293046768/293046768, HPA is disabled
root@Knoppix:~/hpa# hdparm -N p293046768 /dev/sda

/dev/sda:
  setting max visible sectors to 293046768 (permanent)
  max sectors   = 293046768/293046768, HPA is disabled
root@Knoppix:~/hpa#

root@Knoppix:~# hdparm -N /dev/sda

/dev/sda:
  max sectors   = 293046768/293046768, HPA is disabled
root@Knoppix:~#

1. I backed up the volume of the RAID-1 array.
2. Failed out the disk with the problem.
3. Then ran the commands above.
4. Reboot back to the OS.
5. Re-add the disk back into the RAID-1.


Justin.


  reply	other threads:[~2009-01-03 13:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-30 12:26 Justin Piszcz
2008-12-30 17:30 ` Robert Hancock
2008-12-30 18:12   ` David Lethe
2008-12-31 16:33   ` Mark Lord
2009-01-03 13:15     ` Justin Piszcz [this message]
2008-12-30 18:51 ` Kyle McMartin

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=alpine.DEB.1.10.0901030813410.31871@p34.internal.lan \
    --to=jpiszcz@lucidpixels.com \
    --cc=hancockr@shaw.ca \
    --cc=liml@rtr.ca \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@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

all inboxes | Powered by JetHome®