@jtyler Have you had a look into the mentioned error_logs? Let us know what you get.

I try with an update from 1.4.4 to 1.5.4 and install from scratch, same problem. After changing Host Site and clicking “update” nothing append (no message ‘host updated !’) and apache error log says : [Thu Aug 23 11:25:30.658913 2018] [proxy_fcgi:error] [pid 50898] [client x.x.x.x:x] AH01071: Got error 'PHP message: PHP Fatal error: Uncaught Error: Call to a member function get() on null in /var/www/fog/lib/plugins/site/hooks/addsitehost.hook.php:322\nStack trace:\n#0 /var/www/fog/lib/fog/hookmanager.class.php(87): AddSiteHost->hostAddSite(Array)\n#1 /var/www/fog/lib/pages/hostmanagementpage.class.php(3701): HookManager->processEvent('HOST_EDIT_SUCCE...', Array)\n#2 /var/www/fog/lib/fog/fogpagemanager.class.php(220): HostManagementPage->editPost()\n#3 /var/www/fog/management/index.php(54): FOGPageManager->render()\n#4 {main}\n thrown in /var/www/fog/lib/plugins/site/hooks/addsitehost.hook.php on line 322\n', referer: http://x.x.x.x/fog/management/index.php?node=host&sub=edit&id=1 Then Javascript Console says when i click ‘Update’ : jquery-latest.min.js?ver=133:4 POST http://x.x.x.x/fog/management/index.php?node=host&sub=edit&id=1&tab=host-general 500 (Internal Server Error) send @ jquery-latest.min.js?ver=133:4 ajax @ jquery-latest.min.js?ver=133:4 a.ajax @ jquery-migrate-latest.min.js?ver=133:2 submithandlerfunc @ fog.js?ver=133:601 d @ jquery.validate.min.js?ver=133:4 (anonymous) @ jquery.validate.min.js?ver=133:4 dispatch @ jquery-latest.min.js?ver=133:3 q.handle @ jquery-latest.min.js?ver=133:3 If i don’t select any host and do an update the message “Host updated !” appears by the way.

@Basavarajnc said in It takes longer Time (More Than 5 Minutes) Erasing current MBR/GPT tables.: -2. transfer means copying Yes trasfer == copy == move however you get the file to that directory. -5. Now Scedule a deployment I have seen capture as low as 800MB/min depending on your compression setting and the performance specifications of your target computer. The target computer’s CPU is used heavily during image capture to compress the hard drive image before its sent to the fog server. If you have a slow target computer, with an old CPU, or slow hard drive, or too high image compression will cause slow capture speeds. But for image deployment to same computer it should be faster.

Thanks again for your reply. Still no joy. I’ve recopied the contents of the 18.04.1 LTS iso to /images/os/ubuntu/18.04/mate. after cleaning out that directory. My menu config is as follows: kernel nfs://192.168.0.14/images/os/ubuntu/18.04/mate/casper/vmlinuz initrd nfs://192.168.0.14/images/os/ubuntu/18.04/mate/casper/initrd imgargs vmlinuz initrd=initrd root=/dev/nfs boot=casper netboot=nfs nfsroot=192.168.0.14:/images/os/ubuntu/18.04/mate/ locale=en_GB.UTF-8 keyboard-configuration/layoutcode=gb quiet splash toram ip=dhcp rw boot || goto MENU There is no initrd.lz so had to change it to initrd Booting up my test PXE client VM gives me a kernel panic:  I added the following to /etc/exports: /images/os/ubuntu/18.04/mate *(ro,sync,no_wdelay,insecure_locks,no_root_squash,insecure) And rebooted the server. Same result! I don’t want to use a DHCP assigned IP on my PXE server as I need it to resolve local DNS queries from my internal DNS server on the network. Is there a workaround/ Many thanks, Neil

@bricktop135 At which stage do you get the cursor on the black screen? Can take a series of pictures or video so we see the whole boot process?

Your best bet to have a standalone solution is to deploy the image to a temp computer and then capture the image with clonezilla. Both FOG and Clonezilla use partclone to capture the image, but FOG uses an image compression format not understood by partclone. You won’t have the FOG service capabilities with clonezilla but imaging will work standalone.

@quazz said in Edit Image: You could potentially use postdownloadscripts instead for something like this. This is exactly how I go about updating the golden image between image captures. It uses a similar concept to dynamically installing drivers during image deployment. I do take this one step more by creating a file in the golden image that has a sequence number in it, that way I can reference that file in the post install script to only apply the fixes related to that specific sequence number.

@Tom-Elliott You got an idea? @coop90 Can you please provide fog-client logs?

@Mike-Fahey Can you post the commands used to delete and how you see that there is still no free space? If we don’t see what you are, how can we help you?

Can you tell me (sorry a bit too lazy to look) when you quick register a host, does it ask you for a group assignment? If so you could use the persistent group (hack) to create a host template with all of the settings you want by default for new hosts, then when you add the system to a template group, those settings will be copied to the newly registered host. The other way I can think how to do this is create a mysql database trigger, to when a new host is added to the hosts table in mysql, the check box is checked in the database. I’m not really in favor of the second part, but it will work if all other choices fail. The template host/persistent group plugin it a bit cleaner approach.

@andrewg78 I’m still thinking its bit locker that is causing your issue. When you use single disk not resizable then clone the image, you are not changing the geometry of the disk. Please read through this post and see if running the commands to disable bitlocker makes single disk resizable work better. https://forums.fogproject.org/topic/10824/image-upload-deploy-taking-a-long-time/43 Looking over the entire thread just for your info.

@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.

@Korvyr From the pictures yo posted I guess you have a different issue to what has been initially posted. Would you mind opening a new thread and posting your client hardware details there? I will move your posts to that as soon as you opened a new thread.

@x23piracy Having had some trouble to upgrade to 1.5.4 but I finally managed it. The behaviour is still the same under 1.5.4. Having 1 host in the group -> wrong image Adding a second host -> correct image Removing 1 host -> wrong image Cheers Rainer

@louis-csusa @George1 Hi Louis, George1421 created a great post, scroll down to part 2a. You will see the info you need. https://forums.fogproject.org/topic/7727/building-usb-booting-fos-image/3 I added George Incase there’s any new info. Maybe Fog will support APFS? Since I seen reports that Clonezilla can imaged using DD. Also this usb script does not support the new T2 15inch MacBook Pro keyboard. However using a usb hub to connect an usb Ethernet, keyboard I was able to pxe boot and register it. Please note you will need to disable secured boot on an T2 chip Mac.

%WINDIR%\Panther\unattend.xml

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

@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.

@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?