@Sebastian-Roth I am not sure I expressed correctly what I ment…
We already have an existing image stored into fog… from that image I asked to deploy only partition 2. in which you showed me it can be done by modifying the image and by changing the menu Partition from Everything to “Partition 2 only”.

My comment was about why do we see 12 options (10 partition) while may be it could be set dynamically to N the number of partition that image has.

My suggestion was when you generate the edit image page, could an option be coded to dynamically list only the existing partition.

I am not sure if you can see it … but from the filesystem when I do ls d1p* I see
d1p1.img d1p2.img d1p3.img

I know comment is beyond my original post I just wanted to make it clearer.
thank you very much.

Yes I am at Latest stable version is 1.5.5

and yes it seam to be exactly what I needed. thank you !

I have seen the option to choose a partition… but was to afraid to somehow corrupt my image and not been able to revert back to Everything.

There is also that I see 10 partitions or 12 options in the list while I had only 3… which made me worry about the outcome of trying it with the wrong partition. Do you consider to list only the existing partition for that Partition menu?

Currently my only option to fix this - is to boot from a usb key with Parted Magic, and using partclone and copying sda2 from another disk/part. clone disk image to disk image…

I really love not having to open another machine and doing this via fog.

I tried to search before asking but did not find is this can be done using fog.
if not then it is a suggestion ;)

Hi guys,

I got an image of of Single Disk - Resizable using Partclone Compressed.
The disk as 3 part. boot, os, data.
Is it possible using fog to restore only part sda2 (the corrupted os) without restoring data part ?

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *        2048     2099199     1048576   83  Linux
/dev/sda2         2099200    99753983    48827392   83  Linux
/dev/sda3        99753984  1953524735   926885376   83  Linux

@tom-elliott no worry as I have a fix by requesting desktop version… George suggested I report it.
thank you for everything !

I just updated to fog 1.5.4 from 1.5.3 and still the new UI on my cell phone running Android 8.0.0 in chrome gave a strange web page… desktop version is ok on PC and on phone if desktop version is requested.

here some sample… check this out.

I have read the posts… but I can’t find binaries1.5.3.zip and how do I update the latest installer ? I am already at 1.5.3 installed from the tar.gz and not very familiar with git although I used it once from your recommandation.

There is also talk about lshw which was not installed on my EL6x fog vm… it could also be a cause of error if lshw is not installed or tested if it is available for FOG 1.5.3 to use…!?

After my migration from fog 1.4.4 to 1.5.3 I now cannot register hosts.
it says something like “no viable mac to be used”

it has was working well in 1.4.4 and prior with any of those pc before… (DX58SO2 intel board ± 2015.

I also saw an error at boot… not sure if it’s related.

even after completing twice questions, and successfully deploying Linux image on PC I had nothing about that new host.

Any idea ?

@tom-elliott I am willing to try I am already at 1.5.3 on SL69…

so writing with george1421… I issued those commands.:

git clone https://github.com/FOGProject/fogproject.git
cd fogproject
git checkout working
cd bin
[root@fog:/opt/fogproject/bin ]% ./installfog.sh
installing…

Yes. it is working !
file /etc/httpd/conf.d/fog.conf was rewritten correctly.

then I switched back to the master
git checkout master
thank you all.

Scientific Linux is the exact same as CentOS 6.9. Binary, source& config compatible… it’s the source from Red Hat EL6.9… there is also the fact that is was working for years.

@wayne-workman unless you mean that CentOS 6x and EL 6x altogether is also not supported by fog 1.5.x and from your link this is what I understand.

in that case FOG should not offer that update or the readme should, maybe mention it.