Paul Hartman wrote:
On Tue, Jun 1, 2010 at 12:26 AM, Dale<rdalek1...@gmail.com>  wrote:
I am in the process of moving my OS from drive to drive and thought I would
test to see which drive is the fastest.  I got some strange results when I
tested them   One drive is MUCH slower than the others on the buffered disk
reads but I can't see any reason why that would be so.
Check dmesg to see if the drives show any differences...

If they are SATA drives check to see if there is a jumper which forces
it into "compatibility" mode, slow mode, something like that...

If they are SATA and you use an intel chipset motherboard check to be
sure that the SATA header of that drive is set to AHCI and not IDE
mode...

Those are just ideas, things I have encountered. :)


This is from dmesg:

smoker-new ~ # dmesg | grep hda
hda: Maxtor 6E040L0, ATA DISK drive
hda: host max PIO5 wanted PIO255(auto-tune) selected PIO4
hda: UDMA/133 mode selected
hda: max request size: 128KiB
hda: 78156288 sectors (40016 MB) w/2048KiB Cache, CHS=65535/16/63
hda: cache flushes supported
 hda: hda1 hda2 < hda5 hda6 hda7 hda8 hda9 hda10 >
smoker-new ~ # dmesg | grep hdb
hdb: WDC WD800BB-00DKA0, ATA DISK drive
hdb: host max PIO5 wanted PIO255(auto-tune) selected PIO4
hdb: UDMA/100 mode selected
hdb: max request size: 512KiB
hdb: 156301488 sectors (80026 MB) w/2048KiB Cache, CHS=16383/255/63
hdb: cache flushes supported
 hdb: hdb1 hdb2 < hdb5 >
smoker-new ~ # dmesg | grep hdc
hdc: Maxtor 6Y080P0, ATA DISK drive
hdc: host max PIO5 wanted PIO255(auto-tune) selected PIO4
hdc: UDMA/133 mode selected
hdc: max request size: 128KiB
hdc: 160086528 sectors (81964 MB) w/7936KiB Cache, CHS=65535/16/63
hdc: cache flushes supported
 hdc: hdc1 hdc2 < hdc5 hdc6 hdc7 >
REISERFS (device hdc6): found reiserfs format "3.6" with standard journal
REISERFS (device hdc6): using ordered data mode
REISERFS (device hdc6): journal params: device hdc6, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
REISERFS (device hdc6): checking transaction log (hdc6)
REISERFS (device hdc6): Using r5 hash to sort names
REISERFS (device hdc7): found reiserfs format "3.6" with standard journal
REISERFS (device hdc7): using ordered data mode
REISERFS (device hdc7): journal params: device hdc7, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
REISERFS (device hdc7): checking transaction log (hdc7)
REISERFS (device hdc7): Using r5 hash to sort names
Adding 976712k swap on /dev/hdc5.  Priority:-1 extents:1 across:976712k
Adding 976712k swap on /dev/hdc5.  Priority:-1 extents:1 across:976712k
Adding 976712k swap on /dev/hdc5.  Priority:-1 extents:1 across:976712k
Adding 976712k swap on /dev/hdc5.  Priority:-1 extents:1 across:976712k
smoker-new ~ #

It appears that hdb is using UDMA/100 but it has always done that. It's a older drive. This drive used to get somewhere in the 40Mb/sec range tho. I want to say it used to be about 47Mb/sec or so.

All three of those drives are ATA. I have a SATA drive but I didn't list it since it is working good and fast all things considered. It's hooked to a PCI card.

Thoughts?

Dale

:-)  :-)

Reply via email to