C DRIVE EXPANSION FOR WINDOWS 2003

C DRIVE EXPANSION FOR WINDOWS 2003


Extend System Partition on a Windows Server 2003 VM using Dell ExtPart

This explains the steps to Expand C-drive on Windows 2003 server without downing the server. There is no native tool that enables extending system partitions (C:\ drives) on Server 2003.
There are multiple ways to perform this task, however, the only method that can be done online utilizes a Dell utility called ExtPart. It can perform the extension of the system partition with no downtime although sometimes booting into Safe Mode and then running ExtPart is necessary to clear locks on the disk.
Note: This applies to Server 2003 only, newer versions of Windows do not suffer from this limitation, Disk Management as well as the disk part are able to extend system partitions on-the-fly.
Procedures:
The first step is to download the ExtPart utility from (http://www.dell.com/support/home/us/en/04/Drivers/DriversDetails?driverId=R64398) link. Click on the Download File link and save it to your desktop. The file is a self-extracting zip file called ExtPart.exe per the below:

Double-click on it and accept the default path it will extract the utility to:

Click on Unzip and the files will be extracted successfully:

To demonstrate how useful ExtPart is we will use an example whereby our demo VM has a 15 GB C:\ drive and it needs to be increased to 30 GB. A screenshot of the current state of the C:\ drive is below:

We go into the VM settings and can see that the virtual disk is indeed 15 GB in size:

We increase the virtual disk size to 30 GB and apply the change:

Within the VM load Disk Management and select Action > Rescan Disks so that the system sees the newly added 15 GB of storage:

After the re-scan completes you will now see the extra 15 GB of unallocated space:

Now we need to run the ExtPart utility expand the C:\ drive so that it utilizes the 15 GB of unallocated space. To proceed, open the command prompt and go to the location where you extracted the ExtPart utility, in my case, C:\dell\ExtPart:
C:\>cd C:\dell\ExtPart


Then run ExtPart.exe:
C:\dell\ExtPart>extpart.exe Enter the volume that is being expanded, in this example it is the C:\ drive so enter just C: without the backslash:
Volume to extend (drive letter or mount point): C: Then enter the amount in MB to increase the volume by, I entered 15343:
Size to expand the volume (MB): 15343 The output will confirm the new size of the volume (C:\ drive), which is 30678 MB:
New volume size :30678 MB (32169069568 bytes) The full sequence of commands can be seen in the screenshot below:


When going back into Disk Management and re-scanning the disks, we can see that there is still31 MB that is unallocated:

To add that remaining 31 MB to the C:\ drive, we go back to ExtPart and perform the same series of steps but this time add 31 MB:
Size to expand the volume (MB): 31 A screenshot of those steps is below:

Now going back into Disk Management you can see that the C:\ drive is using all of the provisioned space in the disk:

Troubleshooting Steps:
If the utility returns an error such as “the disk is not accessible” or “unable to connect to C:”
1. Close Windows Disk Management console. It’s using Logical Disk Management service which extpart.exe is using.
2. Make sure there are no snapshots
3. Stop some non-essential services i.e.:
• Windows Search
• Indexing Service
Also stop Logical Disk Management Service If it shows running status.

Comments

Post a Comment

Popular posts from this blog

Troubleshooting PSOD

Purple Screen of Death or commonly known as  PSOD  is something which we see most of the times on ESXi host. Usually when we experience PSOD, we take the screenshot of PSOD and reboot the host and then capture the logs and upload it to VMware support for analysis. Let’s analyze the dumps by yourself? Step 1:  Sometimes, we might miss out on the screenshot of PSOD. Well that's alright! If we have core-dump configured for the ESXi, we can extract the dump files to gather the crash logs. Once the host is back up from accident reboot post PSOD, login to the SSH/Putty of the host and go to the core directory. The core directory is the location where your PSOD logging go to. The most important one is the “Core” folder which contains the kernel dump, the PSOD will purge what was in memory to a file called vmkernel-zdump.1 or something to that affect and place it in that directory. So go to # cd var/core  Then list out the files here using ls –ltr . ...
Read more

Avamar & Netbackup Backup Troubleshooting Steps

AVAMAR Backup Failure Troubleshooting Steps 1)       Login to server 2)       Check the system Tray Icon for Avamar Agent 3)       If the check mark shows green Avamar client is communicating with backup Server (Follow the below troubleshooting Steps mentioned at the end of this document to fix the issue) 4)       If the Check Mark Shows Red It means the client is communicating the server but the last backup was Failed (Follow the below troubleshooting Steps mentioned at the end of this document to fix the issue) 5)       If the Check Mark Is Orange it means the Client is not communicating with backup server(Follow the below Steps and later Follow the below troubleshooting Steps mentioned at the end of this document to fix the issue) i)                  ...
Read more
Image
Real Time Isuue " Create virtual machine snapshot " Error : An error occurred while saving the snapshot : Change tracking target file already exists. Resolution :  1.Connect to the ESXi host that the virtual machine is running on using SSH. 2.Navigate to the virtual machine folder using this command.   cd /vmfs/volumes/datastore/virtual_machine/ 3.List the contents of the directory using the ls command and look for .ctk files. Create a temporary directory for the ctk files For example: mkdir temp Move the CBT files to this directory with this command: mv *-ctk.vmdk temp/ 4.Run the snapshot consolidation again.
Read more