Increasing Size of HDDs in a Dell T110 II with RAID and 2 HDDs
I set out to increase the size of a 1TB HDD in a Dell T110 II server. I'm using Clonezilla to create an image and will replace with 2TB HDD. (I have two of them, identical, as it appears two will be needed and I'd not be surprised if being identical isn't required. After all, this is an old system).
It turns out this is a RAID configuration with 2 HDDs (so I hope right now that it's RAID 1 - and know that I will have to figure that out!!).
I've not determined if it's software or hardware RAID yet - I've seen reference to PERC at boot time is all.
I have Clonezilla imaging one of the HDDs right now.
I can imagine simply removing the old HDDs and replacing them with the new ones and then putting the image back onto one with Clonezilla and letting the RAID system deal with the other one (if RAID1). But that must be too easy.
Given this set of things, what might be the most direct approach?
This is a production system so maybe we have a couple of days to get this done before it's needed again.
It turns out this is a RAID configuration with 2 HDDs (so I hope right now that it's RAID 1 - and know that I will have to figure that out!!).
I've not determined if it's software or hardware RAID yet - I've seen reference to PERC at boot time is all.
I have Clonezilla imaging one of the HDDs right now.
I can imagine simply removing the old HDDs and replacing them with the new ones and then putting the image back onto one with Clonezilla and letting the RAID system deal with the other one (if RAID1). But that must be too easy.
Given this set of things, what might be the most direct approach?
This is a production system so maybe we have a couple of days to get this done before it's needed again.
Last Comment
PERC S100 probably, Dell firmware on Intel chipset RAID. You can replace one disk with a larger one, let RAID rebuild then replace the other one, then resize the logical disk in OMSA in later versions, not sure about that working with S100.
If you are running clonezilla sector-by-sector on a PC and reintroduce the disk to the controller it will really confuse the controller since there will be duplicated metadata.
If you are running clonezilla sector-by-sector on a PC and reintroduce the disk to the controller it will really confuse the controller since there will be duplicated metadata.
"I've seen reference to PERC at boot time is all "
There should be a prompt for a keystroke to get into the controller. It should be straightforward (and safe as long as you don't change anything) to see how the RAID is configured. You can confirm if the PERC is actually doing the RAID (vs. software RAID), whether it is RAID 0 or 1, etc.
If you are running Windows Server, you can use Windows Server Backup to make a complete backup, remove the 1T drives, install the 2T drives, set up RAID on the PERC (assuming that was how it was done before), restore from the backup, then extend the partition.
Lee makes a very good point about VMs. If this is not set up as a VM, this may be a very good time to change.
There should be a prompt for a keystroke to get into the controller. It should be straightforward (and safe as long as you don't change anything) to see how the RAID is configured. You can confirm if the PERC is actually doing the RAID (vs. software RAID), whether it is RAID 0 or 1, etc.
If you are running Windows Server, you can use Windows Server Backup to make a complete backup, remove the 1T drives, install the 2T drives, set up RAID on the PERC (assuming that was how it was done before), restore from the backup, then extend the partition.
Lee makes a very good point about VMs. If this is not set up as a VM, this may be a very good time to change.
ASKER
CompProbSolv: Well, if this were *MY* system and time were not of the essence, then I might venture into changing into a VM. But that's not the case. No VM and no time to mess around. "Better is the enemy of good enough" This is good enough for the owner and the operations.
Lee W.: Interesting perspective. I'll remember that!
andyalder: "not sure"? Well, I haven't identified the controller yet or the RAID type#. Likely will within the next couple of hours.
I'm not really into experimenting with this system. I'd rather leave it unchanged.
*****
OK. So, this is PERC S100 and is RAID1 thank goodness.
Lee W.: Interesting perspective. I'll remember that!
andyalder: "not sure"? Well, I haven't identified the controller yet or the RAID type#. Likely will within the next couple of hours.
I'm not really into experimenting with this system. I'd rather leave it unchanged.
*****
OK. So, this is PERC S100 and is RAID1 thank goodness.
ASKER
andyalder:
So, the drive changes would work?
What other methods to resize then in case OMSA doesn't work?
then resize the logical disk in OMSA in later versions, not sure about that working with S100.Oh! I think you meant the resizing then?
So, the drive changes would work?
What other methods to resize then in case OMSA doesn't work?
If OMSA doesn't let you resize after swapping one after another then there is a slightly dodgy process called retagging. You delete the array after the swaps and create a new 2TB logical drive but select the option to not initialise it, since the controller hasn't written to the array the data/OS is still there.
May sound risky but you do have the old disks in hand so can put the last removed one back in and you're back where you started from. To avoid corruption on removed disks you shut down to remove them and you can't really write to the server in the mean time as the data on the old disks would be stale.
May sound risky but you do have the old disks in hand so can put the last removed one back in and you're back where you started from. To avoid corruption on removed disks you shut down to remove them and you can't really write to the server in the mean time as the data on the old disks would be stale.
ASKER
andyalder: Thanks! So, as I interpret it:
PERC S100 ... yes and RAID1
1) You replace one disk with a larger one.
2) Then let RAID rebuild.
3) Then replace the other one.
4) Then let RAID rebuild again.
5) Then resize the logical disk in OMSA in later versions, not sure about that working with S100.
6) You delete the array after the swaps/
7) Create a new 2TB logical drive but select the option to not initialise it.
(since the controller hasn't written to the array the data/OS is still there).
And then ......?
PERC S100 ... yes and RAID1
1) You replace one disk with a larger one.
2) Then let RAID rebuild.
3) Then replace the other one.
4) Then let RAID rebuild again.
5) Then resize the logical disk in OMSA in later versions, not sure about that working with S100.
6) You delete the array after the swaps/
7) Create a new 2TB logical drive but select the option to not initialise it.
(since the controller hasn't written to the array the data/OS is still there).
And then ......?
can put the last removed one back in and you're back where you started from.with what end result? one 1TB and one 2TB or?
And then ..
resize it in disk administrator.
resize it in disk administrator.
ASKER
I've found out that the system has Symantec System Recovery 2011 installed. They've been using it for selected data backup.
Presumably, it will do a bare metal backup and restore.
So, I may be able to use it to create a system backup and then recover the system onto the new, larger RAID1 array? Is that a normal operation? I've not quite found anything that would confirm that.
I did read that the *same connectors* need to be used for the drives... well, OK.
I've done this sort of thing enough times but not with RAID involved and not with Symantec System Recovery.
Clonezilla yes. Acronis yes. etc.
Presumably, it will do a bare metal backup and restore.
So, I may be able to use it to create a system backup and then recover the system onto the new, larger RAID1 array? Is that a normal operation? I've not quite found anything that would confirm that.
I did read that the *same connectors* need to be used for the drives... well, OK.
I've done this sort of thing enough times but not with RAID involved and not with Symantec System Recovery.
Clonezilla yes. Acronis yes. etc.
SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
The PERC drivers are already installed, there is no prep except creating a new array on the controller.
Quite frankly though I'd just add the two drives as another RAID 1 array and move the data across.
Quite frankly though I'd just add the two drives as another RAID 1 array and move the data across.
ASKER
Thanks all!
ASKER
andyalder: I'd thought of doing that. But, since it's the boot drive, what steps to take in that case?
Just move user data and remap user shares to the new location on D: or E:.
ASKER
andyalder: That sounds like you'd intend to KEEP the old array and boot from it.
My notion was to move the boot to the new array and get rid of the old drives or put them to use for storage of data only.
My notion was to move the boot to the new array and get rid of the old drives or put them to use for storage of data only.
Storage
Computer data storage, often called storage or memory, is a technology consisting of computer components and recording media used to retain digital data. In addition to local storage devices like CD and DVD readers, hard drives and flash drives, solid state drives can hold enormous amounts of data in a very small device. Cloud services and other new forms of remote storage also add to the capacity of devices and their ability to access more data without building additional data storage into a device.
45K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
NOT VMs? Shame on the installer of that system! Virtualize it, then reload it as a VM host and do the above!