Re: HPA and failed opcode was: 0x37 ?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Eric D. Mudama wrote:
> On 1/30/07, Eric D. Mudama <edmudama@xxxxxxxxx> 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
-
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Filesystems]     [Linux SCSI]     [Linux RAID]     [Git]     [Kernel Newbies]     [Linux Newbie]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Samba]     [Device Mapper]

  Powered by Linux