I think you might be confusing a few things.

It depends on how you set up your partitions, it sounds like you assigned 10gigaybtes to the root partition.

If so, you can change your image store location to say /home/fog/images instead.

sudo cp -Rf /images/* /home/fog/images/

Then

sudo chown -R fog /images
sudo chmod -R 755 /images
sudo chmod -R 777 /images/dev

Then edit /opt/fog/.fogsettings and change storageLocation to /home/fog/images

Rerun the installer and it should fix everything else. If not, check /etc/fstab and Storage node location.

@killerm Size of HDD isn’t the only factor. The default install might have only given the root partition 10GB for example, and given the rest to /home

Try this command in terminal:

df -h

And paste output here.

@justeverything If the port isn’t open on the host then it can’t communicate, simple as that, to be honest. It’s like trying to call someone who put everyone on a blocklist.

Maybe I’m missing something, but why don’t you just add the NFS share of Windows directly as a storage option? I don’t really see the point in the reexporting, particularily because it doesn’t work by default afaik.

The different color indicates that it doesn’t have the same permissions, specifically this one has less permissions than the others and likely isn’t allowed to be executed with the current permissions.

chmod 777 fog.postdrivers

Should fix the permissions.

That might not be all that’s wrong with it however, did you create this file on Windows?

@Rayco Can you share the PXE boot commands you have?

@srnairn You shouldn’t start dnsmasq by doing “sudo dnsmasq”

Do

sudo service dnsmasq restart

Although that may not be sufficient if you started processes manually, you may have to kill it first.

There should be a button to update the database on the web interface, this should update the relevant tables and it should work fine.

If worst comes to worst and the database is unusable (unlikely), then it’s no problem because you can copy the image folders over and recreate the definitions for them and it will work.

Can you tell us more about the error you got? I’m guessing it’s going to be the Unable to update database one.

I don’t know if this is strictly necessary or even related, but you may have to assign the default storage group for the image definitions.

Click on the image definition, on the left hand side select Storage group, then check the checkbox for your storage group.

Can you try again with image type of Single Disk Multiple Partition ?

And just to verify, you do recapture the image after changing the image settings, correct?

The partclone log would be very useful though, so hopefully you can provide this tomorrow.

I could be wrong, but I get an uneasy feeling whenever someone symlinks to a parent directory. Endless recursive loops come to mind.

Is this hard drive intended as additional storage? (are there images on your current hard drive that will remain there?)

@Joe-Gill Storage nodes are typically used for one of two things afaik, to serve different subnets/physical locations and/or to create a seperate storage group with different images attached to it.

One main FOG server can do basically everything on its own, but of course serving other subnets and what not would be trickier afaik.

Can I ask how you figured out the disk letters were swapped? Please note that in WinPE enviroments (bootable USB, recovery mode, etc) the drive letters aren’t necessarily representative of what it would be if the system itself booted!

Just want to see if we can exclude a possible issue or not.

You can also turn off DHCP config generation by setting bldhcp to 0 in .fogsettings

@Matthieu-Jacquart I find that Windows 10 upgrades mess up sysprep, I’ve made it a habit to just start over every time.

@george1421 More specifically CTRL+C tries to abort the current command/script in terminal, this is also true on Windows. (making it one of the more confusing key strokes)

@Tywyn Would it be possible to provide a screenshot of the client failing to get an IP?

@cojohnson mmcblk is typically an SD card or similar, which is probably why it fails at that point, it runs out of space. Remove the SD card!

I don’t know when/if that scrept got updated. Afaik barely, if at all since 1.2

Recommended ways of updating are use SVN, git or download the compressed file.

I recommend git

https://wiki.fogproject.org/wiki/index.php?title=Installation#Git

@lmioperations installfog.sh takes into account current installations and simply updates to the newest version without changing any settings or the like.

You can substitute dev-branch for master