Posts made by Sebastian Roth

@davido38 Well it looks like the user entry was dropped from the database. You should be able to recreate it:

INSERT INTO users VALUES (0, 'fog', MD5('password'), '2023-01-26 01:33:07', 'fog', 0, '', 0, '');

@Scootframer Don’t think the G9 has been discussed in the forums much yet. But there is a history for the other models:
https://forums.fogproject.org/topic/15132/hp-probook-640-g8-imaging-extremely-slowly
https://forums.fogproject.org/topic/15623/partclone-freezes-or-crawls-after-kernel-update

My very limited knowledge thinks it’s the Fog Kernel, which hasn’t been updated in a bit, doesn’t have a fully optimized driver? Is there a way around this?

Can’t promise you anything but lets start by gathering some more information to see what can be done. What version of FOG do you use and which FOS kernel version is installed (output of command file /var/www/{,html}/fog/service/ipxe/bzImage* run in the FOG server console)?

@switch_apoc Well, this forum topic is pretty straight forward. Just start reading upwards beginning from this post: https://forums.fogproject.org/post/135069

@lperoma Thanks for the update. Good to hear you found this and were able to fix it. Well done! This is beyond FOG itself and it would have taken a lot of posting forth and back to figure this out for us. Although I don’t know much about virtiofs I can imagine it causing problems when being exported as NFS (as FOG does).

@zaboxmaster Just in case you haven’t found out about post deploy scripts yet: https://forums.fogproject.org/topic/7740/the-magical-mystical-fog-post-download-script

@jmcnamee Did using non-resizable image type get you past that point?

@WT_101 Any news on this?

@thommyf said in SSD Alignment:

when i don’t use the resizable image option i will not be able to install the image to smaller drives , right ?

Correct.

I found a way to correct it.
I changed the starting sector in d1.minimum.partitions and d1.partitions file to a size which can be divided through 4096. Then i get a aligned layout.

Yeah that’s kind of a hack to force the starting sector you want.

Maybe you can change that in a future version as not only ssds need that , newer hdds also need 4k sector size.

Can you please share the contents of d1.minimum.partitions and d1.partitions (original as well as modified version) here in the forums so we know the figures you played with.

@switch_apoc This forum topic should probably help you: https://forums.fogproject.org/topic/14455/storage-group-activity-data-displaying-wrong-information

@lperoma said in KMV installation can not locate images folder upon image deploy or capture.:

https://naks.es/downloads/fog.mov

In this video I see a capture task scheduled in debug mode. Just hit ENTER twice to get to the shell and start capturing by running the command fog. If you don’t want debug capture you should not enable the debug checkbox in the web UI when scheduling the capture task.

https://naks.es/downloads/fog-deploy.mov

This video shows a hanging deployment that seems to be waiting on post init scripts. Please check the following folders on your server to see what kind of scripts you have in place:

ls -al /images/dev/postinitscripts
cat /images/dev/postinitscripts/fog.postinit
ls -al /images/postinitscripts
cat /images/postinitscripts/fog.postinit

Yesterday I tried reinstalling fog to no avail.

Do you still get the exact same error message mentioned in your initial post? I am wondering why we don’t see this in the video.

@kalafina Maybe this is an issue related to 32/64 bit not finding the correct path. See here: https://stackoverflow.com/a/64061675

Use c:\windows\sysnative\uwfmgr.exe…

@lperoma said in KMV installation can not locate images folder upon image deploy or capture.:

did you have the chance to see those 2 videos for capture and deploy ?

Not yet but will take a look and reply today.

@kalafina Make sure to use the full path instead of just uwfmgr…

@thommyf said in SSD Alignment:

But the alignment of partitions is beeing corrupted when restoring images to SSDs.
Is there something i can do ?

Yes, don’t use the resizable image type.

I’m on Version 1.5.9-RC1

As well I suggest you think about updating at some point. Maybe wait for the next official release coming out soon but look into backup and planing the update already.

@kalafina said in issues with the uwf snappin:

the user account on the client PC is the built-in Administrator account,

Well, the fog-client software running the snapins is setup to run as SYSTEM account (Windows service). Not sure if that is causing it to fail?

Do the commands return an output when run in a CMD manually? In any way I suggest you update the uwf.bat to look like this for debugging:

uwfmgr filter enable >C:\temp\uwf.txt 2>C:\temp\uwf_error.txt
uwfmgr volume protect C: >C:\temp\uwf.txt 2>C:\temp\uwf_error.txt

Make sure c:\temp exists!

@tag said in Storage Node Kernels:

I’ve simply copied them from the master node to the node webfolder.

Yes, that’s another way to do it.

@h4x0r101376 It’s not an issue to have different kernels unless devices can’t be imaged correctly on the storage node (if they PXE boot from that node at all). In any case you can download kernels for the storage node manually. Find the binaries on Github: https://github.com/FOGProject/fos/releases

They need to go in /var/www/fog/service/ipxe/ and rename the existing files.

@OlivierSchmitt said in letsencrypt usage after installation:

It was not for use on internet.

How do you get a letsencrypt certificate if the FOG server is not facing the internet? By copying the files from another system?

@OlivierSchmitt The certificate is not only used by the web UI but also when PXE booting and by the fog-client. So copying/moving certificate and key files on the FOG server is not enough! You need to re-compile the iPXE binaries and eventually the fog-client as well or use letsencrypt and self-signed certs in parallel to not break the fog-client communication.

Unfortunately there is no proper documentation we can point you to for this. I started a writeup in the wiki some time ago but never got to finish it. This is mainly due to the fact that few people use custom certs (be it letsencrypt or their own internal CA) und so this is very low on the priority list.

As well I want to point out some security concerns. And I really need to stress this point: FOG was not build with the amount of security in mind that it would need to allow for an installation to be accessable from the internet. Sure you can technically do it but it’s all on your own risk.

So I am wondering if you want to re-think hosting you FOG server to be accessable from the internet? Why don’t you setup VPN tunnels for people to access the FOG web UI from different locations?

@tag Thanks for the update. Great to hear you were able to find and fix the issues. Adding this piece of information to the Wiki is a good idea. Though we are in the process of moving that to http://docs.fogproject.org and I am wondering if have a little bit of spare time to help on this?