Example #37 of why RAID is NOT a "backup" solution.
I decided to run RAID5 to protect against drive failure. 4x500gb connected to a 4 port Sil3114 card. OS is running on a separate 2.320gb RAID1 array using onboard sil3112 controller.
The other day, one of my 320s died and I strangely decided to just break the RAID1 array and will recreate a new one when the replacement drive comes in.
Somewhere along the line, my RAID5 array developed an identity complex or something and decided to identify itself as a RAID1 array. All 4 drives are in fine working order, but 2 of the drives show as "reserved" while the other 2 are shown as a RAID1 set.
Of course, this all occurred before I had gotten around to setting up and configuring any backup software. ALL of my data was sitting on that 1.5 TB array.
There were probably other ways to fix this problem but what I ended up having to do was to delete the existing array and then I created a new one using the exact same parameters. Once booted into Windows, Drive Management saw a new drive and I initialized it and assigned a drive letter WITHOUT formatting it.
I ran a quick scan with GetDataBack and it sees my data and I am hoping and praying that it will be able to restore it.
The problem here ISN'T that I decided to go with a RAID5 set. I stand by that initial decision and will keep running RAID5.
No, the REAL PROBLEM is that I let myself get complacent PRESUMING that RAID5 offered enough protection and that I could take my time setting up a REAL BACKUP SOLUTION.
It's a safe bet to say that I now have a backup solution in place and ready to go BEFORE my RAID5 set is recovered and repopulated with data.
Matter of fact, I will be running redundant backup strategies to ensure that I never have to go through the same amount of worry again.