On Sun, 23 Nov 2014 00:45:38 +0100, Pascal Hambourg wrote:
Gary Dale a écrit :
On 22/11/14 06:29 PM, Hendrik Boom wrote:
And it's not hard to copy the file systems, either. I can temporarily
access the new drive using a USB adaptor. fdisk and the lvm utilities
will create the new partitions and then I copy, using dd or rsync or
tar/
[...]
Have you considered getting a USB case for your new drive and doing dd
from your current drive to the new one? Afterward you can install the
new drive then boot from gparted/rescue disk and resize your
partitions.
If the original disk already uses LVM, no need to resize partitions.
Just create another PV in the extra space.
dd-ing the whole drive would lead to the extra space being after all four
partitions. Unfortunately, it's the second partition that contains the
LVM stuff. I'd end up having to move partitions 3 and 4 to the end of
the disk to get the space int partition 2 where it's needed. I have no
idea whether Windows cares about whether the hidden and the EFI
partitions re actually partitions 3 and 4.
But dding the start of the disk, enough to copy the entire windows
partition and the stuff before the first one might be a good idea.
Unless the MBR or something related to it contains information about the
size of the entire disk, which will now be wrong. And it;s the space
before the first partition which is likely to contain the crucial boot
information that Windows might want. That ans the EFI partition, of
course.
It's possible that this might not work well if the hard drive has
significantly different fake geometry. It's just possible that some
things still have to start on cylinder boundaries, however undefined
those are nowadays.
It will contain information about partitions 2, 3, and 4, which I can
delete and change with fdisk. And then still copy partitions 3 and 4 with
dd some some such. I think those partitions are FAT partitions of some
flavour. The EFI has to be if it conforms to standards.
-- hendrik