Common RAID problems

trentlad

trentlad

trentlad

Soldato
Joined
7 Feb 2010
Posts
3,780
I'm experiencing a few issues that are apparent in RAID 0 that were not present using an OS installed on one HDD alone.

1.) Total system hang - about 4 times a day since instillation for about 3 seconds
2.) Sleep Delay - takes forever for it to go to sleep
3.) Building Front Cache - some videos won't play and I have to wait a long time for this message box to disappear before any videos work.

ekezpk.png


I'll update the list if I remember/experience any more but are these issues regularly faced by people installing their OS onto a RAID 0 partition?
 
It depends on,

What OS are you using?
What Mobo and corresponding BIOS?
What ports or adapter card?
What HDD or SSD you're using?

With an R2E, bios 1802, Windows 7 64 Ultimate and 2 x Vertex2 60GB in Raid O using sata II ports and latest intel IRST drivers, I have'nt experienced the above issue you're having.

Check your HDD/SSD forum and you might find something there.
 
Last edited:
I have yep, the latest drivers are installed but that also prevoked me to check my BIOS revision.

Just found a newer BIOS version on the Gigabyte website and they've updated the AHCI ROM specifically in that revision. However, it's a Beta and has been since 2009 so for something as fundamental as a BIOS I certainly didn't want a beta version running.

I'm still gutted that I didn't check the BIOS version before I updated, especially after I read that a main disadvantage of RAID was the loss of all data after a BIOS flash.

I have my RIG h/w setup in my signature but in addition:
RAID Controller - onboard Intel ICH9R
OS - Win 7 64bit Ultimate
BIOS - F2.
OC'ed Components - no need... yet
HDD - 2 x Samsung F3 500GB (HD502HJ)
Unusual Components - Matrix RAID with a RAID 0 and RAID 1 array spread over two HDDs.
Applications Running - Firefox and Steam (I run a very VERY clean system - Actronis TI f.t.w.)

Those are the specifics about my rig, so any other suggestions?
 
Last edited:
trentlad said:
Just found a newer BIOS version on the Gigabyte website and they've updated the AHCI ROM specifically in that revision. However, it's a Beta and has been since 2009 so for something as fundamental as a BIOS I certainly didn't want a beta version running.

I'm still gutted that I didn't check the BIOS version before I updated, especially after I read that a main disadvantage of RAID was the loss of all data after a BIOS flash.

I have my RIG h/w setup in my signature but in addition:
RAID Controller - onboard Intel ICH9R
OS - Win 7 64bit Ultimate
BIOS - F2.
OC'ed Components - no need... yet
HDD - 2 x Samsung F3 500GB (HD502HJ)
Unusual Components - Matrix RAID with a RAID 0 and RAID 1 array spread over two HDDs.
Applications Running - Firefox and Steam (I run a very VERY clean system - Actronis TI f.t.w.)

Those are the specifics about my rig, so any other suggestions?
Click to expand...

This could be the cause for you issues.
 
I read somewhere that having an additional storage drive can also cause hang ups so I'll try to disconnect it and see what happens.

I have my old Seagate Barracuda plugged in, I have a feeling that might be causing some issues. Not sure if the jumpers could do anything but I spent the first three years of my build with that as my only HDD and I had the 1.5GB SATA limiter jumper in place. I took it off and noticed a tiny increase in bench so wondered if that's causing issue.
 
The problem with on-board RAID is any "system hang" for any reason, can affect the stability of the RAID array. Re-building or Re-synching takes time...lots of time...and usually a user will shut-down or go to standby long before the process can complete. Even if your machine is "always on", what happens, when there is another error before the first process is complete ? I've used both 3ware cards and the Intel Matrix controller, and although there performance ( especially the 3ware card ) is admirable, my arrays were almost constantly rebuiling or re-synching. This did not provide all that much performance loss ( surprisingly ), but left unchecked resulted in an ever increasing number of errors. Worst case scenario, a drive is completely dropped from the array. The hoops you have to jump through to re-add the supposedly failed drive is ridiculous.
Click to expand...

Source

Ah jeez that's scary. I really hope it's not error recovery and the hang isn't down to my array re-building/synchronizing. The hang time in the quote sounds like a several minute hang but mine only last 3-10 seconds.
 
You must log in or register to reply here.
Back
Top Bottom