• 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.

Delayed Write Failed w/onboard promise raid

T

ThisIsMatt

Banned
I like to use my onboard raid as just an extra set of ATA channels, using a maxtor 60 gig and 80 gig. However, I continually get a Delayed Write Failure error and then the system becomes laggy with constant momentary (millisecond to 30 second) hang ups until I reboot. It doesn't happen until I try to transfer files between drives or off one drive over the network, and it usually only happens when transferring large/many files.

The drives worked fine in this configuration on my old motherboard with similar onboard raid (also promise, but a slightly different model). It was working on this motherboard (ECS) after I screwed around with it until it finally just started working (I don't know exactly what I did -- I flashed the bios, reinstalled different drivers 200 times, etc). Now I've reinstalled windows and the problem's back and it won't go away.

The drives work fine on the normal IDE channels, but I need those for optical drives.

I've seen things about registry tweaks and write cache tweaks, but I never had to do this before and write caching is not available while on the raid controller.

Any suggestions?
 
I've had the same problems on my Kt333 w\RAID. Exact same problem. I just bought another matching HD so I could RAID them and it went away.
 
take whatever I have to say witha grain of salt but:

Very often there are different drivers for the promise controlers depending on whether you are raiding or not, make sure you haev the right drivers installed.
 
Delayed Write failure indicates that there has been a problem writing to a drive - and since the write comes from a long gone write request that has been buffered in main memory and/or a real RAID controller's own RAM, it cannot be recovered anymore. It thus is fatal.

Looks like you got a hardware and/or driver problem to fix there. Turning write buffering off will just bring the error closer to the application that did the write, and degrade performance
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top