@watson you just need to elevate your privileges to edit the file. what do you mean you lost the images?

@ty900000 you mentioned that it was “a while back” that you set up the server. what version of fog are you running? you may not have the new options available.
i don’t recommend raid 5. most people won’t these days. the exact setup of your storage is entirely up to you, your need, and your budget.

@wanderson fog 0.32 was released in 2011. i’m afraid none of us know how to support it. it may be time to upgrade or migrate to a new install of fog. there have been far more than enough improvements to be worth it. your existing images will be compatible with the latest version of fog (as legacy images. if you migrate to a new server instead of upgrading a few setting will need to be set to recognize them properly, but they will work)

@FeasiblePear the boot menus are ipxe based. updating those files may solve your problem. i recommend updating to the latest stable, or latest RC release for the lastest bug fixes, feature additions, and improvements. (the new zstd compression alone is probably worth the update for a lot of people)

@keith75140 well, it was released 6 days ago. we don’t know of any issues (because nobody’s tested it yet, that we know of). if you find any, let us know.

@keith75140 there’s https://wiki.fogproject.org/wiki/index.php?title=Using_FOG_with_an_unmodifiable_DHCP_server/_Using_FOG_with_no_DHCP_server
or you can use https://wiki.fogproject.org/wiki/index.php?title=USB_Bootable_Media which is targeted at UEFI booting, but you can modify the steps for legacy booting alternatively (use undionly.kpxe instead of ipxe.efi )

@keith75140 there are a few ways you could use a usb or cd boot media to bypass the need for the DHCP options if you’re doing very low volume or just trying fog out, but if you intend to use fog much, you’ll want to have those options set.

@keith75140 fog is a network based imaging solution, maybe it’s not what you’re looking for.

have you made sure to set your DHCP options 66 & 67 appropriately?

@alh the user list shows this, i believe

@george1421 ah, that’s right. i forgot about that. that would make his version a month or two before the first 1.3.0 RC build. there shouldn’t be any problems with upgrading that.

@hernani the latest development version is 6069, so i’m sure you have the version number wrong, but if the version you have is older than the current stable release, you can upgrade to it.

@dwagner sounds like you need to recreate the /images/dev/postinitscripts directory, and it’s contents, a single file named “fog.postinit” with the contents

#!/bin/bash
## This file serves as a starting point to call your custom pre-imaging/post init loading scripts.
## <SCRIPTNAME> should be changed to the script you're planning to use.
## Syntax of post init scripts are
#. ${postinitpath}<SCRIPTNAME>

permissions 777
also, you’ll need to create an empty file named “.mntcheck” in /images/dev too, if you haven’t

unless you’re specifically testing the ipxe boot file, you can just set up a line in the default.ipxe file like this

:bootme
# redirected to dev server for test environments
##test-computer 
iseq ${serial} F8HLK02 && chain http://test-server/fog/service/ipxe/boot.php##params ||

# normal fog server
chain http://normal-fogserver/fog/service/ipxe/boot.php##params

it looks like it made it from the first partition /dev/sda1 to the second /dev/sda2 this time, but are you certain there’s nothing wrong with the drive?

@John-L-Clark i would try running a chkdsk /r on all of the partitions so that it does and try again

@John-L-Clark does the computer run a checkdisk on startup when you boot it again?

@John-L-Clark this doesn’t look like a checkdisk issue. the reason the disk isn’t clean is because the computer is shutdown in hybrid mode instead of being cleanly shutdown. try using from an elevated command prompt “shutdown /s”

you re-issue certificates to the clients by using the “reset encryption data” button. you can apply this to single hosts or to groups.

@george1421 if he’s only got a 100Mbit connection, zstd might actually be faster on the upload too, since the bandwidth will be the major bottleneck, not cpu utilization.