Aug. 19th, 2010

bellinghman: (Default)
Last night, we used Acronis to clone [livejournal.com profile] bellinghwoman's main hard drive. The existing drive was 80 GB, split into two equal partitions. The target drive was 2 TB, and we decided that it should be partitioned as ~1780 GB for C:, and ~70 GB for the other partition. (Yes, that sums to 2 TB, as measured by drive manufacturers.)

This requires some manual picking rather than the 'just do it' option, but we picked the relevant settings, let it reboot so it could get exclusive access to the drives, and off it went, while [livejournal.com profile] bellinghwoman retired to bed.

It took me a little while to note that it was actually copying the first partition to a 932 GB target.

And it copied the second partition to a 932 GB target partition.

Oh, thought I, it screwed up, we'll have to retry once it's finished all of this.

And then once it had finished copying that second partition, it started resizing it back down to the size we'd asked for.

And once it had finished that, and there was space before that second partition, it resized the first partition all the way up to the size we'd asked for.

And it finally finished, leaving the right partition size after all.

I'd love to know just why on earth it didn't make the target partitions the right sizes in the first place.
bellinghman: (Default)
Last night, we used Acronis to clone [livejournal.com profile] bellinghwoman's main hard drive. The existing drive was 80 GB, split into two equal partitions. The target drive was 2 TB, and we decided that it should be partitioned as ~1780 GB for C:, and ~70 GB for the other partition. (Yes, that sums to 2 TB, as measured by drive manufacturers.)

This requires some manual picking rather than the 'just do it' option, but we picked the relevant settings, let it reboot so it could get exclusive access to the drives, and off it went, while [livejournal.com profile] bellinghwoman retired to bed.

It took me a little while to note that it was actually copying the first partition to a 932 GB target.

And it copied the second partition to a 932 GB target partition.

Oh, thought I, it screwed up, we'll have to retry once it's finished all of this.

And then once it had finished copying that second partition, it started resizing it back down to the size we'd asked for.

And once it had finished that, and there was space before that second partition, it resized the first partition all the way up to the size we'd asked for.

And it finally finished, leaving the right partition size after all.

I'd love to know just why on earth it didn't make the target partitions the right sizes in the first place.

May 2016

S M T W T F S
1234 567
891011121314
15 1617 18192021
22232425262728
293031    

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags
Page generated Aug. 14th, 2025 08:35 pm
Powered by Dreamwidth Studios