* ST31000340NS (1000G) Capacity equal 33MB issue.
[not found] <d0d565260802141013q61cb5e7fh7dcf04d7729213f7@mail.gmail.com>
@ 2008-02-14 18:18 ` Richard Liu
2008-02-14 18:29 ` Greg Freemyer
2008-02-14 19:43 ` Mark Lord
0 siblings, 2 replies; 12+ messages in thread
From: Richard Liu @ 2008-02-14 18:18 UTC (permalink / raw)
To: linux-ide
Hello all:
I bought a Seagate ES.2 ST31000340NS (1000GB) and run at Gentoo
Linux kernel 2.6.24.
But Linux kernel report the disk size only 33MB.
I tried Intel ICH5 and Sil3112, but get the same result.
I don't know this issue was caused by libsata or scsi layer .
Could you help me to solved it ?
Here is the relative information.
I think this would be helpful.
==
dmesg
==
ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
ata4.00: HPA detected: current 65134, native 1953525167
ata4.00: ATA-6: ST31000340NS, SN04, max UDMA/133
ata4.00: 65134 sectors, multi 16: LBA48 NCQ (depth 0/32)
ata4.00: configured for UDMA/100
scsi 3:0:0:0: Direct-Access ATA ST31000340NS SN04 PQ: 0 ANSI: 5
sd 3:0:0:0: [sdc] 65134 512-byte hardware sectors (33 MB)
sd 3:0:0:0: [sdc] Write Protect is off
sd 3:0:0:0: [sdc] Mode Sense: 00 3a 00 00
sd 3:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sd 3:0:0:0: [sdc] 65134 512-byte hardware sectors (33 MB)
sd 3:0:0:0: [sdc] Write Protect is off
sd 3:0:0:0: [sdc] Mode Sense: 00 3a 00 00
sd 3:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sdc: unknown partition table
sd 3:0:0:0: [sdc] Attached SCSI disk
sd 3:0:0:0: Attached scsi generic sg2 type 0
==
Seatool
==
# ./st -i /dev/sg2
/dev/sg2
Vendor = ATA
Product = ST31000340NS
Version = SN04
Serial Number =
Copyright =
SCSI Firmware =
Servo RAM Release =
Servo ROM Release =
Servo RAM Date =
Servo ROM Date =
Blocksize = 512, Highblock = 65133, Capacity = 33 MB
-this is a Seagate drive
-this drive does not support DST
-Mode Page Settings [current value (default)]:
-WCE bit = 1 (0)
-RCD bit = 0 (0)
-AWRE bit = 1 (0)
-ARRE bit = 0 (0)
-DExcpt bit = 0 (0)
-Number of cache segments = 0 (0)
==
hdparm
==
hdparm -i /dev/sdc
/dev/sdc:
Model=ST31000340NS , FwRev=SN04 ,
SerialNo= 9QJ09BJ4
Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs RotSpdTol>.5% }
RawCHS=64/16/63, TrkSize=0, SectSize=0, ECCbytes=4
BuffType=unknown, BuffSize=0kB, MaxMultSect=16, MultSect=?16?
CurCHS=64/16/63, CurSects=64512, LBA=yes, LBAsects=65134
IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 udma2 udma3 udma4 *udma5
AdvancedPM=no WriteCache=enabled
Drive conforms to: ATA/ATAPI-6 T13 1410D revision 2: ATA/ATAPI-4,5,6
* signifies the current active mode
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: ST31000340NS (1000G) Capacity equal 33MB issue.
2008-02-14 18:18 ` ST31000340NS (1000G) Capacity equal 33MB issue Richard Liu
@ 2008-02-14 18:29 ` Greg Freemyer
2008-02-14 19:43 ` Mark Lord
1 sibling, 0 replies; 12+ messages in thread
From: Greg Freemyer @ 2008-02-14 18:29 UTC (permalink / raw)
To: Richard Liu; +Cc: linux-ide
On Thu, Feb 14, 2008 at 1:18 PM, Richard Liu <richliu.tw@gmail.com> wrote:
> Hello all:
>
> I bought a Seagate ES.2 ST31000340NS (1000GB) and run at Gentoo
> Linux kernel 2.6.24.
> But Linux kernel report the disk size only 33MB.
> I tried Intel ICH5 and Sil3112, but get the same result.
>
> I don't know this issue was caused by libsata or scsi layer .
>
Don't ignore the controllers themselves.
I am in the process of upgrading the firmware on several 4 month old
sig 3512s because they won't even let the computer boot with a 1TB
drive connected. ie. they lockup during the bios phase.
Previously, I've also had to upgrade older SIG PATA controllers to get
them to see past 500GB.
Sig has new firmware on their site, but you have to do the upload from
DOS. (or supposedly windows. Don't know about that.). ie. use a
boot floppy or a boot thumb drive.
Greg
--
Greg Freemyer
Litigation Triage Solutions Specialist
http://www.linkedin.com/in/gregfreemyer
First 99 Days Litigation White Paper -
http://www.norcrossgroup.com/forms/whitepapers/99%20Days%20whitepaper.pdf
The Norcross Group
The Intersection of Evidence & Technology
http://www.norcrossgroup.com
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: ST31000340NS (1000G) Capacity equal 33MB issue.
2008-02-14 18:18 ` ST31000340NS (1000G) Capacity equal 33MB issue Richard Liu
2008-02-14 18:29 ` Greg Freemyer
@ 2008-02-14 19:43 ` Mark Lord
[not found] ` <d0d565260802141931r2b6296c0l6c223b703e3407f5@mail.gmail.com>
2008-02-15 17:30 ` Mark Lord
1 sibling, 2 replies; 12+ messages in thread
From: Mark Lord @ 2008-02-14 19:43 UTC (permalink / raw)
To: Richard Liu; +Cc: linux-ide
Richard Liu wrote:
> Hello all:
>
> I bought a Seagate ES.2 ST31000340NS (1000GB) and run at Gentoo
> Linux kernel 2.6.24.
> But Linux kernel report the disk size only 33MB.
> I tried Intel ICH5 and Sil3112, but get the same result.
>
> I don't know this issue was caused by libsata or scsi layer .
..
> hdparm
> ==
> hdparm -i /dev/sdc
>
> /dev/sdc:
>
> Model=ST31000340NS , FwRev=SN04 ,
> SerialNo= 9QJ09BJ4
> Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs RotSpdTol>.5% }
> RawCHS=64/16/63, TrkSize=0, SectSize=0, ECCbytes=4
> BuffType=unknown, BuffSize=0kB, MaxMultSect=16, MultSect=?16?
> CurCHS=64/16/63, CurSects=64512, LBA=yes, LBAsects=65134
> IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
> PIO modes: pio0 pio1 pio2 pio3 pio4
> DMA modes: mdma0 mdma1 mdma2
> UDMA modes: udma0 udma1 udma2 udma3 udma4 *udma5
> AdvancedPM=no WriteCache=enabled
> Drive conforms to: ATA/ATAPI-6 T13 1410D revision 2: ATA/ATAPI-4,5,6
>
> * signifies the current active mode
..
Nothing wrong there, but I would really like/prefer to see the output from:
hdparm --Istdout /dev/sdc
thanks.
^ permalink raw reply [flat|nested] 12+ messages in thread
* Fwd: ST31000340NS (1000G) Capacity equal 33MB issue.
[not found] ` <d0d565260802141931r2b6296c0l6c223b703e3407f5@mail.gmail.com>
@ 2008-02-15 6:14 ` Richard Liu
0 siblings, 0 replies; 12+ messages in thread
From: Richard Liu @ 2008-02-15 6:14 UTC (permalink / raw)
To: linux-ide
Dear Mark:
2008/2/15, Mark Lord <liml@rtr.ca>:
> Richard Liu wrote:
> > Hello all:
> >
> > I bought a Seagate ES.2 ST31000340NS (1000GB) and run at Gentoo
> > Linux kernel 2.6.24.
> > But Linux kernel report the disk size only 33MB.
> > I tried Intel ICH5 and Sil3112, but get the same result.
> >
> > I don't know this issue was caused by libsata or scsi layer .
>
> ..
>
> > hdparm
> > ==
> > hdparm -i /dev/sdc
> >
> > /dev/sdc:
> >
> > Model=ST31000340NS , FwRev=SN04 ,
> > SerialNo= 9QJ09BJ4
> > Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs RotSpdTol>.5% }
> > RawCHS=64/16/63, TrkSize=0, SectSize=0, ECCbytes=4
> > BuffType=unknown, BuffSize=0kB, MaxMultSect=16, MultSect=?16?
> > CurCHS=64/16/63, CurSects=64512, LBA=yes, LBAsects=65134
> > IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
> > PIO modes: pio0 pio1 pio2 pio3 pio4
> > DMA modes: mdma0 mdma1 mdma2
> > UDMA modes: udma0 udma1 udma2 udma3 udma4 *udma5
> > AdvancedPM=no WriteCache=enabled
> > Drive conforms to: ATA/ATAPI-6 T13 1410D revision 2: ATA/ATAPI-4,5,6
> >
> > * signifies the current active mode
>
> ..
>
> Nothing wrong there, but I would really like/prefer to see the output from:
>
> hdparm --Istdout /dev/sdc
>
>
> thanks.
>
# hdparm --Istdout /dev/sdc
/dev/sdc:
0c5a 0040 c837 0010 0000 0000 003f 0000
0000 0000 2020 2020 2020 2020 2020 2020
3951 4a30 3942 4a34 0000 0000 0004 534e
3034 2020 2020 5354 3331 3030 3033 3430
4e53 2020 2020 2020 2020 2020 2020 2020
2020 2020 2020 2020 2020 2020 2020 8010
0000 2f00 4000 0200 0200 0007 0040 0010
003f fc00 0000 0110 fe6e 0000 0000 0007
0003 0078 0078 0078 0078 0000 0000 0000
0000 0000 0000 001f 0502 0000 0040 0040
0070 001b 346b 7d01 4123 3468 bc01 4103
207f 0000 0000 fefe fffe 0000 fe00 0000
0000 0000 0000 0000 fe6e 0000 0000 0000
0000 0000 0000 0000 5000 c500 09b9 0136
0000 0000 0000 0000 0000 0000 0000 4006
4006 0000 0000 0000 0000 0000 0000 0000
0021 6db0 7470 6db0 7470 0000 0002 0140
0100 5000 3c06 3c0a 0000 003c 0000 0008
0000 0000 000f 0280 0000 0000 000a 0000
0000 0000 0000 0000 0000 0000 2700 8000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 003d 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 1c20 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 e9a5
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: ST31000340NS (1000G) Capacity equal 33MB issue.
2008-02-14 19:43 ` Mark Lord
[not found] ` <d0d565260802141931r2b6296c0l6c223b703e3407f5@mail.gmail.com>
@ 2008-02-15 17:30 ` Mark Lord
2008-02-16 15:46 ` Mark Lord
1 sibling, 1 reply; 12+ messages in thread
From: Mark Lord @ 2008-02-15 17:30 UTC (permalink / raw)
To: Richard Liu; +Cc: linux-ide
Richard Liu wrote:
> Dear Mark:
>
> 2008/2/15, Mark Lord <liml@rtr.ca>:
>> Richard Liu wrote:
>> > Hello all:
>> >
>> > I bought a Seagate ES.2 ST31000340NS (1000GB) and run at Gentoo
>> > Linux kernel 2.6.24.
>> > But Linux kernel report the disk size only 33MB.
>> > I tried Intel ICH5 and Sil3112, but get the same result.
>> >
>> > I don't know this issue was caused by libsata or scsi layer .
>>
>> ..
>>
>>> hdparm
>> > ==
>> > hdparm -i /dev/sdc
>> >
>> > /dev/sdc:
>> >
>> > Model=ST31000340NS , FwRev=SN04 ,
>> > SerialNo= 9QJ09BJ4
>> > Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs RotSpdTol>.5% }
>> > RawCHS=64/16/63, TrkSize=0, SectSize=0, ECCbytes=4
>> > BuffType=unknown, BuffSize=0kB, MaxMultSect=16, MultSect=?16?
>> > CurCHS=64/16/63, CurSects=64512, LBA=yes, LBAsects=65134
>> > IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
>> > PIO modes: pio0 pio1 pio2 pio3 pio4
>> > DMA modes: mdma0 mdma1 mdma2
>> > UDMA modes: udma0 udma1 udma2 udma3 udma4 *udma5
>> > AdvancedPM=no WriteCache=enabled
>> > Drive conforms to: ATA/ATAPI-6 T13 1410D revision 2: ATA/ATAPI-4,5,6
>> >
>> > * signifies the current active mode
>>
>> ..
>>
>> Nothing wrong there, but I would really like/prefer to see the output from:
>>
>> hdparm --Istdout /dev/sdc
>>
>>
>> thanks.
>>
>
> # hdparm --Istdout /dev/sdc
>
> /dev/sdc:
> 0c5a 0040 c837 0010 0000 0000 003f 0000
> 0000 0000 2020 2020 2020 2020 2020 2020
> 3951 4a30 3942 4a34 0000 0000 0004 534e
> 3034 2020 2020 5354 3331 3030 3033 3430
> 4e53 2020 2020 2020 2020 2020 2020 2020
> 2020 2020 2020 2020 2020 2020 2020 8010
> 0000 2f00 4000 0200 0200 0007 0040 0010
> 003f fc00 0000 0110 fe6e 0000 0000 0007
> 0003 0078 0078 0078 0078 0000 0000 0000
> 0000 0000 0000 001f 0502 0000 0040 0040
> 0070 001b 346b 7d01 4123 3468 bc01 4103
> 207f 0000 0000 fefe fffe 0000 fe00 0000
> 0000 0000 0000 0000 fe6e 0000 0000 0000
> 0000 0000 0000 0000 5000 c500 09b9 0136
> 0000 0000 0000 0000 0000 0000 0000 4006
> 4006 0000 0000 0000 0000 0000 0000 0000
> 0021 6db0 7470 6db0 7470 0000 0002 0140
> 0100 5000 3c06 3c0a 0000 003c 0000 0008
> 0000 0000 000f 0280 0000 0000 000a 0000
> 0000 0000 0000 0000 0000 0000 2700 8000
> 0000 0000 0000 0000 0000 0000 0000 0000
> 0000 0000 0000 0000 0000 0000 0000 0000
> 0000 0000 0000 0000 0000 0000 0000 0000
> 0000 0000 0000 0000 0000 0000 0000 0000
> 0000 0000 0000 0000 0000 0000 0000 0000
> 0000 0000 0000 0000 0000 0000 003d 0000
> 0000 0000 0000 0000 0000 0000 0000 0000
> 0000 1c20 0000 0000 0000 0000 0000 0000
> 0000 0000 0000 0000 0000 0000 0000 0000
> 0000 0000 0000 0000 0000 0000 0000 0000
> 0000 0000 0000 0000 0000 0000 0000 0000
> 0000 0000 0000 0000 0000 0000 0000 e9a5
..
Thanks. By running the above data through hdparm --Istdin,
I see that the drive is indeed identifying itself as a 33MB drive.
Probably because it has been told to do so by either the factory defaults,
or the BIOS, having enabled these features (which can cause it to report
fake values for various things):
* Host Protected Area feature set
* Device Configuration Overlay feature set
So that's why the 1TB drive appears as a 33MB drive.
In the near future, I will be enhancing hdparm to query more
detailed data from underneath those artificial features.
But you'll have to enable the entire 1TB capacity if you want Linux to use it.
It is currently disabled in the drive, and Linux respects that.
Cheers
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: ST31000340NS (1000G) Capacity equal 33MB issue.
2008-02-15 17:30 ` Mark Lord
@ 2008-02-16 15:46 ` Mark Lord
2008-02-17 15:21 ` Richard Liu
0 siblings, 1 reply; 12+ messages in thread
From: Mark Lord @ 2008-02-16 15:46 UTC (permalink / raw)
To: Richard Liu; +Cc: linux-ide
Mark Lord wrote:
> Richard Liu wrote:
>> Dear Mark:
>>
>> 2008/2/15, Mark Lord <liml@rtr.ca>:
>>> Richard Liu wrote:
>>> > Hello all:
>>> >
>>> > I bought a Seagate ES.2 ST31000340NS (1000GB) and run at Gentoo
>>> > Linux kernel 2.6.24.
>>> > But Linux kernel report the disk size only 33MB.
>>> > I tried Intel ICH5 and Sil3112, but get the same result.
>>> >
>>> > I don't know this issue was caused by libsata or scsi layer .
>>>
>>> ..
>>>
>>>> hdparm
>>> > ==
>>> > hdparm -i /dev/sdc
>>> >
>>> > /dev/sdc:
>>> >
>>> > Model=ST31000340NS , FwRev=SN04 ,
>>> > SerialNo= 9QJ09BJ4
>>> > Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs RotSpdTol>.5% }
>>> > RawCHS=64/16/63, TrkSize=0, SectSize=0, ECCbytes=4
>>> > BuffType=unknown, BuffSize=0kB, MaxMultSect=16, MultSect=?16?
>>> > CurCHS=64/16/63, CurSects=64512, LBA=yes, LBAsects=65134
>>> > IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
>>> > PIO modes: pio0 pio1 pio2 pio3 pio4
>>> > DMA modes: mdma0 mdma1 mdma2
>>> > UDMA modes: udma0 udma1 udma2 udma3 udma4 *udma5
>>> > AdvancedPM=no WriteCache=enabled
>>> > Drive conforms to: ATA/ATAPI-6 T13 1410D revision 2:
>>> ATA/ATAPI-4,5,6
>>> >
>>> > * signifies the current active mode
>>>
>>> ..
>>>
>>> Nothing wrong there, but I would really like/prefer to see the
>>> output from:
>>>
>>> hdparm --Istdout /dev/sdc
>>>
>>>
>>> thanks.
>>>
>>
>> # hdparm --Istdout /dev/sdc
>>
>> /dev/sdc:
>> 0c5a 0040 c837 0010 0000 0000 003f 0000
>> 0000 0000 2020 2020 2020 2020 2020 2020
>> 3951 4a30 3942 4a34 0000 0000 0004 534e
>> 3034 2020 2020 5354 3331 3030 3033 3430
>> 4e53 2020 2020 2020 2020 2020 2020 2020
>> 2020 2020 2020 2020 2020 2020 2020 8010
>> 0000 2f00 4000 0200 0200 0007 0040 0010
>> 003f fc00 0000 0110 fe6e 0000 0000 0007
>> 0003 0078 0078 0078 0078 0000 0000 0000
>> 0000 0000 0000 001f 0502 0000 0040 0040
>> 0070 001b 346b 7d01 4123 3468 bc01 4103
>> 207f 0000 0000 fefe fffe 0000 fe00 0000
>> 0000 0000 0000 0000 fe6e 0000 0000 0000
>> 0000 0000 0000 0000 5000 c500 09b9 0136
>> 0000 0000 0000 0000 0000 0000 0000 4006
>> 4006 0000 0000 0000 0000 0000 0000 0000
>> 0021 6db0 7470 6db0 7470 0000 0002 0140
>> 0100 5000 3c06 3c0a 0000 003c 0000 0008
>> 0000 0000 000f 0280 0000 0000 000a 0000
>> 0000 0000 0000 0000 0000 0000 2700 8000
>> 0000 0000 0000 0000 0000 0000 0000 0000
>> 0000 0000 0000 0000 0000 0000 0000 0000
>> 0000 0000 0000 0000 0000 0000 0000 0000
>> 0000 0000 0000 0000 0000 0000 0000 0000
>> 0000 0000 0000 0000 0000 0000 0000 0000
>> 0000 0000 0000 0000 0000 0000 003d 0000
>> 0000 0000 0000 0000 0000 0000 0000 0000
>> 0000 1c20 0000 0000 0000 0000 0000 0000
>> 0000 0000 0000 0000 0000 0000 0000 0000
>> 0000 0000 0000 0000 0000 0000 0000 0000
>> 0000 0000 0000 0000 0000 0000 0000 0000
>> 0000 0000 0000 0000 0000 0000 0000 e9a5
> ..
>
> Thanks. By running the above data through hdparm --Istdin,
> I see that the drive is indeed identifying itself as a 33MB drive.
>
> Probably because it has been told to do so by either the factory defaults,
> or the BIOS, having enabled these features (which can cause it to report
> fake values for various things):
>
> * Host Protected Area feature set
> * Device Configuration Overlay feature set
>
> So that's why the 1TB drive appears as a 33MB drive.
>
> In the near future, I will be enhancing hdparm to query more
> detailed data from underneath those artificial features.
>
> But you'll have to enable the entire 1TB capacity if you want Linux to
> use it.
> It is currently disabled in the drive, and Linux respects that.
..
Okay, hdparm-8.1 is now available from sourceforge.net.
Download it, build it ("make"), and see what you get from "hdparm -N /dev/sdc"
Thanks
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: ST31000340NS (1000G) Capacity equal 33MB issue.
2008-02-16 15:46 ` Mark Lord
@ 2008-02-17 15:21 ` Richard Liu
2008-02-17 19:18 ` Mark Lord
0 siblings, 1 reply; 12+ messages in thread
From: Richard Liu @ 2008-02-17 15:21 UTC (permalink / raw)
To: Mark Lord; +Cc: linux-ide
Dear Mark:
2008/2/16, Mark Lord <liml@rtr.ca>:
> Mark Lord wrote:
> > Richard Liu wrote:
> >
> > Thanks. By running the above data through hdparm --Istdin,
> > I see that the drive is indeed identifying itself as a 33MB drive.
> >
> > Probably because it has been told to do so by either the factory defaults,
> > or the BIOS, having enabled these features (which can cause it to report
> > fake values for various things):
> >
> > * Host Protected Area feature set
> > * Device Configuration Overlay feature set
> >
> > So that's why the 1TB drive appears as a 33MB drive.
> >
> > In the near future, I will be enhancing hdparm to query more
> > detailed data from underneath those artificial features.
> >
> > But you'll have to enable the entire 1TB capacity if you want Linux to
> > use it.
> > It is currently disabled in the drive, and Linux respects that.
> ..
>
> Okay, hdparm-8.1 is now available from sourceforge.net.
> Download it, build it ("make"), and see what you get from "hdparm -N /dev/sdc"
>
> Thanks
>
I downloaded hdparm-8.1
and here is output information.
# ./hdparm -N /dev/sdc
/dev/sdc:
max sectors = 65134/1953525168, HPA is enabled
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: ST31000340NS (1000G) Capacity equal 33MB issue.
2008-02-17 15:21 ` Richard Liu
@ 2008-02-17 19:18 ` Mark Lord
2008-02-17 19:26 ` Mark Lord
2008-02-17 19:48 ` Greg Freemyer
0 siblings, 2 replies; 12+ messages in thread
From: Mark Lord @ 2008-02-17 19:18 UTC (permalink / raw)
To: Richard Liu; +Cc: linux-ide
Richard Liu wrote:
> Dear Mark:
>
> 2008/2/16, Mark Lord <liml@rtr.ca>:
>> Mark Lord wrote:
>>> Richard Liu wrote:
>>>
>>> Thanks. By running the above data through hdparm --Istdin,
>>> I see that the drive is indeed identifying itself as a 33MB drive.
>>>
>>> Probably because it has been told to do so by either the factory defaults,
>>> or the BIOS, having enabled these features (which can cause it to report
>>> fake values for various things):
>>>
>>> * Host Protected Area feature set
>>> * Device Configuration Overlay feature set
>>>
>>> So that's why the 1TB drive appears as a 33MB drive.
>>>
>>> In the near future, I will be enhancing hdparm to query more
>>> detailed data from underneath those artificial features.
>>>
>>> But you'll have to enable the entire 1TB capacity if you want Linux to
>>> use it.
>>> It is currently disabled in the drive, and Linux respects that.
>> ..
>>
>> Okay, hdparm-8.1 is now available from sourceforge.net.
>> Download it, build it ("make"), and see what you get from "hdparm -N /dev/sdc"
>>
>> Thanks
>>
> I downloaded hdparm-8.1
> and here is output information.
>
> # ./hdparm -N /dev/sdc
>
> /dev/sdc:
> max sectors = 65134/1953525168, HPA is enabled
..
Yes, pretty much as expected there.
You can safely now try this:
./hdparm -N1953525168 /dev/sdc
If that works, it will have temporarily restored access to the entire drive.
Then you can try to make it permanent by doing this:
./hdparm -Np1953525168 /dev/sdc
If *that* also works, then reboot and things should be fine,
unless your machine BIOS changes it back again on boot.. :/
If either of those *fails*, then it is because your BIOS
(or possibly the system startup scripts) have "frozen" the configuration
to prevent changes. Dunno why they would do that, but it's possible.
In which case, you could move the drive to another machine temporarily,
and then issue that same command there.
Cheers
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: ST31000340NS (1000G) Capacity equal 33MB issue.
2008-02-17 19:18 ` Mark Lord
@ 2008-02-17 19:26 ` Mark Lord
2008-02-17 19:41 ` Richard Liu
2008-02-17 19:48 ` Greg Freemyer
1 sibling, 1 reply; 12+ messages in thread
From: Mark Lord @ 2008-02-17 19:26 UTC (permalink / raw)
To: Richard Liu; +Cc: linux-ide
Mark Lord wrote:
> Richard Liu wrote:
..
>> I downloaded hdparm-8.1
>> and here is output information.
>>
>> # ./hdparm -N /dev/sdc
>>
>> /dev/sdc:
>> max sectors = 65134/1953525168, HPA is enabled
> ..
>
> Yes, pretty much as expected there.
>
> You can safely now try this:
>
> ./hdparm -N1953525168 /dev/sdc
>
> If that works, it will have temporarily restored access to the entire
> drive.
> Then you can try to make it permanent by doing this:
>
> ./hdparm -Np1953525168 /dev/sdc
>
> If *that* also works, then reboot and things should be fine,
> unless your machine BIOS changes it back again on boot.. :/
>
> If either of those *fails*, then it is because your BIOS (or possibly
> the system startup scripts) have "frozen" the configuration
> to prevent changes. Dunno why they would do that, but it's possible.
>
> In which case, you could move the drive to another machine temporarily,
> and then issue that same command there.
..
Or just hot unplug/replug the drive and try it again.
That should also work, assuming the driver for your controller supports hotplug.
Cheers
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: ST31000340NS (1000G) Capacity equal 33MB issue.
2008-02-17 19:26 ` Mark Lord
@ 2008-02-17 19:41 ` Richard Liu
0 siblings, 0 replies; 12+ messages in thread
From: Richard Liu @ 2008-02-17 19:41 UTC (permalink / raw)
To: Mark Lord; +Cc: linux-ide
Dear Mark:
2008/2/18, Mark Lord <liml@rtr.ca>:
> Mark Lord wrote:
> > Richard Liu wrote:
> ..
> >> I downloaded hdparm-8.1
> >> and here is output information.
> >>
> >> # ./hdparm -N /dev/sdc
> >>
> >> /dev/sdc:
> >> max sectors = 65134/1953525168, HPA is enabled
> > ..
> >
> > Yes, pretty much as expected there.
> >
> > You can safely now try this:
> >
> > ./hdparm -N1953525168 /dev/sdc
> >
> > If that works, it will have temporarily restored access to the entire
> > drive.
> > Then you can try to make it permanent by doing this:
> >
> > ./hdparm -Np1953525168 /dev/sdc
> >
> > If *that* also works, then reboot and things should be fine,
> > unless your machine BIOS changes it back again on boot.. :/
> >
> > If either of those *fails*, then it is because your BIOS (or possibly
> > the system startup scripts) have "frozen" the configuration
> > to prevent changes. Dunno why they would do that, but it's possible.
> >
> > In which case, you could move the drive to another machine temporarily,
> > and then issue that same command there.
I am very appreciate for your help.
Both command
./hdparm -N1953525168 /dev/sdc
and
./hdparm -Np1953525168 /dev/sdc
work fine.
I can get while 1000G disk space.
I tried to read/write some file (around 3G bytes) into the disk.
and uses md5 to verify data.
It seems no problem.
Thank you very much.
> ..
>
> Or just hot unplug/replug the drive and try it again.
> That should also work, assuming the driver for your controller supports hotplug.
>
> Cheers
>
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: ST31000340NS (1000G) Capacity equal 33MB issue.
2008-02-17 19:18 ` Mark Lord
2008-02-17 19:26 ` Mark Lord
@ 2008-02-17 19:48 ` Greg Freemyer
2008-02-17 20:32 ` Mark Lord
1 sibling, 1 reply; 12+ messages in thread
From: Greg Freemyer @ 2008-02-17 19:48 UTC (permalink / raw)
To: Mark Lord; +Cc: Richard Liu, linux-ide
On Feb 17, 2008 2:18 PM, Mark Lord <liml@rtr.ca> wrote:
>
> Richard Liu wrote:
> > Dear Mark:
> >
> > 2008/2/16, Mark Lord <liml@rtr.ca>:
> >> Mark Lord wrote:
> >>> Richard Liu wrote:
> >>>
> >>> Thanks. By running the above data through hdparm --Istdin,
> >>> I see that the drive is indeed identifying itself as a 33MB drive.
> >>>
> >>> Probably because it has been told to do so by either the factory defaults,
> >>> or the BIOS, having enabled these features (which can cause it to report
> >>> fake values for various things):
> >>>
> >>> * Host Protected Area feature set
> >>> * Device Configuration Overlay feature set
> >>>
> >>> So that's why the 1TB drive appears as a 33MB drive.
> >>>
> >>> In the near future, I will be enhancing hdparm to query more
> >>> detailed data from underneath those artificial features.
> >>>
> >>> But you'll have to enable the entire 1TB capacity if you want Linux to
> >>> use it.
> >>> It is currently disabled in the drive, and Linux respects that.
> >> ..
> >>
> >> Okay, hdparm-8.1 is now available from sourceforge.net.
> >> Download it, build it ("make"), and see what you get from "hdparm -N /dev/sdc"
> >>
> >> Thanks
> >>
> > I downloaded hdparm-8.1
> > and here is output information.
> >
> > # ./hdparm -N /dev/sdc
> >
> > /dev/sdc:
> > max sectors = 65134/1953525168, HPA is enabled
> ..
>
> Yes, pretty much as expected there.
>
> You can safely now try this:
>
> ./hdparm -N1953525168 /dev/sdc
>
> If that works, it will have temporarily restored access to the entire drive.
> Then you can try to make it permanent by doing this:
>
> ./hdparm -Np1953525168 /dev/sdc
>
> If *that* also works, then reboot and things should be fine,
> unless your machine BIOS changes it back again on boot.. :/
>
> If either of those *fails*, then it is because your BIOS
> (or possibly the system startup scripts) have "frozen" the configuration
> to prevent changes. Dunno why they would do that, but it's possible.
>
> In which case, you could move the drive to another machine temporarily,
> and then issue that same command there.
>
> Cheers
Mark,
Very cool new functionality in 8.1 Looking forward to testing it this week.
Thanks for your efforts.
I assume DCO is still able to hide sectors from us?
Thanks
Greg
--
Greg Freemyer
Litigation Triage Solutions Specialist
http://www.linkedin.com/in/gregfreemyer
First 99 Days Litigation White Paper -
http://www.norcrossgroup.com/forms/whitepapers/99%20Days%20whitepaper.pdf
The Norcross Group
The Intersection of Evidence & Technology
http://www.norcrossgroup.com
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: ST31000340NS (1000G) Capacity equal 33MB issue.
2008-02-17 19:48 ` Greg Freemyer
@ 2008-02-17 20:32 ` Mark Lord
0 siblings, 0 replies; 12+ messages in thread
From: Mark Lord @ 2008-02-17 20:32 UTC (permalink / raw)
To: Greg Freemyer; +Cc: Richard Liu, linux-ide
Greg Freemyer wrote:
>..
> Very cool new functionality in [hdparm] 8.1
> Looking forward to testing it this week.
>
> Thanks for your efforts.
>
> I assume DCO is still able to hide sectors from us?
..
I'm not sure (haven't tried it here yet).
But the way I read the ATA8 specification,
it sounds like "hdparm -N" should show the true capacity,
regardless of DCO. But what's not clear, is whether one
can then use -Nnnnnnnn to restore the capacity under DCO..
Gotta try it someday, I guess.
^ permalink raw reply [flat|nested] 12+ messages in thread
end of thread, other threads:[~2008-02-17 20:32 UTC | newest]
Thread overview: 12+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <d0d565260802141013q61cb5e7fh7dcf04d7729213f7@mail.gmail.com>
2008-02-14 18:18 ` ST31000340NS (1000G) Capacity equal 33MB issue Richard Liu
2008-02-14 18:29 ` Greg Freemyer
2008-02-14 19:43 ` Mark Lord
[not found] ` <d0d565260802141931r2b6296c0l6c223b703e3407f5@mail.gmail.com>
2008-02-15 6:14 ` Fwd: " Richard Liu
2008-02-15 17:30 ` Mark Lord
2008-02-16 15:46 ` Mark Lord
2008-02-17 15:21 ` Richard Liu
2008-02-17 19:18 ` Mark Lord
2008-02-17 19:26 ` Mark Lord
2008-02-17 19:41 ` Richard Liu
2008-02-17 19:48 ` Greg Freemyer
2008-02-17 20:32 ` Mark Lord
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).