Thank you, deleting the repo=‘php-${php_ver}’ line in .fogsettings solved the issue.

p.s.: must be due to the change from php 5 to php 7 which was not supported by default at the time I upgraded to fog Version 1.3.0-RC-10

@Wayne-Workman So far so good. I think this might have done it. Two birds with one stone.

Thanks Wayne. I’ll write on here if it ends up breaking again. 🙂

@Wayne-Workman @Joe-Schmitt

Thanks for the updated feedback. I will look into the hiding the password as suggested - the script I wrote is probably crude and ugly.

I have another (unrelated) question to ask, but tomorrow and on a new thread.

Thank you again for your time and appreciate the great help and support.

Mark.

@joshuaparker What fixed the issue? The removing the id=‘login-info-form’?

I’ve added a schema change for 1.3.1-RC-2 that is addressed under “General Settings” from the fog settings page. This is just a simple checkbox. It’s default status is “checked” of course, but can be adjusted so you don’t consistently need to make changes during updates.

Thanks so much Tom

i set the “Menu Timeout (in seconds):*” for 2 seconds and thats solved my question, with autodeployment.

I appreciate very much your and your colleagues and work to facilitate my everyday work.

Best Regards.

@Wayne-Workman
That did the trick - thanks! (the mysql stuff worked just as it is)

@Tom-Elliott Woo-hoo, capturing an image now!

A big thank you to everyone who helped track down and fix this. Your support is amazing! Looks like I have another FOSS project to add to my contribution list…

@dadush91 So the good news is that FOG can see the disks and partitions. This looks to me like it’s a hybrid HDD with about 16GB of solid state and then 250GB mechanical, and FOG is seeing these two things as two different disks. Or you have a 16GB thumb drive or SD Card stuck in the laptop somewhere. If that’s the case, take it out and try again. If that’s not the case, try “Multiple Partition Image - All Disks” as the image type and then try to capture again. This is pictured below.

0_1483294993602_Multiple Partition All Disks.png

@Wirefall [Moderator note:] I’ve forked this users post since the issue is similar to the OP of this thread, but deals with a different version of FOG. You can find your post here: https://forums.fogproject.org/topic/9201/fog-will-not-boot-failed-to-get-an-ip-via-dhcp

@iyoung Test completed. LDAP plugin added and test login succeeded.

@Tom-Elliott Thanks, that took care of it. My Google Search-fu clearly needs work.

Remoted with @tom-langenfeld and we were able to fix the issue.

He was running Ubuntu 15.10, and the Ondrej repo would install, but there were no PHP packages for wily apparently. Updated to 16.04 and had to run a few tricks to get mysql working, but once all was working, everything appears to be running properly now.

FOG 1.3.0 installs perfectly fine on Ubuntu 16.04, among others. I test this all the time: https://forums.fogproject.org/topic/8730/fog-installer-distro-check

@rnavarro Look here for how to change the kernel:
https://wiki.fogproject.org/wiki/index.php?title=Kernel_Update

@THEMCV In that case, I’d like you to reduce max clients to 1 just for troubleshooting, and also increase the snapin timeout for the fog client. Set it to something much larger, something that you know the snapin will get done within. But it would seem the default is unlimited already… Can you upload a client log from an affected system?

EDIT - this is the timeout field:
0_1482959351373_2016-12-28_15-08-19.png

@sjensen

Then as Wayne said, make a new thread for it, sounds like your install is… special. Sudo being denied permission is silly.

@Timur my advice is for you is to build a new Ubuntu 16.04 server (or debian 8 or Centos 7 or Fedora 25) and install fog 1.3.0.

Here is a resource:
https://wiki.fogproject.org/wiki/index.php?title=Upgrade_to_trunk

Also:
https://wiki.fogproject.org/wiki/index.php?title=CentOS_7

@abos_systemax said in Fatclone.C: Filesystem isn't in a valid state:

@Wayne-Workman

I kind-a-fixed it by booting to Windows PE, clean the disk with diskpart, create a 100MB parititon and a ‘the rest’ partition; then restoring only partition 2 with FOG, then rebooting to Windows PE to create a bootstore… now Windows can Boot.

I now face another issue, but I’ve posted that in the Windows Issues forums (https://forums.fogproject.org/topic/9177/windows-partition-size)

— fixed that issue as well…

@sjensen i tried sudo at the start of the string. I am getting could not open lock file /var/lib/dpkg/lock - open (13: permission denied)

@lonnie776 while I am glad that youve taken the steps to find and correct a problem, I feel you may want to look at the latest fog has to offer. First we’ve, and by we I mean @Joe-Schmitt , rewritten the fog client and it is much more secure and less resource intensive on the server. As an overall result the client is much faster than the old client and has many more features to work with. I’d highly recommend updating and using this new client for any system.