Could not mount images folder Error

[lschnider]

[root@localhost cmc_it]# sestatus
SELinux status:                 enabled
SELinuxfs mount:                /sys/fs/selinux
SELinux root directory:         /etc/selinux
Loaded policy name:             targeted
Current mode:                   permissive
Mode from config file:          permissive
Policy MLS status:              enabled
Policy deny_unknown status:     allowed
Max kernel policy version:      31

[george1421]

@lschnider You will still have an issue. You did not follow the prerequisites for installing FOG.

Now you need to edit /etc/selinux/config
In that file edit
SELINUX=enforcing
to read
SELINUX=permissive

reboot the fog server.

[george1421]

@lschnider scratch that, it is set to permissive. I did not read well enough.

OK we need to see the error that is just off the top of the screen in your previous picture.

[george1421]

@lschnider Also I’ve seen that date.timezone warning message before. I don’t know if that is something new with 1.5.5 or not. Can you confirm that this FOG setting is correct for your timezone: FOG Configuration->FOG Settings->General Settings->TZ INFO

[lschnider]

Well maybe this is a dumb question but how do you scroll up on that screen. I have been trying to but it wont let me.

[lschnider]

@george1421 The date/time was wrong. I fixed that, i will try to run the capture again.

[george1421]

@lschnider You can’t it a character mode terminal. If its scrolled off the top of the screen then its lost. Lets see if we can fix the TZ issue so those warning messages will go away.

Let me ask you have you messed with / changed the password for the FOG linux service account called fog? This is not the default webui admin called fog this is the linux user called fog? If you changed this account I might expect this error message at this point in the capture process.

[george1421]

@lschnider said in Could not mount images folder Error:

@george1421 The date/time was wrong. I fixed that, i will try to run the capture again.

You may need to reboot the fog server for that setting to get installed.

[lschnider]

@george1421 no i dont believe i have. Is there a way to tell if the password is like it should be?

[george1421]

@lschnider There is a hidden file /opt/fog/.fogsettings The linux user account for fog is listed in there.

Test from a windows computer, ftp to the fog server. Login as fog and the long password from the .fogsettings file. If that works then we need to look at the configuration.

[lschnider]

@george1421 okay i tried to ftp and it says

I will try to get a picture of that error you asked about earlier.

[george1421]

@lschnider OK just to confirm you used the value from the password field from the .fogsettings file? If so I have a tutorial on how to resync the fog service account here:
https://forums.fogproject.org/topic/11203/resyncing-fog-s-service-account-password

Run through that tutorial to ensure everything is reset correctly.

[lschnider]

@george1421 Okay i followed your tutorial and made sure everything was done correctly. Now i am able to capture an image with no problem but im getting a different error when trying to deploy an image.

I have tried two different hard drives, and the second one was a blank 500gb ssd. Both hard drives said the exact same free space.

[george1421]

@lschnider Well that’s an error I haven’t seen before.

can you confirm that this file exists on the fog server. /images/Windows_Basic_Test/d1p2.img

[lschnider]

@george1421 How would i go about browsing to that folder. /images isnt showing anywhere.

[lschnider]

@george1421 just kidding, i was being dumb.
Yes that file is there.

[lschnider]

@george1421 it seems like its not creating a partition big enough when wiping the drive and then creating the partition to write the image to.

[george1421]

@lschnider What language is the target computer OS? Is it US english or something else?

[Sebastian Roth]

@lschnider The “read ERROR: No such file or directory” is a bit miss-leading. What FOG does in the background is it spawns a tool that extracts the d1pX.img file on the fly through a FIFO pipe. In case the gzip extraction is failing (process dies for whatever reason) partclone failes with “No such file or directory” because the FIFO it was reading from is gone.

We have seen people reporting this in the forums every now and then (see forum search). Mostly unsolved or solved for no reason. Quite often it’s been in VM environments and I tend to believe that it might have to do with too little RAM setup for the VM causing the gzip extraction to fail and die. Just a guess in the wild. But see if you can successfully deploy the image if you add more RAM to the VM and try again.

[lschnider]

@Sebastian-Roth So the image i captured was off of a VM and it has 8 gb of RAM allotted to it, but it let me capture it perfectly fine. But when i deploy the image is where its having issues. I’m also deploying to a physical machine. and it has 12 gb of RAM.