Not a partclone image anymore
-
Again, I don’t think this image is of partclone type. My guess is it is of partimage, but it is defined in the definition as Partclone. Please change this and test again.
-
Where is that config file located that I can change the value to partimage from partclone.
-
There is no config file.
This is changed on the GUI.
If you go to the image in image management, you can change the format of the image (Partclone/Partimage) right from the definition. If you don’t see the Drop Down to select the image type, you will need to enable it in FOG Configuration->FOG Settings->General Settings->FOG_FORMAT_FLAG_IN_GUI and check the box and save.
Then you go back to the image in image management and select the appropriate format from the drop down that will now be presented to you.
Once you save the image, you’ll have to restart the host system so the system knows about the change.
-
They are all listed as partclone images, I will change one to partimage and see if it works. Thanks!
-
Partimage doesn’t read the image, and it looks way different, I definitely remember making the images with partclone then.
-
I just re-uploded one of my images and immediately attempted to re-deploy it to my 2 test machines, it worked for one but the other still has the partclone image error. so maybe they just need to be re uploaded.
-
The other, and my best suspicion, is that the “failing” machines are failing because they’re loading the init_32/bzImage32 files and NOT the init/bzImage files. Is this true?
-
Yes It looks like that is what is happening to the other test machine.
-
@kirkk can you please update once again, and try again?
I believe I fixed the init_32 issue. Your image most likely is partclone, and the reason things failed was because it didn’t matter which method you used to image, pigz was not working properly on 32 bit. I think this is now fixed, though I need people to confirm.
Thank you,
-
Alright I will update and let you know what happens. Thanks!
-
That worked, thanks!
