Restore to Larger Drive (SSD) Questions

User discussion and information resource forum for Image products.

Restore to Larger Drive (SSD) Questions

Postby Muad'Dib » Sun Jul 07, 2019 1:34 pm

So today I finally replaced a 256 GB SSD (boot drive) with a 1 TB SSD. From within IFW, I backed up the entire drive, and then restored the TBI file to the new SSD (I used the "Scale to Target" option during the restore to increase my drive C partition size on the new drive). I then removed the old SSD, replaced it with the new one, rebooted, and so far everything is working fine. The only thing I was wondering about is that some additional very small unallocated partitions were created which border the copies of my original partitions. See attached image below for old and new drive partitions (after restore and before replacing/rebooting). The total space of these partitions (marked with red boxes) is about 5GB, so at the moment, it's not really a problem, it's just that I wasn't expecting to see these extra partitions.

I have a few questions about this:

1) Why did it happen?

2) Will it cause any problems (or, is there actually a benefit)?

3) If I want to get rid of the extra partitions, what's the most straightforward way of doing so now? Note that drive C: is encrypted with BitLocker, in case this matters. Also, this machine does not have any version of BootIt installed, and I probably won't be installing it in the near future (if ever), so if possible, please give me options/suggestions without assuming the use of BootIt.

4) How should I have done the backup (and/or restore) differently to avoid these additional partitions (your answer to #1 may also answer this question)?
Attachments
20190707 Old & New SSD partitions.png
20190707 Old & New SSD partitions.png (13.88 KiB) Viewed 197 times
Muad'Dib
 
Posts: 68
Joined: Mon Nov 21, 2011 5:23 am

Re: Restore to Larger Drive (SSD) Questions

Postby TeraByte Support » Sun Jul 07, 2019 10:57 pm

use scale to fit instead with remove gaps if you had any to start with.

to get rid of the gaps, you'd have to resize the partitions.


"Muad'Dib" wrote in message news:17353@public.image...

So today I finally replaced a 256 GB SSD (boot drive) with a 1 TB SSD. From
within IFW, I backed up the entire drive, and then restored the TBI file to
the new SSD (I used the "Scale to Target" option during the restore to
increase my drive C partition size on the new drive). I then removed the old
SSD, replaced it with the new one, rebooted, and so far everything is
working fine. The only thing I was wondering about is that some additional
very small unallocated partitions were created which border the copies of my
original partitions. See attached image below for old and new drive
partitions (after restore and before replacing/rebooting). The total space
of these partitions (marked with red boxes) is about 5GB, so at the moment,
it's not really a problem, it's just that I wasn't expecting to see these
extra partitions.

I have a few questions about this:

1) Why did it happen?

2) Will it cause any problems (or, is there actually a benefit)?

3) If I want to get rid of the extra partitions, what's the most
straightforward way of doing so now? Note that drive C: is encrypted with
BitLocker, in case this matters. Also, this machine does not have any
version of BootIt installed, and I probably won't be installing it in the
near future (if ever), so if possible, please give me options/suggestions
without assuming the use of BootIt.

4) How should I have done the backup (and/or restore) differently to avoid
these additional partitions (your answer to #1 may also answer this
question)?

TeraByte Support
 
Posts: 2737
Joined: Thu May 05, 2011 3:37 pm

Re: Restore to Larger Drive (SSD) Questions

Postby Muad'Dib » Mon Jul 08, 2019 12:48 pm

I had a few questions about this (not all were answered):

1) Why did it happen? --------> So I should have used "Scale to Fit" instead? The documentation doesn't really make it clear that when Scale to Fit should be used instead of Scale to Target. BTW, there were no gaps to start with (as is shown in Disk 3 in the attached image).

2) Will it cause any problems (or, is there actually a benefit)? ----------> Please answer.

3) If I want to get rid of the extra partitions, what's the most
straightforward way of doing so now? Note that drive C: is encrypted with
BitLocker, in case this matters. Also, this machine does not have any
version of BootIt installed, and I probably won't be installing it in the
near future (if ever), so if possible, please give me options/suggestions
without assuming the use of BootIt. --------------> Will BitLocker encryption on the C: drive affect using a partition manager?

4) How should I have done the backup (and/or restore) differently to avoid
these additional partitions (your answer to #1 may also answer this
question)? ----------> I guess this was answered in #1.
Muad'Dib
 
Posts: 68
Joined: Mon Nov 21, 2011 5:23 am

Re: Restore to Larger Drive (SSD) Questions

Postby TeraByte Support » Tue Jul 09, 2019 11:04 pm



"Muad'Dib" wrote in message news:17358@public.image...

I had a few questions about this (not all were answered):

1) Why did it happen? -------->

Because you scaled to target instead of scaled to fit. Manual talks about
difference.

2) Will it cause any problems (or, is there actually a benefit)? ---------->
Please answer.

No.


3) If I want to get rid of the extra partitions, what's the most
straightforward way of doing so now?

There aren't extra partitions, there are unpartitioned areas. Slide/Resize
partitions to take up the space. If bitlocker, disable so can be resized
and also slid faster.

4) How should I have done the backup (and/or restore) differently to avoid
these additional partitions (your answer to #1 may also answer this
question)? ----------> I guess this was answered in #1.

Just use scale to fit on restore (and you also have an option to remove
gaps).


TeraByte Support
 
Posts: 2737
Joined: Thu May 05, 2011 3:37 pm

Re: Restore to Larger Drive (SSD) Questions

Postby Muad'Dib » Wed Jul 10, 2019 2:14 am

Thank you. That was very helpful.
Muad'Dib
 
Posts: 68
Joined: Mon Nov 21, 2011 5:23 am


Return to Image for DOS/Linux/Windows

cron