How Are RAID Arrays Identified By Hardware?

Coward Anonymously Before Me asks: "This is more of a tech/hack question, but recently my highpoint controller forgot my disks were in a raid array. All the Disks still function, and have ZERO problems, aside from being not identified as still in RAID-0. All the data should still be there, but remains unaccessible to me, thus the question how and where would this kind of information be stored? On chip? MBR? and can the data be recovered without 3rd party interaction via free/open source toolkits? or even purchased software?"

Comments

Uhh

[fredrikj]

Did you try Google before submitting that?.

Re:Uhh

[bootprom]

If everyone was like you, people who really needed help with issues that were *not* in the FM would never get it. Forums like usenet, irc, and even ask /. are there to discuss novel issues, not to re-hash old topics over and over. People who ask questions before they RTFM are a detriment to the online community. We are *all* fortunate that people put with the likes of you.

When you *do* RTFM, not only do you get better at manual reading, but you also pick up additional information, so you may be less clueless the next time you have a problem

-BP

Re:vs RTFM

[Lord Bitman]

people get annoyed with me that I ask questions on IRC or message boards which are covered thoroughly in manuals. They respond with, of course, "RTFM"
Am I the only one who thinks that a Manual is a pretty lame source of information to reach for first-thing?
I have a few sources I go through, usually the manual is one of them, but I _Always_ first ask a person who might have the answer on hand. Manuals are not often things which lend themselves to answering typical questions such as "Can I blah?". The problem with "Can I blah" being looked up in a manual, among other things, is that often there are numerous synonyms for 'blah', and only one of them is ever used in the book, especially the index.
Perhaps they mean "Read the entire manual before even using the product". The obvious problem here is that manuals are getting longer every day. I've heard that some Linux Distro comes with a 2000 page manual just for getting it installed. Obviously, to read an entire manual before using a product would leave little time for using any products, and leave you more or less unknowledgeable about the product.
Then there's the problem of phrasing. Manuals may answer your question, but only burried in a lot of other information which isnt related to what you're actually working on. A person who knows already, however, can simply answer your question.
Slashdot, however, is far too public and non-specific. There's no reason to ask this kind of question on slashdot, get some friends or something.