Thanks it saved my day.

@jonathan-cool Fun fact … : if i check this option, the speed deploy is “normal” BUT the post deploy result of a beautiful BSOD … “INACESSIBLE BOOT DEVICE”.

If i go back to the BIOS and uncheck this feature, the SYSPREP works …
So … slow speed or BSOD ? The choice is hard … !

@renanrenan Well now start the debug capture by hitting ENTER twice, then run the command fog to start off and go ahead confirming every step via ENTER.

@dejv said in cannot find disk on system (getHardDisk):

we still need to change to ahci?

Yes this is an Intel and Linux kernel developer issue. There is no resolution at this time.

@Pilar Well the issue this topic is about was solved. May I ask you to open a new topic for this new question. We try to keep things sorted so other people will find information and help more easily.

In that new topic post a picture of the settings you changed to move the image storage location as well as a picture of the error when capturing an image. We’ll tell you what’s missing.

@sebastian-roth this was before i figured out how to view my open forums. I apoligize , please delete or ignore or mark skip. Thank you

@sebastian-roth said in Setting up trusted SSL certificate:

One more thing I missed to tell you. In case you want to use the fog-client software as well you will run into issues with your custom certificate. If you need to know more about this, I can give you the details.

i’d love to know more details about this. Thank you.

@nockdown said in Error(5): Could not map attribute 0x80 in inode 23779: Input/output error:

As I understand this option impacts to partition shrinking and so to image size. Am I right?

Yes. Although it’s probably increasing the size of the image files on the server only by a fraction. Not to worry about I reckon.

@epix Yeah I’ve never seen that wiki instructions. My setup was done ignorant of the settings in that document.

Just be aware that using a windows server as a storage node is not supported by the FOG developers. That doesn’t mean it won’t work but windows servers were never tested and approved by the developers. But neither is using a NAS but that works too.

@george1421 well… i figured it out… 😥
one of my old servers suddenly booted up without me noticing, with another fog sever and it seems that is used that one instead of my current one. sooooo… i’m sorry for wasting your time!

@ombreit It would be a bit more helpful to see the complete command. But it appears your /images/ImgWin10 directory is empty. Did you capture a golden image to this directory before you tried to deploy?

@t_dashs Right you can do that by typing in the IP address of your fog server. But the root of the problem is that you have at least 1 dhcp server not handing out the complete information. Understand this is an network infrastructure problem not specifically a FOG issue.

If you have a computer loaded with wireshark on the same subnet as the pxe booting computer we might be able to find out which one is wrong. You will want to use a wireshark capture filter of port 67 or port 68 Start the wireshark capture then pxe boot the target computer til you get this error. Stop wireshark from scanning. In the data area you will see a discover package sent from the target computer and one or more OFFER packets. The problem lies in one of these offer packets. Either the next-server or dhcp option 66 is not set on the offending dhcp server.

@nick So the next thing I would do is to update the firmware on the mobo just to be sure that isn’t it.

Then try the snponly.efi boot loader. You will need to update your dhcp server for this. The snponly.efi boot loader uses the driver built into the uefi nic. Its akin to undionly.kpxe for bios. The ipxe.efi boot loader is more like a linux kernel in that it has all of the common and known drivers built in, most but not all.

If that fails then here is how to build the latest version of iPXE. Note the build number on your current version of iPXE. Its the hex characters in the brackets after the version number. https://forums.fogproject.org/topic/15826/updating-compiling-the-latest-version-of-ipxe

If this doesn’t work then we will need to get wireshark on a witness computer (second computer on the same subnet as the pxe booting computer). This is a bit more involved so lets start the easier stuff first.

@george1421 said in MySQL issues after new installation:

The default was changed in FOG 1.5.8 or 1.5.9 I think. But that would be only for a new install. The fog installer does not change the table configuration during an upgrade.

I might be wrong here but I don’t think it is yet. @Tom-Elliott ?

@sebastian-roth Correct

@pilar said in I can NOT access the website:

/dev/sda4 352G 19G 315G 6% /bkupFOG

Ok what is this partition?

Will you show me the output of this command
ls -la /bkupFOG

What I’m thinking is that we move the contents of /images to this partition then mount /dev/sda4 over the top of /images. That will give you space and keep from /images from filling up your file system. Don’t do anything yet, lets make sure we understand your current landscape on the server.

@george1421

I just tried another capture after changing the FOG client on the image to point to our FOG server in Germany. This time there was a normal 1 minute pause during the resizing process then Partclone G-zip started and imaged without problems. All seems normal again…gremlins have been eradicated. You can mark this as solved.

@chuck2000 We have see this before when you do an in place upgrade of windows, it seems to leave a shattered hard drive for some reason. Well done getting it worked out.

@cul3r0 In this topic the issue is very likely due to a custom CA and certificates. When FOG generates self signed certs for you it’s usually working out of the box if you don’t mess with it.

As every case is different I may ask you to open a fresh new topic on your own. Link to this one as reference but then more important give us your details, like FOG version, custom modifications and so on.

@george1421 said in User Tracking search not working:

little gear on original post

I see no gear or settings on the original post, leading me to believe this is a moderator-only feature. Thank you for marking the solution!