Expanding a VirtualBox VDI file for Server 2008 x64 R2

By -
I use virtual box as my SharePoint VM host because I want to be able to run 64bit Server 2008 R2 on my Windows 7 host machine.   When I first installed SharePoint 2010, the VDI (Virtual Disk for VirtualBox) I created was too small, so I had to expand it.   This is a bit of a challenge, but by doing some research I figured out how to do it.

The process involves creating a new, larger disk and copying the original boot and main partitions to the newer disk.   This can be done with gparted.  and the steps to do so are well documented here


However there are a few more steps you'll need to follow because you are using 64bit Server 2008 R2:
  • After you've followed the above instructions, mount the newer larger drive as the Primary Master and mount the Server 2008 R2 ISO.
  • Boot to the ISO (hitting any key when prompted)
  • Choose your language then on the next screen select repair
  • Select the partition and click ok
  • Choose the command line option
  • Switch to your c: drive
  • Type bootrec.exe /fixboot
  • Type bootrec.exe /rebuildbcd and after it runs successfully type A and hit enter to add the entry to the BCD store
  • Type exit and reboot the machine.
  • The machine should load, but kind of slowly, and then scandisk will run (allow it to run to completion), then windows should come back up.


Comments

Post a Comment

Popular posts from this blog

ERROR: Failed to create feature receiver...

By -
I was working on a STSDev project which deployed a feature with a feature receiver. I had the feature working without the FeatureReceiver but as soon as I added the FeatureReceiver related attributes to my <Feature> element I got the following error: Failed to create feature receiver object from assembly "Org.Project.Solution, Version=1.0.0.0, Culture=neutral, PublicKeyToken=c632353d405b3209", type "Org.Project.Solution.MyFeature.FeatureReceiver" for feature 6a9b2358-ea4e-486d-a4e4-4f813c52ce88: System.ArgumentNullException: Value cannot be null. Parameter name: type at System.Activator.CreateInstance(Type type, Boolean nonPublic) at System.Activator.CreateInstance(Type type) at Microsoft.SharePoint.Administration.SPFeatureDefinition.get_ReceiverObject() After much digging around I discovered that STSDEV's Solution config file refers to a namespace as well as the dll. My FeatureReceiver's namespace was not prefixed with the right namespace So just
Read more

Renaming a Sharepoint 2007 / WSS 3.0 Server

By -
I recently needed to rename my Sharepoint development machine so I could move it into a new collaborative development environment (versus standalone in a workgroup). A little searching turned up this tutorial [www.jjfblog.com] from a while back, which worked with a slight modification. I have reposted the contents of the tutorial below, with a slight modification (see original post and comments for details). Note: The new collaborative environment uses Team Foundation Server 2008, so look for a later post on collaborative Sharepoint development using TFS. First: Change each alternate access mapping for your MOSS/WSS deployment in Central Administration Open Central Administration Click on the “Operations” Tab Click on the “Alternate access mappings” link under the “Global Configuration” heading Modify each mapping item to reflect your newly chosen server name, making sure to keep port numbers the same (this also include the mapping for Central Administration, don’t worry it's
Read more