@salted_cashews We have not looked at the partition layout yet at all. Probably just because the error did not seem to point that way. Thanks Tom for mentioning that in a chat session!
Can you please post the contents of the text files: d1.fixed_size_partitions (before and after changing it), d1.partitions, d1.minimum.partitions and d1.original.fstypes.
@salted_cashews Make sure you have enough space on your disk: df -h
Now as a test, please do the same with another image file:
zstdmt -d /images/PPS_v9.0R2-dev_CentOS/d1p1.img -o /images/PPS_v9.0R2-dev_CentOS/d1p1_extracted.dat
From my point of view the manual extraction test should give you an error if the image file is fine.
@salted_cashews Possibly this version of file does not detect Zstd compressed files. Please try to manually extract the image to see if that works properly:
zstdmt -d /images/PPS_v9.0R2-dev_CentOS/d1p3.img -o /images/PPS_v9.0R2-dev_CentOS/d1p3_extracted.dat
See if that triggers an error or not.
Hint: You might need to install package zsdt on your FOG server.
@Mark-krikunov Sorry for the confusion. Seems like our version check page had an issue. I just fixed that. Please take a look again to see if it tells you are up to date now?!
What’s the difference between 1.5.6 and 1.5.6.2.
1.5.6 is the latest official release while 1.5.6.2 is the latest development version.
@salted_cashews Please run the same for all image files in that directory: file /images/PPS_v9.0R2-dev_CentOS/d1p*
@salted_cashews Please run the following command on your FOG server: file /images/PPS_v9.0R2-dev_CentOS/d1p3.img
Post output here.
@khalid Is it a MSI or other sort of installer? Can you enable debug for the installer. Definitely possible for MSI. Please post a picture of the snapin settings.
@salted_cashews Take a look at Tom’s post here: https://forums.fogproject.org/post/88286
Though I have not tested this myself lately it should still work I reckon.
@salted_cashews said in Deployment stuck in a loop, never finishes imaging?:
Let me see if I can trace back exactly what we did.
Maybe .bash_history…?
@salted_cashews I find it really strange that the filesystem does not seem to be clean. Are you sure the filesystem was clean when you initially captured the image? Sure the machine was not in some kind of hibernation when it was PXE booted to be captured?
@salted_cashews See if you can grad the partclone.log file and hope we get some more information from that.
@Pi0tR The picture was not uploaded properly. Please upload again.
From what you wrote so far it seems like you are on the right track to debug this. Opening the boot.php URL in a browser is a good start to try and find out what’s wrong. Are those two computers in the same network subnet? Is the FOG in the same subnet as well? Just asking if there might be a firewall between the booting client and your FOG server.
As well, can you copy&paste the whole output you get in the browser when opening the URL? Just wanna make sure it returns the correct iPXE command codes.
Try opening the URL including the MAC address parameter as well: http://x.x.x.x/fog/service/ipxe/boot.php?mac=aa:bb:cc:dd:ee:ff (copy & paste the output of that here in the forum as well just to make sure this is correct too)
@carmonj Better use 500 GB for testing just to make sure.
If you can change the partition layout on your master (source machine) that would make things easier I suppose.
@AndrewG78 said:
There are several identical broadcast responses.
Can’t explain that without having a full wireshark/tcpdump pcap file. Way too much information is missing to be able to get a glimpse on why this might happen
There is tftpd error - Error code 8: User aborted the transfer
It’s kind of a known thing. Before loading the boot file via TFTP the client requests the file size (via RRQ query command). The server answers the size query and for some weird reason the client sends back a “User aborted the transfer” and then sends a new request to actually download the file.
@carmonj Well your partition layout is quite interesting. The boot partition is located after the windows system partition. As FOG don’t move the boot partition to a different location and marks it as fixed to not break anything. So from the numbers I see that you need a disk size of 480 GB or more to be able to deploy this image properly. What disk size is the VM you are trying to deploy here?
@carmonj Do you see any errors or warnings on deploy? As well please let us know if the image is set to non-resizable or resizable. If it’s the later one please post the contents of the text files d1.minimum.partitions, d1.partitions and d1.fixed_size_partitions that you find in the image directory on your FOG server.
@Chimpish You might have messed with the FTP credentials while trying to fix this. Make sure you never use the account named fog (called fogproject from version 1.5.6 on) for login and working on your server as this will cause issues.
https://wiki.fogproject.org/wiki/index.php/Troubleshoot_FTP
Make sure you have the same password in /opt/fog/.fogsettings as well as in /var/www/html/fog/lib/fog/config.class.php and set for the fog Linux account. The password in /opt/fog/.fogsettings will be set in config.class.php and reset on the Linux account if you re-run the FOG installer.
@Wayne-Workman I don’t use slack much and can’t figure out how to get the OAuth token. Have looked though Slack docu and the website and have not found it. Maybe I am just too dumb… 
@ianabc Had a bit more time to look into this now. You have missed one important point here. You need to manually create a new TaskType (web UI -> main menu -> TaskTypes -> Create New Task Type) and name that trusty-install - exactly the name of the task that is used in lib/hooks/boottask.hook.php (line 73). As soon as you’ve created this task type you should see it in Host -> Basic Tasks (or Host -> Basic Tasks -> Advanced Tasks if you’ve checked the “Is Advanced” checkbox when creating it!).
Now you can schedule this task type for any client or group and when it boots up it uses the arguments you set in lib/hooks/boottask.hook.php (line 83 to 93). But only if the names match. So if you name your new task bababoo you need to have that in your lib/hooks/boottask.hook.php line 73 as well.
@dooleyrd I have not used the plugin myself but trying to read up on things I see that Slack has changed the API token authentication a fair bit over time. Not sure if it’s just that our plugin doesn’t work anymore at all.
@Tom-Elliott @Wayne-Workman From this topic I see that it used to work with Slack API Tester App and generated test tokens. But here I read that those are legacy…