Improve company productivity with a Business Account.Sign Up


Perc 5/E crashed during raid 5 expansion

Posted on 2014-02-21
Medium Priority
Last Modified: 2016-11-23
We have a Dell server with a Perc 5/e controller attached to a MD1000 storage unit.  There was one raid 5 virtual disk array with five 300GB drives in a raid 5 configuration that is not split up.  We had a hot spare that was exactly the same as the others so I decided to un-assign it as the hot spare.  Then I followed Dell's instructions to add this drive to the raid 5 array to expand it.  I used the Dell server administration software to do all this.

The reconstruction phase seemed to be going smoothly and got to about 66% and the server locked up and crashed.  With the MD1000 unit attached with the SAS, the server would not boot (the OS boot drives are on the internal raid controller of the server and not on the MD1000).  We disconnected the SAS cable from the MD1000 just to make sure the server OS would still boot and it does fine.  

We connected the SAS back to the MD1000 and using the built-in raid bios management it shows that this new drive is in a foreign state and it fails when we try to import it.  So I decided to pull the new drive we added to the VD just to see if the array and server would come up and of course in our haste we pulled the wrong drive.  We didn't swap any drives around as I know that is a no-no with raid 5.  So we put the accidentally pulled drive back in and the raid 5 started rebuilding and still in the process now.

Since it never finished the expansion and the new drive is stuck in a foreign state what happens to the array?  Is it still expecting to see the new drive or will we be able to clear the configuration of the new drive and bring up the raid 5 array?
Question by:convergint
  • 2
  • 2
LVL 82

Assisted Solution

arnold earned 1500 total points
ID: 39878812
Foreign State means the drive is mislabeled, you need to first clear its "Association Label"
Presumably, the drive still has the "hot spare" label.

The difficulty I see is whether the current rebuild will restore access to the RAID 5 pre-expansion. Using the ServerAdministrator, you should be able to look at the physical disks and use the option "clear foreign config" this will remove the label from the disk.
Hopefully, you have a good full backup of the data prior to your expansion attempt.

Not sure whether you needed to remove the drive from HotSpare status prior to the expansion.
NOTE: RAID 5 especially with 5x300GB going to 6x300 will take a while to complete the expansion process.

Once you have access, it might be better to pull the formerly hot spare drive, now foreign state labeled, and use a different system to clear the foreign state label on the drive.  

Make sure the firmware on the perc and md1000 are current.  The version you have might be a bit outdated such that the scenario you have was addressed by an update.
updates to firmware usually should be done when the RAID is in optimal state.
LVL 10

Author Comment

ID: 39879868
All our firmware us up to date.  We tried all means to recover the file tables with no luck.  It is now with a data recovery company.

I did the same thing expanding the array with two drives two years ago without any issues so that's why I assumed it wouldn't be an issue this time.  Just never took into consideration that the server would crash during the process.

The system basically sees the raid 5 array as being perfect (without the new drive) and is even mounted with the right drive letter but the file tables seems destroyed.
LVL 82

Accepted Solution

arnold earned 1500 total points
ID: 39879943
I suspect the issue here was with the drive being labeled and then you attempted to expand onto it.
There are different possibilities including the state of the raid ahead I.e. Checkpoint might have been needed.
Not sure which/what caused the crash.  The possibility that the drive you pulled (presumably was labeled as failed) was kicked out leading to a "two device" failure.

Expansion of a raid 5 with newer drives are one thing, an expansion with the presence of olderdrives(>3 years) have a higher likelihood of a failure.
LVL 10

Author Comment

ID: 39894125
Data recovery guys couldn't rebuild the raid as it was in a state of flux.  It had some data on spread onto the new drive but the file tables were half corrupted.  

Before I expanded to the spare drive, I did remove it from the hot drive status and the system saw the drive as being unallocated.

There's no chance of rebuilding the old array so I'm closing this.

Featured Post

Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Article by: evilrix
Looking for a way to avoid searching through large data sets for data that doesn't exist? A Bloom Filter might be what you need. This data structure is a probabilistic filter that allows you to avoid unnecessary searches when you know the data defin…
Disk errors can be the source of sundry problems for the Exchange server, the most common one being that the database fails to mount.
This Micro Tutorial will teach you how to reformat your flash drive. Sometimes your flash drive may have issues carrying files so this will completely restore it to manufacturing settings. Make sure to backup all files before reformatting. This w…
In this video, Percona Director of Solution Engineering Jon Tobin discusses the function and features of Percona Server for MongoDB. How Percona can help Percona can help you determine if Percona Server for MongoDB is the right solution for …

580 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question