Could nt mount images folder Permission denied

[KLM]

Hi,
I performed an installation:

Server

• FOG Version: 1.3.3
• OS: Debian
• Powered by Hyper-V
• Dhcp server managed by pfsense
• Added a 700GB virtual hard drive

Description

Created a folder in / image (/image/new) with a symlink linking to /image folder :

By doing so :
Sudo blkid / dev / sdX1
And copy the UUID into a text file UUID = XXXXXXXXXXXXXXXXXXXXXX

Create a new folder new in / images:
Mkdir / images / new
Sudo chown -R fog / images / new
Sudo chmod -R 755 / images / new

Change / etc / fstab for automatic editing of the new disk:
Sudo nano / etc / fstab
Add the following lines:
UUID = XXXXXXXXXXXXXXXXXXXXXX
/ Images / new
Ext3 defaults 0 0

Mount the disc:
Sudo mount -a
Check installation:
Sudo mount

I find myself with a first error, here is a picture:

After changing the / etc / export folder:

I always find myself with the same error.
If anyone has an idea to advance my resolution this will be great.
PS: I’m sorry for my english, i’m french (^_^)

[george1421]

@KLM said in Could nt mount images folder Permission denied:

Added a 700GB virtual hard drive

if your 700GB hard drive is mounted on /images/new the FOG target computer (FOS Linux) will not be able to see it. It is an nfs restriction not a FOG issue. Where we have had success is mounting the new vmdk/vhd over /images and then not touching any other fog default setting.

I do have a tutorial on how to do this with Centos 7, it should translate to Debian without issue. Ref: https://forums.fogproject.org/topic/6642/moving-fog-s-images-files-off-the-root-partition

PS: I’m sorry for my english, I’m an American.

[Quazz]

I could be wrong, but I get an uneasy feeling whenever someone symlinks to a parent directory. Endless recursive loops come to mind.

Is this hard drive intended as additional storage? (are there images on your current hard drive that will remain there?)

[Wayne Workman]

@KLM said in Could nt mount images folder Permission denied:

Created a folder in / image (/image/new) with a symlink linking to /image folder :

That’s probably not a good idea, as @Quazz already said. You could do it proper and move all old image files to the new partition, then mount that partition to /images proper. Another option is to have a second storage node configured for a new location on your server such as /images2

[KLM]

Thanks to you for your responses so fast.
So I will not re-do a VM with bigger disk space since the installation.
Thus I will avoid endless recursive loops.