@george1421 @Junkhacker @Tom-Elliott I see what it does now. I actually tried that out. Basically, it copied the script from fog server and placed that into the target computer. Once the target computer powers up, it will run the script automatically. That actually helps. Thanks for your guys effort. I will close this issue then.

I think there something has to do with the newer computer I have, nothing wrong with the Fog project itself. Sorry for the false alarm

hi guys, any plan to release a new version of the fog project, making all the dev work into prod? thanks

@sebastian-roth thx for ur info

Hi guys, can anyone give me the definition of the image manager, like what those options mean on setting up the image or deploying the image? Any tutorial would be helpful. thanks in advance

@sebastian-roth I successfully built image from the type of computer that don’t work on image deployment. It seems to me that there must be some kind of hardware config that prevents the image deployment to expand the disk properly

@sebastian-roth I cannot update the image here as the platform keeps saying it is too large. Here is the link for it

https://drive.google.com/file/d/1J8FarpqD-0dhHdWd0BCSairqnL84e5Wa/view?usp=sharing

@george1421 Sorry for this late message. Just want to rephrase what we discuss little. The capturing task works fine that it allows me to capture the image properly. The problem is the deployment of image.I just tried deploying image and used the instruction u provided on both computer that works and computer that does not. The outputs from both computers are:

Computer that does not work with image deployment:
Pass 1: Checking inodes, blocks, and sises
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/sda2: {certain number}/{certain number} files (0.3% non-contiguous)

Computer that works with image deployment:
Pass 1: Checking inodes, blocks, and sises
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/sda2: {certain number}/{certain number} files (0.2% non-contiguous)

Basically, the outputs are the same except that percentage of non-contiguous

@sebastian-roth good to know. thanks

hi guys, any plan to release a new version of the fog project, making all the dev work into prod? thanks

@george1421 when you have a moment, can you look at my previous comment? thanks

@george1421 the dev ranch seems not solving the image deployment issue.

@george1421 all good then. Thanks