@sonic136 said in Adding an IPP printer:
Please advise as to how to add a printer as we cannot use the conventional \printerserver\printername…
So how do you configure your printers if not via the conventional name?
@sonic136 said in Adding an IPP printer:
Please advise as to how to add a printer as we cannot use the conventional \printerserver\printername…
So how do you configure your printers if not via the conventional name?
@robellet /var/www/fog is intended to be a link to /var/www/html/fog but seems like it’s not in your case. So you seem to have two versions of the web UI installed. Probably good to clean that up while you are at it. Run diff -Nur /var/www/html/fog /var/www/fog
to see the differences. Post output here if you need help to sort this.
@agray In the directory where you run the installfog.sh script there should be a subdir called error_logs with two files in it post the contents of those here.
@waveydavey said in PXI Image menu on new installation:
067 pxelinux.0 Bootfile name
(actually there are 2x 067 entries - the above on no policy, and ipxe7156.efi on EUFI policy)
legacy BIOS boot file should be undionly.kpxe
(or ipxe.pxe
) and UEFI boot file should be ipxe.efi
@agray Not sure what exactly is going on but the permissions on their folder are not like the installer would set them. So I suggest you simply run the installer as root user again. That should fix the permissions as well as set the fog
account password back to what it was.
@dirtrunner21 said in Fog imaging and M.2 drives:
I’ve tried a newer kernels and they all hang at clearing the MBR/GPT table and go no farther.
This issue is known and fixed. Either update to 1.5.5 or manually update kernel and init.xz! Search the forums and you should find numerous posts on how to do that.
@agray But do you login with that account and use it?
I am asking because this account is NOT meant to be used as a user/admin. FOG itself uses it and if you reset the password you are breaking some of FOGs functionality.
But could also just be a simple permission issue. Please run ls -al /opt/fog/snapins
and post output here.
@blindhelix Are you able to deploy this exact same image to a different host that can PXE boot? Please try and let us know.
As well please post a screenshot of the full image settings in the FOG web UI and output of the following commands: ls -al /images/2018-07-17Win10-1803UEFI
- cat /images/2018-07-17Win10-1803UEFI/d1.fixed_size_partitions
- file /images/2018-07-17Win10-1803UEFI/d1p1.*
@agray Do you use the User account called fog
to login and work on your FOG server?
@jherron Have you tried scheduling tasks for a couple different hosts? Do they all show those errors? It’s very strange but to me it more sounds as if this might be a hardware issue with this particular client machine.
@jherron Probably best if you take a picture of the screen and post here. Helps a lot more than trying to explain what you see.
@JJ-Fullmer Ok, I just prepared a first one to test for you - download 1_bzImage
and put in /var/www/html/fog/service/ipxe. Then edit this host’s settings and set this kernel as Host Kernel and see what you get.
I used a fairly recent kernel version 4.19.13 and so we might even see different behaviour than when we tested some months ago.
@JJ-Fullmer Sorry for the long delay again. I am back on track now to tackle this. Do you think you can get it back for some testing in the next couple of days? I am preparing debug kernels already. So I’ll be ready to go when you are.
I just came across this by accident and wondered if this was ever solved. Reading through it and the related iPXE forum post (link) it seems like this was caused and fixed by Microsoft. So if you have this issue, update and you should be fine.
@salted_cashews I’ve just tried, clean Ubuntu 18.04.1 Desktop install (non LVM as default) and cannot replicate the issue. It’s capturing just fine.
As well I just noticed that you definitely have not had LVM as we see /dev/sda1 in the screenshots. I can’t see why this caused trouble for you. Maybe a disk error?!
Shall I mark this solved or keep it open?
@salted_cashews said in Trying to capture Ubuntu 18.04.1 and I get this.:
but we’ve moved over to CentOS since then
Means you don’t have a system to test anymore?
I formatted a USB 3.0 device using Rufus (latest) …
What do you mean by that? Using USB key as install media?
@whity said:
Instead of registering the hosts from the PC side, can we import the host name with MAC address of a PC using a .CSV file and assign the needed image and deploy? Would that work?
Sure you can import hosts as CSV - see Tom’s post here for some details. Or you can export a CVS from a dummy host created and use that as a template. Find the option to import/export in the Host section of the web UI.
When I am creating a multicast imaging session, the entry shows for a while and then disappears when page is refreshed. Is that behavior normal?
Please check FOG multicast.log (in /var/log/fog/)…
@AndrewG78 I just added the refind_ia32.efi binary to dev-branch
so it will be part of the next release.
@salted_cashews Sorry for my late reply.
Is it possible this is the result of mounting everything on one partition?
I don’t think this can cause the issue. Trying to read up on this I found a bug report that kind of sounds like what you see: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1778140
Although I am still unsure if this can happen with the pre-resize test we do. But can you confirm you are installing on LVM? If unsure run df -h
on your Ubuntu system and post output here.
EDIT: Reading a bit more I found another hint on there being an issue with resize2fs. Again this is on LVM but maybe it can happen on plain partitioning as well. This points us to a second launchpad bug report.
Would you mind trying to install Ubuntu without LVM and see if that fixes it. Although the patch was added to the official e2progs source in October 2018 it has not made it into buildroot which we use for FOG yet (as of now, last e2fsprogs update was in early 2018).
Which install ISO did you use? Desktop or Alternative installer? Just asking so I would setup the same test scenario…
@Vincent I guess what you mean is the quick image option from the PXE menu, right?
This has been discussed in the forums before: https://forums.fogproject.org/topic/10993/login-when-deploying-image