More control with Partitions



  • Hello,
    Here is the situation, the 1TB Hard drive is setup with two partitions. Partition 1 contains the operating system and installed software, Partition 2 contains random data that the users store their documents, pictures, etc. As of FOG 0.32 there is no way to upload just Partition 1 to an image and deploy that to another hard drive with the same/similar configuration. My question is will that feature be available in the near future?



  • Hola Fernando,
    I m really sorry for this, I m not searching for a fight at all. It s just that i found that it was something so interesting and i was so happy that i found the installation files that i wanted to share it here !
    Now i m in production and have to deploy my computer otherwise it would have been a pleasure to test it !


  • Testers

    Dropped it about 5 years back when we still used xp.


  • Moderator

    You guys use deep freeze?


  • Developer

    Thounsand battles are around me :(

    This feature was developed for my university and worked and works fine, the problem is that this feature only works under our special fog version. I would like develope it for the new version of FOG, but actually I don’t have spare time to do it.

    Maybe in FOG 1.4 :)



  • @Fernando Gietz, post: 252, member: 13 said:

    We have developed this feature, but we use fog 0.30.
    The way it operates is simple:
    1 º) When you upload the picture for the first time you save the partition scheme in the database, via web services.
    2 º) for the next time, the web interface gives you the option to choose which partition you want to upload.
    3 º) FOG script on the client, ask via web services if you need to upload the whole disk or just a partition. If the result of the query is running the fogpartinfo ALL, otherwise, it returns the device / dev / sdaX.
    4 º) Once the upload process, the web service takes care of Post_Stage2.php to copy the image file of the partition in its place
    5 º) Saving the partition scheme you know that images have the same schema, so you can share the image files of partitions.

    In this way the code is responsible for making the task of renaming files, and avoid human error.

    Example:
    The source name image is aula-bz-cursos-A6A-rembo-mantenimiento. We can upload all partitions, sda1(NTFS) or sda5 (NTFS) and share it with aula-bz-cursos-A6A-rembo-gx620_produccion image

    ""
    what is shown in the screenshot above…
    A special version of fog to allow to work not only with hard drive but also to restore partitions only.
    I didn’t test it but i m also interested in that functionnality :-)


  • Senior Developer



  • hi,
    i think it s coming from there…
    http://www.fogehu.es/index.php/


  • Developer

    This feature is not in the official FOG version, sorry.



  • Hello there, where can i find the feature of fernando please? I don’t find out a thread/wiki talking about this


  • Moderator

    There is a thread/wiki article about some custom mods a guy made for his company. See if you can find that.



  • Did anyone ever get a line on the source code or a walk through on this? I am managing dual boot laptops and it would be very useful (and a time saver) to (for example) image the Windows partition while leaving the Centos partition unchanged.



  • this feature is really interesting I am managing a park of laptops and I want to keep the manufacturer restore partition. does somone have the sourcecode or a clear walktrough of how to do that in 0.32 or 0.33



  • To Blackout:No.

    But you can manually rename/remove the image files so the system cannot find them, it will then skip that partition.

    Reply:thats true and working…but when i try to use the same image for another Pc it tells me wrong partition table…so how can i use this image for any another pc?



  • hi prattyy
    would you explain your test to know more …
    because i try this before but not complete
    and what is the path of the image in the Fog.



  • @prattyy, post: 3360, member: 1074 said:

    Ohh yes sorry I completely misunderstood this.
    I deleted the image of second partition and it works
    Will do some more tests with diffrent operating systems
    Thanks boon
    Nice! I like the easy ones ;)



  • Ohh yes sorry I completely misunderstood this.
    I deleted the image of second partition and it works
    Will do some more tests with diffrent operating systems
    Thanks boon



  • @prattyy, post: 3330, member: 1074 said:

    @catsrules
    so you are saying that before i deploy the image i shoud delete my second partition??
    and what should i do after the deployment to restore the partition and its data?
    I believe he meant that you should delete the second partition from the FOG server, so it does not overwrite the user data partition upon restore.



  • @Catsrules, post: 2142, member: 296 said:

    That is cool, I would be interested in something like that. Would it to to much trouble to post the coding behind this? Even if it is for the older version, I bet people would find it useful, maybe even update it to the newer version.

    @LanStack
    At the moment the only way to do this, it to do what Blackout said, and rename or delete the secondary partition image. Then when fog does a restore, will not be able to find the second partition and error out and skip it. As long as your partition layout is exactly the same on every computer, it will not destroy any data on the secondary partition.

    The thing that sucks about this setup is whenever you update you image, you will need to remember to rename or delete the secondary partition, otherwise it will overwrite all the data on the secondary partition with the one on the server, and that is not good.

    @catsrules
    so you are saying that before i deploy the image i shoud delete my second partition??
    and what should i do after the deployment to restore the partition and its data?



  • This post is deleted!

Log in to reply
 

502
Online

38916
Users

10685
Topics

101347
Posts

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