Slackware This Forum is for the discussion of Slackware Linux.
|
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
|
06-02-2006, 07:20 AM
|
#1
|
Member
Registered: Nov 2003
Posts: 360
Rep:
|
Question about hdparm
I'm using Slackware 10.2 (updated to slackware-current) with 2.6.16.19 kernel series.
This are my harddrive's results from hdparm:
Quote:
root@nykey:~# hdparm -tT /dev/hda
/dev/hda:
Timing cached reads: 1764 MB in 2.00 seconds = 880.56 MB/sec
Timing buffered disk reads: 162 MB in 3.01 seconds = 53.89 MB/sec
root@nykey:~# hdparm -tT /dev/hdd
/dev/hdd:
Timing cached reads: 1776 MB in 2.00 seconds = 887.70 MB/sec
Timing buffered disk reads: 168 MB in 3.03 seconds = 55.47 MB/sec
root@nykey:~# hdparm /dev/hda
/dev/hda:
multcount = 0 (off)
IO_support = 0 (default 16-bit)
unmaskirq = 0 (off)
using_dma = 1 (on)
keepsettings = 0 (off)
readonly = 0 (off)
readahead = 256 (on)
geometry = 65535/16/63, sectors = 156301488, start = 0
root@nykey:~# hdparm /dev/hdd
/dev/hdd:
multcount = 0 (off)
IO_support = 0 (default 16-bit)
unmaskirq = 0 (off)
using_dma = 1 (on)
keepsettings = 0 (off)
readonly = 0 (off)
readahead = 256 (on)
geometry = 16383/255/63, sectors = 156301488, start = 0
root@nykey:~#
|
And my results from "dmesg | grep hd"
Quote:
Kernel command line: auto BOOT_IMAGE=Kernel2.6 ro root=301 hdc=ide-cd
ide_setup: hdc=ide-cd
ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hdaMA, hdbio
ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdcMA, hddMA
hda: WDC WD800JB-00JJC0, ATA DISK drive
hdc: HL-DT-ST GCE-8523B, ATAPI CD/DVD-ROM drive
hdd: ST380011A, ATA DISK drive
hda: max request size: 128KiB
hda: 156301488 sectors (80026 MB) w/8192KiB Cache, CHS=65535/16/63, UDMA(100)
hda: cache flushes supported
hda: hda1
hdd: max request size: 512KiB
hdd: 156301488 sectors (80026 MB) w/2048KiB Cache, CHS=16383/255/63, UDMA(100)
hdd: cache flushes supported
hdd: hdd1
hdc: ATAPI 52X CD-ROM CD-R/RW drive, 2048kB Cache, UDMA(33)
|
Now I have seen on some threads other peoples hdparm and they had some few differences like:
I have
Quote:
IO_support = 0 (default 16-bit)
|
and they had
Quote:
IO_support = 1 (default 32-bit)
|
.
I have and they had .
I have and they had .
The geometry option I belive is different from one to another depending on the disk capacity, model, vendor, etc.
So my question is to someone who has a clue with this things... wich parameters are right ? Mine or the other people ? And if mine are not OK how can I set them and what would be the right choices ?
This is long I know, but just wanted to be as explicit as I could to help with your answer. Thank you in advance.
Last edited by nykey; 06-02-2006 at 07:21 AM.
|
|
|
06-02-2006, 07:58 AM
|
#2
|
Senior Member
Registered: Dec 2005
Location: Campinas/SP - Brazil
Distribution: SuSE, RHEL, Fedora, Ubuntu
Posts: 1,508
Rep:
|
Its depends of your hardware, cables and disk model.
If you are using flat cables with 80 wires and the disk is plugged on the first IDE channel, you may try to put your disk in 32 bit mode (-c 1) and udma5 (-X 69).
Use this options with caution. Read the hdparm man page. Using udma5 on a unsupported hardware can trash your system. If it is your personal computer, than its ok, at next reboot the system will be fine again.
After changes, run hdparm -t a couple times, and ignore the first run. Compare with previous runs to see any improvements.
good luck,
|
|
|
06-02-2006, 08:56 AM
|
#3
|
Moderator
Registered: Jan 2005
Location: Central Florida 20 minutes from Disney World
Distribution: SlackwareŽ
Posts: 13,971
|
Quote:
Originally Posted by nykey
The geometry option I belive is different from one to another depending on the disk capacity, model, vendor, etc.
So my question is to someone who has a clue with this things... wich parameters are right ? Mine or the other people ? And if mine are not OK how can I set them and what would be the right choices ?
|
Hi,
First you should get the disk(s) information by;
Code:
#hdparm -i /dev/hda #hd information at boot
#hdparm -I /dev/hda #get from drive user friendly output
#hdparm -I /dev/hdd #information
You can then use this output to select what is supported on the desired device. As long as the motherboard supports the desired options then you should be able select the options. Yes your cables should be 80 pin for the I/O devices hd,cdrom or whatever. As long as the device supports the desired data transfer.
When your system boots modern hard disk systems will select the optimum setting for the hardware that it is connected too. Sometimes this is not always correct. Then you can use the hdparm command to change to the desired setting(s).
If you man hdparm you will get a lot of useful information, sure the man hdparm is succinct but you can get a lot from the output.
|
|
|
06-02-2006, 09:46 AM
|
#4
|
Member
Registered: Nov 2003
Posts: 360
Original Poster
Rep:
|
gwsandvik, this is the output of those commands... could you tell by this if I should enable/disable anything further, I really am not into this and a bit afraid not to screw everything up. Thanks for replays.
For hda I get:
Quote:
root@nykey:~# hdparm -i /dev/hda
/dev/hda:
Model=WDC WD800JB-00JJC0, FwRev=05.01C05, SerialNo=WD-WCAM95146812
Config={ HardSect NotMFM HdSw>15uSec SpinMotCtl Fixed DTR>5Mbs FmtGapReq }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=66
BuffType=unknown, BuffSize=8192kB, MaxMultSect=16, MultSect=off
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=156301488
IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 udma2 udma3 udma4 *udma5
AdvancedPM=no WriteCache=enabled
Drive conforms to: device does not report version:
* signifies the current active mode
root@nykey:~# hdparm -I /dev/hda
/dev/hda:
ATA device, with non-removable media
Model Number: WDC WD800JB-00JJC0
Serial Number: WD-WCAM95146812
Firmware Revision: 05.01C05
Standards:
Supported: 6 5 4 3
Likely used: 6
Configuration:
Logical max current
cylinders 16383 16383
heads 16 16
sectors/track 63 63
--
CHS current addressable sectors: 16514064
LBA user addressable sectors: 156301488
device size with M = 1024*1024: 76319 MBytes
device size with M = 1000*1000: 80026 MBytes (80 GB)
Capabilities: LBA, IORDY(can be disabled)
bytes avail on r/w long: 66 Queue depth: 1
Standby timer values: spec'd by Standard, with device specific minimum
R/W multiple sector transfer: Max = 16 Current = 0
Recommended acoustic management value: 128, current value: 254
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 *udma5
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=120ns IORDY flow control=120ns
Commands/features:
Enabled Supported:
* READ BUFFER cmd
* WRITE BUFFER cmd
* Host Protected Area feature set
* Look-ahead
* Write cache
* Power Management feature set
Security Mode feature set
* SMART feature set
* Mandatory FLUSH CACHE command
* Device Configuration Overlay feature set
Automatic Acoustic Management feature set
SET MAX security extension
* DOWNLOAD MICROCODE cmd
* SMART self-test
* SMART error logging
Security:
Master password revision code = 65534
supported
not enabled
not locked
not frozen
not expired: security count
not supported: enhanced erase
HW reset results:
CBLID- above Vih
Device num = 0 determined by the jumper
Checksum: correct
root@nykey:~#
|
For hdd I get:
Quote:
root@nykey:~# hdparm -i /dev/hdd
/dev/hdd:
Model=ST380011A, FwRev=3.06, SerialNo=3JV3V3J7
Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs RotSpdTol>.5% }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4
BuffType=unknown, BuffSize=2048kB, MaxMultSect=16, MultSect=off
CurCHS=65535/1/63, CurSects=4128705, LBA=yes, LBAsects=156301488
IORDY=on/off, tPIO={min:240,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:
* signifies the current active mode
root@nykey:~# hdparm -I /dev/hdd
/dev/hdd:
ATA device, with non-removable media
Model Number: ST380011A
Serial Number: 3JV3V3J7
Firmware Revision: 3.06
Standards:
Used: ATA/ATAPI-6 T13 1410D revision 2
Supported: 6 5 4 3
Configuration:
Logical max current
cylinders 16383 65535
heads 16 1
sectors/track 63 63
--
CHS current addressable sectors: 4128705
LBA user addressable sectors: 156301488
LBA48 user addressable sectors: 156301488
device size with M = 1024*1024: 76319 MBytes
device size with M = 1000*1000: 80026 MBytes (80 GB)
Capabilities:
LBA, IORDY(can be disabled)
bytes avail on r/w long: 4 Queue depth: 1
Standby timer values: spec'd by Standard
R/W multiple sector transfer: Max = 16 Current = ?
Recommended acoustic management value: 128, current value: 0
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 *udma5
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=240ns IORDY flow control=120ns
Commands/features:
Enabled Supported:
* READ BUFFER cmd
* WRITE BUFFER cmd
* Host Protected Area feature set
* Look-ahead
* Write cache
* Power Management feature set
Security Mode feature set
* SMART feature set
* FLUSH CACHE EXT command
* Mandatory FLUSH CACHE command
* Device Configuration Overlay feature set
* 48-bit Address feature set
SET MAX security extension
* DOWNLOAD MICROCODE cmd
* SMART self-test
* SMART error logging
Security:
supported
not enabled
not locked
not frozen
not expired: security count
not supported: enhanced erase
HW reset results:
CBLID- above Vih
Device num = 1 determined by CSEL
Checksum: correct
root@nykey:~#
|
|
|
|
06-02-2006, 01:58 PM
|
#5
|
Senior Member
Registered: Mar 2006
Distribution: SLACKWARE 4TW! =D
Posts: 1,519
Rep:
|
Hi,
Please remember I'm new to linux. I know enough know to get myself in trouble
But I have a very similar hard drive to yours, but I don't know what the differences are in my drive vs. yours.
It looks like after the 800JB-XXX where the XXX is the difference I'm talking of.
So what deviates my drive of 800JB-xxxxxx vs. WD800JB-00JJC0 I don't know. Maybe you can find out what that means at their site.
I can tell you with these settings, which slackware just did for me after installing. I didnt key any of these in. I'm on the stock kernel right now too, as I'm slowly reloading this pc.
The write caching and multi-sectors is off on yours. I've got an old laptop that slackware does not enable them on. I manually turned them on for my laptop and get a really big performance difference which I measured with 'hdparm -tT /dev/hda'
I wonder tho if slackware is detecting your IDE drivers correctly tho? I read somewhere before I got into tweaking this here for my laptop, and found that IDE drivers could be hindering what linux will let you run at.
Personally I read the man pages, and found them useless on this subject matter of hdparm and IDE channels for whatever it's worth.
I suggest finding the spec's for your drive not from Linux to be honest, but to go to Western Digital's web-site. They let you key in the make, model and serial number and tell you everything you need to know. I would say once you find that stuff out, then just change it in linux on the fly, if it works and no errors you're probably fine. Just be sure you know what you are doing before you make changes. This is definitely not a scenario where you simply want to copy other peoples settings, which is obviously why you posted
Good luck.
Here's my info for whatever it's worth:
bash: hdparm -i /dev/hdb
Quote:
/dev/hdb:
Model=WDC WD800JB-xxxxxx, FwRev=17.xxxxx, SerialNo=WD-slkfjsdkfdkf
Config={ HardSect NotMFM HdSw>15uSec SpinMotCtl Fixed DTR>5Mbs FmtGapReq }
RawCHS=16383/16/63, TrkSize=57600, SectSize=600, ECCbytes=40
BuffType=DualPortCache, BuffSize=8192kB, MaxMultSect=16, MultSect=16
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=156301488
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: device does not report version:
* signifies the current active mode
|
bash: hdparm /dev/hdb
Quote:
/dev/hdb:
multcount = 16 (on)
IO_support = 1 (32-bit)
unmaskirq = 1 (on)
using_dma = 1 (on)
keepsettings = 0 (off)
readonly = 0 (off)
readahead = 8 (on)
geometry = 9729/255/63, sectors = 156301488, start = 0
|
Quote:
bash: hdparm -tT /dev/hdb
/dev/hdb:
Timing cached reads: 1756 MB in 2.00 seconds = 878.00 MB/sec
Timing buffered disk reads: 140 MB in 3.01 seconds = 46.51 MB/sec
|
Last edited by Old_Fogie; 06-09-2006 at 10:48 PM.
|
|
|
All times are GMT -5. The time now is 09:39 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|