Just to be clear about partimage ?



  • Just to be clear about partimage ?

    I understand that Partimage was the old way, yes I had a .32 server on Ubuntu 14 server. However I was having issues and wanted to have a clean build so I took a day and put together a new build. Gotta love VM’s :)

    Anyway, I have Ubuntu Server 13.10 with Fog 1.2.0 running under ESXi 5.5, fog on Local storage and images on external SAS enclosure with H700.

    All went well outside having to run the restart on multicast service, but I’m with others in saying I believe I like the individual imaging anyway… However I have my images I rsynced from the .32 server I retired.

    I set the flag for legacy in the GUI, however it still tries to use partclone ? I have them selected as partimage, and I restarted all tasks. It doesn’t seem to care…lol

     My question is, does the new install do something to the images that basically it says they are partclone and not partimage ?  I attached the 2nd vmdk that had my images before I installed 1.2.0.  Is there any manual way I can tag the image as partimage so I can just download and re-upload as partclone and get rid of my mess ?
    

    I have about 320Gb of images I don’t want to do over for obvious reasons (time)

    Many thanks in advance for all your work, I’m loving Fog ! Was a former snap deploy user… THAT was a mess I will not return to !

    Oh, also what kernel should I be using ? Do I need to upgrade it after the new install or is it on the newest ?


  • Moderator

    See this post for more instructions/documentation:
    https://forums.fogproject.org/topic/9001/partimage-for-old-images



  • Just to let you know I didn’t just leave this thread :)

    I did have that enabled and had it switched under the image itself.

    However I didn’t have a chance to get that model back on the bench, as soon as I do I’ll report back ( hate when people don’t post solution if something worked )

    The good side is that I have imaged about 42 machines, 8 different models and all seems to be going good ! Loving fog !

    The only real issue I see is that I have to keep restarting multicast service after every boot.

    I’ll update this as soon as I get that box back on the bench. Thanks !

    As far as my old images, figured I would just a fast machine and switch back and forth networks. Download from Snap deploy, register fog and re-upload it. I have 2 different PXE servers. Acronis snap deploy on one network, and fog on another. Soon to be leaving snap all together :)


  • Senior Developer

    You have to enable the IMG_FORMAT_FLAG_IN_GUI option from FOG Configuration->FOG Settings->General Settings I think



  • [QUOTE]Go to Image Management->List all or search relevant image->click on it to edit->On the page will be a “selector” to choose partimage or partclone.[/QUOTE]

    So, I’m not having a problem with this particular issue, but I can’t help but notice that there is no location to change the image type. Thoughts?

    ""


  • Senior Developer

    Go to Image Management->List all or search relevant image->click on it to edit->On the page will be a “selector” to choose partimage or partclone.



  • Did you actually set the image to be of Partimage style?

    I guess that’s the part I’m stumped on ? Whats needed on my end to tell fog it’s partimage and not partclone ?

    How do I set them to partimage style ?


  • Senior Developer

    I tend to keep the kernels as updated as I can. Though when we release, the released version doesn’t automatically update.


  • Senior Developer

    [quote]I set the flag for legacy in the GUI, however it still tries to use partclone ? I have them selected as partimage, and I restarted all tasks. It doesn’t seem to care…lol[/quote]

    Did you actually set the image to be of Partimage style?

    All the “Flag for legacy in gui” does is enable the ability to specify what imaging method needs to be used for an image, it doesn’t automatically set them to partimage.


Log in to reply
 

Looks like your connection to FOG Project was lost, please wait while we try to reconnect.