@bartont126 I’m glad you have it all worked out. I checked in on the other threads and it looks like you found out about the dirty bits and shutting windows down properly and how to add additional storage to your fog server. well done.

@stakey Which version of FOG is this? Do you see all the hosts if you set to LIST instead of SEARCH (FOG Configuration -> FOG Settings -> FOG View Settings -> VIEW DEFAULT SCREEN)?

@bartont126 On Linux systems you can easily mount drives anywhere in the filesystem. So you can just hock up the huge drive to your machine, check the name it came up with, mount that, move your images and remount it in /images location.

Hint: Please be very careful with those commands and make sure you understand every step before proceeding! There is a chance that you wipe all your data from the server if you don’t know what you do and things go wrong! I am not liable for any actions done blindly following the steps posted here.

That said, shutdown the server, connect the new drive and boot it up again.

sudo -i fdisk -l

That should print out all the disks, where quite often /dev/sda is your system disk and the new one might be /dev/sdb. See if it is partitioned properly yet. If not, go ahead:

aptitude install parted parted /dev/sdb mklabel gpt mkpart primary ext4 1MiB 100% mkfs.ext4 /dev/sdb1 mkdir /newdisk mount /dev/sdb1 /newdisk service nfs-kernel-server stop mv /images/* /newdisk mv /images/.mntcheck /newdisk umount /newdisk rmdir /newdisk mount /dev/sdb1 /images service nfs-kernel-server start

You should see the new bigger disk space in the FOG web UI now. But to make this change persistent you need to add an entry to /etc/fstab so the big disk will be mounted automatically on boot. Add the following line.

/dev/sdb1 /images ext4 defaults 0 0

Now reboot you FOG server and see if everything is up to your needs.

@flipwalker This is what you’re looking for: https://forums.fogproject.org/topic/8151/pxe-quick-registration-w-a-hostname/2
If you need further help, just ask.

Rather than changing FOS /etc/fstab file, I believe it would be better to pass it as a kernel argument like clamMount=x.x.x.x:/some/clam/av/dir and have the script mount that dynamically. Then it can be user adjustable like image mounts are already.

@martinetwork There is no way we can help without you telling us more details about your network. Broadcast domains, VLANs, switches, routers/layer-3-switches, config, …

Quite often forwards are to be configured for one particular sender. So your PDQ waking properly does not mean much.

@wayne-workman as in RC12? Ok I have another Issue I will be posted but testing again to make sure I can replicate it before posting. Its with Snapins not reporting they are finished and then keep trying to run over and over again. Windows 10 and Windows 7.

Trying to avoid updating to RC and waiting for next stable but if its fixed in an RC we might have to go for it.

@D_quiros Please check the apache logs. See my signature…

@george1421 said in Target computer booting from router not fog:
1_1518442700261_Ubuntu_FOG-2018-02-12-14-32-36.png 0_1518442700157_Ubuntu_FOG-2018-02-12-14-32-02.png

@sebastian-roth That did the trick! That server can now update its kernel.

It’s interesting to see how two different causes have similar results.

@george1421 that’s what I told him too.

@orioliz Have you done a proper filesystem check on that system? Boot it up using a live Linux CD/DVD and run fsck /dev/sda1

@wayne-workman
Thanks, next time i will take some time before acting and wasting my time.
I keep this guide for the next time.
Thank.
Eric.

@msi said in Image capture task did not complete:

By the way, love the new look on the FOG

@Joe-Schmitt

@jburston see the wiki article called “password central”. If you need further help, please open a new thread for the new issue and post the last 200 or so lines from your fog.log file.

Fixed by changing memory size in php.ini

@tom-elliott yes it went back to the full amount.

@george1421 He’s referring to the autologout module, but you’re definitely not wrong.

@blkeller, duly noted. Updating the time restraints means updating the entry in SQL, not hard, and I can have that done fairly easily. Even not allowing the setting to hold on to anything less than 5 minutes isn’t too hard, though do I set it to 0 if it’s below 5? Just thoughts on how best to approach. I don’t think it should warrant an “error” to update the host because that field isn’t really necessary for normal imaging functions.

@wayne-workman Absolutely. As soon as I can I will.

@Julianh I am sorry to say that but your setup is quiet complex with so many disks mounted in various locations and I don’t think we’ll be able to reliably guide you through a migration here in the forums. I am not sure what to advice. As Wayne said, 1.4.4 can deploy 1.2 images. So unmounting and moving the disks to the new system should work.