Windows will randomly rewrite the MBR

Force the cloned disk image onto a smaller disk


I have an image captured using Clonezilla as a SAVEDISK on a 160GB hard drive.
A newer version of the PC with a 120 GB hard drive is now available. The used storage space is only 20 GB

Is there some way to force Clonezilla (or some other program) to change the original size of the pictures to 120GB or less so that Clonezilla can write them to the new PC?





Reply:


Clonezilla relies on Partclone to save and restore file systems. While it is useful, even using the option, that alone is not enough. When restoring the original file system on the smaller hard drive, Partclone encounters a search error that tries to write beyond the hard drive's limit. So this is a limitation not only of Clonezilla but also of the underlying tools that it uses.

However, you can temporarily restore the image to a 160 GB hard drive and use a file system resizing tool such as a. B. (for NTFS) or (for ext3 / 4) to reduce the file system, for example to 25 GB. There is no need to resize the partition table like GParted does. Use Clonezilla again to create a new image using the savedisk option.

When restoring the image to the smaller hard drive, use the option to skip clonezilla and verify that the hard drive is the same as or larger than the original hard drive. Since you have shrunk the file system, Partclone will not encounter a search error and your data will be restored to your smaller hard drive.

If you used the proportional recovery of the partition table option (), Clonezilla creates an appropriate partition table and changes the size (extension) of the original file system so that all of the free space becomes available on the new hard drive.

The bug has been fixed.



Restore the image to a hard drive of 160GB or more ... could be virtual.
Start this computer with PartedMagic Live CD.
Resize the partition with parted.

In Windows or Linux, insert the drive as a secondary drive
and resize using parted, gparted, or Windows Disk Manager.




I solved it with a Windows 10 image as follows

  1. Temporarily move some files when your source drive is almost full.
  2. A three-fragmented drive leaves more room to shrink. So defragment by clicking with the right mouse button on the drive -> Tools
  3. shrink as small as possible through Windows Disk Management
  4. Launch Clonezilla, Expert, Device-Device, Local, select and finally the option
  5. Switch off and disconnect the old drive
  6. Reboot to the new drive and hold down the Shift key while logging into Windows. Select Restart -> Troubleshoot -> Startup Repair

In the past the 4th step failed, but since 2015 Clonezilla supports GPT with the option. I think this is why this is working now:
http://clonezilla.org/downloads/stable/changelog.php

Clonezilla live 2.4.2-38 ... Proportion GPT partition layout can be created with the option.

The sixth step is necessary because Windows does not recognize the boot drive in the Optimizer (SSD trim) and tries to repair the drive at random, so something is wrong in the table for the boot sector / partition, but the repair through boot is fixed.

EDIT: I uploaded a video of the whole process:
https://www.youtube.com/watch?v=GJ2LVY5ja-o


If the storage space is not used, switch to expert mode and activate the image. Then restore it. The partition size check is skipped and restored successfully (only if <120 GB is used).


My situation:

  • Clonezilla image (from Windows 7) based on 128 GB drive (100 MB system partition + 117 GB "C"),
  • new 120 GB drive.

The following suggestions (like https://superuser.com/a/592283/229908) didn't solve the problem for me.

What worked for me was:

  1. Restore the image on a different (larger) drive.
  2. Defragment this drive (as Clonezilla appears to be restoring the data as it was structured on the original drive, so there may not be enough free space to shrink the partition to the target size).
  3. Shrink the partition (in my case 117 GB "C") to the size of the target drive / partition (in my case 111 GB) or, more safely, to a smaller size.
  4. Install Windows 7 on the destination drive (and let it create its system partition using advanced options).
  5. Use Clonezilla to restore (with command) each partition from the resize drive to the corresponding partition on the destination drive.

The main trick why this worked was to create a partition table (in my case automatically by installing Windows) that corresponds to the target drive, and then only copy (over) content that would not affect the partition configuration. Even if the source partition to be restored was smaller than the destination because the partition table is not affected, the destination partition does not need to be "expanded" after the operation.


In my case alone did not solve the problem. I don't know if the problem is exactly the same as mine. But I left my penny here.

I tried cloning a disc from a 930 GB hard drive (source drive) with a GPT partition table to an 890 GB SSD (destination). Please note that I am a Linux user and I have dual boot with Windows 10. I tried to leave all partitions unchanged and only slightly reduce the size of my data partition.

  1. Using gparted, I resized the larger data partition to make it a total size that would fit the target SSD, and ended up moving all of the free space
  2. I used Clonezilla-Live from USB pen, with advanced mode and enabled.

It failed . It looks like Clonezilla cannot clone the partition table to the target disks at startup because it incorrectly uses the sfdisk utility instead of the sgdisk utilities for older partition types. My solution:

  1. The same as before (overall size must fit)
  2. I manually copied the partition from one drive to another using the Clonezilla shell with this command ( only for GPT partitions! ):

    sgdisk / dev / sdSourceDeviceName -R / dev / sdDestinationDeviceName

  3. Performed Clonezilla disc-to-disc clone with the option and option to NOT CREATE a partition table on the target disk selected. (In this case, Clonezilla uses the target partitions as is and resizes partitions when the sizes are smaller for good performance.)

It worked . I got all partitions the same size as the source (yes, I just reduced the larger partition a little). Dual boot with Windows still works fine. greetings

We use cookies and other tracking technologies to improve your browsing experience on our website, to show you personalized content and targeted ads, to analyze our website traffic, and to understand where our visitors are coming from.

By continuing, you consent to our use of cookies and other tracking technologies and affirm you're at least 16 years old or have consent from a parent or guardian.

You can read details in our Cookie policy and Privacy policy.