New FOG install, now can't find old image files in FOG
-
So, I was hoping someone could assist me with a FOG install.
I had everything up and running on my network, but I recently made some changes. I am now running pfSense for firewall and routing software, on a dedicated Optiplex 7010. FOG was installed on Ubuntu 18.04.1 LTS, on a ThinkPad E540 with 16GB of RAM, a 480GB SSD, and a 1TB HDD for the /images partition.
When my network configuration changed, I couldn’t get the settings to change in FOG, with regard to the TFTP IP and DHCP IP, so I wiped Ubuntu/FOG completely. I then reinstalled FOG on the same machine with Ubuntu 18.04.2 LTS. I formatted the SSD partitions, but did NOT format /images. I am amble to see the previously saved images via Terminal and File Manager, but I can’t get them to come up in FOG List All Images.
I guess I’m wondering how I can import them so the new Fog install will recognize them.
Any and all assistance will be greatly appreciated! Thanks in advance!
-
@PITSKing fog pulls that information from the database, not the files. if you recreate the “profiles” for the images and point them to the existing files, they should work.
-
@Junkhacker, so, I just need to recreate the “Image” in FOG and direct it to /images/WhateverPreviousImage, and it should be recognized?
-
@PITSKing Right with FOG there are 2 parts to “images”. The first part is the raw data files stored in
/images/<image_name>the second part is the metadata stored in the database. You moved the raw data files but what is lacking at the moment is the metadata. If your old fog server is running and its 1.4.4 or newer, you can export the metadata from the old server using the web ui and then import that metadata using the web ui into the new fog server. If you don’t have the old fog server available, you will have to recreate the metadata by hand. -
@PITSKing As we’ve had this kind of question a couple of times lately I just want to add that the image definition/metadata needs to match the settings you had on your previous FOG server for each image exactly. If it was set to be a non-resizable image on the old FOG server and you create it as resizable it will fail to deploy…
-
Thanks to everyone for the assistance so far.
@george1421, unfortunately, I already wiped the old FOG server and rewrote the HDD with this copy, so I’m afraid the metadata is gone. Just so I’m clear, when you said I’ll have to recreate it by hand, I’m assuming that means I need to create the new Image inside the FOG web ui?
@Sebastian-Roth, I honestly don’t remember how I created the Images on the original server. I suppose I’ll have to do some trial and error. If I get it wrong and it fails, can I simply edit the Image Type after the Image is created? Or would I have to delete it and create a new one? Also, does the compression level matter any? Would that have to be set exactly the same as well?
-
@PITSKing said in New FOG install, now can't find old image files in FOG:
I’m assuming that means I need to create the new Image inside the FOG web ui?
Yes.
-
@PITSKing said in New FOG install, now can't find old image files in FOG:
If I get it wrong and it fails, can I simply edit the Image Type after the Image is created?
Yes you can! Compression level does not play a role on deploy but Compression type does, gzip vs. Zstd…
