You are not logged in.
I bought a new harddisk for my laptop,WD 3200 BEVT.It works very well except that i notice it works under udma5,but it support udma6.
hdparm -i /dev/sda
/dev/sda:
Model=WDC WD3200BEVT-22ZCT0 , FwRev=11.01A11, SerialNo= WD-WXEY08FP0490
Config={ HardSect NotMFM HdSw>15uSec SpinMotCtl Fixed DTR>5Mbs FmtGapReq }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=50
BuffType=unknown, BuffSize=8192kB, MaxMultSect=16, MultSect=?16?
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=625142448
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 udma6
AdvancedPM=yes: unknown setting WriteCache=enabled
Drive conforms to: Unspecified: ATA/ATAPI-1,2,3,4,5,6,7
* signifies the current active mode
Also i get some messages
Mar 21 21:54:35 archlinux ata3: SATA max UDMA/100 mmio m512@0xf8407000 tf 0xf8407080 irq 22
Mar 21 21:54:35 archlinux ata4: SATA max UDMA/100 mmio m512@0xf8407000 tf 0xf84070c0 irq 22
Mar 21 21:54:35 archlinux ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Mar 21 21:54:35 archlinux ata3.00: ATA-8: WDC WD3200BEVT-22ZCT0, 11.01A11, max UDMA/133
Mar 21 21:54:35 archlinux ata3.00: 625142448 sectors, multi 16: LBA48 NCQ (depth 0/32)
Mar 21 21:54:35 archlinux ata3.00: configured for UDMA/100
Mar 21 21:54:35 archlinux ata4: SATA link down (SStatus 0 SControl 310)
Mar 21 21:54:35 archlinux scsi 2:0:0:0: Direct-Access ATA WDC WD3200BEVT-2 11.0 PQ: 0 ANSI: 5
Mar 21 21:54:35 archlinux Driver 'sd' needs updating - please use bus_type methods
Mar 21 21:54:35 archlinux sd 2:0:0:0: [sda] 625142448 512-byte hardware sectors (320073 MB)
Mar 21 21:54:35 archlinux sd 2:0:0:0: [sda] Write Protect is off
Mar 21 21:54:35 archlinux sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Mar 21 21:54:35 archlinux sd 2:0:0:0: [sda] 625142448 512-byte hardware sectors (320073 MB)
Mar 21 21:54:35 archlinux sd 2:0:0:0: [sda] Write Protect is off
Mar 21 21:54:35 archlinux sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Mar 21 21:54:35 archlinux sda: sda1 sda2 sda3 < sda5 sda6 >
Mar 21 21:54:35 archlinux sd 2:0:0:0: [sda] Attached SCSI disk
and this is my /etc/mkinitcpio.conf
# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run. Advanced users may wish to specify all system modules
# in this array. For instance:
# MODULES="piix ide_disk reiserfs"
MODULES="sata_sil"
# BINARIES
# This setting includes, into the CPIO image, and additional
# binaries a given user may wish. This is run first, so may
# be used to override the actual binaries used in a given hook.
# (Existing files are NOT overwritten is already added)
# BINARIES are dependancy parsed, so you may safely ignore libraries
BINARIES=""
# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in anyway. This is useful for config files.
# Some users may wish to include modprobe.conf for custom module options,
# like so:
# FILES="/etc/modprobe.conf"
FILES=""
# HOOKS
# This is the most important setting in this file. The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'modload' may be used in place of 'udev', but is not recommended
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
# This setup specifies all modules in the MODULES setting above.
# No raid, lvm2, or encrypted root is needed.
# HOOKS="base"
#
# This setup will autodetect all modules for your system and should
# work as a sane default
# HOOKS="base udev autodetect pata scsi sata filesystems"
#
# This is identical to the above, except the old ide subsystem is
# used for IDE devices instead of the new pata subsystem.
# HOOKS="base udev autodetect ide scsi sata filesystems"
#
# This setup will generate a 'full' image which supports most systems.
# No autodetection is done.
# HOOKS="base udev pata scsi sata usb filesystems"
#
# This setup assembles an pata raid array with an encrypted root FS.
# Note: See 'mkinitcpio -H raid' for more information on raid devices.
# HOOKS="base udev pata raid encrypt filesystems"
#
# This setup loads an lvm2 volume group on a usb device.
# HOOKS="base udev usb lvm2 filesystems"
HOOKS="base udev autodetect sata filesystems"
Any suggestion?
Last edited by ashunter (2009-03-23 05:17:35)
Offline
I wouldn't worry about that.
Your harddisk is connected via SATA so the UDMA modes don't matter anyway. And even if the theoritical maximum interface bandwidths (150 MB/s for SATA I and 100 MB/s for UDMA5) would matter for your setup -- the harddisk isn't capable of delivering more than 100 MB/s in the first place.
1000
Offline
You think this is a hardware problem?But i check it under win xp,and it works under udma6 mode.Perhaps this is not a serious problem,but i really want my harddisk works as it should.
Offline
It's not a problem. What does 'hdparm --direct -t /dev/sda' tell you?
1000
Offline
hdparm --direct -t /dev/sda
/dev/sda:
Timing O_DIRECT disk reads: 188 MB in 3.01 seconds = 62.55 MB/sec
Offline
See? That's a bit faster than my external 2,5" harddisk (55 MB/s, also 5400 RPM/320 GB), but still way too slow to be of significance here regarding a theoritical 100 MB/s limit. Even my quite recent 7200 RPM/500 GB 3,5" drives won't do more than 90 MB/s.
1000
Offline
Understood.The udma modes just set a limit of theoritical maximum interface bandwidth,which is higher than the real bandwidth even under udma5,so that's enough.Thanks for your replies.
Offline