@julianh said in Running out of Space during Imaging:

can I redirect the /images/dev to another disk?

Yes, you can do that. But there are some other questions to ask to figure out why you are having these problems and if there are any obvious quick wins we can help you with:

What is the output of df -h Output of lsblk Is this in a VM or a physical machine? Do you have more than one spare disk you can use for the FOG Server?

@sebastian-roth

I just happen to be harvesting 1TB drives from workstations for server use. The 250GB drives I picked up for $10 each are adequate for the floor computers.

Thank you for the firm point at cause.

I’m testing your idea but the msi is very badly done ! 😞

@szeraax Thanks for the update. It’s definitely an issue that we will be seeing more and more in the next month.

Not because it is solved, but because I will just have to wait for a magical time in the future when FOG has support for booting NVMe hard drives decently.

Unfortunately those things rarely solve themselves magically. People have to work on it. In this case having the hardware at hand seems to be very crucial as your findings reveal (same zbook model showing different behavior). By the way, have you checked firmware versions?
So what I am trying to say is that it might need your work on testing these things on your devices to hopefully figure things out. But on the other hand I do understand that you/we don’t have the time and expertise to dig through this.

Maybe try going back to using rEFInd plus adding the clover NVMe driver? As I understand it you should be able to add that driver by simply creating a directory drivers_x64 (EFI/boot/drivers_x64) and putting that clover driver EFI file there. rEFInd should scan that directory and load the driver.

Not sure if we’d mark this solved.

Of course - checked the logs and I had the user name or password in wrong in fog. Had to be easy. Thanks!

So I looked at the file with my wireshark at home (forbidden in office)
There´s no data.

I will set up a new fog from scratch and try to WOL the devices. I will report later.

thanks Wayne. I will do this this weekend and if I need help post back here.

@wayne-workman said in Image not syncing:

As far as the “error contacting server” message, can you visit https://sourceforge.net/ at your work? If not, that’s probably why.

I can access it on my network. I have perform below command in order to try and fix the syncing issue. Than I re-ran the fog installtion file to re-install. When I was checking the master fog storage under storage. I noticed password for the user fog was simply password and wasn’t matching the password in the .fogsettings file.

sudo mv /opt/fog/.fogsettings /opt/fog/fogsettings-firstInstall

Perfect! That worked a treat.

In the interest of housekeeping, can I now delete that group? If so do I need to remove hosts first?

Thanks,
Matt

@sebastian-roth @Tom-Elliott
Thank you both so much, through a combination of things I have it working. you guys ROCK!

Thanks again!

@sebastian-roth I was referring to my intended use case. I want to capture an image from a computer and automatically copy the individual files from the image onto a file server. In order to do that, I need a script that runs on the server, not the host. I could find a way to trigger it still (some primitive form of RPC, maybe a quick HTTP request with wget), but it wouldn’t be quite as convenient.

@tom-elliott I am actually thinking it might have been a BIOs setting. It was on RAID mode so I reinstalled Windows and just captured it and it appears to have booted back into my Windows this time.

I’ll finish up this install and try again and let you know.
Thanks!

@techadmin Yes you can delete those. Also you should read this: https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_MySQL#Repair_broken_database

@UWPVIOLATOR This has been fixed in v0.11.14, which will be released with the next server RC. I’d still recommend using process-explorer to find out why the file is locked though.

To get v0.11.14 you can either wait for the next server release, or download it from here: https://github.com/FOGProject/fog-client/releases/tag/0.11.14

@bigchief Sounds like a mismatch of bios/ueif to me. A UEFI system can sometimes have the feature to optionally legacy boot (bios). What mode is the firmware in? (bios/legacy or UEFI)? So figure that out - and then dig through the firmware settings to make sure no optional Legacy modes are enabled.

Also, could be something as simple as turning off the HDD’s RAID mode in firmware and enabling AHCI mode.

@warp said in WoL and VLAN:

On the other hand a tool of WoL Windows works well !

Maybe that’s from a different subnet/vlan? Can you try from a Windows machine in the same subnet as your FOG server is, so 172.16.8.x! If that works than we can start looking into FOG being the issue.

@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.