875P HDD Performance w/Promise controller

I performed 3 tests on my FIS2R motherboard with the drives connected to the ICH5R controller and the Promise controller in various combinations. The ICH5R controller supports drives up to ATA 100 speeds, and the Promise controller supports drives up to ATA133 speeds (for parallel drives). HDD1 is a ATA100/7200RPM drive, and HDD2 is a ATA133/7200RPM drive.
I used both HD Tach v2.61 and Aida32 v3.61 for these tests. Both gave me similar results, so I'm posting only the results that I got from Aida in the quick linear mode.
Configuration 1:
      HDD1: ICH5R - 30.4 MB/s
      HDD2: ICH5R - 38.7 MB/s
Configuration 2:
      HDD1: ICH5R - 30.5 MB/s
      HDD2: Promise - 38.8 MB/s
Configuration 3:
      HDD1: Promise - 30.4 MB/s
      HDD2: Promise - 38.7 MB/s
When both drives were connected to the ICH5R controller (configuration 1), Aida confirmed that both HDDs were running at ATA100. This is what I would expect, but why is HDD2's benchmark 30% higher if they are both running at ATA100?
When HDD1 was connected to ICH5R and HDD2 was connected to Promise (configuration 2), both POST on bootup and Aida confirmed that HDD2 was running at ATA133. HDD1 was at ATA100. This is what I would expect, but why don't I see an improvement in the benchmark for HDD2?
When both drives were connected to the Promise controller (configuration 3), POST on bootup and Aida said HDD2 was running at ATA100. Why doesn't HDD2 run in the ATA133 mode? Is it because the Promise controller chooses the slower of the 2 drives as it's maximum rate?
Can anyone explain what's going on here?
Also, under Device Manager, I noticed that the Promise controller is identified as a SCSI device. I assume that this is normal.
MSI 875P FIS2R motherboard BIOS 1.4
CPU: 2.4 GHz P4/800 MHz
OS: W2K
RAM: 2X 512M Kingston Value DDR RAM, CL=3
Video: Radeon 9500 Pro
HD1: Maxtor 40G, 7200 RPM, ATA 100, NTFS formated
HD2: Maxtor 120G 7200 RPM ATA 133, FAT 32 formated
PS: Enermax 431W
Speakers: Logitech Z640

Quote
Originally posted by Keyan
You can check the WD easily - on boot, the Promise controller will report the drives attached and the DMA (hopefully 5) that they are in.
If using 875 FISR2, you only can choose SATA or Raid on promise IDE. So the the Promise controller will report SCSI only .
There could be about a thousand reasons why it's slower - slower write time on the WD, drive fragmentation, going across buses over PCI, some other program was aceesing one or both drives at the same time, the stars in the sky were aligned improperly , etc... Oh, and transferring a large file across paritions is ALWAYS slower than it is from drive to drive, you only have one read/write head working on a single drive, while you have 2 working when you go between 2 drives.
I also try to copy from partition to partition in my HItachi and speed also is very fast .
Now it is weird that changing the IDE channel is making both drives go into DMA 5 vs. one going to PIO....have you tried different cables?
I try 3 different cables and every cable can work on UDMA 5 Mode .

Similar Messages

Intel or promise controller?

I was wondering what controller I should use for my new system on a 875P NEO??
I have two SATA drives, and am wondering on which of the two controllers I should place them. The intel or the promise???
So how do they compare, cons and pros...

Quote
Originally posted by Mitch66
Quote
Intel RAID controller is integrated directly into the chipset since Promise is connected via PCI. It makes significant differencein peak bandwidth since PCI offers maximum of 133 MB/s ehich is less than SATA maximum speed 150MB/s. From this point of view Intel offers better performance.
Does not realy matter, -does it? My Raptor is never over 60 MB/s anyway. Has anyone got a drive delivering 133 MB/s+ ? :D
That is not really the point here, now is it?
The whole PCI bus maxes out on 133 MB/s, so if you run your raptor on the promise controller you only have 73 MB/s left.
The ICH5R is always the best choice on occasions like this.

[Athlon64] CAN'T SEE SINGLE SATA DRIVE / K8T NEO no Promise controller

I have a K8t NEO -the cheapskate version with no PROMISE SATA controller or on-board Firewire
I have been running on XP SP2 on 2 IDE drives, everything is ok. I added a SINGLE SATA drive and turned the VIA SATA controller on in BIOS. I did the MSI Live Update and have the latest VIA SATA driver, latest chipset, latest BIOS, latest EVERYTHING. At boot, the VIA SATA controller reports my Hitachi SATA as Channel 0 Primary" in the SATA devices table. Going into the SATA RAID menu it tells me "You can't make RAID with just one drive" which is true, of course. But the point is the controller SEES the drive.
I've run MSI Live Update and have the latest BIOS, latest SATA XP driver, latest EVERYTHING.
Windows XP doesn't see the SATA drive.
In XP I see a VIA RAID CONTROLLER in Hardware / Device Manager which is DISABLED. When I right-click then click ENABLE on the VIA RAID CONTROLLER the machine reboots immediately. I tried safe mode, same thing. I tried BIOS settings of "No PNP O/S Installed" and "Yes PNP O/S Installed" and reset the NVRAM. No change.
I think there must be an IRQ conflict.... I have a sound card (on-board sound is turned OFF in BIOS) and AGP video card, and that's it- no WiFi NIC or anything else to eat up IRQ resources. I use the Realtek on-board ethernet.
I tried my Windows 98 partition and that booted, detected the new hardware (VIA SATA) and I installed the driver from the MSI CD and Win 98 is happy with the SATA drive..... it sees the drive just fine.
How do I make Windows XP see the SATA drive?

Have you tried starting XP with CD and entering recovery, log on as admin and see if SATA drive is there? Remember to "F6" with a floppy drive of SATA drivers for
-XP-... I'm assuming you already have as you said all is uptodate. When the boot BIOS for the VIA SATA apprears and you press "TAB" I believe it is, you can mess with the SATA functions. Sorry if does not apply to your compy or you've already done all this.... BTW you CAN run a RAID array with one HDD, at least thats what I did on my Promise controller.
In my Device Manager under Disk drives it looks like this (notes bracketed are noting position):
Promise 1+0 Stripe/RAID0 SCSI Disk Device (Bus Number 0, Target ID 1, LUN 0 (G:\ 1-160GB IDE Seagate/notice ONE drive)
Promise 2+0 Stripe/RAID0 SCSI Disk Device (Bus Number 0, Target ID 0, LUN 0) (F:\ 2x200 SATA)
ST3160023A (Location 1 (1) VIA IDE D:\)
VIA SATA RAID 0 SCSI Disk Device (Bus Number 0, Target ID 0, LUN 0) (E:\ 2x120 SATA)
WDC WD800JB-00CRA1 (Location 0 (0) VIA IDE C:\)
Under the boards BIOS, is the SATA drive listed under the BOOT table??? In my system it lists the above 5 partitions (7 HDD's total), floppy, 2 CD/DVD drives, etc...
Oh also in Device Manager IS the VIA SATA controller appearing in the "SCSI and RAID controllers" tab??? I have set mine to just SATA before and of course now it says "VIA SATA RAID Controller"... for you it should read "VIA SATA Controller". Remember there are 2 different drivers for the SATA controller, one for SATA and one for SATA RAID. Look on your floppy disk or if you saved out the updated driver. I made a new floppy with the latest XP drivers. When booting from WINXP CD, and promted for "F6" and press it, later it will show you TWO different drivers after reading the floppy disk for XP. You obviously want the non RAID driver... hope that helps somewhat... g'luck

Tryng to format Raid 1 (Mirror) array on Promise controller

Ok, I installed the two brand-new, indentical hard drives, booted up the computer, the promise utility noticed that I had two drives plugged in with the promise controller set to RAID mode, so it ran the thing and I set the array to security (aka: Raid 1) so then it does it, and says I can reboot. Now, the manual said that the only step I have to complete now to finish it is to run FDISk or whatever to format the "drive" (Since the array is treated as one drive). I do have to do this, but hwo do I do it? I run Win 2000 Pro if that helps at all. I am trying to make it an NTFS filesystem however, so would FDISk even work? I thought FDISk only makes FAT32 file systems... Anyway, what do I do to finish setting up my RAID 1 array and get to finally use it?
Doggonit

I use Win 2000 Pro and there is no Maintenance or Performance in the Control Panel. I tried reinstalling the drivers and even uninstalling the drive as it showed up in the Device Manager under drisk drives. It simply came back the same way as before, as some 1x2 Promise RAID1 SCSI drive that was functional etc, but I dont know hot to format it and I can't see it in Windows Explorer, or in the BIOS, altough during bootup it shows the Array every time and if I check out the Promise array manager (Ctrl+F) I can see it and it is functional and all that.
Ok, this is it:
In the device manager (Control Panel->System->Hardware->Device Manager) under the disk drives menu I see my working 80Gb drive that the OS is on, and has its "Location" as: " Location 0 (0) " and then there is the:
Promise 1X2 Mirror/RAID1 SCSI Disk Drive Device
In the properties of this it says: Bus Number 0, Target ID 0, LUN 0
Also, for the Write cache, the box is unchecked, as in not enabled, and it is grayed over, so I can't even change it. I guess this is beacuse the drive is not yet formatted and cannot be written to yet, right?
Is there a conflict between the 80GB drive and the RAID1 Array on the BIOS level that I should fix somehow? Is the Location of the 80GB one be 1 or do those numbers for the array have to be 1 ?
I think I really wont be able to get this to work without some major help. Now I see why IDE drives still rule. They are more accesible from the BIOS.
Doggonit

Promise controller acting strange, known issue?

at this point, i tracked all of my problems down to my promise controller..
while my hd's are on the promise controller, raid0, no go on the win2k install, and strange things with xp, like slow datatransfer..
but there are loads and loads more strange problems.
now i've connected my s-ata hd's to the via controller, using softwre raid0, but no problems anymore..
is it a known problem with the promise controllers?

Hi fboecom
Yes, you need Via IDE ( PATA IDE) enabled otherwise your CDs and IDE HDDs won't function.
To use Via SATA, the S ATA IDE needs enabled for SATA1 and 2.
I see I am going to have to do some work on the promise, it may well be the IDE3 connector works, except for optical drives. Ser1 & Ser2, I have had working in conjunction with the Via. But that was when originally trying to set up the Maxtors. I think I may have had the promise either disabled or on SATA. I will be ordering stock this week, so I will get another SATA drive and see just what works.
By the time you buy another disk next year, Promise will have rewritten their drivers, they will have to for new MS systems in pipeline, plus new 939 pin chips coming soon and Mobos to match.
Read this link, if you want to see how Merlinen got, is it 10 HDDs to run, I#m still thinking about his next advance.
https://forum-en.msi.com/index.php?threadid=44351&sid=
Enjoy
jocko

Raid 0 SATA on Promise Controller, Sata drive on Intel?

Hi all, wondering if I can run this setup:
(Specs in my Sig)
2 SATA WD Raptors, RAID 0 on the Promise controller
1 Maxtor 80Gig SATA on the Intel Controller
Is this an option or not?
I am setup on the Raptor's already and would like to install another HD on the Intel if it can be done like mentioned.
Thx for the help!
/D

Ok, I connected to the Intel SATA 1 plug and all is fine. WinXP found the drive, installed it and away I go.
Only other question I have..Is there a specific driver I should use for it now?
It shows up in the Device Manager as Follows in 2 places:
Disk Drives
Maxtor 6Y080M0
and
IDE ATA/ATAPI Controllers
Intel(R) 82801EB Ultra ATA Storeage Controllers
Intel(R) 82801EB Ultra ATA Storeage Controllers
Primary IDE Channel
Primary IDE Channel
Secondary IDE Channel
Secondary IDE Channel
I'm not sure if it should show under SCSI and RAID Controllers.
Blazer: That link is dead. I would like to read the article if ya can find it again. Thx
Dirtnapper: I read another post here somewhere about what you are looking to do. It can't be too far back in the pages, possible in a link in the RAID guide at the top.
/D

Promise controller setting for added harddrive

Hi,
I have 2 SATA hard drives (non-raid) on the 1st channel of my board (Intel controller). My XP boot drive is on drive 0 and other stuff on drive 1. I have an addition SATA drive (non raid) I installed on the 2nd channel (Promise controller). To get it to start I set it as RAID on drive 3. My question is, should I set the onboard Promise back to SATA or leave it as RAID. It works now as is. I was going by the FAQ on this site, but I did not see it say anything about setting it back. Thanks.

A follow up...
When I set the Promise Controller back to AS SATA, Windows "lost" the drive. It placed its yellow sign next to Promise Controller in device manager and the Disk Manager would not show the drive. I tried uninstalling the Controller in device manager and rebooted. Same.. yellow flag. I tried updating the driver to the latest (downloaded from MSI). It said something about the driver was reverting to the old one (which didn't work). Hmmm, so I updated the driver to the one from the Install CD that came with the board.. Success. All is working again. Odd, but now working. I may try to redownload the drivers and update but it is working, so I will leave it for now. Ihope this may help others.

Disable Promise controller on K8T NEO?

Does anyone know how to disable the Promise controller on the K8T NEO-FIS2R? I have disabled it in bios but I still see the Promise screen when I boot, or am I the only one that has this problem?

Never mind, I found the answer in another post

Promise controller is buggy!

I used Promise for about 3 months now. No problems with data integrity but it has definately some bad influence on the memory (controller).
Since the Promise controller was responsible for failing the MS Memory diagnostics util (http://oca.microsoft.com/en/windiag.asp) and because I got some overal instability problems, I switched back to the VIA controller for my RAID0.
MS Memory diagnostics now runs the tests without problems as do Memtest86 and Prime95. So there IS definately something WRONG with the promise controller!
Perhaps it has caused more problems (for example my freezing network connection). I'll test that in the next few days.
O, about the speed? There is almost no difference between the two. VIA is about 2Mb/s faster as Promise, in Sandra 32bit.
I like the 'passed' word.

Quote
I think the rule should be go with whatever is the most stable.
I agree, and if I don't had any other problems I would had stay on the Promise cause I indeed never had instability issues with my raidset. And VIA seems just as stable as Promise with that advantage that Memdiag runs now like a charm. And perhaps my NIC too.

Promise controller

I was wondering if I can use the Promise controller as a regular IDE controller. I have 2 CDRWs and 3 HDs. The only problem is that the cables cant reach.

sorry but im not really sure. if the promise controller is enabled and you plug it in i don't see why it wouln't work.
try plugging in just one drive as a master on the end of the cable and tell us if it works

Intel Ich5r -- Promise Controller

PROBLEM -
I have 2 SATA drives under the Intel ICH5R controller and one extra SATA drive running in slot 3 that is eing controlled by the probise controller. The goal is to have all drives under one controller, Intel or Promise. At first i wanted to have them all under the ICH5R controller but have found this doesnt work. Now i am wanting to know if it is possible to have all 3 drives running under the promise controller and if so then is it possible to simply transfer the current raid setup from the intel to the promise without having to start from fresh.

The purpose was not putting the 3rd drive intro raid but to have that drive run independently as its own entity under the same controller to eliminate loading up 2 controllers as it adds time to load up and also to resources.. Thats what im trying to reduce as this system takes a long time to load.

Survey - Promise controller and RAID 1

Who out there is running RAID 1 with and onboard Promise controller? I have been been battling this for nearly a month (link). I started out by following the MSI manual to the letter, then on to online suggestions, no luck.
For anyone who's successfully running RAID 1, I'd really be interested in the following survey info (mine included):
Mobo: (MS-6380 v1.0)
Promise Controller: (FastTrak100 - 20265R)
OS: (Win2k SP3)
Drives: (WD400BB)
Filesystem(s) on drives: (NTFS)
OS on RAID array?: (yes)
Array created from existing OS install?: (yes - tried both)
Setup difficulties?: (yes, not done yet)
TIA,
Danny

Been using RAID-1 here for quite some time now, no problems at all. Even had a Maxtor fail and recovery/rebuilding of the array was childs play.
Mobo: KT3 Ultra ARU
Promise Controller: PDC20276
OS: win 98-SE
Drives: two WD800JB
Filesystem(s) on drives: FAT32
OS on RAID array?: NO
Array created from existing OS install?: YES
Setup difficulties?: NO

K6 Delta Promise controller problem

I have a little configuration there:
PSU: 450W
MSI KT6 Delta-FIS2R
512MB DDR400 (CL3) Memory (not in compatibility list)
Athlon XP2600+
VGA Club3D MX440 64MB
CDRW/DVD attached in VIA PATA (Cyberdrive 32x12x48, Toshiba 16x48)
1 x 36GB SATA WD Raptor attached in VIA SATA controller
2 x 160GB SATA Maxtor 8MB 7200rpm attached in Promise controller (not in RAID mode)
OS: Windows XP, SP1, with a couple of Updates through Windows update
The problem is that, my two Maxtor drives attached to Promise controller, get a Scandisk EVERY time I boot. This also happened to my WD, but after updating VIA4-1, drivers and BIOS, this problem was fixed.
When I try to update Promise's drivers with the latest ones (378_55), they just don't work (The device gets an yellow "!" symbol, in the device manage).
The machine works just fine in all other aspects. It's only that problem that makes my nerves break. Any suggestions?

Quote from: Bas on 17-December-11, 01:00:24
The Promise BIOS is part of the motherboard BIOS, you can't flash it separate.
Thats's what I thought.
Quote from: Bas on 17-December-11, 01:00:24
I doubt you ever used the promise else it would have recognized the drives.
Just turn it off and use the SB600, it's faster anyway.
You are probably right about me using the SB600 as I as very unfamiliar with the board, and both RAID controllers looks almost the same when POST-ing
What I don't understand is why they put in an rather advanced RAID controlled like the T3 when the SB600 one was faster anyway? Would it not make more sense that the system would be faster with two separate controllers working on separate disks?

Slow hdd performance

Ok I did some research and still can't figure out why writing/reading speed is so slow in practice
hdparm -tT /dev/sda
/dev/sda:
Timing cached reads: 1012 MB in 2.00 seconds = 506.11 MB/sec
Timing buffered disk reads: 336 MB in 3.01 seconds = 111.58 MB/sec
With dd I get ~10 MB/s (dd if=/dev/zero of=/test bs=100M count=10)
Internally copy from mc 5-6 MB/s
I did multiple tests
What is going on here?
hdparm -I /dev/sda
/dev/sda:
ATA device, with non-removable media
Model Number: ST31000520AS
Serial Number: 5VX0WRYD
Firmware Revision: CC32
Transport: Serial
Standards:
Used: unknown (minor revision code 0x0029)
Supported: 8 7 6 5
Likely used: 8
Configuration:
Logical max current
cylinders 16383 16383
heads 16 16
sectors/track 63 63
CHS current addressable sectors: 16514064
LBA user addressable sectors: 268435455
LBA48 user addressable sectors: 1953525168
Logical/Physical Sector size: 512 bytes
device size with M = 1024*1024: 953869 MBytes
device size with M = 1000*1000: 1000204 MBytes (1000 GB)
cache/buffer size = unknown
Nominal Media Rotation Rate: 5900
Capabilities:
LBA, IORDY(can be disabled)
Queue depth: 32
Standby timer values: spec'd by Standard, no device specific minimum
R/W multiple sector transfer: Max = 16 Current = 16
Advanced power management level: 192
Recommended acoustic management value: 254, current value: 254
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6
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:
* SMART feature set
Security Mode feature set
* Power Management feature set
* Write cache
* Look-ahead
* Host Protected Area feature set
* WRITE_BUFFER command
* READ_BUFFER command
* DOWNLOAD_MICROCODE
* Advanced Power Management feature set
Power-Up In Standby feature set
SET_FEATURES required to spinup after power up
SET_MAX security extension
* Automatic Acoustic Management feature set
* 48-bit Address feature set
* Device Configuration Overlay feature set
* Mandatory FLUSH_CACHE
* FLUSH_CACHE_EXT
* SMART error logging
* SMART self-test
* General Purpose Logging feature set
* WRITE_{DMA|MULTIPLE}_FUA_EXT
* 64-bit World wide name
Write-Read-Verify feature set
* WRITE_UNCORRECTABLE_EXT command
* {READ,WRITE}_DMA_EXT_GPL commands
* Segmented DOWNLOAD_MICROCODE
* Gen1 signaling speed (1.5Gb/s)
* Native Command Queueing (NCQ)
* Phy event counters
Device-initiated interface power management
* Software settings preservation
* SMART Command Transport (SCT) feature set
* SCT Long Sector Access (AC1)
* SCT LBA Segment Access (AC2)
* SCT Error Recovery Control (AC3)
* SCT Features Control (AC4)
* SCT Data Tables (AC5)
unknown 206[12] (vendor specific)
Security:
Master password revision code = 65534
supported
not enabled
not locked
frozen
not expired: security count
supported: enhanced erase
188min for SECURITY ERASE UNIT. 188min for ENHANCED SECURITY ERASE UNIT.
Logical Unit WWN Device Identifier: 5000c500250e4711
NAA : 5
IEEE OUI : 000c50
Unique ID : 0250e4711
Checksum: correct
smartctl -a /dev/sda
smartctl 5.42 2011-10-20 r3458 [i686-linux-3.2.13-1-ARCH] (local build)
Copyright (C) 2002-11 by Bruce Allen, [url]http://smartmontools.sourceforge.net[/url]
=== START OF INFORMATION SECTION ===
Model Family: Seagate Barracuda LP
Device Model: ST31000520AS
Serial Number: 5VX0WRYD
LU WWN Device Id: 5 000c50 0250e4711
Firmware Version: CC32
User Capacity: 1,000,204,886,016 bytes [1,00 TB]
Sector Size: 512 bytes logical/physical
Device is: In smartctl database [for details use: -P show]
ATA Version is: 8
ATA Standard is: ATA-8-ACS revision 4
Local Time is: Fri Mar 30 00:45:54 2012 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 623) seconds.
Offline data collection
capabilities: (0x73) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
No Offline surface scan supported.
Self-test supported.
Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 219) minutes.
Conveyance self-test routine
recommended polling time: ( 2) minutes.
SCT capabilities: (0x103f) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.
SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 119 099 006 Pre-fail Always - 216824470
3 Spin_Up_Time 0x0003 096 096 000 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 526
5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 3
7 Seek_Error_Rate 0x000f 077 060 030 Pre-fail Always - 58496816
9 Power_On_Hours 0x0032 084 084 000 Old_age Always - 14481
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 037 020 Old_age Always - 265
183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0
184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0
187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0
188 Command_Timeout 0x0032 100 098 000 Old_age Always - 8590065682
189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0
190 Airflow_Temperature_Cel 0x0022 070 054 045 Old_age Always - 30 (Min/Max 18/31)
194 Temperature_Celsius 0x0022 030 046 000 Old_age Always - 30 (0 16 0 0 0)
195 Hardware_ECC_Recovered 0x001a 039 021 000 Old_age Always - 216824470
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x003e 200 199 000 Old_age Always - 9
240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 152454159153810
241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 3670022033
242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 448914133
SMART Error Log Version: 1
No Errors Logged
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed without error 00% 14007 -
# 2 Extended offline Interrupted (host reset) 00% 13651 -
# 3 Extended offline Aborted by host 90% 8256 -
# 4 Short offline Completed without error 00% 310 -
SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
cat /etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
devpts /dev/pts devpts defaults 0 0
shm /dev/shm tmpfs defaults 0 0
/dev/sr0 /mnt/cd iso9660 ro,user,noauto,unhide 0 0
#/dev/dvd /media/dvd auto ro,user,noauto,unhide 0 0
#/dev/fd0 /media/fl auto user,noauto 0 0
UUID=934647db-14d1-4641-820c-e42c0f63c0e5 /boot ext2 defaults 0 2
/dev/mapper/lvm-home /home ext4 defaults,noatime 0 2
/dev/mapper/lvm-root / ext4 defaults,noatime 0 1
/dev/mapper/lvm-swap swap swap defaults 0 0
tmpfs /tmp tmpfs noatime,nodev,nosuid,noexec,size=1536M 0 0
/dev/mapper/data /mnt/data ext4 acl,user_xattr,noatime 0 2
dmesg | grep ata
[ 0.000000] BIOS-e820: 000000001f5d7000 - 000000001f5d9000 (ACPI data)
[ 0.000000] BIOS-e820: 000000001f600000 - 000000001f608000 (ACPI data)
[ 0.000000] Memory: 481496k/515072k available (3766k kernel code, 31608k reserved, 1441k data, 524k init, 0k highmem)
[ 0.000000] .data : 0xc04ad9d5 - 0xc06160c0 (1441 kB)
[ 14.174799] Write protecting the kernel read-only data: 1112k
[ 14.661110] libata version 3.00 loaded.
[ 14.684788] ata1: SATA max UDMA/133 abar m1024@0xffe40000 port 0xffe40100 irq 45
[ 14.684809] ata2: DUMMY
[ 14.684826] ata3: SATA max UDMA/133 abar m1024@0xffe40000 port 0xffe40200 irq 45
[ 14.684842] ata4: DUMMY
[ 14.685022] ata_piix 0000:00:1f.1: version 2.13
[ 14.685081] ata_piix 0000:00:1f.1: PCI INT A -> GSI 18 (level, low) -> IRQ 18
[ 14.685243] ata_piix 0000:00:1f.1: setting latency timer to 64
[ 14.699846] scsi4 : ata_piix
[ 14.705173] scsi5 : ata_piix
[ 14.715618] ata5: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0xf100 irq 14
[ 14.715642] ata6: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xf108 irq 15
[ 15.006827] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 15.008016] ata1.00: ATA-8: ST31000520AS, CC32, max UDMA/133
[ 15.008034] ata1.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 31/32)
[ 15.009380] ata1.00: configured for UDMA/133
[ 15.013441] ata3: SATA link down (SStatus 0 SControl 300)
[ 40.720777] EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts: (null)
[ 59.246412] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
[ 59.339759] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: acl,user_xattr
EDIT: Replaced quote with code - ngoonee
EDIT: Ok, sorry - miskoala
Last edited by miskoala (2012-03-30 08:18:09)

I booted this drive from another computer (Asrock M3A770DE mobo) and works fine, speed with dd was ~100MB/s
I also update bios on my first computer with Intel D945GSEJT (there is selected AHCI mode) still the same transfers with dd (~10Mb/s)
I have no idea what to do with it now
EDIT:
More tests with other hdd (Samsung HD502IJ), dd on mounted NTFS partition:
Intel D945GSEJT booted from Archlinux iso:
hdparm: ~75 MB/s
dd: ~10 MB/s
Intel D945GSEJT booted from Archlinux iso, HDD connected to PCI SATA controller (Promise 378):
hdparm: ~60 MB/s
dd: ~10 MB/s
Asrock M3A770DE booted from Archlinux iso:
hdparm: ~87 MB/s
dd: ~76 MB/s
Asrock M3A770DE booted from Archlinux iso, HDD connected to PCI SATA controller (Promise 378):
hdparm: ~81MB/s
dd: ~76 MB/s
What is broken on D945GSEJT?
Last edited by miskoala (2012-03-30 13:47:23)

Extremely Poor Pacman/HDD Performance

This is a problem I have been having for a while now.
After about a month after a clean Arch install, Pacman's performance, and the performance of the OS itself, severely degrades to the point of operations that took seconds taking minutes.
After a fresh install, Pacman would take about 10 seconds or so to display any matches to a search I preform. The computer now starts accessing the HDD for about 5 or 6 minutes per search, and so intensively that the rest of the computer comes to a halt while Pacman is doing it's job.
This HDD activity that completely chokes the computer is becoming more apparent in other operations as well. Firefox (which is an enormous memory hog, I know) will kill the machine. Even opening an xterminal can take about 6 or 7 seconds after some intense HDD activity.
The computer is old, a 10GB HDD, 64MB of RAM, and a 1Ghz processor, but I don't think it should be having such a hard time with the hard disk activity as it is. I run xorg7 and openbox. The only other graphical elements on that are a wallpaper and a simple panel program. There aren't many daemons running besides your run-of the-mill stuff like syslog and dbus.
I've already taken the steps in the "improving pacman's performance" article on the wiki page, but no dice. Can anyone help?

The dmesg you posted is a common problem with IDE devices in the latest kernels due to the lack of recognition 0f the 80-wire cable for UDMA. The normal use of 80-wire cables in IDE was to accomodate faster transfers and as such was a weak workaround for crosstalk problems.
In present kernels, the 80-wire system is not recognized therefore the speed of performance is degraded to UDMA 2.
See the following URL for a kernel patch force for 80-wire:\\
http://pixca.net/2008/02/03/limited-to-udma33-due -to-40-wire-cable/
The results of the install to kernel are presented, but no verifiable reports have been given for the patch from other users. Two answers by the same poster give no confidence in whether he loaded the kernel fix since his dmesg makes no reference to the 80-wire libata changes as does the original posted data.
This seems to affect every IDE interface in different ways and is based on not requiring 80-wire confirmation in scsi/sata since it is different than IDE interface and controller.
This may be causing your slowdowns.....give it a second look..

875P HDD Performance w/Promise controller

Similar Messages

Maybe you are looking for