The ongoing nightmare known as the Samsung F4 continues:
I really wanted to test to see if Win 7 X64 WITH SP1 was faster than Win 7 X64. So I formatted the drive to 25 GB and loaded Win 7 X64
SP0 ON THE DRIVE in AHCI mode and loaded with latest Intel RST 10.0.0.46 drivers.
They wouldnt load during install when on floppy, but they could be afterwards in dev man update driver.
So I rebooted and ran HDTune as a first shot baseline
Note first that WHEN THE O/S is ON the drive AAM cannot be set to 128 or 254 - defaults to 0 and cannot be changed.
Update - with drive configured as SATA IDE Win 7 X64 it can be set, but still charts bad
So I ran the HDtune and got 4 intervals with the crappy spikes
Then HDTune crashed (remember some apps dont like 4096 emulated to 512 HDD)
Ran the bench a second time and got only 1 crappy spike, then ran HDTune again, perfect trace with the usual 58-104-137MB/s min avg max results. Is the drive loosening up with heat?
So I then installed SP1 to X64 because I wanted to really know if it helps HDD somehow. Well, that turned out to be a bad idea. Immediately after reboot reran HDtune and guess what - airmark type total crappola and
SAME HIGH CPU USAGE - 40% as airmark. Thats quite a jump from 1.9% up to now
So what have we learned here?
AHCI doesnt do squat, SATA IDE is fine
Make sure AAM is set to 254
Apps are dubious
AS RUN ON 4096 HDD with Win 7 X64 SP1
with boot O/S on drive
Never run your O/S on a Samsung 4096 HDD as currently sold
Now heres the funny part:
Moved the samsung AHCI (with O/S) down boot order to my XP SP3/Win 7 X64 dual boot SATA IDE (changed bios back), booted to XP, and made sure AAM was set to 254 and ran bench - perfection again
So, I am now calling BS on this aligning thing
No matter what I do I get the same benches when the drive is REMOTE
XP with 32K offset, Win 7 1024 offset, diskpart XP or Win 7, Easeus, Paragon partitioning/formatting
What it boils down to ITS THE BIOS - hard wired to 512B sectors and 63rd sector startpoint of first partition
To make aligning relevant you need an uEFI bios, and HDD frmware that will show the drive as virtual 512B or real 4096B, like the MSI one click toggle bios
As on the new Gigabyte P67 mobo's
http://www.overclockers.at/news/details_zum_gigabyte_p67a-ud7_und_mehr
Whether you select LBA, Large or CHS as geometry, an MBR bios will make 63rd sector as start, no matter how far in you put it
The 2 ARM RISC chips do the virtual aligning, not the user
The next puzzle is if Win 7 can read the HDD at the magnetic domain level ignoring the emulated sectors, is that the problem??
So, I'm gonna get a WDC green EARS drive to continue my testing in Ubuntu. At least that drive works all the time - I hope!
At least they give you a little info on the label, but not a word about the sector size (as seen by O/S) - no total LBA number which would tell us, but i consider that a good sign. Maybe under right circumstances drive can be seen as actual 4096 sector HDD.
WDC also has 1--8 pins while F4 does not, only 1-2-3-4