Could not mount images folder Error
-
@lschnider OK just to confirm you used the value from the
passwordfield 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-passwordRun through that tutorial to ensure everything is reset correctly.
-
@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.
-
@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 -
@george1421 How would i go about browsing to that folder. /images isnt showing anywhere.
-
@george1421 just kidding, i was being dumb.
Yes that file is there. -
@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.
-
@lschnider What language is the target computer OS? Is it US english or something else?
-
@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.
-
@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.
-
@george1421 the target computer had windows7 english on it before pushing out a new image.
-
@george1421 @Sebastian-Roth so i was able to capture and deploy an image. but i am only open to do it with the firewall turned off, i followed the tutorial again but cant seems to find what im missing on the firewall.
-
@Sebastian-Roth turns out that the RAM on the physical machine was actually bad.
-
@lschnider If you “must” have the firewall enabled, Joe (one of the developers) has working on a firewall configuration for FOG. Those settings are found here: https://forums.fogproject.org/topic/6162/firewall-configuration
-
@george1421 i actually dont need it enabled, i went ahead and set it to disabled permanently. I am now having a different issue but i will start a new discussion for that.
-
@lschnider FWIW: Some people “need” to have it enabled because of internal security policies. That is why the developers came up with a list of required ports.