Cannot image - Mount point cannot be found

[zclift15]

Server Debian 10
Version 1.5.7
Client Win10

Currently I cannot image any computers as I recieve this error after attempting to deploy

[george1421]

@zclift15 Look in /images and /images/dev for a hidden file .mntcheck If that file is missing then it will throw that error.

ls -la /images
ls -la /images/dev

I’ve seen this happen if/when someone moves the location of the /images directory because they were adding new storage.

[zclift15]

@george1421 Yeah that would definitely be it we did not mount images until after installation for server reasons. where can I get that file?

[zclift15]

Wait no its there. My guess is that it came over because its our old /images directory from our outdated server

[george1421]

@zclift15 So just go in an touch that file in both directories.
touch /images/.mntcheck
touch /images/dev/.mntcheck

Or just rerun the fog install script and it should recreate the missing file structure.

EDIT: Ok rereading your last post the files are in there??

[zclift15]

@george1421 okay I ran those commands and now I get this error

[george1421]

@zclift15 ok so what does this look like ?
ls -la /images

and more to the point, does /images/Laptop_Fall19 have files in it?

[zclift15]

@george1421
yeah seems like its empty. Also not a directory?

[zclift15]

This post is deleted!

[george1421]

@zclift15 Well I missed that its not a directory because we’ve been tracking a similar error at that just point in the deploy script: https://github.com/FOGProject/fos/blob/master/Buildroot/board/FOG/FOS/rootfs_overlay/bin/fog.download#L76

Back to your point, that needs to be a directory with files in it. That is why the error is being thrown there. The script is checking to ensure the imagepath directory exists, which of course is no, because its a file.

I think you need to go back to your old server and find the files. If you old server is still operational I can give you the commands to connect and copy the files.

[zclift15]

@george1421 Actually its a new image so I can just recapture it

[george1421]

@zclift15 Did you capture it first time on this fog server, or did you copy it over? I’ve never seen fog do that so I’m curious…

Before you recapture it, remove the files from the images directory or the capture will fail at the very end.

[zclift15]

@george1421 Yes I did, and thanks for the tip!`

[zclift15]

@george1421 I just finished recapturing but the file is still not a directory

[george1421]

@zclift15 That is not possible.

How fog works is that the capture creates a directory in /images/dev/<mac_address> that <mac_address> matches the mac address of the target computer. The files are uploaded into that directory. After the capture is done and just before it reports updating the database, the target computer will connect to the FOG server over ftp, and issue a FTP move command to move the directory from /images/dev/<mac_address> to /images/<image_name>. At no time a file should be created with the same name as <image_name>

When you capture the image, is that mac_address directory created, or is that directory still in existence? If everything is working correctly, there should be no directories in /images/dev that have a mac address name unless an upload is currently underway.

[Sebastian Roth]

@zclift15 Make sure to change ownership of every file und sub dir… chown -R fogproject:fogproject /images

[zclift15]

@Sebastian-Roth Okay That seems to have solved that problem but now, (no matter how safely I shut down windows) fog is spitting the windows dirty bit error at me

@george1421

[george1421]

@zclift15 This is one way to shut it down cleanly shutdown -s -t 0 That should close all files, and clear the dirty bit flag.

[Sebastian Roth]

@zclift15 As well read through this: https://wiki.fogproject.org/wiki/index.php?title=Windows_Dirty_Bit