• Hello,

    I own a Clonezilla server with images already present.
    I would like to add files to my FOG 1.5.5 server on a CentOS 7.

    Actually, i use this command:

    scp -r root@X.X.X.X:/images/Master /images/

    My files are well moved and are exploitable. On the other hand, it does not go back on FOG.
    On the web interface, I create an image with the same name as the folder but, no link is made.

    How can I do? Is it absolutely necessary to have a csv file like transfert between FOG?


  • @george1421

    Thank you for your answer. You can close the ticket. I will do your technique.

    Best regards.

  • Moderator

    Well I see you have 2 issues here. One we can fix and the other will take some effort on your part.

    The easy one: The FOG images have 2 parts. Of course you already know about the raw data files. These files exist in /images on your fog server. Within the /images directory the files are in directories typically based on the image name. The other part is the metadata that describes the image files. That information is stored in the sql database. Its possible if you have a consistent naming convention for you to rebuild the metadata by hand. For example, I have an image name of Win101803ProU. I know the directory path of that image because FOG defaults the image path to be the same as the name. I also know its a windows 10 image, uefi. From there I can fill out the remainder of the data fields based on knowing its a full disk image (single disk resizable) and what compression level and data compressor to use (these last to are only important when capturing the image). So if you know the location and parameters for your image you can manually create the image definition in the FOG Web ui.

    The harder one: The image files are not directly compatible between Clonezilla and FOG. FOG creates and stores fog specific disk geometry files when it captures image. It helps FOG when setting up the target disk before the image push. Clonezilla doesn’t create these files that fog needs. Clonezilla and FOG do use the same image capture tool (Partclone) but where they differ is the image compression methods. Meaning: The raw image files are compatible but not really usable.

    While it sounds like a lot of work, IMO its quick to use clonezilla to deploy an image to a test client, then turn around and capture it right away with fog (without letting the target OS boot), than it would be to convert these blob image files between Clonezilla and FOG disk formats.