• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Fasttrack66+2 30gb 75GXPs=Holy Sh!t.

Plester

Diamond Member
just whipped up this array raid0, it is blindingly fast, and you can't hear these drives spinning - freaky. HD Tach 2.52 - 8.8ms access, 40mb/sec average read.
 
RAID is nice, been thinking of getting one myself (hotrod100) but I don't think the 8.8ms access number is realistic.

Did u test the whole drive, or just the first 8GB? Sometimes the truncated 8GB test yields unrealistically low access numbers.

Gotta put a check in the 'advanced size check' box to do the whole disk.

access = (mathematically) seek + latency.

ave seek on most current ata drives is ~8.5ms, and ave latency on 7200rpm drove is 4.2ms, which would yield ave access somewhere around 12.7ms.
 
I am on a Promise FastTrak 66 with RAID 0+1 and four WD 20.5 ATA66 drives. Been running strong for 4 months now. Definitely the way to go. I can't imagine my setup with ATA 100.:Q
 
Radboy i'm sure you are right, HD Tach 2.52 doesn't have the 'advanced size check' option, and 2.61 gives me a bsod. regardless, 60gigs of ide raid for $310 ($29 hacked fasttrack included) is too good.
 
"RAID is nice, been thinking of getting one myself (hotrod100) but I don't think the 8.8ms access number is realistic.

Did u test the whole drive, or just the first 8GB? Sometimes the truncated 8GB test yields unrealistically low access numbers.

Gotta put a check in the 'advanced size check' box to do the whole disk.

access = (mathematically) seek + latency.

ave seek on most current ata drives is ~8.5ms, and ave latency on 7200rpm drove is 4.2ms, which would yield ave access somewhere around 12.7ms."


Radboy,

I have a Quantum Fireball+ LM 20.5GB, and I get 9ms and under. When I had this HD in my P83 system, I was getting about 10.2ms access. Either you don't know what you're talking about, or it just simply hasn't any truth to it.

I'm not even using ATA33 though, my cables are so old they don't support it (or something like that). Highest sustained transfer I got was ~15-16MB/s... :| Oh well, at least it's still really responsive, being a 7200rpm drive with 2MB cache and all.

-RSI
 
If you already have a single drive connected to this controller (actually I have the 100 with 1 ibm 75gxp) can you add a second drive on the fly as a raid 0 strip without having to reformat?

 
Anybody - sorry, once you set up the array you need to fdisk it, and start from fresh. if you go with raid0(the least reliable) i strongly suggest a small backup hard drive on the regular ide channel, that you can ghost to and from. it makes setting these things up a breeze, and big peace of mind.
 
zippy, RSI, et al. The average access time is figured by adding the seek time plus latency. Seek time is the time required to move the access arm to the correct cylinder. And latency is the time it takes the disk to rotate.

HD Tach + Sandra seem to count only the seek time and leave out the latency. But Sandra gives me 4/5ms (average access time) for my 75GXP and I dont have any idea what it is measuring. The box says 8.5ms average seek time then add 4.16ms for latency and you get 12.66ms average access time.

 
RSI, Radboy is correct. You must be making the same mistake as Plester. I own the same Quantum drive you have and it scores in the mid 11's on HDTach which is where it is supposed to be.

HDTach gives proper measurements if you set it up correctly mastermind.
 
I couldn't get HD Tach to work on the IBM's. Same BSOD like Plester but I realized its just a bug. Kinda scary to get BSOD's after just installing a new drive but the older versions are supposed to work.
 
Back
Top