Mounting /images/dev on /images failed - permissions denied

[El-Fogito]

Hello everyone,

Here is my problem:

I work on two sites and I have 1 fog server on each site.
The first (which I made 1 year ago) and which works very well. No problems to report, I use it daily for IT management.

The second (on a second site) causes me a lot of problems. However, I copied the same procedure in detail. But it seems that certain things were not configured automatically (I had to correct problems related to TFTP in particular, + certain paths have changed)

So my problem: When I try to capture an image: I obviously create a “container” image to accommodate the image after my sysprep. I run the task and everything seems to work (the size of the image appears fine etc…)

Except that when I want to deploy my image to a PC, here is my error:

failed to restore and exited with exit code 1 (writeImage)
Info :
Args Passed : /images/***/d1p1.img /dev/nvme0n1p1

What does this mean exactly, my understanding is that either a disk is not found, or a missing authorization that allows the door to be opened for recording.

I’ve been “playing” with the permissions for 4 days by comparing the server that works to this one, but nothing works. I constantly get errors like this.

Here are images of my errors:

![fog2.png]
(/assets/uploads/files/1720699038237-fog2.png) ![fog3.png]

However, the image seems to be created… I think it remains temporarily in /images/dev and that it is not installed in /images with the correct name. Rights problem?

I find very little information on the subject. I’m starting to get tired… Thank you in advance for your help

[george1421]

@El-Fogito will you post the output of the following commands executed on the fog server. You may need to execute the sudo su - command to allow you to run all of these commands.

df -h

ls -la /images

showmount -e 127.0.0.1

cat /etc/exports

Where it is failing is the fos linux engine (OS running on the target computer), it connects to the FOG server using NFS as ‘root’. For some reason this connection is being blocked. Lets see the configuration so we can know what to test next.

[El-Fogito]

@george1421 Thank you for your prompt response

here is :

[El-Fogito]

@El-Fogito for information :

I sent the same commands to the other FOG server:

[george1421]

@El-Fogito Hmmm everything looks good. I should have verified this question first but is 10.20.10.38 the IP address of the correct fog server?

Is the target computer on the same subnet as the fog server?

The print out of your troubled fog server told me that things are setup as they should be and you didn’t create an unknown configuration.

[El-Fogito]

@george1421the correct server is 10.10.10.38, the bad one is 10.20.10.38

they are in the same network yes, only different Vlans but with the same rules

[george1421]

@El-Fogito ok lets get our hands a little dirty to debug this issue.

Schedule another image capture on this troubled server. Pick a target computer that is available for you. Before you schedule another capture tick the debug checkbox then schedule the deployment.

On the target computer you will see several screens of text that you must clear with the enter key. Eventually you will be dropped to the FOS Linux command prompt. At the command prompt try to ping the troubled fog server.

now lets try to mount the images/dev share. On the target computer issue the following commands

mkdir /ntfs
mount  10.20.10.38:/images/dev /images 

If the mount is successful then issue a ls -la /images this should show the content of the /images/dev directory on the fog server.

umount /images

If everything is good then you can single step through the deployment by keying in fog at the fos linux command prompt.

[El-Fogito]

Hello,

I’m reviving the topic, my problem is still not resolved (I am deploying on 180 computers this week)…

I captured an image this morning, my PC restarts as if the image had been captured successfully

I also see the size of the image in the management console:

But here’s the problem:
In active tasks, a second loading (I imagine moving from images\dev to \images) is blocked. This is the crux of my problem. Database problem? what to do ? Here is a screen

[El-Fogito]

@El-Fogito

always same error when trying to deploy

my image is stored in image\dev with another name (mac address of the PC captured)

[Tom Elliott]

@El-Fogito I suspect the fogproject user that is supposed to be handling the FTP connection which does the FTP move from /images/dev/<macofhostcaptured> -> /images/<nameofimagepathcaptured> is out of sync or simply non-functional.

Can i make a bold request and as you to install the working-1.6 version of FOG?

It shifts the mechanisms of file transfer and moves to SSH instead of relying on FTP. This may have it’s own issues of note but we can work on fixing those. As well, it will help fix the NFS security flaws you seem to have running currently so you will have slightly more security conscious FOG install to boot.

[Tom Elliott]

@El-Fogito In the mean time you can manually move the image to the proper spot:

Since I don’t know the mac of the original capture machine you’ll have to get that yourself unfortunately.

From the FOG Server terminal:

sudo mv /images/dev/<macofhostyoucaptured> /images/Nuc7i5BNKSDC-AC001-C000-win11
sudo chown fogproject:root /images/Nuc7i5BNKSDC-AC001-C000-win11
sudo chmod 777 -R  /images/Nuc7i5BNKSDC-AC001-C000-win11

This should get you to a point of being able to deploy the image.

[El-Fogito]

@Tom-Elliott at the point where I am, no problem starting over with a new installation.

Could you give me a link to install this version? that I am sure to do what you asked me

[El-Fogito]

@Tom-Elliott said in Mounting /images/dev on /images failed - permissions denied:

sudo chmod 777 -R /images/Nuc7i5BNKSDC-AC001-C000-win11

I moved it manually, gave rights etc. The problem continues

[El-Fogito]

@Tom-Elliott I can’t find the installation of FOG working-1.6

[Tom Elliott]

@El-Fogito

You can get fog from github:

git clone https://github.com/fogproject/fogproject.git --branch=working-1.6

Normally you’d be in the users root directory (typically /home/<username> or /root if you’re the root user)

After it’s cloned cd to the newly downloaded fogproject folder:

cd fogproject
git pull
cd bin
sudo ./installfog.sh -y

That should do all the work. If you already have a branch of github fogproject on your machine run:

cd /path/to/fogproject/installer
git pull
git fetch --all
git checkout working-1.6
git pull
cd bin
sudo ./installfog.sh -y

it’s basically the same thing.

as for “Same issue after moving folder” can you describe what you mean? Unless I got a typo of the location for the image path an error may be there, but it should definitely be a different error.

[El-Fogito]

@Tom-Elliott Here is…

I typed these commands:

apt-get -y install git -y
apt install wget

cd/root
git clone https://github.com/fogproject/fogproject.git --branch=working-1.6

fog project cd
git pull
CD bin
./installfog.sh -y

I got this error when loading packages:

error: Installing package: php-mysql…………Failed! (Will try later)

The interface changes a little but I get the hang of it.
I’ll capture an image and get back to you

[Tom Elliott]

@El-Fogito Interesting that you got the error for php-mysql, though I suppose if it completed the “will try again later” actually worked.

[El-Fogito]

@Tom-Elliott

So I launched a task to capture my image and it was in principle a success, here is the screen:

BUT… once the download is complete, this is the error I receive:

Here again, the “second task” remains stuck at 1%

My capture is still stuck in \images\dev with my computer’s macadress

I’m helpless (I’m in production at the moment)

[El-Fogito]

@Tom-Elliott

FYI

[Tom Elliott]

@El-Fogito So, can you please manually edit the “failed” image from the /images/dev location and manually move it where it needed to go? (as well adjust the permissions again.

Also, can you please look at your /etc/ssh/sshd_config file and look for the line that has “Subsystem” and “sftp”

I am just guessing, but it likely looks like:
Subsystem sftp /usr/libexec/openssh/sftp-server

If you can change it to:
Subsystem sftp internal-sftp and restart ssh services on the server, this should address the “Unable to start SFTP” error you were seeing.

To restart ssh service you would run:

sudo systemctl restart sshd

We’re getting closer I think, but it’s just a guess at this point. I apologize for it seeming kind of hit and miss, but thus is the approach we must take on forums.