On one system, two Raptor 150s:
[ 0.739402] ata1.00: HPA detected: current 293044655, native 293046768
[ 0.739491] ata1.00: ATA-7: WDC WD1500ADFD-00NLR5, 21.07QR5, max UDMA/133
[ 0.739577] ata1.00: 293044655 sectors, multi 0: LBA48 NCQ (depth 31/32)
[ 0.742454] ata1.00: configured for UDMA/133
[ 1.059146] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 1.061406] ata2.00: ATA-7: WDC WD1500ADFD-00NLR5, 21.07QR5, max UDMA/133
[ 1.061494] ata2.00: 293046768 sectors, multi 0: LBA48 NCQ (depth 31/32)
[ 1.064360] ata2.00: configured for UDMA/133
Two disks in a RAID-1 (mdadm) configuration, how come the first one
has an issue w/HPA as the firmware of both disks is the same..?
l1:~# smartctl -a /dev/sda | grep -i bytes
User Capacity: 150,038,863,360 bytes
l1:~# smartctl -a /dev/sdb | grep -i bytes
User Capacity: 150,039,945,216 bytes
l1:~#
Why does this occur?
Justin.
Justin Piszcz wrote:
> On one system, two Raptor 150s:
>
> [ 0.739402] ata1.00: HPA detected: current 293044655, native 293046768
> [ 0.739491] ata1.00: ATA-7: WDC WD1500ADFD-00NLR5, 21.07QR5, max
> UDMA/133
> [ 0.739577] ata1.00: 293044655 sectors, multi 0: LBA48 NCQ (depth 31/32)
> [ 0.742454] ata1.00: configured for UDMA/133
>
> [ 1.059146] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> [ 1.061406] ata2.00: ATA-7: WDC WD1500ADFD-00NLR5, 21.07QR5, max
> UDMA/133
> [ 1.061494] ata2.00: 293046768 sectors, multi 0: LBA48 NCQ (depth 31/32)
> [ 1.064360] ata2.00: configured for UDMA/133
>
> Two disks in a RAID-1 (mdadm) configuration, how come the first one
> has an issue w/HPA as the firmware of both disks is the same..?
>
> l1:~# smartctl -a /dev/sda | grep -i bytes
> User Capacity: 150,038,863,360 bytes
> l1:~# smartctl -a /dev/sdb | grep -i bytes
> User Capacity: 150,039,945,216 bytes
> l1:~#
>
> Why does this occur?
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.
> -----Original Message-----
> From: [email protected] [mailto:linux-raid-
> [email protected]] On Behalf Of Robert Hancock
> Sent: Tuesday, December 30, 2008 11:30 AM
> To: [email protected]
> Cc: [email protected]; [email protected]
> Subject: Re: 2.6.27.10: ata1.00: HPA detected: current 293044655,
> native 293046768
>
> Justin Piszcz wrote:
> > On one system, two Raptor 150s:
> >
> > [ 0.739402] ata1.00: HPA detected: current 293044655, native
> 293046768
> > [ 0.739491] ata1.00: ATA-7: WDC WD1500ADFD-00NLR5, 21.07QR5, max
> > UDMA/133
> > [ 0.739577] ata1.00: 293044655 sectors, multi 0: LBA48 NCQ (depth
> 31/32)
> > [ 0.742454] ata1.00: configured for UDMA/133
> >
> > [ 1.059146] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl
300)
> > [ 1.061406] ata2.00: ATA-7: WDC WD1500ADFD-00NLR5, 21.07QR5, max
> > UDMA/133
> > [ 1.061494] ata2.00: 293046768 sectors, multi 0: LBA48 NCQ (depth
> 31/32)
> > [ 1.064360] ata2.00: configured for UDMA/133
> >
> > Two disks in a RAID-1 (mdadm) configuration, how come the first one
> > has an issue w/HPA as the firmware of both disks is the same..?
> >
> > l1:~# smartctl -a /dev/sda | grep -i bytes
> > User Capacity: 150,038,863,360 bytes
> > l1:~# smartctl -a /dev/sdb | grep -i bytes
> > User Capacity: 150,039,945,216 bytes
> > l1:~#
> >
> > Why does this occur?
>
> 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.
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid"
> in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
Warning - this hidden area could have been used to circumvent some
security, hold viruses,
steal data, whatever. I have unfortunately seen this trick more times
than I care to
get into.
If this disk drive is installed on a computer where such things are
a possibility, then I suggest bringing system down to single user mode,
having a witness
by your side, then resizing the disk and using dd to grab contents of
the "new" blocks,
so you can inspect it.
With the right software, and access to the sg driver, then one can
easily use this area as
their own private repository to keep stuff until the opportunity
presents itself to take
the data offsite.
FYI, there is no way to prevent somebody from resizing disk in this way
if they can write
to the sg driver, some of our customers use our software to resize in
this way and to monitor
changes, but you can really just set up a shell script to do this
yourself.
David
http://www.santools.com/smart/unix/manual
On Tue, Dec 30, 2008 at 07:26:40AM -0500, Justin Piszcz wrote:
> On one system, two Raptor 150s:
>
> [ 0.739402] ata1.00: HPA detected: current 293044655, native 293046768
> [ 0.739491] ata1.00: ATA-7: WDC WD1500ADFD-00NLR5, 21.07QR5, max UDMA/133
> [ 0.739577] ata1.00: 293044655 sectors, multi 0: LBA48 NCQ (depth 31/32)
> [ 0.742454] ata1.00: configured for UDMA/133
>
> [ 1.059146] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> [ 1.061406] ata2.00: ATA-7: WDC WD1500ADFD-00NLR5, 21.07QR5, max UDMA/133
> [ 1.061494] ata2.00: 293046768 sectors, multi 0: LBA48 NCQ (depth 31/32)
> [ 1.064360] ata2.00: configured for UDMA/133
>
> Two disks in a RAID-1 (mdadm) configuration, how come the first one
> has an issue w/HPA as the firmware of both disks is the same..?
>
> l1:~# smartctl -a /dev/sda | grep -i bytes
> User Capacity: 150,038,863,360 bytes
> l1:~# smartctl -a /dev/sdb | grep -i bytes
> User Capacity: 150,039,945,216 bytes
> l1:~#
>
> Why does this occur?
>
Bonghits... Anyway, pass libata.ignore_hpa=1 if you want to use the full
capacity of your disk.
regards, Kyle
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
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 [email protected]
> 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.