I’ve successfully used FOG on :
Intel NUC DBN2820FYK
Intel NUC D54250WYB
Programming the BIOS on either is tricky, especially for the first one. I used both in legacy mode.
For the first unit, after PXE boot/deployment, you MUST turn PXE boot OFF in the BIOS if you want it to ever boot properly again.
Even though both were used in Legacy mode, both still had to have the UEFI settings set. Frankly the BIOSes are bafflingly thought out in reverse and quite annoying.
The point is, in earlier svn (eg: 2961) this was not an issue. At least not that I noticed or recall.
The following entries containing an apostrophe in the Advanced Configuration Options custom text:
[CODE]
:MENU
menu
item --gap – --------------- Advanced Menu ---------------
item DBAN Darik’s Boot and Nuke
item GANDALF32 Gandalf’s Win8PE x86 updated (Win8.0)
item HIRENS Hiren’s Boot CD
[/CODE]
… display as:
[CODE]
Darik's Boot and Nuke
Gandalf's Win8PE x86 updated (Win8.0)
Hiren's Boot CD
[/CODE]
Thanks. This gives me something to chew on.
This is only in theory right now, but it’s what I’m hoping to be the next server deployment, should the pilot work first of course.
As I read the user guide, I interpret it to mean that it can only be done on the same subnet, which is not what I intend.
Concurrently, the instructions are for downstream nodes to simply be local repositories but management and deployment commands are still carried out at the master. This I do not want.
Each server must be master of its own domain. All resources for FOG to operate on their own private subnet, including the management webpage for that server for the technician at that site to use. We don’t want them accessing the master server, but we still want them to be able to make their own images on their Fog server (saving them to their own 3=other drive/group/node)
Please enlighten me. I’m not having a good day rtfm on this one.
It is running in Hyper-V, but I’m not replicating the Hyper-V Server or the machine. Neither of which would perform what I want.
Mirroring the images is easy in so many ways, it’s having to manually remove/add/edit the image definitions on each subsequent downstream fog server that is the problem.
I want to replicate that specific image repository only AND alter the image definitions on the destination server without affecting anything stored on any destination server’s 3 drive and its associated image definitions.
eg:
Master Server
2= 12 images (newly changed)
3= 20 images
image definitions total= 32
Destination Server
2= 16 images (old)
3= 2 images
image definitions total= 18
Mirroring/Sync occurs …
Destination Server
2= 12 images (newly changed)
3= 2 images
image definitions total= 14
I have an svn3077 Fog server with three HDD setup. 1=OS+Fog, 2=PublishedImages, 3=Sandbox&WorkImages
2 and 3 are on their own separate HDD.
2 is Storage Node “DefaultMember”, Master, attached to storage group “Default” with image path “/images”
3 is Storage Node “other”, not master, attached to storage group “Other” with image path “/other”
I have several other Fog servers, each on their own subnet; each with their own PXE, DHCP etc, to be set up identically.
I want to keep a live mirror of the master server’s 2=PublishedImages and the associated image file definitions on all the other servers.
I’m not sure Fog can do this or how to do it if it can. According to a thread from August 2014 my best bet is to cron or manually rsync, then manually alter the image definitions on each server.
Am I wrong? Can Fog do what I want?
Installing package: mysql-client
dpkg-query: no packages found matching tftpd-hpa
Installing package: tftpd-hpa
dpkg-query: no packages found matching tftp-hpa
Installing package: tftp-hpa
dpkg-query: no packages found matching nfs-kernel-server
Installing package: nfs-kernel-server
dpkg-query: no packages found matching vsftpd
Installing package: vsftpd
Skipping package: net-tools (Already installed)
Skipping package: wget (Already installed)
dpkg-query: no packages found matching xinetd
Installing package: xinetd
Installing package: sysv-rc-conf
Skipping package: tar (Already installed)
Skipping package: gzip (Already installed)
dpkg-query: no packages found matching build-essential
Installing package: build-essential
Skipping package: cpp (Already installed)
Skipping package: gcc (Already installed)
Skipping package: g++ (Already installed)
dpkg-query: no packages found matching m4
Installing package: m4
dpkg-query: no packages found matching htmldoc
Installing package: htmldoc
dpkg-query: no packages found matching lftp
Installing package: lftp
Skipping package: openssh-server (Already installed)
dpkg-query: no packages found matching php-gettext
Installing package: php-gettext
dpkg-query: no packages found matching php5-mcrypt
Installing package: php5-mcrypt
dpkg-query: no packages found matching php5-mysql
Installing package: php5-mysql
Confirming package installation.
Checking package: apache2…OK
Checking package: php5…OK
Checking package: php5-json…OK
Checking package: php5-gd…OK
Checking package: php5-cli…OK
Checking package: php5-curl…OK
Checking package: mysql-server…OK
Checking package: mysql-client…OK
Checking package: tftpd-hpa…OK
Checking package: tftp-hpa…OK
Checking package: nfs-kernel-server…OK
Checking package: vsftpd…OK
Checking package: net-tools…OK
Checking package: wget…OK
Checking package: xinetd…OK
Checking package: sysv-rc-conf…OK
Checking package: tar…OK
Checking package: gzip…OK
Checking package: build-essential…OK
Checking package: cpp…OK
Checking package: gcc…OK
Checking package: g++…OK
Checking package: m4…OK
Checking package: htmldoc…OK
Checking package: lftp…OK
Checking package: openssh-server…OK
Checking package: php-gettext…OK
Checking package: php5-mcrypt…OK
Checking package: php5-mysql…OK
Configuring services.
What is the storage location for your images directory? (/images)
Setting up fog user…OK
Setting up and starting MySql…OK
Backing up user reports…OK
Did you leave the mysql password blank during install? (Y/n) n
Please enter your mysql password:
Please re-enter your mysql password:
Setting up and starting Apache Web Server…OK
Changing permissions on apache log files…OK
Downloading kernels and inits…OK
You still need to install/update your database schema.
This can be done by opening a web browser and going to:
[url]http://172.19.244.13/fog/management[/url]
Press [Enter] key when database is updated/installed.
Visiting [url]http://172.19.244.13/fog/management[/url] to click on Install results in:
Install / Update Successful!
Click here to login.
The following errors occured
Update ID: 162 - 0
Database Error:
Can’t DROP ‘stID’; check that column/key exists
Database SQL:
ALTER TABLE fog.snapinTasks DROP INDEX stID
Update ID: 162 - 1
Database Error:
Can’t DROP ‘stID_2’; check that column/key exists
Database SQL:
ALTER TABLE fog.snapinTasks DROP INDEX stID_2
Update ID: 162 - 2
Database Error:
Can’t DROP ‘stJobID’; check that column/key exists
Database SQL:
ALTER TABLE fog.snapinTasks DROP INDEX stJobID
Update ID: 162 - 3
Database Error:
Can’t DROP ‘stJobID_2’; check that column/key exists
Database SQL:
ALTER TABLE fog.snapinTasks DROP INDEX stJobID_2
Update ID: 162 - 4
Database Error:
Can’t DROP ‘stJobID_3’; check that column/key exists
Database SQL:
ALTER TABLE fog.snapinTasks DROP INDEX stJobID_3
Virgin install to a fresh Ubuntu 14.04.2 .
Checked out revision 3077.
Ubuntu
< snip >
Here are the settings FOG will use:
Base Linux: Debian
Detected Linux Distribution: Ubuntu
Installation Type: Normal Server
Server IP Address: 172.19.244.13
DHCP router Address:
DHCP DNS Address:
Interface: eth0
Using FOG DHCP: 0
Internationalization: 0
Image Storage Location:
Donate: 0
DHCP will NOT be setup but you must setup your
current DHCP server to use FOG for PXE services.
On a Linux DHCP server you must set:
next-server
On a Windows DHCP server you must set:
option 066 & 067
Option 066 is the IP of the FOG Server: (e.g. 172.19.244.13)
Option 067 is the undionly.kpxe file: (e.g. undionly.kpxe)
Are you sure you wish to continue (Y/N) y
Installation Started…
Installing required packages, if this fails
make sure you have an active internet connection.
Okay, who forgot to feed the gerbil?
[url]https://svn.code.sf.net/p/freeghost/code/trunk/[/url] is down for the count.
bzImage
bzImage32
init_32.xz
init.xz
… are coming down as 635 bytes.
You could roll back to an earlier known-good SVN in the meantime.
In about a month’s time or so this whole conversation will be moot for me as I’ll be replacing the images with updated recipes captured via PartClone.
If there is a bug and a solution I’m trying to find it not for my sake. I’ve already instructed our techs to use QuickImage and unicast in the meantime.
If the PartImage-captured PartImage-deployed image has a sector problem when multicast, then would it not also be corrupt when it is unicast?
Aggressively zero’ing the drives prior to PartImage Multicast results in the same.
Interestingly, interrupting a PartImage-multicast session will corrupt the drive similarly to the point where FOG will refuse to work with that drive until it is re-zero’d.
Uptime is fun, but our FOG servers aren’t mission-critical. They are restart once a month along with patch and app upgrade installations.
These images were uploaded under Partimage and are PartImage images as created via an older FOG version (probably 0.32). They unicast as PartImage. The FLAG has been set since it was first available in 1.0.0 or whatever.
The PartClone image was created 5 months ago, with whatever version of PartClone was in FOG at that time.
By quoting from that article, if you are categorically saying the PartImage images cannot be multicast with the current FOG, then could you please update that article to say that in no-uncertain terms?
Alrighty then. My first test with Multicasting a PartClone image succeeded. Any PartImage image continues to fail and fubar the HDD.
Testing continues …
Multicasting does transfer the image. Data transmission and HDD writing does occur.
At first restart, before even attempting to boot from the HDD, I’ve booted to GParted and that’s where I see the imaginary partition table, instead of what should be there.
The images tested are indeed set to PartImage. I will test with a PartClone image shortly.
This server is running SVN2876 with iPXE 1.0.0+ (d38b) . It has never been 0.32 or 1.2.0, it was originally installed as SVN 2331 I believe, and updated maybe four times to land now at SVN2876.
Looking at the trunk.tar … I see that the ipxe files come with. ( fog_trunk\packages\tftp\ ).
You are forcing auto-download of the latest bzImage files when a new server is installed, but you do offer the means to download any bzImage kernel the user later desires from the FOG menus. Would you consider building in the ability to allow to change the iPXE files post-install as well? They too have versions.