Posts made by jeffj

I am working on a Latitude 5300 Laptop it has a NVMe SSD installed I am booting to the Dell USB 3.0 to Ethernet adapter with PXE boot to image these machines. The workstation will boot to the fog menu but when I try upload an image i get this after the bzimage and init.xz loads – “usb usb2-port2: cannot enable. Maybe the USB cable is bad?” If I unplug the usb and plug it back in it will stop and allow me to plug the usb back in once I do it works properly. attached is a screenshot after I have re-seated the usb nic. Any help to not have to do the “Re-seat” step would help me out a lot.

I have tried adding the Kernel Args. usbcore.old_scheme_first=1 has_usb_nic=1 and it has not resolved the issue.

I am running FOG Version 1.5.6 bzImage Version 4.19.36

Secondly, if we could get the NVMe drive to be recognized using the SATA Mode “Raid on” instead of “AHCI” would help out as well.

@george1421

Also, something to note, I had another machine I was testing this on and if you do not do the disk cleanup and remove the old windows installations the new inits work just fine. It appears the cleanup messes something up for some reason.

@george1421 Correct

@george1421 Actually as long as you update the init.xz and init_32.xz it appears to work in 1803!

No I hadn’t.

Since you suggested it I did and it appears to be working now. Glad it was such an easy fix! Thanks!

So I am trying to update my image of a machine I updated to Winodws 10 Version 1803 (Spring update 2018) and I am getting the “Error Could Not Open inode XXXXXXX Through Library”

I visited the (https://forums.fogproject.org/topic/11207/error-could-not-open-inode-xxxxxx-through-the-library) and updated the init.xz and the init_32.xz files and tried to re-run the capture task but am still having the same error occur.

I will note I ran disk cleanup and removed previous windows installations before trying to update this image to reduce the size of the image as much as possible.

Server Info
FOG Version 1.5.2
Ubuntu 16.04 LTS

@Tom-Elliott yes

Okay when creating a new image that was resizable I receive the dirty filesystem 0,0 error.
rebooted the system and turned fast startup off.
After doing so I was able to create the image successfully.
Tried to deploy the newly created image on the smaller HDD and so far so good we are writing the image now.

Recap for marking the post solved.

Could not image HDD with known good image was getting a “No image file(s) found that would match the partition(s) to be restored (performRestore)”
Ran Debug mode to see what partitions were being created on the HDD.
Checked the partition table on the image on the server.
Noticed that the image was a MPS(Multiple Partition Single Disk) and HDD in host was smaller than the original used to create the image.
Disabled Fast booting on the host I need to re-create an image from.
Re-created an image using SDR (Single Disk Resizable).
Was then able to deploy the image to the host with the smaller HDD with no problems.

AH yeah it is a smaller drive than the original. I happen to have another one of those computers I can recreate an image using single disk resizable. If my memory serves me correctly I was having trouble getting it to create an image that way. I will update this when I run into problems.

when entering fdisk and selecting ‘n’ command it tells me all space for primary partition in use at the top of the first image it cut off the command but i used ‘p’ to print the partition tables the rest of what I did is in the picture.

After running the ‘fog’ command it still fails with the same error I also rechecked the partitions using lsblk and it is how it was before the image deploy command.

here is the requested information

Server

• FOG Version: 1.4.0 RC-6
• OS: Ubuntu 16.04 LTS

Description

I am unable to deploy an image to a host the attached picture is what happens was able to deploy no problems before I upgraded from 1.3.0 RC-16

I am using UEFI and the bootfile is ipxe.efi
I am not having trouble on machines that use undionly.kxe and are legacy booting.
I checked the images folder and the image is present.

Nevermind disregard this post I switched out the adapter and now it is booting. thanks for your time.

Sorry for the confusion yeah the Inspirons are using a usb ethernet adapter, realtek that is dell branded to be specific. I just mentioned the XX20/30 series to show that using undionly.pxe works on some machines to help narrow the possibilities of what is wrong.

the 7000 series no longer boots to the pxe menu it stops at “Start PXE over IPV4” unfortunately there is no error message.

I have also tried the realtek.efi file since the initial post and that still did not boot.

Server

• FOG Version: 1.4 RC-6
• OS: Ubuntu 16.04 LTS

Description

I upgraded FOG, I had Version 1.3 RC-16 and I was able to boot to uefi for my Inspiron 7000 series using ipxe.efi as the boot file and the ethernet adapter as the dell ethernet adapter. I can boot fine using undionly.kpxe for my E5420/E5430 series computers. I am at a loss for what to try next I checked the .fogsettings file, default.ipxe, and the storage node and the server ip is correct in all the locations. I have tried intel.efi and ipxe7156.efi to no avail. nothing else has been changed that I know of. Any help would be appreciated.

@Tom-Elliott

Thanks again tom! marking as solved.

@Tom-Elliott

okay after running those commands and re-running the installer it now fails when installing package php7.0-fpm

the fog error log has this to say:

Unpacking php7.0-fpm (7.0.12-1+deb.sury.org~xenial+1) …
Processing triggers for man-db (2.7.5-1) …
Processing triggers for ureadahead (0.100.0-19) …
Processing triggers for systemd (229-4ubuntu11) …
Setting up php7.0-fpm (7.0.12-1+deb.sury.org~xenial+1) …
Not replacing deleted config file /etc/php/7.0/fpm/php.ini
php_invoke: Enable module gettext for fpm sapi
php_invoke: Enable module iconv for fpm sapi
php_invoke: Enable module fileinfo for fpm sapi
php_invoke: Enable module exif for fpm sapi
php_invoke: Enable module ftp for fpm sapi
php_invoke: Enable module shmop for fpm sapi
php_invoke: Enable module sysvsem for fpm sapi
php_invoke: Enable module sockets for fpm sapi
php_invoke: Enable module sysvshm for fpm sapi
php_invoke: Enable module opcache for fpm sapi
php_invoke: Enable module readline for fpm sapi
php_invoke: Enable module bcmath for fpm sapi
php_invoke: Enable module sysvmsg for fpm sapi
php_invoke: Enable module json for fpm sapi
php_invoke: Enable module posix for fpm sapi
php_invoke: Enable module pdo for fpm sapi
php_invoke: Enable module ctype for fpm sapi
php_invoke: Enable module tokenizer for fpm sapi
php_invoke: Enable module calendar for fpm sapi
php_invoke: Enable module phar for fpm sapi
php_invoke: Enable module curl for fpm sapi
NOTICE: Not enabling PHP 7.0 FPM by default.
NOTICE: To enable PHP 7.0 FPM in Apache2 do:
NOTICE: a2enmod proxy_fcgi setenvif
NOTICE: a2enconf php7.0-fpm
NOTICE: You are seeing this message because you have apache2 package installed.
initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused
insserv: warning: script ‘binfmt-support’ missing LSB tags and overrides
insserv: Default-Start undefined, assuming empty start runlevel(s) for script binfmt-support' insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script binfmt-support’
initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused
insserv: warning: script ‘screen-cleanup’ missing LSB tags and overrides
insserv: Default-Start undefined, assuming empty start runlevel(s) for script screen-cleanup' insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script screen-cleanup’
Job for php7.0-fpm.service failed because the control process exited with error code. See “systemctl status php7.0-fpm.service” and “journalctl -xe” for details.
invoke-rc.d: initscript php7.0-fpm, action “restart” failed.
dpkg: error processing package php7.0-fpm (–configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
php7.0-fpm
E: Sub-process /usr/bin/dpkg returned an error code (1)

@Wayne-Workman

as much as I hate giving up on fixing a problem it appears that rebuilding will be the easier route. thanks for the link for rebuilding fog server I was unaware of how to copy the images and and migrate them to a new server.

@Wayne-Workman

when doing that and trying to restart apache2 it errors out here are the error details

Job for apache2.service failed because the control process exited with error code. See “systemctl status apache2.service” and “journalctl -xe” for details.

here is the systemctl status apache2.service output:

Loaded: loaded (/etc/init.d/apache2; bad; vendor preset: enabled)
Drop-In: /lib/systemd/system/apache2.service.d
└─apache2-systemd.conf
Active: failed (Result: exit-code) since Tue 2016-10-18 12:16:23 CDT; 5min ago
Docs: man:systemd-sysv-generator(8)
Process: 28519 ExecStart=/etc/init.d/apache2 start (code=exited, status=1/FAILURE)

Oct 18 12:16:23 fog apache2[28519]: * The apache2 configtest failed.
Oct 18 12:16:23 fog apache2[28519]: Output of config test was:
Oct 18 12:16:23 fog apache2[28519]: [Tue Oct 18 12:16:23.340112 2016] [:crit] [pid 28529:tid 3074751040] Apache is running a threaded MPM, but your PHP Module is not compiled to be threadsafe. You need to recompile PHP.
Oct 18 12:16:23 fog apache2[28519]: AH00013: Pre-configuration failed
Oct 18 12:16:23 fog apache2[28519]: Action ‘configtest’ failed.
Oct 18 12:16:23 fog apache2[28519]: The Apache error log may have more information.
Oct 18 12:16:23 fog systemd[1]: apache2.service: Control process exited, code=exited status=1
Oct 18 12:16:23 fog systemd[1]: Failed to start LSB: Apache2 web server.
Oct 18 12:16:23 fog systemd[1]: apache2.service: Unit entered failed state.
Oct 18 12:16:23 fog systemd[1]: apache2.service: Failed with result ‘exit-code’.

here is the journalctl -xe output:

Unit apache2.service has failed.

– The result is failed.
Oct 18 12:16:23 fog systemd[1]: apache2.service: Unit entered failed state.
Oct 18 12:16:23 fog systemd[1]: apache2.service: Failed with result ‘exit-code’.
Oct 18 12:16:23 fog polkitd(authority=local)[905]: Unregistered Authentication Agent for unix-process:28506:7432110 (system bus name :1.902, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)