Question about pulling Fog images in from a backup drive.



  • Hi all,

    I previously backed up all of my Fog image files to a USB drive. I have a few images that I have uploaded into Fog, but is it possible to import 5-6 images when I don’t have a csv file?



  • @Sebastian-Roth -465.7 GB


  • Developer

    @dbrilliant said in Question about pulling Fog images in from a backup drive.:

    Once it pulled the image, then it showed the proper size.

    You need to know that the image size in the web UI is only updated when using the image. But it’s not a sign for the image being valid or not.



  • @dbrilliant I’ve added all the images properly, and will test them out. Thanks all for your assistance. :)



  • @Sebastian-Roth -Yes, it’s working now. Once it pulled the image, then it showed the proper size.



  • @Sebastian-Roth Thanks Sebastian,
    I will give the next available 3050 I can get to, a thorough test to see if it will download the image. And if I receive any errors, I’ll let you know.


  • Developer

    @dbrilliant said in Question about pulling Fog images in from a backup drive.:

    DOS/MBR boot sector MS-MBR Vista english at offset 0x162 “Invalid partition table” at offset 0x17a “Error loading operating system” at offset 0x199 “Missing operating system”, disk signature 0x59988117

    Not sure if this really is as bad as it sounds. I am wondering about “MS-MBR Vista” and “disk signature 0x59988117”. I am not sure about the later but from memory I’d think that disk signature for MBR disks is different. But maybe this is some other signature unique to your installation, not sure. The other codes could just be information strings that would be shown if the MBR code doesn’t find an operating system or sees an invalid partition table but shouldn’t be used in normal operation.

    Edit: I was wrong about the disk signature. Seems fine from what I read here: https://thestarman.pcministry.com/asm/mbr/Win2kmbr.htm#DiskSigs

    gzip compressed data, last modified: Fri Jan 26 11:44:04 2018, max compression, from Unix

    So GZIP compression sounds good.



  • @Sebastian-Roth said in Question about pulling Fog images in from a backup drive.:

    file /images/3050Corp/*

    Oh boy, this doesn’t look good:
    grubb@fogserver:~$ file /images/3050Corp/*
    /images/3050Corp/d1.mbr: DOS/MBR boot sector MS-MBR Vista english at offset 0x162 “Invalid partition table” at offset 0x17a “Error loading operating system” at offset 0x199 “Missing operating system”, disk signature 0x59988117
    /images/3050Corp/d1p1.img: gzip compressed data, last modified: Fri Jan 26 11:43:53 2018, max compression, from Unix
    /images/3050Corp/d1p2.img: gzip compressed data, last modified: Fri Jan 26 11:44:04 2018, max compression, from Unix
    /images/3050Corp/d1p3.img: gzip compressed data, last modified: Fri Jan 26 11:47:46 2018, max compression, from Unix
    grubb@fogserver:~$


  • Developer

    @dbrilliant said in Question about pulling Fog images in from a backup drive.:

    Then I chose Windows 7 as this is a Windows 7 64 bit image, then single disk-multiple partition which was the original settings, Partclone gzip (as these were formerly in Fog v1.2). Then the default for compression, partitions, etc… I I triple-checked the image path, and all was good. Any ideas?

    So far this seems to match the settings. Maybe run file /images/3050Corp/* and post here as well so we see if the files are actually in gzip compression format.

    From what you write it sounds as if you still cannot deploy that image to a client, right? So please take a picture of the error you get on screen when the client tries to deploy this image and post here. I am sure we can help you.



  • @Sebastian-Roth

    grubb@fogserver:~$ ls -al /images/3050Corp
    total 28377912
    drwxrwxrwx  2 grubb grubb        4096 Nov  9 16:07 .
    drwxrwxrwx 14 fog   root         4096 Nov  9 13:43 ..
    -rwxrwxrwx  1 grubb grubb         512 Jan 26  2018 d1.mbr
    -rwxrwxrwx  1 grubb grubb    17921802 Jan 26  2018 d1p1.img
    -rwxrwxrwx  1 grubb grubb 10019524626 Jan 26  2018 d1p2.img
    -rwxrwxrwx  1 grubb grubb 19021504672 Jan 26  2018 d1p3.img
    grubb@fogserver:~$
    

  • Developer

    @dbrilliant Please run ls -al /images/3050Corp and post output here.


  • Senior Developer

    @george1421 1.0.0 introduced and used partclone. 0.32 and earlier used partimage.


  • Moderator

    @dbrilliant said in Question about pulling Fog images in from a backup drive.:

    Partclone gzip (as these were formerly in Fog v1.2)

    FOG v1.2 is a bit before my time, but I think partclone is right. If it was older then it the cloning tool would be partimage. If your partclone picked image file is not working then try partimage. 4 files sounds like the older format.

    Just for comparison reasons, this is the image file format of FOG 1.4.4 created image.

    -rwxrwxrwx  1 fog root          3 Apr  5  2018 d1.fixed_size_partitions
    -rwxrwxrwx  1 fog root    1048576 Apr  5  2018 d1.mbr
    -rwxrwxrwx  1 fog root        190 Apr  5  2018 d1.minimum.partitions
    -rwxrwxrwx  1 fog root         15 Apr  5  2018 d1.original.fstypes
    -rwxrwxrwx  1 fog root          0 Apr  5  2018 d1.original.swapuuids
    -rwxrwxrwx  1 fog root    9053858 Apr  5  2018 d1p1.img
    -rwxrwxrwx  1 fog root 8151244586 Apr  5  2018 d1p2.img
    -rwxrwxrwx  1 fog root        190 Apr  5  2018 d1.partitions
    


  • I copied over all the images, but tried one as a test, which was the most important one.
    The path of where the img is:
    /images/3050Corp
    There are 4 files that were copied over
    Then I chose Windows 7 as this is a Windows 7 64 bit image, then single disk-multiple partition which was the original settings, Partclone gzip (as these were formerly in Fog v1.2). Then the default for compression, partitions, etc… I I triple-checked the image path, and all was good. Any ideas?



  • Thanks George, I’ll give this a shot. I’ve already copied the images over to /images/… So now, it’ll be matching everything up.


  • Moderator

    The short answer is… maybe.

    Understand with FOG there are two components to an “image”.

    The first is the raw data files that exist on the FOG servers hard drive. These are typically stored in /images/<image_name>. The second component is the metadata that is stored in the mysql database.

    If you are a good guesser, you can copy the image files to /images and then manually rebuild the metadata. You need to know the directory name of the target image directory and the OS of the target stored in the image directory. The rest could be left as default.

    For example lets say I have a thumb drive with an image on it, and on the thumb drive my images are in this path /mnt/images/Win10Entx64 I would know by the naming convention that the files in /Win10Entx64 is windows 10 enterprise 64 bit version (just as an example). I would copy the directory /mnt/images/Win10Entx64 to /images/Win10Entx64 on the FOG server then go into the WebGui and set up a “new” image this way.

    The boxes in blue are known because that is based on my knowledge of what is in that directory I just copied over.

    (1) You will have to take your best guess on if it was single disk resizable vs single disk non-resizable.
    (2) If the source image is from FOG 1.3.0 or later then its Partclone Gzip, unless you change the image compressor to ZStd.

    0_1542224314381_new_image.png


 

531
Online

5.4k
Users

12.6k
Topics

118.7k
Posts