RAID-0 temporarily hanging

[Guest]

Archived from groups: microsoft.public.windowsxp.hardware (More info?)

I just raided 2 WD 36gig Raptors on a Broadcom 4852 Raid Controller in
RAID-0 configuration. This is my O/S disk with Windows XP Pro on it.

The Windows install went fine on it, but working in Windows, I notice
the raided drives will sometimes hang for maybe 4-5 seconds where I
can't even move the mouse cursor. The hang will eventually clears up,
but this is extremely annoying. It seems to happen when I'm
transferring a lot of data or accessing other hard drives on the raid
controller. Is this common for raided drives? I updated to the latest
firmware and Windows XP drivers.

Thanks for any help or suggestions.

 

[Guest]

Archived from groups: microsoft.public.windowsxp.hardware (More info?)

I don't think this is the case with WD Raptors. I have heard of many
success stories with them in RAID-0 configuration.

 

[Guest]

Archived from groups: microsoft.public.windowsxp.hardware (More info?)

You must not have RAID installed if youre acessing the "other drive" connected
to the controller.In RAID 0 the 2nd hd is unaccessable,it doesnt show in
xp,it
will only show in RAID boot menu,and the RAID software.Do you have a RAID
boot menu as xp starts,with intel RAID software,the two drives are shown,what
does broadcom show.Also,try updating the controller drivers in device
mgr,also
if intel chipsets are on the board get the software from intel.

"davidyeo@gmail.com" wrote:

> I just raided 2 WD 36gig Raptors on a Broadcom 4852 Raid Controller in
> RAID-0 configuration. This is my O/S disk with Windows XP Pro on it.
>
> The Windows install went fine on it, but working in Windows, I notice
> the raided drives will sometimes hang for maybe 4-5 seconds where I
> can't even move the mouse cursor. The hang will eventually clears up,
> but this is extremely annoying. It seems to happen when I'm
> transferring a lot of data or accessing other hard drives on the raid
> controller. Is this common for raided drives? I updated to the latest
> firmware and Windows XP drivers.
>
> Thanks for any help or suggestions.
>
>

 

[Guest]

Archived from groups: microsoft.public.windowsxp.hardware (More info?)

When I say I'm accessing another hard drive, I'm talking about another
HD (not part of my raided drives). The 3rd drive is connected to the
controller, but not raided.

 

[dl]

Archived from groups: microsoft.public.windowsxp.hardware (More info?)

You might want to read the post of 04/08/2005
subject "Western Digital Drives and Raid - Warning"

see if it applies

<davidyeo@gmail.com> wrote in message
news:1123699672.840710.65780@g43g2000cwa.googlegroups.com...
> I just raided 2 WD 36gig Raptors on a Broadcom 4852 Raid Controller in
> RAID-0 configuration. This is my O/S disk with Windows XP Pro on it.
>
> The Windows install went fine on it, but working in Windows, I notice
> the raided drives will sometimes hang for maybe 4-5 seconds where I
> can't even move the mouse cursor. The hang will eventually clears up,
> but this is extremely annoying. It seems to happen when I'm
> transferring a lot of data or accessing other hard drives on the raid
> controller. Is this common for raided drives? I updated to the latest
> firmware and Windows XP drivers.
>
> Thanks for any help or suggestions.
>

 

[dl]

Archived from groups: microsoft.public.windowsxp.hardware (More info?)

Well you certainly have a problem.
Lag is not usual with raid

<davidyeo@gmail.com> wrote in message
news:1123720264.707685.165600@g14g2000cwa.googlegroups.com...
> When I say I'm accessing another hard drive, I'm talking about another
> HD (not part of my raided drives). The 3rd drive is connected to the
> controller, but not raided.
>