Need help with my Highpoint RAID
I've had a Highpoint RocketRAID 100 for awhile now, and I've been too lazy to switch from Windows software striping (which was set up before I bought the card) to using the card until now.
So I uninstalled the software striped drive and updated the BIOS and driver for the highpoint card.
I went into the BIOS utility and created an array. But, uh, I don't know how to make it show up in Windows XP. I went into the Disk Manager and intialized the drive, but the only thing it would let me do is convert it into a dynamic disk (which I did, and can reverse if need be).
Do I need to go into DOS and format it or something?
Side question, one that's probably been asked a million times, what's the consensus on cluster size? This time I made it 32k, but I can still change it.
While this is probably irrelevant, the two drives are WD400BB's (ata-100, 2mb cache, 40gb). There is a WD800JB on the controller that isn't on the array that will be moved to the onboard IDE later. Right now I'm setting up the array so I can benchmark it compared to the WD800JB, and decide which drive I will put Windows on when I get rid of my current Windows HD, an archaic ATA 66 thing.
Thanks.
So I uninstalled the software striped drive and updated the BIOS and driver for the highpoint card.
I went into the BIOS utility and created an array. But, uh, I don't know how to make it show up in Windows XP. I went into the Disk Manager and intialized the drive, but the only thing it would let me do is convert it into a dynamic disk (which I did, and can reverse if need be).
Do I need to go into DOS and format it or something?
Side question, one that's probably been asked a million times, what's the consensus on cluster size? This time I made it 32k, but I can still change it.
While this is probably irrelevant, the two drives are WD400BB's (ata-100, 2mb cache, 40gb). There is a WD800JB on the controller that isn't on the array that will be moved to the onboard IDE later. Right now I'm setting up the array so I can benchmark it compared to the WD800JB, and decide which drive I will put Windows on when I get rid of my current Windows HD, an archaic ATA 66 thing.
Thanks.
0
Comments
I assume you have the right drivers installed for the card and that it shows up in xp ok. Since you created an array (i guess Raid-0) of 2 drives, it will show up in XP as one big drive which you will have to create a partition and format it as usual. You dont have to make it a Dynamic at all.
After benching quite a bit I chose 16/16 for my WB1200JB's on onboard HPT. 32/32 was almost as good though.
I figured my ATTO would inrease a little. After all, consumer level RAID is pretty much software raid, and I didn't think it would be much better than my drives set up with Windows striping.
My reads went up. A lot. Almost 200%. I'm freakin' thrilled!. All this time my PoserRaid™ was only about as fast as a single drive was.
I'm gonna go install some stuff now
Maybe you all can help me figure out what to do with my new array:
My plan is to install Windows and my programs on the raid drives and put all my music, movies, and documents on the 80gb drive. I know that if one of my drives fail that I'll loose Windows, but that's not really a big deal.
But do I need to fast read times for Windows, or does that only matter on startup? And should the swap file be on the array with the programs or on the other drive?
The other drive is the aforementioned WD800JB. Here's it's atto on the slave of IDE1 on the HPT controller. It *should* be about the same once I move it to the mainboard VIA IDE.
Any ideas?
My writes are higher in this screenshot than the last one because the latency was increased. But how can I get my reads back up to 70 like they were before Windows was on the drive? Did they bench so high because they were empty?
It totally killed my midrange, but helped the smaller range. Weird.
This is the atto after I changed the jumpers. They were both set on Master, I had forgotten that WD's like the jumpers off if they're single drives.
Anyway, the controller card recognizes them quicker but it didn't seem to affect benchmarks.
Do you have anything else on on the controller? Are you certain both cables are Ultra ATA cables?
After looking at your WD800JB ATTO I noticed that it looks low for one of those. If it is defragged and running right it should top out right around 50K. Your array with the drives and controller you are using should be a minimum of 75K (usually better)
This is what I am getting with mine after loading windows and tweaking.
.
.
.
.
Still not as good as before I put Windows on it, but at least the midrange isn't really, really bad any more!
Now if I could only get those 70mb/s reads back...
The cables are indeed ATA 100. They came with the card, those nice teflon coated ones.
Thanks for all your help mtgoat!
MM,
That may have been true as general rule years ago but the newer WD's, especially the JB's actually do better with other configs. I worked with Tex on some of this while some others did it idepenently so it really does wash out. My WD1000JB's like 32/8 (on HPT 1520) far better than anything else while my WD600JB's like 32/16 (on onboard SI) better. I have swapped the 600JB's to the HPT controller to see if that was the factor but it wasn't, so it must have more to do with the density of the drives. Then I have another machine with 2 Maxtor 740's on a HPT 372 and they like the old 16/16 best by a long shot. So my conclusion is; It is always best to test!
I think Mac and Equito are the other two WD RAID'ers here.
Which side of the slash is cluster and which side is stripe again? (as in 16/16 and 32/8).
And I'm not sure exactly how to set that up. I had an option for cluster size and an option for allocation unit size (one on the card bios, and one in windows, but i forget which was where), and I set both to 32 in this case. But I didn't see an option for stripe size.
Edit
Sorry I missed the second part.
The option for stripe size is in the HPT bios when you set up the array and the cluster is in the format partition.
YGPM
What about me? My WD1200JB's are royally offended you didn't mention them!
On a more serious note though, yea, I absolutely agree. 16/16 was the defacto a couple of years ago, but now it's not so black and white. However... My WDJB's, on a HPT 372, have always ran best on 16/16, though 32/32, 32/16, 16/8, all worked almost as well. I haven't properly tested my Raptors yet but I get the feeling the 16/16 I'm running them on at the moment, (Silicon Image controller) isn't quite the best for them. So like Mtgoat said, test test test, but 16/16 is always a good place to start.
Sorry I left ya out.
I do have a system for repairs here with HPT374 / 2 x WD800JB's RAID0 NTFS 16/16
Here's something interesting, check this out: