Menu

=?UTF-8?Q?Clonezilla_recognizes_VirtualBox_virtual_machine_dis?= =?UTF-8?Q?ks_that_are_larger_than_they_actually_are_B=C3=A1ez?=

Help
santopitar
2022-11-27
2022-12-10
  • santopitar

    santopitar - 2022-11-27

    Hello. I run maintenance for a high school. I have different builds for
    different PC profiles (W10+Apps, W10.Apps+LinuxMint.Apps, etc...).

    I make images of the builds with Clonezilla so that I can restore them to
    the corresponding machines. I have the problem that when I want to update
    the operating systems that are in the images from last year, I can't do
    them for the computers that are in use because they have already been
    modified by the users. What I was doing so far is restoring last year's
    image, updating the OS, and recreating a new, updated image.

    So I thought I'd create virtual machines with VirtualBox to restore the
    images to, and keep the virtual machines clean as master installations,
    which I can update every year and then create a new, updated Clonezilla
    image of them. So far, so good. Clonezilla works with virtual machines but
    has a problem. It recognizes VirtualBox disks that are larger than they
    really are (a 120GB virtual disk is recognized as 128GB).

    This causes the images it generates of the virtual disks to be larger than
    the original disk, so they cannot be restored to the original physical
    disk. It has a solution but it is complicated (reduce the installation
    partitions, then reduce the size of the disk and recreate the image with
    Clonezilla). Any idea why this happens? Is there an easier solution? Thanks
    in advance.

     
  • Steven Shiau

    Steven Shiau - 2022-12-03

    Sometimes different Linux kernel will give different size about disk. Therefore please try to use the same version of Clonezilla live to do that.
    BTW, if the difference is very small, you can try to enter expert mode, and check the option "-k1" and "-icds" when restoring. It might work.

    Steven

     
  • santopitar

    santopitar - 2022-12-04

    Thanks... I will try. But there is between 5-8 GB more.

    Now the solution for me is resize the VDI disk of VirtualBox to the correct size, although is a lot of work. But my question is why there is 5GB more?. If I have a virtual machine of 80GB (for example), in the Virtual Media Administrator of VirtualBox the VDI has 80GB... if I boot the virtual machine with Gparted live, there is 3 partitions (sda1(/), sda2(/home), sda3(swap)) that sum 80GB, and THERE IS 5GB at the end of the hard disk without partitions (?).

     
  • Steven Shiau

    Steven Shiau - 2022-12-10

    Is this only reproducible on VirtualBox? Do you have any issue about physical machine?

    Steven

     

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.