I have been using Linux as my primary OS since 1999ish, except for a brief period early in the history of 67 Bricks when I had an iMac. Whenever I have used Windows it has invariably been in some kind of virtualised form; this was necessary in the iMac days when I was developing .NET applications in Visual Studio, but these days I work solely on Scala / Play projects developed in IntelliJ in Linux. Nevertheless, I have found it convenient to have an installation of Windows available for the rare instances where it’s actually necessary (for example, to connect to someone’s VPN for which no Linux client is available).
My Windows version of choice is the venerable Windows 7. This is the last version of Windows which can be configured to look like “proper Windows” as I see it by disabling the horrible Aero abomination. I tried running the Windows 10 installer once out of morbid curiosity, it started talking to me, so I stopped running it. I am old and set in my ways, and I feel strongly that an OS does not need to talk to me.
So anyway, I had a VirtualBox installation of Windows 7 and, because I am an extraordinarily kind and generous soul, I had given it a 250G SATA SSD all to itself using VirtualBox’s raw hard disk support.
Skip forward a few years, and I decided I would increase the storage in my laptop by replacing this SSD with a 2TB SSD since such storage is pretty cheap these days. The problem was – what to do with the Windows installation? I didn’t fancy the faff of reinstalling it and the various applications, and in fact I wasn’t even sure this would be possible given that it’s no longer supported. In any case, I didn’t want to give Windows the entire disk this time, I wanted a large partition available to Linux.
It turns out that VirtualBox’s raw disk support will let you expose specific partitions to the guest rather than the whole disk. The problem is that with a full raw disk, the guest sees the boot sector (containing the partition table and probably the bootloader), whereas you presumably don’t want the guest to see the boot sector if you’re only exposing certain partitions. How does this work?
The answer is that when you create a raw disk image and specify specific partitions to be available, in addition to the sda.vmdk
file, you also get a sda-pt.vmdk
file containing a copy of the boot sector, and this is presented to the guest OS instead of the real thing. Here, then, are the steps I took to clone my Windows installation onto partitions of the new SSD, keeping a partition free for Linux use, and ensuring Windows still boots. Be warned that messing about with this stuff and making a mistake can result in possibly irrecoverable data loss!
Step 1 – list the partitions on the current drive
My drive presented as /dev/sda
$ fdisk -x /dev/sda
Disk /dev/sda: 232.89 GiB, 250059350016 bytes, 488397168 sectors
Disk model: Crucial_CT250MX2
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0xc3df4459
Device Boot Start End Sectors Id Type Start-C/H/S End-C/H/S Attrs
/dev/sda1 * 2048 206847 204800 7 HPFS/NTFS/exFAT 0/32/33 12/223/19 80
/dev/sda2 206848 488394751 488187904 7 HPFS/NTFS/exFAT 12/223/20 1023/254/63
Step 2 – create partitions on the new drive
I put the new SSD into a USB case and plugged it in, whereupon it showed up as /dev/sdb
Then you need to do the following
- Use
fdisk /dev/sdb
to edit the partition table on the new drive - Create two partitions with the same number of sectors (204800 and 488187904) as the drive you are hoping to replace, and then you might as well turn all of the remaining space into a new partition
- Set the types of the partitions correctly – the first two should be type 7 (HPFS/NTFS/exFAT), if you’re creating another partition it should be type 83 (Linux)
- Toggle the bootable flag on the first partition
- Use the “expert” mode of fdisk to set the disk identifier to match that of the disk you are cloning; in my case this was 0xc3df4459 – Googling suggested that Windows may check for this and some software licenses may be tied to it.
So now we have /dev/sdb
looking like this:
$ fdisk -x /dev/sdb
Disk /dev/sdb: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: 500SSD1
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xc3df4459
Device Boot Start End Sectors Id Type Start-C/H/S End-C/H/S Attrs
/dev/sdb1 * 2048 206847 204800 7 HPFS/NTFS/exFAT 0/32/33 12/223/19 80
/dev/sdb2 206848 488394751 488187904 7 HPFS/NTFS/exFAT 12/223/20 705/42/41
/dev/sdb3 488394752 3907029167 3418634416 83 Linux 705/42/42 513/80/63
Note that the first two partitions are an exact match in terms of starts, end and sector count. I think we can ignore the C/H/S (cylinder / head / sector) values.
Step 3 – clone the data
Taking great care to get this right, we can use the dd
command and we can tell it to report its status from time to time so we know something is happening. There are two partitions to clone:
$ dd if=/dev/sda1 of=/dev/sdb1 bs=1G status=progress
... some output (this is quite quick as it's only 100M)
$ dd if=/dev/sda2 of=/dev/sdb2 bs=1G status=progress
... this took a couple of hours to copy the partition, the bottleneck probably being the USB interface
Step 4 – create (temporarily) a VirtualBox image representing the new disk
There are various orders in which one could do the remaining steps, but I did it like this, while I still had /dev/sda
as the old disk and the new one plugged in via USB as /dev/sdb
$ VBoxManage internalcommands createrawvmdk -filename sdb.vmdk -rawdisk /dev/sdb -partitions 1,2
This gives two files; sdb.vmdk
and sdb-pt.vmdk
. To be honest, I got to this point not knowing how the boot sector on the disk would show up, but having done it I was able to verify that sdb-pt.vmdk
appeared to be a copy of the first sector of the real physical disk (at least the first 512 bytes of it). I did this by comparing the output of xxd sdb-pt.vmdk | head -n 32
with xxd /dev/sdb | head -n 32
which uses xxd
to show a hex dump and picks the first 32 lines which happen to correspond to the first 512 bytes. In particular, you can see at offset 0x1be
the start of the partition table, which is 4 blocks of 16 bytes each ending at 0x1fd
, with the magic signature 55aa
at 0x1fe
. The disk identifier can also be seen as the 4 bytes starting at 0x1b8
. And note that everything leading up to the disk identifier is all zeroes.
Step 5 – dump the boot sector of the existing disk
At this point, we have /dev/sda
with the bootsector containing the Windows bootloader, we have a freshly initialised /dev/sdb
containing a copy of the Windows partitions and a bootsector that’s empty apart from the partition table and disk identifier, and we have the sdb-pt.vmdk
file containing a copy of that empty bootsector. We have also arranged for the new disk to have the same identifier as the old disk.
What is needed now is to create a new sdb-pt.vmdk
file containing the bootloader code from /dev/sda
and then the partition table from /dev/sdb
. There are 444 bytes that we need from the former. So we can do something like this:
$ head -c 444 /dev/sda > sdb-pt-new.vmdk
$ tail -c +445 sdb-pt.vmdk >> sdb-pt-new.vmdk
We can confirm that the new file has the same size as the original, we can also use xxd
to confirm that we’ve got the bootloader code and then everything from that point is as it was (including the new partition table)
Step 6 – the switch
We’re almost done. All that’s left to do is:
- Replace the old SATA SSD with the new 2TB SSD
- Run VirtualBox – do not start Windows but instead remove the existing hard drive attached to it (which is the “full raw disk” version of
sda.vmdk
), and use the media manager to delete this. - Quit VirtualBox
- Recreate the raw disk with partitions file but for
/dev/sda
(which is what the new drive is): VBoxManage internalcommands createrawvmdk -filename sda.vmdk -rawdisk /dev/sda -partitions 1,2
- The previous command will have created the
sda-pt.vmdk
boot sector image from the drive, which will again be full of zeroes. Overwrite this with the sdb-pt-new.vmdk
that we made earlier, obviously ensuring we preserve the original sda-pt.vmdk
name and the file permissions. - Start VirtualBox, add the newly created
sda.vmdk
image to the media manager, and then as the HD for the Windows VM - Start the Windows VM and hope for the best
I was very gratified to find that this worked more-or-less first time. In truth, I originally just tried replacing the old sda.vmdk
with the new one, which gave the error “{5c6ebcb7-736f-4888-8c44-3bbc4e757ba7} of the medium ‘/var/daniel/virtualbox/Windows 7/sda.vmdk’ does not match the value {e6085c97-6a18-4789-b862-8cebcd8abbf7} stored in the media registry (‘/home/daniel/.config/VirtualBox/VirtualBox.xml’)”. It didn’t seem to want to let me remove this missing drive from the machine using the GUI, so I edited the Windows 7.vbox
file to remove it, then removed it from the media library and added the replacement, which I was then able to add to the VM.