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.
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
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
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 (?).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
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.
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
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 (?).
Is this only reproducible on VirtualBox? Do you have any issue about physical machine?
Steven
It happens with virtual disks of VirtualBox (VDI extensions). I have no
tried with other types of virtual disks.
El sáb., 10 dic. 2022 10:51, Steven Shiau steven_shiau@users.sourceforge.net escribió: