expand VHD strange failure

I had a 1500GB VHD that i have expanded by shutting down the VM and then in the host changing it to 2000GB. (it said max was 2040, im assuming the MBR limit, so i chose a little less than that)

Once i rebooted the guest I could see the extra 500GB partition. So I did the usual right click, expand partition to use the new free space.

However it then gave a strange error:

Code:

---

Log Name:      System
Source:        VDS Basic Provider
Date:          24/11/2012 11:31:40 PM
Event ID:      1
Task Category: None
Level:        Error
Keywords:      Classic
User:          N/A
Computer:      fileserver1
Description:
Unexpected failure. Error code: 490@01010004

---

It shows up in Computer Management Storage as a 2000GB drive

However in Computer the drive still shows as a 1500gb drive. IVe ran scandisk in windows and it reports no errors and the capacity as 1500gb.

This is strange, and its the main staff fileserver too so need to sort it ASAP ...

Is there something stupid Ive missed?

also on the LUN its on in the SAN there is plenty of space on the LUN.

bumped for the GMT folk :)

Another way to do it
Shut down server ‘A’ (the server who’s vhd you want to extend)

Attach this shutdown server ‘A’ vhd to another server ‘B’ as an additional drive (using hyper v manager)

Fire up the server ‘B’ that now has the server A as an additional drive

Check computer management\ disk management to see if the disk is visible

Open a cmd prompt
Type diskpart
Type List disk
NOW select the relevant disk, you should be able to tell by the size

Eg type select disk=2

Type list partition

Select partition=1
Type extend

Type exit


Now within disk management you should see all the disk space allocated

Shutdown server ‘B’

Remove server ‘A’ as an additional disk and reattach it to original server in hyper v manager

Start server and all should be OK

Drop me a PM tomoz if it doesn’t work and I’ll help you out

thanks for the reply, great idea. Havent had a chance to do any of it yet as it will require out of hours work and I wont get a chance till Saturday or Sunday. Will let you know how it goes.

This does work, we use this method on our older w2k3 hyperV guest (.vhd) servers as you cannot expand the system disk, basically just add it as a additonal disk to another hyperV server and run the cmds and hey presto all sorted

Mike