Not all WD6400AAKS' are created equal...

[XtremeTiramisu]

Fixed this problem by using Hitachi's Feature tool: http://www.hitachigst.com/hdd/support/download.htm I burned the .iso, booted it, changed it - it's pretty easy to figure out the utility - and voila!

Now I get 12.2ms seek time with the highest numerical AAM setting. Seeks are definitely more noticable though but I don't mind HD seeks, I suppose I could mess around with it a bit and find a better noise/performance balance but I'm not going to bother right now. It also seems to 'stick' after reboots and power downs. I just hope this doesn't somehow damage the drive :p I know it shouldn't because it's not running out of spec or anything but it almost feels like overclocking the HD versus how it was before

If you're the same person who suggested the Ftool on NCIX forum, let me tell you that it's not working for me.
I tried to burn the ISO to my CD-RW and also tried to burn the ISO to a bootable CD-RW and I still cannot use ftool. If I try to run ftool under command prompt, it says the application is 16bit, so it's not compatible with 32bit or 64bit windows.

The system will boot with the bootable CD-RW that I just created with the ISO but I still can't use the ftool.........
Please let me know how you got it to work, with a step by step guide please.

[bullseye81]

I burned v210 of the feature tool using nero. The files and DOS folder show up correctly in explorer, however its not a bootable CD - "Non system drive found"

What did you use to burn the image, and were there any special settings to make it bootable?

[Pudi]

I burned v210 of the feature tool using nero.

Try to use PowerISO or Alcohol 120% instead, nero suxx badly for burning ISO imho

[XtremeTiramisu]

I use the newest Nero 8 Ultra edition to burn the ISO.
After it's burned, I set the system to boot from D drive. But as soon as the system reads the CD after about 10 sec, it reboots itself...very weird.
I also tried to burn the samsung utiltity ISO to the same CD-RW and the system will boot and read its content. But unfortunately, I still can't use the samsung utiltity.......
It's the god damn compatibility issue all along...I think the easiest solution would be a windows software based utility to set AAM. Like HD Tune, if they come up with a version that's RAID/AHCI intel based driver friendly, then it's all good. I'm sure this can be done. By this day and age, I really hate to deal with DOS and its commands. With the very only exception when I use it to flash the bios using AFUDOS. That's a great tool to convert the older Maximus Formula to the next generation X48 Rampage Formula with one simple string of command.
Ok rant is over...
and I've my eyes on the upcomming WD Caviar Black 750GB/1TB new HD

[MACMAC]

Ok rant is over...
and I've my eyes on the upcomming WD Caviar Black 750GB/1TB new HD

Might want to stick with the 1TB model, since the 750GB is based on the older 250GB/platter design

[MadMan007]

I didn't do anything special. Yes I had 'no boot disk' error because my system is set up with AHCI and that probably is why yours reboots. I've run in to non-booting before a few times with other iso's. It's not that hard to work around, just set the CD SATA/IDE controller to IDE or compatible mode to run the utility then change it back. It shouldn't hurt any RAID configurations because you're just booting the DOS program not changing the RAID configuration itself. I'd done the same when I did have a RAID configuration on an ICH9R and when I switched back to RAID the RAID arrays were still there and working fine - it's the same thing as when the BIOS gets reset to defaults. Don't hurt me if it hoses a RAID configuration though. :P Or just use an IDE optical drive. I know that isn't step-by-step instructions but that's the fix for problems booting off the iso, there really aren't many steps, just burn the iso, boot off the CD (change AHCI/RAID to regular IDE if needed), change the AAM, reboot to BIOS and change back to AHCI/RAID, reboot to OS and profit.

There may be a way to make it work with a BartPE CD using the standard drivers but you'd probably have to change the SATA/IDE mode anyway and the Feature Tool may not run in that environment. Another option might be to make a bootable DOS USB drive but I did it with the CD because it was the easiest way to try first.

And no I didn't put this info on NCIX forums, just ocforums. I always use some variation of 'Madman' as my nick.

Here are screenies:
Before-


After-

[MadMan007]

Might want to stick with the 1TB model, since the 750GB is based on the older 250GB/platter design

I don't think it is, check the .pdf spec sheet:
http://www.westerndigital.com/en/lib...879-701276.pdf

heads/disks
1TB 6/3
750GB 5/3

So they are probably just short-stroking the 750GB model with the same platters. If the 750GB used 3 250GB platters it would need 6 heads too. All the other performance numbers are the same.

[Gogeta]

Thanks for the update, MadMan007. I'll give this tool a shot tonight...my 6400AAKS currently has access times around 15ms as well.

I'm hoping you can clarify on one thing you mentioned, however. What do you mean by the drive seems to "stick" after reboots and power offs?

[XtremeTiramisu]

Thanks a lot MadMan007.
I'm actually using AHCI config like you! I'm not using RAID if you had checked my sig.
I've a single WD5000AAKS drive setup in AHCI.
And you were absolutely right, I had to change AHCI config back to IDE in BIOS to have a successful boot from the burned .iso CD-RW.
In AHCI mode, the system would reboots as soon as it reads the disc upon boot.
I can boot with the CD-RW and use ftool to change AAM value to highest performance level 254.
I ran the HD Tune Pro AAM test in both Enabled set to 254 performance mode and Disable mode (254 by default), I get the same score of 13.4ms
Not a huge improvement becouse my particular WD5000AAKS was originally 13.7ms by default (128).
However my other WD5000AAKS has 15.7ms by default and I'll do the same to see if there will be greater seek time improvement.
One thing I've found is my other WD5000AAKS with slower seek time has higher avg read: 74mb/s
The faster seek time in ms on my other WD5000AAKS has a slower avg read : 68mb/s

[MadMan007]

Thanks for the update, MadMan007. I'll give this tool a shot tonight...my 6400AAKS currently has access times around 15ms as well.

I'm hoping you can clarify on one thing you mentioned, however. What do you mean by the drive seems to "stick" after reboots and power offs?

What I mean is the faster AAM setting remains in effect after reboots. Somewhere or another I read about WinAAM settings not staying after reboots or power downs so the person had to run WinAAM every time they booted. It could have been old outdated info though.

Tiramisu - STR shouldn't be affected by AAM much, it's primarily a function of rotational speed and areal density, in other words how fast data can be streamed sequentially off the platters. For your two drives I really don't know, they may be different firmwares I know that's affected other drives such as the Seagate 500GB 7200.10

[XtremeTiramisu]

MadMan007:

You're right about the AAM setting is not staying permanently after reboot or power down. I set the AAM to disabled and exit ftool. After a reboot, I enters ftools again to check the AAM setting and it's reverted back to Enabled at 254.
I've no idea why m WD5000AAKS is now set to Enabled but performance mode at 254 by default?!
Also like I've mentioned earlier, I must reboot the system after I changed AAM setting and exit ftool to go into bios to change IDE mode back to AHCI.
So I don't know if Ftool is useful or useless in my case...

XT

[MadMan007]

Hmm, I'd have to boot the CD again to look at the exact options. I know there is an 'OK' or maybe 'Save' button at the bottom of the AAM screen in Ftool. I do believe though that disabling it after saving it to 254 or another setting would just keep that setting because it gets overwritten in the drive firmware. In other words, you've changed it so that 254 is the default or disabled setting. Why it reverts to enabled I don't know but if you want to have a lower AAM setting just use that and leave it enabled I guess.

For me it stays permanently but I just left it enabled at 254.

[XtremeTiramisu]

Hmm, I'd have to boot the CD again to look at the exact options. I know there is an 'OK' or maybe 'Save' button at the bottom of the AAM screen in Ftool. I do believe though that disabling it after saving it to 254 or another setting would just keep that setting because it gets overwritten in the drive firmware. In other words, you've changed it so that 254 is the default or disabled setting. Why it reverts to enabled I don't know but if you want to have a lower AAM setting just use that and leave it enabled I guess.

For me it stays permanently but I just left it enabled at 254.

Yeah, both of my WD5000AAKS drives in two different systems are permanently set a Enabled 254 performance mode. One has 13.4ms seektime which is the one listed in my sig. The other one went down to exactly 14.0ms from 15.7ms originally; no noticeable difference in noise. Both drives are using the same 12.0 firmware but the slower 14.0ms drives is hooked up to a P5K-Deluxe. Both system configurations have their PCI-E freq. set at 110. What I'm not so sure of is whether the difference in ms comes from the drive itself (both have the same firmware) or the motherboard. But it makes sense to me that my Maximus Formula with Rampage 0403 bios shows slightly faster HDD benchmark than P5K-Deluxe.

XT

[Gogeta]

What I mean is the faster AAM setting remains in effect after reboots. Somewhere or another I read about WinAAM settings not staying after reboots or power downs so the person had to run WinAAM every time they booted. It could have been old outdated info though.

Haha, for some reason I thought you were talking about a physical aspect of the drive "sticking" such as the read head with a more aggressive AAM setting...I was quite skeptical.

Reading it again now it makes perfect sense.

[Eluder]

I got one of these today and man are they fast! Didn't have to touch AAM, nor did I bother checking it since it looks like it's set to performance mode already based on seek times.

I did some tests using HDTune 2.55 while the drive was in an Antec MX-1 eSATA enclosure, and then after cloning my main drive to the WD6400AAKS, directly connected to the SATA controller on an Asus Maximus motherboard.

Here are the snapshots.

[MACMAC]

It's odd/anger-inducing that the 'original' firmware is SO much faster than the new one

[icywater]

i bought 4 WD6400AAKS, 2 dated 18 of march 2 dated 18 of april, the one that dated april has 18ms access time. I used features to change the AAM to 254 and everything is ok.

here is my 200Gb raid 0




and my raid 5 of the left over space

[Eluder]

It's odd/anger-inducing that the 'original' firmware is SO much faster than the new one

I can check which firmware my drive has, but I know my build date is June 3, 2008, so it's a brand new drive. 00A7B, is not the firmware version of the drive though...

[importpsycho]

I think I got it...
disabling AAM complete didn't do anything
but enabled high seemed to work
but why is mim transfer rate so crap?



p.s. does partitioning has anything to do with HD speed?
right now it's 3xx and 3xx, with only first partition formated, couldn't wait for 640 to format....

[Soulburner]

Guys when I use the Hitachi Tool it can't find any drives connected.

If anyone has an idea why, I'd like to hear it.

Here are my results:

[Soulburner]

Hitachi's tool can't find my drive...if anyone is wondering, WinAAM does work, tough.

[chad]

I had to delete my array before I was able to use this disk, hope that works

[lolhalol]

ive bought three units off diff shops and they all seem to perform slightly diff... on estimates... no real screenies coz ive sold them off and went 1tb ..

[MediumRare]

Bought 2 of them from Newegg and received the "00A7B" versions. AAM was set to off by default and ran HD Tune with those default settings....



Turned on AAM and set to highest settings and there was no change. But when I set AAM to lowest setting my access rate slowed to 17.6

So I just set them back to default settings, AAM off, and back at 11.8. Looks like only the "00A7B" versions have fast access times with AAM off...others need to have it enabled and set to highest setting.

-peace out

[XSAlliN]

Guess 07A7B0 - is the worst model. It's intended for Europe so you don't have to worry about it.



Western Digital took the Greedy way with this models. Of course all of them come with 2 platters, but first version was released for marketing purpose. They uses some quality components to build them since they have very good speed (read/Write and access time) and low noise with AAM disabled. If I set the AMM to max the access time decreases to 13.6 ms but the noise level is unbearable for me (sigh-sigh-Krrr-Krrrr-sigh-sigh-sigh-sigh- Krrr-krrr.....sigh-Krrr-Krrrr-sigh-sigh-sigh....). Constantly, similar to an old SCSI HDD like the one you use for industrial servers. About AAM, if I set it back my aces time increases to 17.9 ms. It wasn't integrated from DOS so it turned back to normal after shutdown.

Are those 3.3 ms that important? I know that a CPU is capable of millions of instructions per ms and theoretically has to wait for HDD, bust most people forget that the system has another important component which helps the CPU and the HDD when it comes to load time - the Memory. As seen in Ram Drive tests, you don't get better FPS from a high performer storage device, you get a better load time and a better access - and yeah, you could say that shows some improvement but I doubt 13.6 ms vs 16.3 MS is equivalent to that.

Anyway, wile Seagate tries to show even more respect for their customers with their latest policy, Western Digital abuses their...our trust by lowering the quality on their best selling HDD. Some how, I don't feel right knowing that I spent the same money as others if not more, for the same model (theoretically) and yet mine has different performance. I know that when you buy a CPU you gamble with his OC potential, but in that case the official specifications or the same for all models. I never seen somebody complaining about buying a E8400 which works only at 2400 Mhz.