@sami-blackkite Looks like you’re on the dev branch, which is good. Updating is always a good first step in troubleshooting stuff like this in case it’s already fixed.
I’m not seeing anything in the commits (https://github.com/FOGProject/fogproject/commits/dev-branch) that actually looks related since the version you’re on, but sometimes a refresh still helps.

I took a look at the default settings of a new image and it’s close to what I use, only difference is I set compression to 11.

Are you familiar with a debug capture/deploy task? If not, simply check the ‘debug task’ checkbox when queuing up the capture task. It allows you to step through the capture process and you can catch any messages that might be telling us why it’s behaving odd. Just use the command fog once it’s booted up and ready to start the image and you’ll hit enter for each step. You can also set it up to watch it and step through over ssh if you want by, before running the fog command, getting the ip address with ifconfig and then setting a password with passwd then you can ssh into the debug session from your workstation with ssh root@ip.add.re.ss then the password you set. The password will only exist for that session on that machine. SSH just makes screenshotting and or copying any error messages to share here a bit easier.

@Lukaz You could try doing a post download script that takes the hostname you set for that fog host and put it in the /etc/hostname file.
I think there may be other locations that hostnamectl sets on newer linux builds, but this could still work.

I haven’t done a linux post download script but you can see some other examples in these posts, mostly windows based, but I’m sure we can apply the idea to linux without too much trouble. Just gotta mount the client disk in FOS (Fog operating system that you boot into over the network for the imaging process) after imaging is done and inject the fog hots hostname variable (not sure what the var name is off the top of my head) into /etc/hostname on the client. It’s a bit of work initially, but once setup should just work from then on.

https://forums.fogproject.org/topic/8889/fog-post-install-script-for-win-driver-injection?_=1682187993801

https://forums.fogproject.org/topic/7740/the-magical-mystical-fog-post-download-script

@sami-blackkite That’s the right option.
What version of FOG are you on?

@TanguyPSV I would suggest giving the dev-branch a try. See the “choosing a fog version” of this page.
https://docs.fogproject.org/en/latest/install-fog-server

Running the installer on the current server will upgrade your instance without losing the db. This will get you to the latest and greatest version.

@GlaDio Check out https://docs.fogproject.org/en/latest/storage-node

Your existing fog server will manage the database. You can set up your NAS as a storage node or a separate server as a storage node by running the fog installer in storage node mode on that server.

Then you can set an image to be synced between the main server and the node or set an image to only be stored on the node and clients will boot to the fog server which will point them to the storage node to download the image.

@GlaDio Now I could be wrong about this but I don’t think this is how you want to go about this.
Maybe if your NAS can do iscsi you could do that as it would appear more like a real disk but because you would have a file share for what is also a file share you’ll probably run into problems. The client will try to mount the /images share from fog but even if it is successful, that client won’t in turn be able to chain to the next file share. Even if that did work, you’re adding another link in the chain during imaging that could be unreliable.

I believe there’s some old guides around on setting up a NAS as a storage node. It’s much better to have a full linux server where you can install fog as a storage node, but technically speaking it can be made to work by simply having an NFS share to point to as a storage node. Here’s one from the wiki that hasn’t been converted to the new docs site just yet https://wiki.fogproject.org/wiki/index.php?title=NAS_Storage_Node

I would suggest going that route instead. I’ve tried to make sub directories of the /images folder that are share paths (like for drivers for driver injection) but found that clients couldn’t get to them after mounting the /images share and I believe you’d run into the same issue.

All that said, if you want to continue down this other path the permissions probably need to be set on the NAS first then on FOG. There’s also probably some special nfs mount parameters to make it read/write and to allow permission changes to traverse.

@GlaDio Can you give the full error?
And can you also give us the output of

ls -l /images

Also, what exactly are you trying to configure? Are you wanting to set up a separate storage node on a NAS? Are you trying to mount an nfs share on the fog server that you’re hoping will then mount to clients via the fog server? Are you trying to move the /images directory from the server to a NAS?

@SOSF2 Oh good.
Just re-read some of your post and I have more questions

Why did you move /images to the home path? I suppose it should work as long as the /etc/exports file on the server is exporting that path as an nfs share and that path has the proper permissions (which I see it does).

What does /etc/exports say on your server?

@SOSF2 Check out this doc https://docs.fogproject.org/en/latest/change-fog-server-ip-address there are a few other places you need to make changes

@cornycopia Hi!
Are you familiar with powershell at all? If not, it’s too hard to learn,
I have made a powershell module to help with managing these things (see my signature for more links)

For example there’s a command to make a new fog host https://fogapi.readthedocs.io/en/latest/commands/New-FogHost/
I would recommend giving that a go.

That said, let’s take a look at why this isn’t working

The first issue I see with your body is the macs need to be an array
You might also have to have the modules param defined in the body.
In my PowerShell function I have a function to get all the modules and I filter it to the default ones so that the behavior is the same as when you add a host in the gui instead of creating a host with nothing in it.
https://fogapi.readthedocs.io/en/latest/commands/Get-FogModules/

Here’s a simplified table of that output, I think the ids are always the same in all installs, but they could be unique to your install

id name
-- ----
1  Directory Cleaner
2  User Cleanup
3  Display Manager
4  Auto Log Out
5  Green FOG
6  Snapins
7  Client Updater
8  Host Registration
9  Hostname Changer
10 Printer Manager
11 Task Reboot
12 User Tracker
13 Power Management

Anyway, here’s an example of a json body for creating a host with the default service modules enabled (these are my defaults, you may have different ones configured)

{
  "macs": [
    "A4:BF:01:6E:E4:F2"
  ],
  "name": "demo",
  "modules": [
    "7",
    "9",
    "13",
    "6",
    "11",
    "2",
    "12"
  ]
} 

@cul3r0 The https redirect is actually only working for me if I go to the fqdn on http, i.e. http://fog-server.domain.tld will redirect to https but http://fog-server will not redirect.
I’m pretty sure it’s possible to adjust the rules to redirect everything to the fqdn on https. You can probably mess with the rules to make it rewrite anything to go the the fqdn on https

@JJ-Fullmer I captured an image from the surface go 4 with the new kernel that has UFS support and I was able to deploy that image with its 4k block based partition table without issue.
Of course that image can now not be deployed on 512e block based disks.

If I ever get the time, I may try testing manipulation of the parition blocks and using an efi tool in a fog post install script to make it so an image can be deployed to either but its probably unlikely to be possible.

For reference, here’s what the 4k block based partitions look like

d1.partitions

label: gpt
label-id: DEECB42F-8F01-49B9-85BE-8398A932E4E5
device: /dev/sda
unit: sectors
first-lba: 6
last-lba: 31246330
sector-size: 4096

/dev/sda1 : start=         256, size=       76800, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=FE5BA595-3498-4D4A-B741-9EB5D84C1EA5, name="EFI system partition", attrs="GUID:63"
/dev/sda2 : start=       77056, size=        4096, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=752C5B50-96B7-4130-9789-9A02B05F8A75, name="Microsoft reserved partition", attrs="GUID:63"
/dev/sda3 : start=       81152, size=    31024716, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=C088525B-56B9-4D7E-A040-1C8F5A782ADC, name="Basic data partition"
/dev/sda4 : start=    31106048, size=      139776, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=E2B6791E-DC55-4039-A658-9007B5749FEE, attrs="RequiredPartition GUID:63"

d1.minimum.partitions

label: gpt
label-id: DEECB42F-8F01-49B9-85BE-8398A932E4E5
device: /dev/sda
unit: sectors
first-lba: 6
last-lba: 31246330
sector-size: 4096

/dev/sda1 : start=         256, size=       76800, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=FE5BA595-3498-4D4A-B741-9EB5D84C1EA5, name="EFI system partition", attrs="GUID:63"
/dev/sda2 : start=       77056, size=        4096, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=752C5B50-96B7-4130-9789-9A02B05F8A75, name="Microsoft reserved partition", attrs="GUID:63"
/dev/sda3 : start=       81152, size=    31024716, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=C088525B-56B9-4D7E-A040-1C8F5A782ADC, name="Basic data partition"
/dev/sda4 : start=    31106048, size=      139776, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=E2B6791E-DC55-4039-A658-9007B5749FEE, attrs="RequiredPartition GUID:63"

Something odd is it doesn’t look like the main OS partition (sda3) shrunk, but it for sure did as it is only 10.56 GB on the server (compressed size) and deploys around 20 GB on the client, same size as the VM based 512e image.

@AlleneBrick @alexamore90
Lets clarify further first.

What DHCP server are you using and what is its ip?
What do you want the fog server ip to be?

@alexamore90 I’m not sure where you are wanting to change your ip.

Is fog your DHCP server?
Are you needing to change the ip of the Fog Server?
Did you change or add a different DHCP server on this new ip?
If it’s a new DHCP server, have you pointed option 66 to fog? (https://docs.fogproject.org/en/latest/installation/network-setup/dhcp-server-settings/)

@FRG You can specify the disk to image to in the host settings screen with the host primary disk field

By default Fog will use the first disk it finds (I believe) or you can specify per host.
i.e. if you wanted it to image to a second disk you could specify /dev/sda2 or /dev/nvmen1n1

@cul3r0 It does not, that configuration is elsewhere. If you enabled https support at install then you have to do something special to get that disabled for pxe because it embeds the self-signed cert made at install into the on-the-fly pxe compilation process.

@ksrvpvl Ok, I think I’m getting what you’re saying. I misunderstood earlier.

Is your custom menu option to boot to winPE working? Or are you asking for help with that part too? There is some very basic guidelines on creating a winpe boot option here https://docs.fogproject.org/en/latest/ipxe

The plugin system needs to be enabled in the fog settings, then you should see a plugin menu where you can activate and then install the tasktypeedit plugin. Some basic plugin system info is here https://docs.fogproject.org/en/latest/plugins but it looks like you got past that bit now.

I also found this post https://forums.fogproject.org/topic/10274/creating-task-with-tasktypemanagement?lang=en-US&page=1 where someone was doing the same thing. Perhaps it may offer some help.

It’s looking like I have to find a way to either capture the image or a separate image from a device that defaults to 4k logical sectors or a way to force the device to change sector size to 512 when deploying a 512e based image

I tried hdparm but got this error

hdparm --set-sector-size 512 --please-destroy-my-drive /dev/sda

/dev/sda:
READ_LOG_EXT(SECTOR_CONFIGURATION) failed: No such file or directory

I also tried capturing the image using the new kernel on the off chance that would make a difference, but no good.

I guess I will have to try making an image from a 4k native device since it’s not being changed?

@Sebastian-Roth or @Tom-Elliott any chance you have some time to help me out with this issue?
It’s looking like its a 4k block issue.
I was trying to find a formulaic way to change the partitions files to line up to the 4k layout, like dividing by 8 and some other tweaking as needed but found it more complicated than expected.

Any ideas?

The image did complete but it did not boot into Windows. Looks like I need to embed the storage controller driver for UFS.

Or it could be a 512b vs 4k block disk type issue.