Posts made by Sebastian Roth

@JJ-Fullmer said in “Deploy Image” Not Working for HP Probook 450 G9:

I think you’re thinking of this post https://forums.fogproject.org/topic/16720/hp-elitebook-840-g9-cannot-deploy-image

No, that’s not the one. But I found it: https://forums.fogproject.org/topic/16746/using-deploy-image-via-pxe-with-more-than-two-nics

@LLamaPie @LLamaPie @rodluz Took a while until I found the time to look into this. But I found the bug and just pushed a fix to the latest dev-branch. Please update and you should not run into the issue no matter how many NICs you have.

@Tom-Elliott Would you like to check working-1.6 as well?

@brakcounty said in Limit disk space that FOG can use:

is there a way to tell FOG to limit the available space to use for images?

No, not that I am aware of at least.

I will be mounting the images from the host to the VM with an internal switch via SMB.

Not sure if this is possible to do (export NFS share on a SMB mount) on the one hand and then if it’s wise to do on the other hand.

@Tom-Elliott said in Fog Snap-In Permissions Issue?:

Is it possible it’s requesting the resource from a different server than the one you know the files are on?

Just along these lines… do you have more than one FOG node in your network?

The remote server returned an error: (404) Not Found.

The snapin files are not requested via HTTP URL directly but through a helper script. See if you have /var/www/fog/service/snapins.file.php on your FOG server(s).

@CedricoR @lebrun78 Check out this topic, seems to be related: https://forums.fogproject.org/topic/16859/rhel-initramfs-unpacking-failed-kernel-panic-not-syncing

@WT_101 @hutch Looks like we have a very similar issue with Ubuntu 22.04 installs as well: https://forums.fogproject.org/topic/16850/problem-after-deployment-with-release-1-5-10

@Jamaal said in Dell Latitude 5530 issue:

it goes right to the ctrl alt delete screen and then the administrator password is not working

To me this sounds like a wrong or missing driver could be causing this.

@george1421 Would you have an idea how to debug this issue?

@ITRecords Have been pretty busy with other things and forgot about this topic. Whoops.

Ok, so we have a plain disk drive here (sure virtual disk but no LVM or fake-RAID) which makes it pretty easy.

1. Make sure there is no FOG task (deploy or capture) running!
2. Stop NFS daemon: systemctl stop nfs-kernel-server
3. Unmount the partition: umount /dev/sdb1
4. Install an easy tool for expanding the patition: apt install cloud-guest-utils
5. Test expanding the partition: growpart -N -v /dev/sdb 1 (note the space before the partition number)
6. Expand partition: growpart -v /dev/sdb 1 (note the space before the partition number)
7. Expand filesystem in partition: resize2fs /dev/sdb1 (no space before partition number)
8. Mount partition: mount /dev/sdb1 /images
9. Start NFS: systemctl start nfs-kernel-server

@mattah_18 Is fast boot disabled on this machine? How do you shutdown the machine before capture?

@FlareImp said in Showing Last Check-in Time:

dumb question but where would I find the log file for hooks?

See my signature.

@capitald Let’s take a step back. Before we get into this any further we need to think about the whole connection between fog-client and the FOG server. The fog-client wouldn’t get as far as loading a snapin if there was a general problem with the SSL certs and trust.

So is must be very specific some issue at this stage. So you use the location plugin? Were both nodes setup with HTTPS (which is not the same encryption layer we are looking at here)?

@flat4vw said in Lenovo ThinkPad P15:

How and where do you check to see what ipxe file is using so I can test.

Check your DHCP server configuration. If you told FOG to setup DHCP for you that would be in /etc/dhcp/… (filename depends on the Linux OS you use). If you have a Windows or other DHCP server in your network then you should know where to look.

@AlexPDX This “bug” appears on new installs as well as on upgrades from any previous version.

This is just a minor thing because if things were right it would show the node’s kernel version instead of “Unauthorized”. It’s just not able to pull the kernel version information. Will be fixed when we find the time but this is not a show stopper.

@Mentaloid Confirmed a bug in 1.5.10. Will be fixed in the next version. Will keep you posted here.

Moving the topic to bug reports.

Code:
https://github.com/FOGProject/fogproject/blob/1.5.10/packages/web/lib/pages/snapinmanagementpage.class.php#L466
https://github.com/FOGProject/fogproject/blob/1.5.10/packages/web/lib/fog/storagenode.class.php#L200

@robertkwild Which version of FOG do you use and is the image type resizable or non-resizable?

@ITRecords Just so I get this right. From your initial post it sounds like you have increased the size already. Right? What was the size beforehand?

Please run fdisk -l /dev/sdb and post output here. First I was misslead to think this was setup as LVM but it’s a normal type partition by the looks of it.

Be aware that size calculations vary. Some multiply by 1000 others by 1024 and that causes some difference as well.

@Squanchy2112 Yes sure, you can Update from 1.5.9 by simply running the 1.5.10 FOG installer.

@robertkwild said in updating fog on centos 7:

it took ages compiling the ipxe binarys but now its been succesfully updated

THat’s right. Usually takes a few minutes depending on the CPU you have.

@ITRecords Please run the following commands and post output here:

df -h
mount
lsblk
pvs
vgs
lvs

If you are keen read through this and go about it: https://forums.fogproject.org/topic/16729/ubuntu-help-boot-problem-n00b/

Though I suggest you make sure you have a backup beforehand. And in case you are unsure better ask.

@danibashkov said in Exec format error during network boot:

Could not boot image: Exec format error (http://ipxe.org/2e008001).

Most likely the kernel image is missing or corrupt. Please check using the following command: file /var/www/{html/,}fog/service/ipxe/bzImage

As well I may ask how your DHCP server is being setup? Did you say yes for FOG to install and setup DHCP for you on the FOG server or do you manage your own DHCP server in the network? Just asking because possibly this might be a 32/64bit issue as well.

@Goll420 said in updating fog on centos 7:

Hi Tom, sorry to hi-jack the thread, but …

Why not open your own one?

what if you DON’T have the git installed?

Either install git or grab the tar.gz / zip archive version found on the website to download: https://fogproject.org/download

sudo -i
# or
su -
tar xzf fogproject-1.5.10.tar.gz
cd fogproject/bin
./installfog.sh

Our FOG server is on an isolated network without internet access so it’s not an option for me really.

Well, how did you install FOG in the first place then? Internet access is needed. Maybe you can install a NIC (wireless LAN or cable) to get internet access temporarily?