Re: ST31000340NS (1000G) Capacity equal 33MB issue.
Dear Mark: 2008/2/16, Mark Lord [EMAIL PROTECTED]: 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 - To unsubscribe from this list: send the line unsubscribe linux-ide in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: ST31000340NS (1000G) Capacity equal 33MB issue.
Richard Liu wrote: Dear Mark: 2008/2/16, Mark Lord [EMAIL PROTECTED]: 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 - To unsubscribe from this list: send the line unsubscribe linux-ide in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: ST31000340NS (1000G) Capacity equal 33MB issue.
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 - To unsubscribe from this list: send the line unsubscribe linux-ide in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: ST31000340NS (1000G) Capacity equal 33MB issue.
Dear Mark: 2008/2/18, Mark Lord [EMAIL PROTECTED]: 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 - To unsubscribe from this list: send the line unsubscribe linux-ide in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: ST31000340NS (1000G) Capacity equal 33MB issue.
On Feb 17, 2008 2:18 PM, Mark Lord [EMAIL PROTECTED] wrote: Richard Liu wrote: Dear Mark: 2008/2/16, Mark Lord [EMAIL PROTECTED]: 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 - To unsubscribe from this list: send the line unsubscribe linux-ide in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: ST31000340NS (1000G) Capacity equal 33MB issue.
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 -Nnnn to restore the capacity under DCO.. Gotta try it someday, I guess. - To unsubscribe from this list: send the line unsubscribe linux-ide in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: ST31000340NS (1000G) Capacity equal 33MB issue.
Mark Lord wrote:
Richard Liu wrote:
Dear Mark:
2008/2/15, Mark Lord [EMAIL PROTECTED]:
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 HdSw15uSec Fixed DTR10Mbs 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 003f
2020 2020 2020 2020 2020 2020
3951 4a30 3942 4a34 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
2f00 4000 0200 0200 0007 0040 0010
003f fc00 0110 fe6e 0007
0003 0078 0078 0078 0078
001f 0502 0040 0040
0070 001b 346b 7d01 4123 3468 bc01 4103
207f fefe fffe fe00
fe6e
5000 c500 09b9 0136
4006
4006
0021 6db0 7470 6db0 7470 0002 0140
0100 5000 3c06 3c0a 003c 0008
000f 0280 000a
2700 8000
003d
1c20
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
-
To unsubscribe from this list: send the line unsubscribe linux-ide in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: ST31000340NS (1000G) Capacity equal 33MB issue.
Richard Liu wrote:
Dear Mark:
2008/2/15, Mark Lord [EMAIL PROTECTED]:
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 HdSw15uSec Fixed DTR10Mbs 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 003f
2020 2020 2020 2020 2020 2020
3951 4a30 3942 4a34 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
2f00 4000 0200 0200 0007 0040 0010
003f fc00 0110 fe6e 0007
0003 0078 0078 0078 0078
001f 0502 0040 0040
0070 001b 346b 7d01 4123 3468 bc01 4103
207f fefe fffe fe00
fe6e
5000 c500 09b9 0136
4006
4006
0021 6db0 7470 6db0 7470 0002 0140
0100 5000 3c06 3c0a 003c 0008
000f 0280 000a
2700 8000
003d
1c20
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
-
To unsubscribe from this list: send the line unsubscribe linux-ide in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: ST31000340NS (1000G) Capacity equal 33MB issue.
On Thu, Feb 14, 2008 at 1:18 PM, Richard Liu [EMAIL PROTECTED] 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 - To unsubscribe from this list: send the line unsubscribe linux-ide in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: ST31000340NS (1000G) Capacity equal 33MB issue.
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 HdSw15uSec Fixed DTR10Mbs 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.
-
To unsubscribe from this list: send the line unsubscribe linux-ide in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
