[Last Call] Learn how to a build a cloud-first strategyRegister Now

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 360
  • Last Modified:

RAID5 Cheat

I have a RAID5 set up with 3 HDD of 250GB each. If I methodically replace one drive at a time with a larger drive and let the RAID rebuild each time, will I eventually get to a larger RAID array and maintain my data?
2 Solutions
Nope.  Not only that, but you put your data at risk.   All it takes is one bad block at any time and you lose a chunk of data, and some RAID controllers will even abort the rebuild, so you will be required to contract a recovery specialist.

Do it the right way, backup, blow away, build it the way you want, restore.
(P.S.  the free space will show up as unallocated.  It won't expand a file system.  It won't expand a logical device.  The controller just thinks you had a disk failure and  put in a replacement drive bigger than you needed.   If  you used X blocks before, then you will end up with using X blocks on the replacement disk for the same LUN, not X + Y blocks.
Paul MacDonaldDirector, Information SystemsCommented:
[dlethe]'s right.  The controller would just carve out 250GB of your 500GB drive and you'd be stuck with the same amount of storage space.
[Video] Create a Disruption-Free Workspace

Open offices have their challenges. And Sometimes, it's even hard to work at work. It's time to reclaim your office and create a disruption-free workspace. With the MB 660, you can:

-Increase Concentration
-Improve well-being
-Boost Productivity

rhondotbobAuthor Commented:
THough I might be able to cheat. Oh well, client is paying for it. So what I have here is easy money. Thanks
Your best bet would be to copy the data to another drive, replace the 3 RAID drives with bigger ones (creating a new RAID set), and then copying the data back.  
While you temporarily put the data at risk, its a calculated risk.  Clearly you would want to have a known-good backup prior to performing any work on the array.

The additional space would show up as unallocated and you would need to configure the unallocated space on both the array controller and on the operating system using the new space.

Also, if this is a SATA or SAS array, make sure the controller can support drives larger than 400 GB before performing the work.  Sometimes this simply requires a firmware upgrade.  Sometimes you have to replace the array controller.

Good luck and here's hoping you have no issues when performing the upgrade.
But if you take a backup, then it will require much less time to build an array then multiple rebuilds plus expansion (assuming this was even possible).  Not only that, if your controller supports background init, then you could kick off the recovery and run it concurrently with a background init, so it builds the new array once, while restoring at the same time.  All without any risk of data loss.  (Assuming your backup is good).

So doing it the right way is much safer, could take minutes instead of days, resizes the file system at the same time ... and even if you have some catastrophic failure, your original disk drives with the data are still good.
andyalderSaggar makers bottom knockerCommented:
"Nope" is not the correct answer; the procedure you outline is supported on some cards but not on others, so the first question should be "what's the controller?"

It does leave you without parity for an extended period of time of course, and it does take ages but it may be valid. It was common practice with some controllers, but that was when disks were smaller so rebuilds took less time.

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now