Something i don’t anderstand is : I’ve got an other highscool to handle and i’m using fog on ubuntu too. I’ve got to upgrade the distribution here (to 17.10) and i’ve got no issue like this or at all…

@jpLeca Could you please send your last answer in your native language as well. Might help us all understand a bit more and could be helpful to other users too.

@george1421 Eh, saying ‘try’ sounds less like orders. I’m a boss of nobody but myself.

Hi,

I found a solution:

kernel tftp://${fog-ip}/boot/ubuntu/trusty/amd64/linux initrd tftp://${fog-ip}/boot/ubuntu/trusty/amd64/initrd.gz imgargs linux auto=true console-setup/layoutcode=fr keyboard-configuration/xkb-keyboard=fr locale=fr_FR.UTF-8 hostname=master domain=maestria.fr url=http://${fog-ip}/preseed_path/preseed_name.cfg quiet initrd=initrd.gz root=/dev/nfs netboot=nfs nfsroot=${fog-ip}:/tftpboot/boot/ubuntu/trusty/amd64/ boot

It’s look to work just need to configure my preseed file correctly.

Thank’s

@zago123 I was talking about the version of the ISO specifically. Apologies for not making that clear the first time.

@george1421

Thanks for that - I’ve got it booting - my menu entry now looks like:

Menu Item: fog.ubuntu-server
Description: Ubuntu Server 16.04
kernel tftp://192.168.0.22/os/ubuntu/16.04/server/vmlinuz
initrd tftp://192.168.0.22/os/ubuntu/16.04/server/initrd.gz
imgargs vmlinuz initrd=initrd.gz root=/dev/nfs netboot=nfs nfsroot=192.168.0.22:/images/os/ubuntu/16.04/server/ locale=en_GB.UTF-8 keyboard-configuration/layoutcode=gb
boot || goto MENU

Many thanks again for your help!

@tom-elliott
Filesystem Size Used Avail Use% Mounted on
udev 3.9G 0 3.9G 0% /dev
tmpfs 787M 9.3M 778M 2% /run
/dev/sda1 451G 5.7G 423G 2% /
tmpfs 3.9G 212K 3.9G 1% /dev/shm
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup
tmpfs 787M 60K 787M 1% /run/user/1000
/dev/sdb1 1.8T 614G 1.2T 36% /media/fog/d40b9b49-226e-4e64-b365-0b7b71d9ed3b

i used this and it worked: https://wiki.fogproject.org/wiki/index.php?title=Moving_your_images_directory/Adding_Storage_to_the_Images_directory

Thanks!

Thank you so much! It’s working now!

@wayne-workman
That’s my plan I am copying the entire image directory and going to migrate.

@tom-elliott Oh la la!! works very verry fine 🙂

@tom-elliott I am not quite sure what was wrong. I was working with someone else here on the forums on trying to do the automation and he had me run a script on mysql which ended up messing up a few things (accident). I was trying to work with the persistent groups piece. I ended up having to do a restore of the FOG server and that’s when the issues happened. I think I just had some duplicate entries somehow once I did the restore.

I look forward to a new GUI layout! You guys are rock stars!

@wayne-workman
That Worked!

[root@10fogserver MonitorFogStorageNodes]# git log -1 commit bb920e4367b5076ac2bb7bb70575ec4b647d5aee Author: wayneworkman <13314799+wayneworkman@users.noreply.github.com> Date: Wed Feb 21 13:53:10 2018 -0600 Fix spacing in evaluations [root@10fogserver MonitorFogStorageNodes]# ./MonitorNodes.sh [root@10fogserver MonitorFogStorageNodes]#

Thanks @Wayne-Workman

@it-john The key things to backup are a mysqldump of the fog database, images, snapins, and your ssl keys. Not sure if the script gets the ssl keys, those are new as of 1.3.

@mottz I guess you are capturing an UEFI based system, right? FOG still can’t capture UEFI boot entries from a system on capture. It’s been in the pipeline but I can’t say when we’ll get to it.

Just for CentOS 7 or Debian 9 I would recommend 8GB, plus whatever space you need for imaging. Also, the makeFogMobile scripts have matured, they are available here: https://github.com/FOGProject/fog-community-scripts/tree/master/MakeFogMobile

@wayne-workman

That’s exactly what I did. I wrote a shell script and put it in rc.local. It checks through the mac if the computer is in the fogserver database and from there it makes the change of hostname and join in our domain.

Thanks to all for your help!!!

@george1421 Figured. Thanks. Can you mark this solved? I can’t see where I can do it. I’ll open another post if I run into something else I think I need your help with. Thanks again for your assistance.

So is this solved?

With the postinit scripts messed up, deployment/capture will probably not happen. The postinit scripts are run first then tasking starts.

@zpoling said in Error capturing image after increasing drive size:

So if I ever encounter an error, should I go to the Wiki first and not the forums?

All of the standard troubleshooting we recommend for standard problems is usually documented in the wiki as best as we can.
This list has all of our troubleshooting articles:
https://wiki.fogproject.org/wiki/index.php?title=Installation#Troubleshooting

But there are of course nuggets spread all over the wiki.

@taspharel said in CPU Usage high:

In the long term the question remains: Why did that happen at all and is it related to our error regarding the web-gui “freeze” when looking at scheduled tasks?

Well it might be related as in the “freeze” might have been caused by the same “zombie” jobs. But I don’t really know.

Looking at the three tasks in the database again I see that all of them had stImageID zero. Don’t think that is valid. Not sure if that was causing it.