Link to home
Start Free TrialLog in
Avatar of netbones
netbonesFlag for United States of America

asked on

Resize Partition on Dell T110 PERC S100

We have a Dell T110 server that is simply running out of space on the C: drive.  The OS defaulted to 12Gb during install and we are continually hitting that limit, causing problems of course. There is another partition of ~140Gb for data.

The OS & Data drive are configured in the PERC S100 "software" controller as RAID 1 with another drive, both 160Gb.

I replaced drive 0:1 with a 320Gb drive, resync'd and that's ok. Did the same with the 0:0 drive and now I have two new 320Gb drives, however they are being controlled by the PERC controller and I cannot resize them under Windows Server 2003 R2, even with 3rd party tools.

Any ideas?
Avatar of suribaba801

Create yourself a bootable 'puppy linux' cd or usb.
This small os of 100 mb includes gparted to resize logical drives and it will absolutely recognize your raid controller so you can access disks and resize any logical drive: its free and powerfull.

Let me know what u think.
Avatar of nobus
use the free paragon partition manager, it lets you resize easily :
Avatar of skullnobrains

Link to home
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Don't resize your partitions, it isn't necessary. 12GB for 2003 server is quite adequate for the system partition. You should rather follow leew's suggestions in the link below which explains how the system partition is properly managed. He is one of EE's top experts:
it's not that easy to change an existing system to a set of generic good practices.
and it is a pity to see that managable system directory size which used to be a feature in windows2000 (if you configured it properly) and a must-have in any decent OS is something that would take hours of work to achieve on later versions.

now some steps are easy and can help to gain a lot of space quickly
- move a profile directory
- move the swap file
- remove a bunch of restoration points
- disable indexing service and remove the files
- uninstall a few big programs and reinstall them on another drive

i'd recommend more complex steps such as the ones described in the article or the linked folders hack i mentioned above only if you identify an endlessly growing directory and you consider this behavior as acceptable as long as it does not eat up the system drive

once more treesize is THE good tool that will let you know what is eating up your drive in a matter of seconds. it is free, and  clean software.

like @rindi, i think that there should be a reasonably clean and much easier solution than repartitionning if you have 12G on your system drive.
Link to home
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Does it mean that in Windows Disk Management you don't see the new space?
Avatar of netbones


The free space is not visible in Disk Manager.  

I have no option to resize the drive in the PERC controller configuration. I tried blowing away the data drive (freeing it up), and I still could not extend.

So, it looks like I have to backup/restore.

Would GHOST work?
GHOST is supposed to work, but only if it has the right drivers.  This is a VERY common controller.  Read the release notes and verify.  If this was my data I would never trust a software product to backup then restore over my backup if I didn't test it on a scratch drive first.

... it just isn't worth the aggravation if there is a problem, and you really don't know if problem is that the backup is no good, or the restore is no good, until you do both.

Old 160GB or larger disks are cheap, maybe you have an old USB-attached one or one from an old computer.  You can pick them up used for $10-20 at a used equipment dealer.   I've seen backups go bad with Ghost and other products, and worst case if you test you have a copy of the data you can give to a family member for an offsite backup just in case of a disaster.  

Remember, even if the backup works perfectly, it doesn't protect data against doing something stupid like deleting the wrong files.
Does the RAID utility not give a chance to allocate the space to virtual volume?
Yes, Noxcho - this older controller does not provide such a feature.
Correct, unfortunately.  I've tried using a ghost boot cd with the original drive and a new drive, using -fni as the options.  It sees the drives, gets to the point where I can tell it to clone, and then within a few seconds comes back as done (although it's not). It creates a 200Mb partition on the new drive and that's it.

Any recommendations for offline drive cloning?
I clone all day long by getting a USB stick loading it with Ubuntu LINUX.  Then use the built in partition magic (or partition manager, sorry, can't remember).

BUT .. this must done with the disks behind the PERC. Reason, there is metadata at the beginning of the drive.   So you have to put both source and destination drives in at the same time.  Build the RAID1 on the destination disks with the PERC, then image.

If you weren't cloning with the PERC, then that would explain why Ghost fails too.  Ghost is dealing with the metadata at the beginning and is confused.
I'll try that - cloning while attached to the PERC.  I'll let you know how it goes.
Just a little more help here please -

The server has 4 disks :

RAID 1 - Drives 0:0 & 0:1
Non-Raid: 0:2 & 0:3 - these are software raid 1 using Windows Disk Management.

Should I remove 0:2 & 0:3, replace with new bigger drivers and set as RAID1 in PERC, and then boot to Ghost and image RAID1 (0:0/0:1) to the new RAID1 (0:2/0:3)?
No, I would leave 0:2 / 0:3 alone.   Create the backup as-is.  Then shut down.  Replace the 0:0/0:1 with the NEW disks, build a new group, then restore.

Document all RAID settings before doing anything. go through every screen on the controller, just in case.
i think solving the problem in windows really is much easier, but it's your choice to follow the resizing route.

just to clear why you could not resize from any windows tool : windows see the different LUNs as different physical units, and expanding a physical unit is meaningless

beware that windows does not like drive ids to change so a cloned system running on a different LUN might end up unbootable in some cases.

other than that clones proovably work
Windows doesn't see the extra space - the LUN is defined in the PERC controller as 160Gb, and any unused space isn't shown.  Windows tools won't see the space if the PERC controller doesn't so that's why I have to do this from the PERC side.

In my previous question, I was referring to using Ghost to clone the RAID 1 volume. Since there are only 4 connections to the PERC interface, I was thinking I could take out the 0:2/0:3 volume (it's not being set as RAID1, only defined in Windows), put in new drives and setup a new RAID 1 that I could then use Ghost to clone to, then put those 2 drives in the 0:0 and 0:1 slot.

Link to home
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Thanks! I'll give it a shot. I have all the drives and backups already protected so if it doesn't work I can easily go back. I'll be working on this later today and I'll post my results and apply points.
if you configure a bigger LUN elsewhere, you should be able to directly dd either the disk if there is no metadata at the beginning (easy to see using the file command on the raw device) or a specific partition if you're unsure.

you may have to run fixmbr from the recovery cd or a tool doing the same task depending on how you created the partitions and in what order the LUNs are presented
Link to home
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
The easiest way IMHO is the to take backup when the smaller drives are in RAID then reconfigure the RAID with bigger drives and simply restore from backup using Ghost boot CD.
Thanks to all of you - I was able to get the OS cloned to a larger partition with Ghost, but only by booting the system directly and doing the clone.  I previously had the OS drive on a seperate system trying to ghost it but that didn't work (see previous comments).

I can't wait to get these guys on another server!