Apparently "Initialize Array" is on by default in the new BIOS that I flashed to my controller card last week, so I inadvertently lost all of the data on my 200GB RAID5 array. I know that it's silly, but I kinda feel like I'm going to throw up now. Oh well, at least there are plenty of geeks around here who can identify...
I just lost my entire RAID array... :(
- Thread starter WhiteKnight
- Start date
I'll be able to recover some of the stuff. Documents, mp3s, but I definitely lost a lot. I updated the BIOS because I was installing a new mobo and processor and the new BIOS addressed a minor issue I'd been having before.
Damn. I wouldn't be able to sleep at night knowing that my RAID array has the only copy of my data. I run two servers and a workstation and all of them get backed up regularly to an external USB drive.
Well, it's a RAID5 array so I thought that it would be ok. I didn't count on a manufacturer sneak attack. I also just don't have the means to back up 200GB on a regular basis.
...just too..donno, seems "unorganized"..maybe it's a psychological factor....Ouch.
But...
RAID arrays and backups serve two entirely different purposes and neither is a substitute for the other.
But...
RAID arrays and backups serve two entirely different purposes and neither is a substitute for the other.
next time you should try software raid available through windows it works really well and you wont have this problem.
WHAT kind of HBA does that? If I initialise an array, there are three steps to do so with most controllers. Not to mention an "ARE YOU SURE?" prompt! That just sounds silly to me!
-DAK-
-DAK-
Your opinions does not count.
Microsoft Dynamic disk is one of the most ill conceived and half baked storage ideas ever.
Windogg
I have a Promise SX4000 and there was definitely no "this will erase all of the data are you sure" prompt. In the past, I had a problem with the array going critical and telling me that a drive had failed, even though it hadn't. The problem could be solved by deleting the array then recreating it. It would not be reinitialized assuming that all of the settings were the same as the last time, thus the array was restored. The problem is that Promise, in their infinite wisdom, apparently turned intialization on by default, though I saw no option to turn it off anyway.
Actually, the idea was Veritas' idea, but I agree with your opinions about it.
Just wait till we get to GPT partitioning with IA64 systems. That sounds neato, and disasters can theoretically be hand-edited just like good ol partition tables in the MBR.
Man, that sucks. I know the feeling.
I was building my first RAID array (RAID-1) with two brand new, larger capacity drives in my first self-built machine. I was so happy. My old 20 gig drive was solid for years. Anyway, I get everything set up and slave up the old 20 gig to transfer all the data over. Soon as I start up the machine, I see smoke and smell the burning. Yup, my 20 gig just died. I turn it over and see the PCB is burnt. It felt like somebody hasd just ripped my soul out of my body. Like somebody was playing a cruel joke on me.
Luckily, I did have some data backed up. But I lost a lot of music that night. LOL.
I was building my first RAID array (RAID-1) with two brand new, larger capacity drives in my first self-built machine. I was so happy. My old 20 gig drive was solid for years. Anyway, I get everything set up and slave up the old 20 gig to transfer all the data over. Soon as I start up the machine, I see smoke and smell the burning. Yup, my 20 gig just died. I turn it over and see the PCB is burnt. It felt like somebody hasd just ripped my soul out of my body. Like somebody was playing a cruel joke on me.
Luckily, I did have some data backed up. But I lost a lot of music that night. LOL.
I was wondering if that was the Promise RAID controller. I know someone who had their controller fail and they bought a new controller...except that if they set the new controller up with their old settings, it would initialize the drives.
According to Promise, there was no way to turn this option off. They offered two workarounds: 1) set up the controller and then real quick unplug the drives or cut the power. If your timing is perfect, it might not corrupt the drives. Or 2) buy an identical set of new hard drives and configure the controller while hooked up to those. Then, after it's done initializing, turn off the power and connect your old drives in place of the new ones.
On the other hand, I just replaced one of my MegaRAID 1500 controllers out here and the new card recognized all the old drives (22 of them on that system), restored the old configuration automatically, and booted right up. Even if I rearrange the drives, it'll give me a warning, but it'll still figure everything out and come right up.
I figured this had to be a "toy" IDE raid controller! :|
Yes with LSi you can move anything and everything around. As long as the drive gets the start command and spins up in a timely manner. Roaming is permitted, the HBA FW will assign the new drive positions on the fly.
-DAK-
TRENDING THREADS
-
Discussion Zen 5 Speculation (EPYC Turin and Strix Point/Granite Ridge - Ryzen 9000)- Started by DisEnchantment
- Replies: 25K
-
Discussion Intel Meteor, Arrow, Lunar & Panther Lakes + WCL Discussion Threads
- Started by Tigerick
- Replies: 23K
-
Discussion Intel current and future Lakes & Rapids thread- Started by TheF34RChannel
- Replies: 23K
-
-
Facebook
Twitter