1.

Solve : HD mystery - slower than 2001 IDE drives?

Answer»

I have a bit of a mystery with a brand new factory-installed Seagate Barracuda SATA hard drive installed in a relative's new HP Pavilion desktop.  

The hard drive is a Seagate OEM Barracuda 7200.7 SATA, 200 GB, 7200 rpm, with an 8MB buffer.
It is slower in seek time (15.5 ms) than the much older IDE drive listed at the bottom of this message.  According to Seagate, this drive should have an average seek of 8.5 ms.  The drive passes all health tests on both HD Tach and HD Tune.  Both programs consistently report the ~15.5 ms seek time.

It pulls an average of 50 MB/s and 76.1 Burst consistently.  CPU usage seems a bit high at ~9.0%.

Using Everest I can confirm that everything seems to be in order.  It's using a driver 5.1.2535.0  dated 01-Jul-01 which I believe are the standard legacy drivers.  The only thing I see which might be out of order is that both the maximum and active UDMA Transfer Mode is UDMA 5 (ATA-100).  This drive supports up to ATA-150 and I THOUGHT there is existent a mode UDMA 6, but perhaps I am mistaken.

The much older drive which seeks faster is WD1200, IDE, 2MB buffer, 5400 rpm with an average seek of ...  ---> 13.3 ms <--- .   It averages a transfer rate of 40 MB/s and 62 Burst, with 3% CPU usage.

Any ideas why this brand new SATA drive would have such a slow, long average seek?  All ideas appreciated.  And thank you!Since it is relatively new drive i would requst an RMA from the manuf.
My guess is a bad connector and or cable, or the drive itself.

patio.  I am guessing that this is XP. Which service pack are you using? (I noticed that there is a filter available (VIA) to be able to attain UDMA 6 for 2000 / ME / '98 which is not required for XP with SP2, I seem to remember.)

See if any motherboard drivers need to be updated.

Try Driver Detective. It helped me to find 75% of my drivers, but I would have to pay to get the other 25%Another idea is to use Diskeeper 9 Professional which will give you an idea of the improvement obtained after defragmentation and will also say if the MFTs need padding.

How was the drive partitioned and formatted? Was it partitioned with diskpart and formatted directly to HPFS/NTFS?

If you run - chkdsk - with no switch from a command window what do you see as to there being 4096 bytes in each allocation unit and are any bad sectors being reported.

E.G.



Quote

How was the drive partitioned and formatted?


Mac --

Thanks for your replies.  The lag in seek time was noted both before and after I did a fresh XP install.  The seek average was ~15.5 ms in the 'just brought home from Best Buy' condition, and the seek average was still ~15.5 ms after I did a complete reinstall of XP and reformat.

In its current state, the drive was formatted using the XP install CD program.  There is an initial small 1GB FAT32 partition just for the sake of having a DOS-bootable partition there.  Then, the remaining and subsequent partitions use NFTS.

The drivers for the chipset were immediately updated to a Nov 2005 version just after the reinstall of XP.   It has an ASUS motherboard with the AMD Athlon 64 3500+ (2.2Ghz) processor.  It has integrated video, so I used ATI's chipset drivers for this update.

I suppose I should be happy with the average MB/s and Burst rates reflected above in my original post.  But this average seek of ~15.5 ms is really bugging me.  It doesn't seem to fit, and Seagate says it should be around 9.0 ms.

I am waiting for the computer owner to send me the chkdsk reports on the partitions, and I'll let you know what is learned.  Thanks again.
Should be interesting. Manufacturers often produce goods which are rated. Wrist-watches are a usual example, as they can be rated A through to F, if I remember correctly.

Quality control determines which are A and which are F as there is all too often a discrepancy in quality and performance. I wouldn't know how to tell on a hard-drive, btw.

Best buy you say. Well, maybe the drive will improve with use, especially if chkdsk /r is used frequently, as much of the magnetised surface has been lying dormant for some time and I SUSPECT that there may be some shelf-life before use effect. (Pure speculation I have to say.)

FYI You shouldn't need the filter to achieve UDMA6 with either XP SP1 or XP SP2

Has the drive had a burn-in test?

(Bug report: Wristwatches , written above as Wrist-watches. If I don't use the hyphen the misspelling shows.)Mac --
Here is the chkdsk report on one of the NTFS partitions.  It's the partition containing the XP SP2 install.  See anything of note???

Microsoft Windows XP [Version 5.1.2600]

(C) COPYRIGHT 1985-2001 Microsoft Corp.

E:\WINDOWS>chkdsk

The type of the file system is NTFS.
Volume label is WindowsXP.
WARNING! F parameter not specified.
Running CHKDSK in read-only mode.
CHKDSK is verifying files (stage 1 of 3)...
File verification completed.
CHKDSK is verifying indexes (stage 2 of 3)...
Index verification completed.
CHKDSK is verifying security DESCRIPTORS (stage 3 of 3)...
Security descriptor verification completed.

31455238 KB total disk space.
4416188 KB in 24797 files.
7888 KB in 1922 indexes.
0 KB in bad sectors.
93814 KB in use by the system.
65536 KB occupied by the log file.
26937348 KB available on disk.

4096 bytes in each allocation unit.

7863809 total allocation units on disk.

6734337 allocation units available on disk. Quote
It's using a driver 5.1.2535.0  dated 01-Jul-01 which I believe are the standard legacy drivers.

Wouldn't legacy drivers indictae drivers for SOMETHING 'old'? Quote
Mac --
Here is the chkdsk report on one of the NTFS partitions.  It's the partition containing the XP SP2 install.  See anything of note?

Microsoft Windows XP [Version 5.1.2600]

(C) Copyright 1985-2001 Microsoft Corp.

E:\WINDOWS>chkdsk

The type of the file system is NTFS.
Volume label is WindowsXP.
WARNING! F parameter not specified.
Running CHKDSK in read-only mode.
CHKDSK is verifying files (stage 1 of 3)...
File verification completed.
CHKDSK is verifying indexes (stage 2 of 3)...
Index verification completed.
CHKDSK is verifying security descriptors (stage 3 of 3)...
Security descriptor verification completed.

31455238 KB total disk space.
4416188 KB in 24797 files.
7888 KB in 1922 indexes.
0 KB in bad sectors.
93814 KB in use by the system.
65536 KB occupied by the log file.
26937348 KB available on disk.

4096 bytes in each allocation unit.

7863809 total allocation units on disk.

6734337 allocation units available on disk.


Not unless you can.

Is this install fully updated post SP2?

Is it a converted volume, from FAT32 to NTFS, or was it formatted directly to NTFS?

Converting can produce a performance loss.

How does the file structure look in the defrag window? Is there a lot of red showing?




Discussion

No Comment Found