Also I have this rEFInd hangup screen… there are a solution? hw Is a hp all-in-one the temporary solution Is to Press f9 at boot to start via pxe so if hard disk Is the First start option in BIOS list Windows starts up normally, but Is Crazy pressing f9 Every time when you have to do a multicast session of 20-30 PC…

@itcchs-bob There are a couple of things going on here then. (good you found the root of the issue)

Starting with Win10 20H2 microsoft changed the disk structure where they placed the recovery partition at the end of the disk and marked it as non-movable. In the FOG dev branch FOG version 1.5.9.110 and later has a fix for this locked partition.

There are some disk layouts that also are problematic to shrink. Think about it a 512GB hard drive could potentially have a partition starting location beyond the last block on a 256GB disk. So its always problematic haveing a source disk larger than a destination disk. Can FOG deploy larger to smaller disk? Yes as long as all of the conditions are right.

If I’m doing a one to many image deployment, I always create my golden image on a VM with the disk set to the smallest disk I will every deploy to. So for Win10 I create a 70GB disk, and Windows Server a 120GB disk. This way when deployed the disk always grows to the final size.

@george1421

No bitlocker enabled, so I’m not sure why it’s not resizing that partition. I’m in the middle of another image capture attempt, and though it captured the OS partition quickly(and then took 15 ish minutes to move on to the next one after the ‘Cloned Sucessfully’ message) it’s back to the thing where it’s stalled for no apparent reason and dropped back down to miserable speeds.

I am entirely mystified about what is going on. It doesn’t seem to be consistent in what it’s doing. sigh Is there something else I can grab to help identify what’s going on?

@ljh said in High DB utilization:

So it looks like that fixed my issue

FWIW: Which “that” is the fix? Switching over to innodb engine or the reboot?

Hi,

Sorry to revive an old thread but it is still happening.

For example with ThinkPad T450, T460, T470 it goes very fast (6-8GB/min). With ThinkPad E14 G2 it only goes around 600MB/min.

Thank you

@george1421 , thanks, i will see that.

@celsoares said in ACPI BiOS Error:

Sorted out! Thank you so much for the availability…

Just for clarity for the next person who finds this thread: Did you install the 4.15.2 kernel and it worked correctly?

If yes, you can create a fog settings group for those 100 HP computers to apply that kernel name to all devices with out having to hand edit each host record.

Related article: https://wiki.fogproject.org/wiki/index.php?title=Migrate_FOG

@nono The values in fogsettings should remain as the installer created them. As I said the fogstorage account is for external access to the master fog node from storage nodes. That account only has edit rights to the database, it can’t create or delete tables or schemas, that is the function of the fogmaster account. If you change it to fogstorage your next fog upgrade will fail because it doesn’t have the right access level to update tables in the fog database.

@willingmost7 said in not entering fog menu after nbp completed:

it is on the same subnet.

OK good. Lets follow this tutorial to capture a pcap of the pxe booting process. https://forums.fogproject.org/topic/9673/when-dhcp-pxe-booting-process-goes-bad-and-you-have-no-clue Upload that to a file share site and either post the link here or DM me the link in FOG chat and I’ll take a look at it. There is something unexpected going on here. The pcap will tell us.

@john-l-clark What version of the FOS Linux kernel are you using? (web ui -> fog configutation -> kernel update) Are you on 5.15.x

@beeppy said in HTTP ERROR 500 - Fresh install:

Any news when CentOS9/PHP8 will be supported?

I don’t have any timing on when FOG 1.5.10 will be released. From the last time I talked with the developers FOG 1.5.9.120 or so in the dev branch will probably be what will be 1.5.10 when its released.

So just as an FYI it might not be until 1.5.11 is released. Also when we look at the statistics not many people are installing FOG with Centos anymore. Market share wise of the (RHEL variants) centos 7 is still the leader. On a total market share side, most people install FOG on debian or ubuntu now.

@einsteinagogo I removed the storage node, and included it in a new storage group Test, and removed it from the Defaults, but the Task still complains about updating database.

Hi,

Any ideas ?
I saw in DB that even if task manager is empty in web UI, the 2 tabels “tasks” and “snapins tasks” are still containing data…
And if I launch several deployment tasks with the associated snapins, either the snapins do not appear at all (empty web ui), or they are offset (see picture)
snapin.jpg

If my database is broken, is it possible to recreate a new empty one and import some important tables ?

Thans,
Matthieu

If you get this error after renaming an image (eg: from SUMMER22-Blah to Summer22-Blah) on the web-based interface, the solution is to log in to fog via ssh & rename the image folder itself in /images.:
$ mv SUMMER22-Blah SUMMER22-Blah2
$ mv SUMMER22-Blah2 Summer22-Blah

out of context post. Post in reference to this thread: https://forums.fogproject.org/topic/16108/lenovo-thinkstation-p340-tiny-not-conected-to-fog-server?_=1656514236859

Is your fog server on the same IP subnet as the pxe booting computer?
If Yes, then lets execute this tutorial to capture what the dhcp server is telling the target computer. https://forums.fogproject.org/topic/9673/when-dhcp-pxe-booting-process-goes-bad-and-you-have-no-clue

Post the pcap to a file share site like google drive, etc. Share as public with link. Either DM me the link using FOG chat or post the link here and I will look at the pcap.

@einsteinagogo Compiling iPXE binaries trusting your SSL certificate…

failed on the last server build!

Hello

I had a problem when deploying an image with the FOG

Error message :

read ERROR: No such file or directory
Args Passed: /images/<image>/d1p2.img /dev/<disk>*

For me, it was a problem of user rights on the FOG

Before :
drwxrwxrwx. 2 root root 190 Jun 29 15:07 <image>

After:
drwxrwxrwx. 2 fogproject root 190 Jun 29 15:07 <image>

I had to do a “chown” on my image folder in the /images directory to add the owner to “fogproject”

When creating a new image in the FOG GUI, the folder rights management is not well handled

Sincerely