Posts made by ch3i

@fl0pp Hi, 10.60.60.24 is the NAS or your FOG server ?

EDIT: It seem to be your FOG Server. You have to configure your storage node with the IP address of your NAS (10.60.60.4), the FTP path (???) and NFS path (/volume1/images).

There are a lot of topic about that and the Wiki : https://wiki.fogproject.org/wiki/index.php?title=NAS_Storage_Node and https://wiki.fogproject.org/wiki/index.php?title=Use_FOG_with_FreeNAS

@boeleke I’m working in a School and use Trunk version Trunk versions of FOG are “stable”.

@boeleke For QNAP the NFS path seem to be : /share/your_nfs_share but for the ftp access it’s /your_nfs_share. In FOG trunk (https://wiki.fogproject.org/wiki/index.php/Upgrade_to_trunk) you can differentiate NFS and FTP path. In your version FTP and NFS path must be the same !

@boeleke FTP and NFS path or the sames on your NAS ?

@Erik-Rafael Which router/switch you use ?

@boeleke Hi, If your NAS is mounted on your FOG server via NFS you can’t re-export it as NFS via FOG server. You have to create a node storage with IP of NAS ans specify NFS and FTP path in the node settings. Before you have to create a user “fog” in your NAS with the same password of the “fog” user of the FOG server.

When you’ll upload/download image on that node (Your NAS) the fog client will connect directly on your NAS not via your FOG server.

@loosus456 Hi, FOG use partclone to backup image, I think there is no way to convert VHD(X) to partclone image. You can check on partclone website : http://partclone.org/

@Nika If you want to do that for each download you can modify the inits to add another wipe tool (dban binary for example) and modify the fog.download in the init/bin/ to execute dban before download the image.

@Nika I don’t understand, what do you want to do ?

If it’s to use the task included in FOG like Capture, Deploye, Wipe, … you don’t need extra scripts.

@Nika Hi, you don’t need no more scripts to do these tasks.

@Sebastian-Roth said:

• You should never use tools like resizefs, gparted or fdisk on your system disk (sda in your case) within the running system!

I use it each time I have to extend partition on linux within the running system (I use snapshot before )

@Tom-Elliott Hi Tom, with your Start/Stop configuration all services work fine. I’ve modify it by hand… I’had understood that you had updated the installer with these settings. You will add these modifications on the installer ?

 * Setting permissions on FOGMulticastManager.service script...OK
 * Enabling FOGMulticastManager.service Service................OK
 * Setting permissions on FOGImageReplicator.service script....OK
 * Enabling FOGImageReplicator.service Service.................OK
 * Setting permissions on FOGSnapinReplicator.service script...OK
 * Enabling FOGSnapinReplicator.service Service................OK
 * Setting permissions on FOGScheduler.service script..........OK
 * Enabling FOGScheduler.service Service.......................OK
 * Setting permissions on FOGPingHosts.service script..........OK
 * Enabling FOGPingHosts.service Service.......................OK
 * Setting up FOG Services.....................................OK
 * Starting FOGMulticastManager.service Service................OK
 * Starting FOGImageReplicator.service Service.................OK
 * Starting FOGSnapinReplicator.service Service................OK
 * Starting FOGScheduler.service Service.......................OK
 * Starting FOGPingHosts.service Service.......................OK

@arnaudrigole Hi, sorry, I’ve not seen that you had another vdisk, why you have not extend existing vdisk ???

@arnaudrigole Oups, you have to use fdisk before

@arnaudrigole Hi, you can resize with resize2fs : resize2fs /dev/sda1. Take a snapshot before, if your are not sure you can chat with me in french.

@plegrand Hi, Could you try in debug task ?

Chosse debug task after select deploy task :

After PXE boot, you have to run fog task with fog command

@mitzayapa said:

This is what i should have then ?

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface

auto lo
iface lo inet loopback

# The primary network interface

auto em1
iface em1 inet manual
  bond-master bond0
  bond-primary em1

auto p255p1
iface p255p1 inet manual
  bond-master bond0

auto bond0
iface bond0 inet static
  bond-slaves em1 p255p1
  bond-mode 2
  bond-miimon 100
  address 192.168.137.51
  netmask 255.255.255.0
  gateway 192.168.137.1

It’s seem to be good, it’s not necessary to configure your p255p1 and em1 interfaces :

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface

auto lo
iface lo inet loopback

# The primary network interface

#auto em1
#iface em1 inet manual
#  bond-master bond0
 # bond-primary em1

#auto p255p1
#iface p255p1 inet manual
#  bond-master bond0

auto bond0
iface bond0 inet static
  bond-slaves em1 p255p1
  bond-mode 2
  bond-miimon 100
  address 192.168.137.51
  netmask 255.255.255.0
  gateway 192.168.137.1

@mitzayapa Hi, have you configured your switch to enable LACP ?

I use it on a debian 8 (in vmware esxi 5.5) with that interfaces config :

auto bond0
iface bond0 inet static
	address 172.20.0.4
	netmask 255.255.0.0
	gateway 172.20.1.50
	slaves eth0 eth1
	bond_mode balance-alb
	bond_miimon 100
	bond_downdelay 200
	bond_updelay 200

@jloke Hi, It’s seem to be a network problem, like DHCP or network. Could you try with dev revision (on a test server) : https://wiki.fogproject.org/wiki/index.php/Upgrade_to_trunk

@Tom-Elliott I’ll test, thx