ProLiant Servers (ML,DL,SL)
1753947 Members
7484 Online
108811 Solutions
New Discussion

Who Me Too'd this topic

keke99
Collector

Smart Array P410i

Greetings,

 

We have a Proliant DL380 G6 running Windows Server 2008 R2 x64.  The Smart Array is configured using RAID 5.

 

I want to replace the 4 main disks (900GB Total RAID 5) with 3, larger SSD drives (1.5TB RAID 5).

 

  • At first, I wanted to swap 1 disk at a time with an SSD Drive (using 4 SSD disks in this scenario).  Once all disks had been rebuilt, I was going to expand to use the full capacity.  That didn't work. I later read online that you can't mix Spin Drives and SSD Drives on a given RAID.

 

  • Then, while the machine was running, I inserted 3 SSD drives into available bays.  I then created a second RAID 5 out of those 3 SSD disks.  That part worked ok.  Let's call this RAID "3SSD-RAID5" (vs the old RAID "4SPIN-RAID5").

 

  • Using PartitionWizard, I cloned my 4SPIN-RAID5 into the newly created 3SSD-RAID5.  That worked (in Boot mode).

 

  • Once the 3SSD-RAID5 was created and the computer was turned off, I removed my 4SPIN-RAID5 out of the bays.  Then, moved my 3SSD-RAID5 into the first 3 slots where my 4SPIN-RAID5 was.

 

  • Rebooted the machine... Got a big red warning that I had performed an illegal disk move and that reconfiguring my RAID was going to result in the original RAID (and the data) being lost.

 

  • Got a little scared... turned the machine Off... Removed the 3SSD-RAID5 and replaced my original 4SPIN-RAID5 into their original bays (in proper order), but I did NOT replace the 3SSD-RAID5 back into *their* bays (the ones they were in when I built the second RAID in Windows). 

 

  • Rebooted and got disk failure messages on my original disks.  

 

  • Turned off computer... inserted the 3SSD-RAID5 into their original bays, while keeping my 4SPIN-RAID5 as they were.  Rebooted.

 

  • Everything was back to normal.

 

  • Changed my underwear

 

 

So based on what I read, the RAID info is contained on the controller, but also on the disks as well.

 

Why wasn't the controller able to just pick up the 3SSD-RAID5 I had moved from their original locations into the 4SPIN-RAID5 bays?  I thought the controller would just detect a new disk configuration... re-read the disk info... and re-configure its settings accordingly??

 

I suspect that maybe, I did too many things at once.  Maybe once the 3SSD-RAID5 was done being cloned, I should have turned off the computer... remove the 3SSD-RAID5 from the bays.  Let the controller first detect that.  Then, remove the 4SPIN-RAID5 and let the controller detect that.  Finally, place the 3SSD-RAID5 back into the first 3 bays.

 

Don't know.  Seems to me that as long as you move the whole RAID block at once (while the computer is Off, of course)... the controller should pick up the changes just as you can move around single disks on a regular PC.  You may need to make boot order changes, but your data is just going to be fine.  The parallel seemed obvious to me... but I guess it wasn't.

 

 

Now, my next plan is to do:

 

  • CloneZilla disk image of my 4SPIN-RAID5.

 

  • Remove the 4SPIN-RAID5 and build a new 3SSD-RAID5 into the first 3 bays.

 

  • Restore the CloneZilla disk image onto the 3SSD-RAID5.

 

Is there a more efficient way to do this?

 

Thanks... and sorry for my long message...

 

Who Me Too'd this topic