Well, I checked permissions on those directories, and verified the path exists on my storage node. I think I’ll just need to buy bigger hard drives and do a local storage node. I really had hoped to use the FreeNAS but I’ve been after this for weeks and at this point it’s just worthless to keep wasting time.

I’m attempting to use a FreeNAS box as my storage node. I’ve followed the instructional Wiki for this process with moderate success. Unfortunately, after the image has been resized and captured I receive the following error on the client.

• Reattempting to update database…Failed
• Error returned: Type: 2, File: /var/www/html/fog/lib/fog/fogftp.class.php, Line: 708, Message: ftp_put(/mnt/Galaxy/data/images/dev/d850e63eca64): failed to open stream: No such file or directory, Host: 10.0.0.160, Username: Free

####################
An error has been detected
####################

Could not complete tasking (/bin/fog.upload)

I’m guessing this is an FTP authentication error, but I haven’t been able to hunt it down on my own. I appreciate any help.

I set up a FOG server a few years ago just to test it out as an imaging solution for the mid-sized business I work for. Then I purchased a pair of FreeNAS devices for onsite and offsite backup.

I had been using the 4TB harddrive in my FOG server as my images storage node, but I decided I wanted to have more space and image more machines, so I followed the step by step walkthrough for configuring FreeNAS to be a storage node for FOG.

The only issue I have observed is that when FOG creates an image on the FreeNAS the ‘Captured’ field displays ‘Invalid Date’.

None of my images stored to the default storage node in the FOG server received this message. What could be wrong? What information should I share to help you help me?

Thanks!

@george1421

Excellent. With your expert assistance I’ve arrived at Version 1.4.4, Rev 6077.

I’ll try a Single Disk - Resizable capture tonight.

@george1421

I used the instructions here and I think I upgraded too far. What in this causes me to upgrade to bleeding edge rather than stable?

sudo -i
git clone https://github.com/FOGProject/fogproject.git /root/fogproject
cd /root/fogproject
git checkout dev-branch
cd bin
./installfog.sh

Can I roll back to 1.4.4 from 1.5.0? (I’m on SVN 6080)

@george1421
Wow, I didn’t realize I was so far behind. Is there a mailing list I should be on to get notified of new releases?

Also, I’ve read about so much bugginess with Ubuntu 14.04. Would you recommend I do a clean setup on a different distro?

@sebastian-roth

Sorry for taking so long to respond. Here is my FOG version.

And here is the actual error.

I ended up getting the upload to work, but not as Option 1 ‘Single Disk - Resizable’, rather I had to select Option 2 ‘Multiple Partition Image - Single Disk (Not Resizable)’.

While I am glad I have an image, I don’t understand why I’ve been able to upload other images as Option 1 with no troubles. I will try the fix you described.

I have a functional FOG Server running version 689680. I am able to capture images with no difficulty throughout my organization, except for my personal system. Every time I attempt to PXE boot to capture the image I get an error at ‘Saving original partition table’

'The protection MBR partition is oversized! Auto-repairing.

The protective MBR’s 0xEE partition is oversized! Auto-repairing.

An error has been detected

Cannot determine partition type (getPartitionTableType)
Args Passed: /dev/sda

Computer will reboot in 1 minute.’

I have seen similar threads, but either I’m so bad with Linux I can’t follow the instructions or my issue is actually unique. I don’t know. My drive is SSD, 256 GB.

If I’m in the wrong place, please let me know. Thanks in advance!

@george1421 Thanks, I will.