If I understand your question correctly, your source computer only has a single hard drive, but your target computer has 2 hard drives. Can you deploy to this? Yes. in the host definition for the target computer update “Host Primary Disk” field to point to the correct disk.

@stucraster I have a tutorial around moving your imaging files off the root partition here: https://forums.fogproject.org/topic/11048/moving-fog-s-images-files-off-the-root-partition-2017-edition

Usefull commands are lsblk to show block devices (i.e. storage devices) and df -h to show mounted disks.

@leonj So try to go to the web interface, and then immediately check the apache error log file. Post the last 20ish lines of that, sanitized if necessary. Also - we need to know what versions of MySQL and PHP and php-mysqlnd you are using.

This message is telling me that either you change the password of the linux user fog’s password on the storage node or the settings in the storage node configuration on the master fog server is incorrect.

Understand this is the FOG service account called fog not the web ui’s default administrator account also called fog

@tom-elliott Hello, sorry, I did not understand what I had to try?

@UFR Thanks for letting us know. Should we take a deeper look at why this might happen with Fedora 28 you think?

@vince-villarreal Possibly someone capture an image over the original one. Run ls -al /images/<imagename> (put in the name of your image instead of <imagename>) to see the date of the files. Does that make sense to you?

Other than that could it be you are trying to deploy this image to a computer with a smaller disk?

@cmale What do you see in the apache error logs when you get the blank page. See my signature…

@snaggel I’ve run into this issue quite a lot in my environment. It took a ton of work to figure it out. I sometimes copy images from one fog server to another, and in the process the permissions on the folder/containing files were getting changed. In my case, running <code>sudo chmod 777 -R /images</code> fixes my issue.

@china-boy There’s not enough information in your post.

@kagashe The integrity plugin is not code-complete, I think. You can use md5-sum or sha256-sum to check the hashes of your image files manually though.

@zach-garner You can use it as often as you want.

@newlined you can fix this Behavior if you remove the /var/www/fog and then do: sudo ln -s /var/www/html/fog /var/www/fog

What version of FOG are you running? The simplest method to enforce a replication to begin again is to simply restart the FOGImageReplicator service.

For most this is accomplished by doing: sudo systemctl restart FOGImageReplicator, similarly Snapin Replication would be: sudo systemctl restart FOGSnapinReplicator.

There is currently no way to force a replication to begin via the GUI. This is because the services are at the linux level and run on boot up as root. These FOG Services (FOGImageReplicator, FOGSnapinReplicator, FOGPingHosts, FOGSnapinHash, FOGScheduler, FOGMulticastManager, FOGImageSize) run separately from the GUI environment. That said, you can adjust the times that these cycle via the GUI, and it will receive its information on the next run cycle.

created another group and linked to the 35 nodes, traffic was ceased

0_1532717283762_76cf347b-343b-4041-8db1-caa3338e7bd3-image.png

Please mark this as solved.

I was replacing the Kernel here /var/www/fog/service/ipxe and it was suppose to be here /var/www/html/fog/service/ipxe.

Kernel 4.15.2 works if it’s installed in the right place. Sorry for wasting your time.

@Amerhbb This is an interesting one. Seems like this is something from the Linux kernel itself: https://github.com/torvalds/linux/blob/master/drivers/firmware/efi/efibc.c

Not really sure what do advice yet…

@kermit1991 Try following George’s great instructions here: https://forums.fogproject.org/topic/11202/fogcontroller-class-php-undefined-offset-3-line-1046