• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

RAPTOR RAID Revisions

P

P3N1X[H]

Limp Gawd
Joined
Jul 27, 2004
Messages
174
OK now i have RMA'd my two 74GB Raptor drives, and sitting with two A1 revisions in a Raid 0 64k Stripe.

I also have two A0 revisions from the RMA as well. I have to send the drives back in about 3 weeks, because i did an advance replacement so i have 4 drives on hand. two A0 and two A1. IT makes sense that the A1 revision is newer, so i chose to use the A1's.

Now it still does the same thing. I will get an IRQ LESS OR EQUAL followed by SCSIPORT.SYS the driver causing the problem. i also had a stop error code 0x0000000D7 followed by a few others, i cant remember now, nor am i at the machine. but i can provide them later when i get home from work.

I'm using the latest driver available for the 2 port Talon controller, and also using the 3.09 bios release.


Relevant Specs on my system

500Watt Fortron PS
MSI K7N2 Delta-L motherboard, 5.7 bios release
AMD XP 3200+
1 Gig of Mushkin Low Latency Memory
ATI Radeon x800 Pro
Creative Audigy 2 Value




So now it seems that im having a problem even when i have 2 matching revisions. im guessing the next step is to RMA the controller card which i have contacted the relevant company about since they wanted to RMA the card first, then when they found out i had mismatching revisions they said to match the revisions. now theyre matching and im still getting the same error. so is it possible the hardware is bad? i dont think my memory is bad either because i had 2 sticks of kingston hyper-x before i upograded to the low latency mushkin memory, and all runs 110% when i was on my ide seagate drive, no problems at all there.so im stuck wondering evermore again
 
More than likely the controller card. I'd RMA that.
 
nice to hear some one else say that. cuz its driving me insane. i spent plenty on 2 raptors, and likle 60bux on the damn talon when it came out and ive had nothing but headaches with it. yup yup, ive already contacted Pacific Digital, lucky for me theyre in Irvine, CA, and im just a half hour from there. so ill RMA the controller and get back to yall on what happens. but has anybody has expereince with raid controllers, going bad. i mean yes i know its possible. as for why it would go bad? just manufac defect or whatnot? kinda odd that they right away wanted to RMA the card rather than ask more questions about it, so maybe they know something. anyhow im just rambling on here its early in the morning and work is slow and im bored and BLAH! stupid computers and their rules LOL
 
Theres no way you'd have 4 bad Raptors. It must be the card. Raptors don't die that frequently. Not from defects anyway.

Cards do go bad. Who knows why? Obviously something failed. As to why I could only speculate.
 
And kinda on topic, Just curious any differences in the A0 and A1 revisions? :confused:
 
From what I gather, mostly firmware tweaks to improve host compatibility. Of course, mixing revisions will make comaptibility even worse in a RAID, as the drives may sync with the host differently, which is Fenix's problem.
 
no no the drives work 110% when alone

when in raid they fail and i get bluescreens...well by fail i mean fail to boot. it 'works' when it works but getting into windows can take 2 or 3 bluescreens sometimes...most the time what i have to do when it bluescreens is i select load last known good config, and sometimnes i will get into windows like that, othertimes it still crashes....so yea the controller im gonna RMA it when i get home tonite...pull that sucker out of my box, pop back on my seagate ide...i just love seagate btw...so ill rma the controller and hope things turn out fine....

glad to hear im not alone in having a problem with raptors in raid.

but yes according to PD i need mathicn revisions, and they told me i cant mix n match, but they didnt speak of diff in revisions only that the way TCQ is handled and WD wouldnt even tell me or even confirm that they even HAD diff revisions. they wont discuss that kinda info with peons like me LOL fuckers! but clearly theres several diff revisions of the drive out now. A0, A1, A2. so when goin raid make sure they match ppl

on a funny side note, the 2 replacements i got were A0/A1 and they were made June 6th and June 8th. so its like theyre still making A0 and A1, and in stores all i can find are A2. so thats something interesting to ponder...whya re they still making A0 A1 when A2 is out and they change the way things work......yet still make old revisions with unchaged stuff? it doesnt make sense if yall are following me there......
 
well i dont know why i never thought of this before. but i didnt.

Pacific Digital said to change pci slots before i RMA the card, because there might be an IRQ conflict. so knowing my creative audigy was the only thing else on the pci bus. i took it out and it works perfect now.

so i check my bios and its on its own irq now, and when i had the soundcard in its original slot the soundcard and raid card were sharing an IRQ, so after playing musical pci slots i got em each on their own irq now and its working great. no blue screens or anthing..

1 problem. i used to get around 80 or 90 megs in a sustained read on HDTACH, but now im only averaging 50megs in sustained now...thats not right is it?


edit. its still giving a driver irq less or equap still, so i had to pull out my audigy completly and use the onboard nforce2 audio. :( anyhow ill see how it goes
 
You must log in or register to reply here.
Back
Top