Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have just flashed my BIOS and now my machine does not detect my raid5 array! It has three 2TB drives in it so that is a LOT of data that will be lost!

I have NOT deleted the array and it does not offer me to reboot

I'm using Nvidia MediaShield! and Windows 7. Any ideas guys? Thanks!

Update: here is the GUI raid configuration. As you see it shows one disk in the array but for some reason not the other two!

Click for image of raid configuration error

share|improve this question

closed as off-topic by HopelessN00b Feb 19 '15 at 1:58

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "Questions on Server Fault must be about managing information technology systems in a business environment. Home and end-user computing questions may be asked on Super User, and questions about development, testing and development tools may be asked on Stack Overflow." – HopelessN00b
If this question can be reworded to fit the rules in the help center, please edit the question.

I'm going to guess that restoring from backup isn't an option... – Bart Silverstrim Jun 21 '12 at 14:03
FakeRAID is, in my experiences, not very reliable...if you're going to do RAID, you really should consider either true software RAID or a RAID controller. If you want to reconsider your configuration for reliability down the road. – Bart Silverstrim Jun 21 '12 at 14:05
Is this a personal machine, or one you're supporting for work within the scope of the FAQ? (I ask because "Fake RAID" like the NVidia chipsets are not often used in business/corporate environments) – voretaq7 Jun 21 '12 at 14:56

Could you try:

For NVidia chipset motherboards:

Goto BIOS - Integrated Peripherals - RAID Setup and enable RAID in the top option, then enable it for the ports that you have your RAID drives plugged into. Then Press F10 to save and exit.

share|improve this answer
Thank you for your response. That is exactly how I have it setup but nothing is being detected. – cogergo Jun 21 '12 at 14:08

Not come off like too much of an ass, but first of all, this is really not the right place to be asking this question (I'd think SuperUser might be a more appropriate site) - this site is for professional system administration - and secondly you're probably basically screwed.

Before you throw in the towel, you might want to search for tools to recover data from a damaged RAID array. I'm pretty sure you're using software RAID, and a quick Googling revealed a large number of options for software promising to recover your data. Might want to ask around about which ones are any good, or if you have other options specific to the consumer-grade product you have, but that's best done somewhere else, like SuperUser. Beyond that, you're looking at thousands of dollars for professional data recovery.

Other than that, the only thing I can recommend you do about this situation is learn from it.

  1. Software RAID is awful. Never use it. For anything. Really, this is why - there's absolutely no redundancy built into the system. Your config/array gets an error, you're outta luck. At least with hardware RAID, configurations are present on both the controller card and the disks, so you can do something if the controller (or the disks) run into an error with the array.

  2. RAID is not the same as data protection or backups. There's a saying in systems administration that data you don't backup is data you don't care about losing. For a consumer-based solution, at the very least, copy your data over to a high capacity external drive every so often, and store it somewhere safe when it's not being actively used.

  3. In general, RAID5 is a bad idea with large disks, especially large, consumer-grade disks. It doesn't offer enough redundancy, and you'll often run into issues where either a second drive fails during the days it takes to rebuild an already failed drive (so your array is dead), or you'll run into bit-level errors if you ever do need to rebuild it (so it won't rebuild, and your array is dead). In your particular case, you basically sacrificed a third of your drive space for no benefit - you wasted a whole 2 TB drive and are probably worse off. If you had all three as independent disks, and one failed, you wouldn't be in a spot where ALL your data is at risk.

My advice for next time (and this is from a guy who has a ~10 TB RAID array in his desktop at home) is:

First of all invest in a "RAID Adapter Card." I use an Adaptec that lets me put 8 disks in a variety of RAID levels, performs like a champ, and doesn't chew up system resources to maintain the array. (Hardware RAID cards have memory and small processors for this very purpose.) It's gone about 5 years without a single hiccup too, as an added bonus.

Second of all, consider what you're actually getting for the money you put in. Like I said above, you basically threw away the money you spent on that 3rd drive, and ended up getting a system that's slightly worse for it (system performance suffers, you've lost all your data instead of just a portion, etc.). Look at maybe getting a small NAS drive, such as the one I bought for a technically less inclined person in my life - 4x 2TB drives, in RAID 0, 1, 5, or 10, plug and play and accessible over the network, for several hundred dollars. (Buffalo was the brand name, I think.) Or you can do what I did and drop a couple grand on a proper RAID array, if it's worth that much to you. Everything in life has a value, and everything in life has a cost. What are the actual benefits of what you're doing (RAID), and what is it costing you? Is it actually "worth it?"

Finally, take a little bit of time to understand the limitations of the system you're setting up. RAID is not a backup solution, so what happens if a disk fails? Two disks? The controller card? What about a house fire? (etc.) What can you do to mitigate or remove those potential pitfalls (such as some sort of backups). Think ahead a little bit now, and save yourself a lot of pain later.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.