@tom-elliott It does, this was incredibly helpful thank you.

@salted_cashews said in Is a direct upgrade possible in this scenario while retaining all previous configurations and images?:

To be honest, I’m not 100% sure how our guy knew that was causing a problem.

People with even some Linux experience normally check free space as a first-step in troubleshooting. Glad you got it figured out.

@adrien17 I sent you a chat message earlier with some further debugging information. You should be able to see it in the little chat button next to your profile picture on the top navbar.

@sebastian-roth
The dhcp-10-8-34-106 is what Debian auto set as my host name when it auto-configured on my Internets dhcp when i installed Debian.

As for the stated fix below i got to the "Configuring dhcp… " in the last step of fog install and then it says Failed! and sends me back to the command line.

I am going to attempt a fresh install and see if it does it still… It no longer gives me a No address or No DNS it just gets past that step then says failed when configuring the dhcp.

I had a similar issue, but (dumb) lucked into a solution.

Dell Optiplex 3040, BIOS set for UEFI: Onboard NIC (IPv4) first, Windows Boot Manager second.

Installed Win10 Enterprise from USB. After the install and first time on the desktop, before installing anything else, a reboot would come out of the UEFI network boot with Preparing for Automatic Repair. (I gave it plenty of time — about 14 hours! — never got past that screen.) I installed again and got the same results.

I made one change in the BIOS: added a check to ‘Enable Attempt Legacy Boot’ and then installed again. This time, at the first reboot, the screen went dark and … nothing. Manually powered off and back on and was able to log into Windows. But the next reboot, again the screen went dark and stayed that way. So I removed the check from ‘Enable Attempt Legacy Boot’ and now Win10 is working fine, normal reboots, exiting from the UEFI network boot into Windows.

Hope that might be helpful to someone.

@sebastian-roth I forgot to mention, since I only saw it once, but on one of the startups with REFIND_EFI selected and before changing “scan_delay” to 0 the computer attempted to boot into “automatic repair” mode but froze on the screen. After rebooting the PC I wasn’t able to reproduce that.

@Tom-Elliott, I imagine the situation is “you’re damned if you do and damned if you don’t”. It will fix some and break others. However, having the option in the GUI would be useful.

We figured out the problem and got it running properly now thanks though.

@tom-elliott Hi Tom, sorry for the late answer, yes that sql statement solved my issue. Solved!

UPDATE globalSettings
SET settingCategory=‘FOG Boot Settings’
WHERE settingKey
IN (‘FOG_ADVANCED_MENU_LOGIN’,‘FOG_EFI_BOOT_EXIT_TYPE’,‘FOG_PXE_MENU_TIMEOUT’,‘FOG_PXE_MENU_HIDDEN’,‘FOG_PXE_ADVANCED’,‘FOG_KEY_SEQUENCE’,‘FOG_NO_MENU’,‘FOG_BOOT_EXIT_TYPE’,‘FOG_PXE_HIDDENMENU_TIMEOUT’,‘FOG_IPXE_MAIN_COLOURS’,‘FOG_IPXE_MAIN_CPAIRS’,‘FOG_IPXE_MAIN_FALLBACK_CPAIRS’,‘FOG_IPXE_VALID_HOST_COLOURS’,‘FOG_IPXE_INVALID_HOST_COLOURS’,‘FOG_IPXE_HOST_CPAIRS’,‘FOG_IPXE_BG_FILE’);

@george1421 helped out with sorting the command 😉

@culture20 FWIW, The developers put this document together a while ago. https://forums.fogproject.org/topic/6162/firewall-configuration

There is also guidance on selinux: https://forums.fogproject.org/topic/6154/selinux-policy

I have not heard of any issues having ipv6 enabled with FOG.

@brendojohnso The message is clear, the file system is not safe to mount. Look over this article and you should be able to fix it: https://wiki.fogproject.org/wiki/index.php?title=Windows_Dirty_Bit

@george1421 It is that model. And I am using 1.4.4 Fog (noticed there is 1.5) I honestly spaced checking the firmware I did see a 2013 date for it though which might be the issue. I work for a small company it is just a clients computer so I may see one again I may not kind of thing. If I get another one I will have to check the firmware I think you probably on to something. Thanks for the help again @george1421

@george1421 I just verified, that line is indeed in my fog.conf file. If you look through the code that is posted on that particular thread, the change has already been made in the code that is posted. But, I did open the file on my server just to verify. Like i said, it is correct.

@zago123 What exactly did you change. Other users might come across this and hope to find your answer.

@Kagashe Please post a picture of the error so we see what is actually going wrong.

Another question in addition to George’s:

Look in the fogsettings file: cat /opt/fog/.fogsettings and look for the field called username. What is it set to?

This username is the only account that FOG will set the password for. The default is fog.

Generally, users of FOG are quite notorious for setting up the OS with an account called ‘fog’ even though every relevant wiki article and every thread on the topic advises against it. Don’t know why really, I guess the universe wants it that way.

References:

https://wiki.fogproject.org/wiki/index.php?title=Password_Central https://wiki.fogproject.org/wiki/index.php?title=.fogsettings

@chris-whiteley Why not just put a fog storage node on the other side of the link. Then you wouldn’t run the risk of over committing your WAN. You can define a specific replication bandwidth. That IS something that fog can manage. You could even use an older dual core desktop computer as a FOG storage node. FOG Servers don’t need a lot of resources.

@wayne-workman it’s alright… Close this one please. Thanks.

@msi said in Snapin not running:

I checked the port 445. its open.

Then it’s likely just a DNS configuration issue: if the FOG server can’t resolve hostnames, then it can’t ping them. If you’d like help with that please open a new thread, though this is ultimately not a FOG issue, so it may be best to search other resources on how to configure DNS (assuming this is the issue).

ty solved

@x23piracy this is correct.