On Tue, May 17, 2011 at 12:21 AM, Stroller
strol...@stellar.eclipse.co.ukwrote:
On 16/5/2011, at 12:56pm, Adam Carter wrote:
...
Yes the new drive is bigger, going from 66G to 500G. Single partition
only, ...
So how do i proceed? Is it;
1. dd the mbr without partition table, to get
On Monday 16 May 2011 02:01:13 Adam Carter wrote:
WRT why it stopped after 10MB, if i specified a smaller size it would just
stop after whatever was specified, so its just doing a single chunk equal
to whatever bs has been specified as.
I recall zeroing drives/partitions and getting this
To check my understanding - would it be correct to say that;
1. Using dd to copy the first 512 bytes (MBR) is ALL that is needed to
setup the partitions - that is i wont need to run fdisk etc afterward.
This is correct if you only have primary partitions. It will not copy the
extended
On 16 May 2011 07:31, Adam Carter adamcart...@gmail.com wrote:
To check my understanding - would it be correct to say that;
1. Using dd to copy the first 512 bytes (MBR) is ALL that is needed to
setup the partitions - that is i wont need to run fdisk etc afterward.
This is correct if you
On Mon, 16 May 2011 11:37:10 +0100, Mick wrote:
Then you can use gparted and resize partitions, add new ones, etc.
BTW do not resize ntfs partitions unless you have booted into them
defragged them first.
If you're going to resize/move partitions afterwards, you may as well
just dd the whole
On 16 May 2011 11:45, Neil Bothwick n...@digimed.co.uk wrote:
On Mon, 16 May 2011 11:37:10 +0100, Mick wrote:
Then you can use gparted and resize partitions, add new ones, etc.
BTW do not resize ntfs partitions unless you have booted into them
defragged them first.
If you're going to
On Mon, 16 May 2011 12:16:51 +0100, Mick wrote:
If you're going to resize/move partitions afterwards, you may as well
just dd the whole drive in one go.
But the OP's new drive is larger, so I assume that he will be
rearranging partitions afterwards - could be wrong.
So if you've got to
But the OP's new drive is larger, so I assume that he will be
rearranging partitions afterwards - could be wrong.
So if you've got to rearrange the partitions anyway, it is easier to just
dd the whole thing in one go and then do the rearranging.
Alternatively, set up the new partition
On 16/5/2011, at 12:56pm, Adam Carter wrote:
...
Yes the new drive is bigger, going from 66G to 500G. Single partition only,
...
So how do i proceed? Is it;
1. dd the mbr without partition table, to get the boot code (so bs=446
count=1)
2. use fdisk to set one big primary partition,
On 16 May 2011 15:21, Stroller strol...@stellar.eclipse.co.uk wrote:
On 16/5/2011, at 12:56pm, Adam Carter wrote:
...
Yes the new drive is bigger, going from 66G to 500G. Single partition only,
...
So how do i proceed? Is it;
1. dd the mbr without partition table, to get the boot code (so
On 16/5/2011, at 4:35pm, Mick wrote:
GParted is the next choice, then - I understand it to be more than just a
graphical front-end, and I don't think you'll have such good results trying
to use command-line tools to expand NTFS partitions.
...
After your dd the data over to the new disk
On Monday 16 May 2011 17:03:36 Stroller wrote:
On 16/5/2011, at 4:35pm, Mick wrote:
GParted is the next choice, then - I understand it to be more than just
a graphical front-end, and I don't think you'll have such good results
trying to use command-line tools to expand NTFS partitions.
On Mon, 16 May 2011 16:35:07 +0100, Mick wrote:
Only to add that the new larger drive will appear as small as the
original because the fs size is after all that of the smaller drive.
After your dd the data over to the new disk you will need to run
gparted as suggested by Stroller, or use
On Monday 16 May 2011 20:54:58 Neil Bothwick wrote:
On Mon, 16 May 2011 16:35:07 +0100, Mick wrote:
Only to add that the new larger drive will appear as small as the
original because the fs size is after all that of the smaller drive.
After your dd the data over to the new disk you will
On Sunday 15 May 2011 17:45:05 Adam Carter wrote:
I'm cloning a windows disk using gentoo;
On the old 66GB disk;
# dd if=/dev/sdb of=/root/winmbr.bin bs=512 count=1
# dd if=/dev/sdb1 bs=10M | gzip -v winpartition.gz
Then after swapping in the new 500GB disk;
dd if=/root/winmbr.bin
Joost Roeleveld writes:
On Sunday 15 May 2011 17:45:05 Adam Carter wrote:
Why is dd saying no space left after copying 10MB when sdb1 is 65GB?
Did you reboot after the first dd?
Probably, undless he is using som external drive.
Or at least, force a re-read of the partition tables?
On Sunday 15 May 2011 08:45:05 Adam Carter wrote:
I'm cloning a windows disk using gentoo;
On the old 66GB disk;
# dd if=/dev/sdb of=/root/winmbr.bin bs=512 count=1
# dd if=/dev/sdb1 bs=10M | gzip -v winpartition.gz
Then after swapping in the new 500GB disk;
dd if=/root/winmbr.bin
On Sunday 15 May 2011 18:52:21 Mick wrote:
On Sunday 15 May 2011 08:45:05 Adam Carter wrote:
I'm cloning a windows disk using gentoo;
On the old 66GB disk;
# dd if=/dev/sdb of=/root/winmbr.bin bs=512 count=1
# dd if=/dev/sdb1 bs=10M | gzip -v winpartition.gz
Then after swapping
On Sunday 15 May 2011 19:15:16 Volker Armin Hemmann wrote:
On Sunday 15 May 2011 18:52:21 Mick wrote:
On Sunday 15 May 2011 08:45:05 Adam Carter wrote:
I'm cloning a windows disk using gentoo;
On the old 66GB disk;
# dd if=/dev/sdb of=/root/winmbr.bin bs=512 count=1
# dd
On Sunday 15 May 2011 19:40:30 Mick wrote:
On Sunday 15 May 2011 19:15:16 Volker Armin Hemmann wrote:
On Sunday 15 May 2011 18:52:21 Mick wrote:
On Sunday 15 May 2011 08:45:05 Adam Carter wrote:
I'm cloning a windows disk using gentoo;
On the old 66GB disk;
# dd if=/dev/sdb
WRT why it stopped after 10MB, if i specified a smaller size it would just
stop after whatever was specified, so its just doing a single chunk equal to
whatever bs has been specified as.
I think the re-read of the partition table is probably the problem - so
thanks for that suggestion.
To check
21 matches
Mail list logo
