« Process-creation bug in SocksCAP | Main | Not just a tech blog... »

March 16, 2010

TrackBack

TrackBack URL for this entry:
http://www.typepad.com/services/trackback/6a00d8357ac57769e20128772fbb2e970c

Listed below are links to weblogs that reference New Tech Tip: Expanding RAID1 arrays on Dell PERC 6/i Integrated RAID controllers:

Comments

Christian Thomasberg

hey, Nice guide!
I was just in the same situation, but found a safer way:
You can expand the volume in the Dell OpenManage Server Administrator. Its a bit more safe than to recreate the virtual disk :)
1. Select the PERC controller in the OMSA
2. Select Virtual disks
3. Select Reconfigure next to the volume and click execute.
4. This will expand the virtual disk nice and safely.
4. Afterwards expand the partition with diskpart as you say in your guide

/Christian

Ian Pittam

Great article!

Just to let you know that I successfully carried out the same
exercise on a Dell PERC 5/i RAID Controller with no data loss.
I replaced 2x 2.5" 73GB SAS Drives for 2x 2.5" 146GB SAS Drives in a PowerEdge 1950.

Ian

Matt

Thanks for a great article and for giving me hope!. I can confirm that this procedure does *NOT* work on a Dell SAS 6/i controller as much as I wished it would have.

Neither the RAID BIOS method or the Open Manage Server Admin tool suggested by Christian worked (config item did not appear).

We ended up "ghost" imaging the drive and deleting and recreating the raid. and ghosting back.

Fair warning ... the image took 30 mins to create and took 2.5 hours to put back.

-Matt

Bob Wall

One note on ths that might seem obvious to some but it wasn't to me until I spent a weekend doing this in vain: the Perc 6/i does NOT support drives larger than 2TB. And probably never will, as Dell doesn't seem to be updating it's firmware. I went through this whole procedure moving 2TB to 4TB and ended up with...2TB. Backed out and went back to the original setup. Incidentally, the basic procedure went a bit differently for me - had to restart then import the foreign config before it would start rebuilding the array, and then had to assign the 2nd drive as a hot spare before it would accept it into the array.

Verify your Comment

Previewing your Comment

This is only a preview. Your comment has not yet been posted.

Working...
Your comment could not be posted. Error type:
Your comment has been posted. Post another comment

The letters and numbers you entered did not match the image. Please try again.

As a final step before posting your comment, enter the letters and numbers you see in the image below. This prevents automated programs from posting comments.

Having trouble reading this image? View an alternate.

Working...

Post a comment

ABOUT STEVE

  • Steve Friedl is a software and network security consultant in Southern California. He has been a C and UNIX developer since 1981 and has an exceptionally broad background in this area. Some areas of expertise include:

    • C and C++ systems software development on the UNIX and Win32 platforms
    • Communications, including serial and TCP/IP based controllers
    • Enterprise internet security administration and configuration
    • Penetration tests, audits, and network reviews
    • Security forensics, reverse engineering, and tools development
    • General UNIX and Windows system/network administration
    • The Windows Printing System
    • Database software development
    • Technology problem solving and research
    • Technical writing and standup training

Unix Wiz

Stephen J. FriedlSoftware ConsultantOrange County, CA USASteve@unixwiz.net