@Greg-Plamondon said in Wrong Partition is mounted during deployment. (FOG 1.5.7.56): do you mind sharing your complex post download script with me Sorry I will not do that because that is our secret sauce. But I can tell you I’ve documented it in the tutorials. https://forums.fogproject.org/topic/11126/using-fog-postinstall-scripts-for-windows-driver-injection-2017-ed And in parts 3, 4 and 5 here: https://forums.fogproject.org/topic/7740/the-magical-mystical-fog-post-download-script

@Sebastian-Roth I found a workaround. I was able to clear the “Domain Password Legacy” value and then typed the current password in the “Domain Password” field and that worked. I will work some sql magic and will be good to go. Thanks for responding.

fog_error_1.5.9. RC.log Jul 08 16:06:23 PLGDVFOG01 systemd[1]: Starting The PHP FastCGI Process Manager... Jul 08 16:06:23 PLGDVFOG01 systemd[1]: Started The PHP FastCGI Process Manager. --2020-07-08 16:06:26-- https://10.180.8.90//fog//maintenance/backup_db.php Connecting to 10.180.8.90:443... connected. WARNING: cannot verify 10.180.8.90's certificate, issued by ‘/CN=FOG Server CA’: Self-signed certificate encountered. HTTP request sent, awaiting response... 302 Found Location: ?node=schema [following] --2020-07-08 16:06:26-- https://10.180.8.90//fog//maintenance/backup_db.php?node=schema Connecting to 10.180.8.90:443... connected. WARNING: cannot verify 10.180.8.90's certificate, issued by ‘/CN=FOG Server CA’: Self-signed certificate encountered. HTTP request sent, awaiting response... 200 OK Length: unspecified [text/plain] Saving to: ‘/home//fogDBbackups/fog_sql_1.5.9-RC2_20200708_040626.sql’ 0K . 70.1M=0s 2020-07-08 16:06:26 (70.1 MB/s) - ‘/home//fogDBbackups/fog_sql_1.5.9-RC2_20200708_040626.sql’ saved [1305] ERROR 1146 (42S02) at line 1: Table 'fog.globalSettings' doesn't exist fog install. log To improve the overall security the installer will create an unpriviledged database user account for FOG's database access. Please provide the database *root* user password. Be asured that this password will only be used while the FOG installer is running and won't be stored anywhere: OK * Backing up user reports.....................................Done * Stopping web service........................................OK * Setting up Apache and PHP files.............................OK * Testing and removing symbolic links if found................OK * Backing up old data.........................................OK * Copying new files to web folder.............................OK * Creating the language binaries..............................Done * Creating config file........................................OK * Downloading kernel, init and fog-client binaries............Done * Copying binaries to destination paths.......................OK * Enabling apache and fpm services on boot....................OK * Creating SSL CA.............................................OK * Creating SSL Private Key....................................OK * Creating SSL Certificate....................................OK * Creating auth pub key and cert..............................OK * Resetting SSL Permissions...................................OK * Setting up Apache virtual host (SSL)........................OK * Starting and checking status of web services................OK * Changing permissions on apache log files....................OK * Backing up database.........................................Done * You still need to install/update your database schema. * This can be done by opening a web browser and going to: https://10.180.8.90/fog/management * Press [Enter] key when database is updated/installed. * Update fogstorage database password.........................Failed!

@Sebastian-Roth The Mac shows up in the table. Assigned to my device, but under pending. So I went to pending and approved the Mac addresses. Though when I went back and tried to remove the temporary Mac that is in the primary field and move the built in MAC address to the primary field but it still gives the error when I save that the Mac is already assigned (to the machine who’s page I’m on). There are 3 Mac addresses in the mix. The temporary usb adapter another USB adapter that the user usually has. This one doesn’t support PXE hence the temp adapter. The Wifi Mac that I keep as a secondary because we use the client and I want the machine to still check in while on Wifi.

@Sebastian-Roth Thanks Sebastian, I already know the answer and it’s Yes. Also, I’ve already pulled down the dev-branch and got the error before my initial post. So what’s next? Should I delete the previous dev-branch install and download/run it again?

This is now resolved, on checking it appears that the kernel downloaded was the ARM64 instead of 64.

I actually brought my laptop in from home, this I know is a uefi BIOS, on testing it, it booted into Fog with no issues ( it has been imaged in the past with FOG. So i then knew that UEFI boot was working. I have to hold my hands up on checking the HP 250 G7 it had not had secure boot switched off in the BIOS, this is a silly error and for this I blame my technician lol, (well i should have checked myself) on checking this morning i saw it was still on, I was lead down the FOG path after the kernel update failed. however i now have a different issue which i shall post.

@sudburr Is the partition layout still fine when you see this blkid: error: /dev/sda4 thing on subsequent tries? May I ask you to do the following: Let it try to capture a few times more. Every time you save a copy of the /images/dev/aabbccddeeff/d1.partitions (this aabb… is the MAC address of the host without colons) file to another location for us to compare those afterwards. Whenever you see the blkid... error you name it d1.partitions_fail_X (put in numbers instead of X) and if you don’t see the error you name it d1.partitions_ok_X.sfdiskPartitionFileName What kind of VM do you use? I am wondering if I am able to replicate the issue using the same setup?!

@george1421 Yep thanks for your help George, we have it pixie booting now, unfortunately, on checking it this morning the Tech had not switched secure boot off in the laptop bios. due to the other issue i had been having i thought it was FOG, FOG is blameless in this instance.

@george1421 I was able to edit the Grub.cfg and add our Fog server IP in and then boot with USB and register and capture and deploy. Thank you again for all the help.

Alrighty, so my work-arounds for this issue were to use a virtual drive of 28GB to make the original image, alternatively you can delete the 4th partition to make imaging completely compatible, but you lose the ability to do an OS reset in Windows. If you move the partition to where it used to be in v1909, Windows can’t find it and that also loses the ability to reset, so if you have to move it, just delete it i guess… another alternative if using clonezilla you can image and use gparted to first move the 4th partition to the end of the drive, then resize the 3rd partition, this seems to work fine without losing the option to reset, tested on 2 different machines, a Clevo Laptop and an HP All in One. Otherwise typically just make sure the drive you are imaging to with FOG is generally larger than the source disk you imaged from and everything should be fine… generally speaking…

Hi, I also encounter a TFTP problem with a fresh installation of FOG 1.5.8. System: Debian 10 When starting PXE on the client machine, it asks me to enter the IP of the TFTP server, but that does not change anything. I have 3 DHCP on my network, but the 3 broadcast the 66, 67 from my fog server. Were you able to solve your problem?

@george1421 You have a great point. I discussed it with the boss, and we went the path of no client on the laptops. It is a relatively small number right now that need a somewhat quick turnaround. I figure we can bang out renaming and joining manually for these. Perhaps I will investigate other methods if there is a future order or it is the direction we end up going. Thanks!

Just to be clear (I can read your request 2 different ways), fog doesn’t care about the source image or how its setup. FOG only moves disk blocks from the source computer to storage on the FOG server and then from storage on the FOG server to the target computer. How you prepair the reference image before cloning and what happens to the target computer after FOG is done is up to the IT technician. But in general terms, for MS Windows you will want to setup the computer in audit mode to perfect how you want the target computers to appear, then sysprep the reference image and power it off (using a sysprep command line option). Then you pxe boot the reference image with FOG and capture the image. On the target computer side, you register the target computer with FOG. Then you assign an image to the target computer and create a deploy task. When the target computer is pxe booting FOG will image the computer then reboot it. On the first reboot the target computer will startup OOBE/Winsetup to complete the installation on the target computer, at this point of the first boot of the target computer FOG is no longer involved with the imaging process (said knowing that if the target computer is configured appropriately the FOG client will carry out an required post install commands). There is a wiki page that describes capturing your first image that you might want to look over: https://wiki.fogproject.org/wiki/index.php?title=Booting_into_FOG_and_Capturing_your_first_Image

It’s completly dumb i just didn’t created the image entirely so i couldn’t upload anything ^^" But thanks anyway for your help and your work !

Issue solved, yet we have now version 1.5.9 RC and there is new problem with node offline

Yes SVN method has been removed, only the git and tarball method is actively supported now. https://wiki.fogproject.org/wiki/index.php?title=Getting_FOG This process is recommended for new installs as well as upgrades to existing installs.