@george1421 Well progress is good.

I can pxe boot the dell (redhat) kernel with this

Menu Item: os.platformR620
Description: Platform Specific Firmware R620
Parameters:
kernel tftp://${fog-ip}/os/dell/psf620/SA.1
initrd tftp://${fog-ip}/os/dell/psf620/SA.2
imgargs SA.1 initrd=SA.2 root=live:http://${fog-ip}/dellsquashfs.img rootfstype=auto rd.live.image rd.writable.fsimg rw DEBUG=0 share_type=NFS loglevel=7 BUILD=0 selinux=0 edd=off rd.md=0 rd.dm=0 quiet – share_script=drm_files/apply_bundles.sh
boot || goto MENU
Menu Show with: All Hosts

SA.1 and SA.2 to into the /tftpboot path and squashfs.img -> dellsquashfs.img goes into the http root of /var/www/html

It boots but doesn’t complete what is needed. But I have access to the command prompt. Focus is on this parameter now: share_type=NFS

Some searching on the target system shows these options:
2021-07-08 13_40_07-Window.png

Now we know the script that is responsible to making the connection and the values supported for share_type.

looking into the script I see two new clues.

2021-07-08 15_45_16-Window.png

$share_location and $share_opts making an NFS mount.

@scoude said in Modify path /images to /home ???:

Hi everybody,
I have a 1.5.5 Fog version on Debian 9.3. By default, my images storage directory was /images.
And my wish was to put images on new directory /var/images (/var is mount on LVM mapper…).
So here are the actions I done :
1/ create a /var/images directory
2/ set good rights and owner for this new directory (see /images rights)
3/ move all files from /images to /var/images (be careful to move all files : with dot, etc.; ls -la to be sure !)
4/ connect to database with mysql client and change path :
use fog;
update nfsGroupMembers set ngmRootPath=‘/var/images/’;
update nfsGroupMembers set ngmFTPPath=‘/var/images/’;

5/ change path in /etc/exports :
/var/images *(ro,sync,no_wdelay,no_subtree_check,insecure_locks,no_root_squash,insecure,fsid=0)
/var/images/dev *(rw,async,no_wdelay,no_subtree_check,no_root_squash,insecure,fsid=1)

6/ apply nfs changes :
exportfs -ra

That’s all !

This works fine for me.

Thank you.

@george1421 Excellent explanation 🙂 Thanks for the help. I will close the post as resolved I believe it will work 🙂

@rodluz I don’t understand the hiding of private ip addresses, never have and never will. Either way, glad you were able to get this working for you!

@astrugatch Latest laster is 1.5.9 as of now. There have been a fair amount of fixes since then. I would suggest you use dev-branch to make sure you have all those fixes included.

@tom-elliott said in WebGui language will not change:

installlang=1 /path/to/foginstaller/bin/installfog.sh -y

Hello Tom

thank you for your answer. I did what you described. But it doesn’t work. The language cannot be selected. What does “installlang = 1” mean

thanks
Marcel

@sebastian-roth Thanks for the swift response, looking closer at the fog image files this is exactly the file I will need to modify! From our perspective it would be great to have an audit trail for hardware built in to future versions, but I understand if there isn’t much demand for it, though slightly surprised as it seems useful to me for a whole variety of reasons outside of our specific use case (in which it is required!).

@yeet If you look at the very top of that wiki page it actually explains all of the arch types.

Type Architecture Name ---- ----------------- 0 Intel x86PC 1 NEC/PC98 2 EFI Itanium 3 DEC Alpha 4 Arc x86 5 Intel Lean Client 6 EFI IA32 7 EFI BC (EFI Byte Code) 8 EFI Xscale 9 EFI x86-64

Unless you think you might run across 1, 2, 3, 4, 5, 8 you probably won’t need to configure them. FOG Doesn’t have a iPXE boot loader anyway for those arch.

@yuma Misunderstood this as being a tutorial on how to set this up. Somehow missed your question. So moving this topic back to general questions now.

Anyone able to help here? I don’t do much ISO booting stuff.

@Bristow-0 Great work!! Thank you very much for updating all the translations.

@yeet The concepts are covered here: https://forums.fogproject.org/topic/14278/creating-custom-hostname-default-for-fog-man-reg

You will want to edit the fog.man.reg script and comment out the sections you don’t want. It helps if you know linux bash scripting or can follow programming. The idea is for you to make your custom fog.man.reg file then patch FOS Linux every time it boots, replacing the FOG supplied script with your custom script.

You can download the current fog.man.reg file from the fog github site: https://github.com/FOGProject/fos/blob/master/Buildroot/board/FOG/FOS/rootfs_overlay/bin/fog.man.reg

OK @tom-elliott, keep me posted, I’d love to see this site available in French. It looks more serious for the decision makers…

@Yeet The FOG installer doesn’t ask for a DHCP server IP. Though it asks for router/gateway and DNS server IP to be used in the DHCP configuration (if you tell it to enable this service on the FOG server).

@mechalas yes, now it works perfectly. Cool

@sebastian-roth
I figured such. The usb method on my offline imaging switch is redundant since pxe works fine on that. Just would have been nice to be able to image remotely booting via USB, kind of like Acronis+mapping to an SMB share that stores the images. If only my network team would enable tftp/pxe on their dhcp servers. We have it only on our hq subnet but it is being used by SCCM, and SCCM takes a very, very long time to image a PC. We only use it to get a base Windows 10 image and work on it from there, then capture/upload our custom dept images to the FOG server.

@eliphas said in Fog storage node selection by latency instead of load:

Just reinstalled the two slaves today, now they are full servers. Was thinking, if I add the slave1/slave2 as storage nodes to the master1 again, would not the master1 still point the clients to them?

In the above configuration (since they are all now full fog servers) the image raw files will replicate from the master to the storage nodes (full remote fog servers). What will not happen automatically is the image definitions in the database will not be auto synchronized. You will need to do an export using the web gui on the master node and then an import on the storage node to get the image definitions.

Ok now to the clients. Since there is a full fog server at each site, you will have each site configured to talk to its local FOG server. The central server is not in the picture when pxe booting or imaging the remote sites.

@MEIT-TC No, FOG does not keep track of a client’s IP address. While the database actually has a field called hostIP (code ref) this is not being used in the code.

So if you are really keen you could try to work on implementing this.

@chuck2000 said in Failed to get an IP via DHCP:

The image size is 240GB which in nearly the size of the entire SSD

Without looking into this off the top of my head, I would say the source disk was encrypted with bitlocker, so during image capture partclone sees this and does a sector image copy instead of a disk image. You can see this during the blue partclone screen while its running you will see the format as RAW.

@tom-elliott

Are there any plans to make a windows/mac/linux app that would allow FOG images to be mounted and read allowing the user to copy files from an image?

Thanks

@rodluz you can try this, https://forums.fogproject.org/topic/6463/expose-fog-host-and-image-properties-to-post-install-scripts?_=1620751811503 and make a review of host, image and hostinventory items…