Unable to move /images/dev/*mac to /images/*image

[Ocelottruth]

Hello,

I have been trying to get fog working for a couple of weeks now to no avail. This is the error that I continue to run up against.

Unable to move /images/dev/*macaddress to /images/*imagename

I have done both the chmod and chown commands, but they have not helped either.

Could this be a hardware issue? Or is it still a permissions issue?

Could a firewall be blocking something?

Any help is appreciated!

[chad-bisd]

that move is done via ftp. make sure that the “fog” user has rights to the files and the directories and that you can log into ftp from another console using the fog username and the password specified in the fog settings.

[Ocelottruth]

Sorry, I am a novice when it comes to linux, but I am still learning.

How would I go about checking/adding permissions to the fog account?

[Ocelottruth]

Sorry, I am running Ubuntu 12.04 on an esxi host

[Tom Elliott]

So there are a few things to check to make sure the permissions are set, but it’s easier just to ensure all is set fine.

I’m going to assume you haven’t enabled login with the root account. Make sure the user you are logged in as has access through sudo.

[code]sudo chown -R fog.root /tftpboot/
sudo touch /images/.mntcheck /images/dev/.mntcheck
sudo chmod -R 777 /images[/code]

That should be it to verify all permissions are set properly.

The following steps will make sure you know the fog users’ password.

[code]sudo passwd fog[/code]

Set the password and confirm as requested.

Once that’s all done reset the passwords on:
(?) Icon->fog settings->FOG_TFTP_PASSWORD

And probably will be the same for:
Storage Management->All Storage Nodes-><YOUR STORAGENODE>->Management Password.

[Ocelottruth]

I have completed all of those steps, then tried to upload the image once again. I do get something a little different now. When it boots to pxe, it flashes some numbers, to quick for me to read, then boots back to windows. Once I go back into the fog console, the task is gone. If I create the task again, it gives me the same move error as before.

I do notice that before it gets to the failed to move error, a lot of bios and driver checks fail. Not sure if this has any effect on the above.