From: Steven Scholz <steven.scholz@imc-berlin.de>
To: "Eric D. Mudama" <edmudama@gmail.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: HPA and failed opcode was: 0x37 ?
Date: Tue, 30 Jan 2007 16:54:43 +0100 [thread overview]
Message-ID: <45BF6A43.5070909@imc-berlin.de> (raw)
In-Reply-To: <311601c90701300750w2f2f3c86k5cda7109ab0df347@mail.gmail.com>
Eric D. Mudama wrote:
> On 1/30/07, Eric D. Mudama <edmudama@gmail.com> wrote:
>> 0x37 is READ NATIVE MAX ADDRESS EXT, which is the 48-bit version of
>> the command to figure out how big the drive "really" is. It appears
>> that model of drive indicated support for 48-bit commands, but then
>> aborted the 48-bit version of READ NATIVE MAX ADDRESS.
>
> Er, oops, 0x27 is the read. 0x37 is the "SET MAX ADDRESS EXT" ...
> would appear your drive has a host-protected area or is in the
> set_max_locked/set_max_frozen state.
Well as the kernel log mentioned there is a HPA:
hda: Host Protected Area detected.
current capacity is 78140160 sectors (40007 MB)
native capacity is 185074430006016 sectors (94758108163 MB)
> There's nothing functionally to worry about, but maybe your BIOS has
> decided to protect part of the drive?
What is the "SET MAX ADDRESS EXT" used for?
Steven
next prev parent reply other threads:[~2007-01-30 15:54 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-30 14:02 HPA and failed opcode was: 0x37 ? Steven Scholz
2007-01-30 14:07 ` Steven Scholz
2007-01-30 15:44 ` Eric D. Mudama
2007-01-30 15:50 ` Eric D. Mudama
2007-01-30 15:54 ` Steven Scholz [this message]
2007-01-30 15:53 ` Steven Scholz
2007-01-30 16:44 ` Alan
2007-01-30 16:46 ` Steven Scholz
2007-01-30 17:26 ` Alan
2007-01-30 17:19 ` Steven Scholz
2007-01-30 18:07 ` Alan
2007-01-30 18:04 ` Steven Scholz
2007-01-30 18:23 ` Eric D. Mudama
2007-01-30 18:32 ` Sergei Shtylyov
2007-01-30 19:56 ` Eric D. Mudama
2007-01-30 20:01 ` Eric D. Mudama
2007-01-31 8:29 ` Steven Scholz
2007-01-31 12:54 ` Sergei Shtylyov
2007-01-31 13:08 ` Steven Scholz
2007-01-31 13:12 ` Sergei Shtylyov
2007-01-31 13:38 ` Steven Scholz
2007-01-31 9:51 ` Steven Scholz
2007-01-31 12:50 ` Sergei Shtylyov
2007-01-31 13:04 ` Steven Scholz
2007-01-31 13:33 ` Alan
2007-01-31 13:26 ` Steven Scholz
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=45BF6A43.5070909@imc-berlin.de \
--to=steven.scholz@imc-berlin.de \
--cc=edmudama@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.