Best posts made by Wayne Workman

@george1421 I agree. Default should be “Replication - disabled/unchecked”

FOG Users - when they see that checkbox, they will immediately know what it does. So no worries of confusion.

@Nicolas-Bricet Are you using IPv6 throughout your university?

Can you give us a YouTube video of the issue you’re seeing? Just a short smartphone video of a computer booting until it hangs would be good.

After the new drive is formated and mounted and you can SEE it in the linux system,

open the CLI, go to the new image directory (wherever you mounted it)

create a .mntcheck file there, then create the dev folder and a .mntcheck file in there.

touch .mntcheck;mkdir dev;touch dev/.mntcheck

The new directory needs 777 permissions assigned to it recursively as well (you may change this later after it’s working)

I’m keeping my instructions and commands here generic so that this can help others.

chmod -R 777 /the/path/to/your/new/hdd/mount/goes/here

Then you need to add the new images and new dev folders to the exports file:

vi /etc/exports

You’ll see the two lines in there already for your old local storage node. They will have IDs, and in 1.2.0 they start at 1.
Copy those two lines, change the IDs to 3 and 4. Modify the paths so they are correct.

Then either reboot or restart NFS and RCP.

Tom has changed up a lot of things in the pre-process before partclone goes to work.

Most of the errors are usually non-impacting.

Now, it just shows them so you know what’s going on.

IMHO I say this feature can wait till FOG 2.0 is released. I really want to see 1.3.0 released soon.

@wwarsin said:

@Tom-Elliott Hi Tom, I just tried that and recieved the following error (I’m on SVN 5666 now)

FOGFTP: Failed to rename file. Remote Path: //var/www/html/fog/service/ipxe/bzImage/backup/bzImage_20151207_214012, Local Path: /var/www/html/fog/service/ipxe/bzImage, Error: ftp_rename(): Rename failed.

You’ll find the FTP credentials and host used for the Kernel updater here:

FOG Configuration -> FOG Settings -> TFTP Server ->

• FOG_TFTP_HOST #This is the IP that FTP uses for putting the kernel in place.
• FOG_TFTP_FTP_USERNAME #This is the username FTP uses.
• FOG_TFTP_FTP_PASSWORD #This is the password FTP uses.
• FOG_TFTP_PXE_KERNEL_DIR #This is where FTP tries to put the kernels.

Also, @Tom-Elliott I’ve recently discovered a bug. I don’t know how long it’s existed but I was able to figure it out today. On both our Administration FOG setup, and my building’s FOG setup (which is separate), the FOG_TFTP_PXE_KERNEL_DIR is missing a slash in the path:
/var/www/html/fog/service/ipxe/ The one colored red. I manually corrected it on both and it works, but we didn’t manually remove that slash. Just pointing that out to maybe help others with the issue.

@Jordonlovik said:

Do I have that correct?

Not really no. Sorry.

the .mntcheck files are empty. They are blank. When NFS mounting occurs on the client, it then verifies that mounting was done correctly and is working. It does this by checking for a file called .mntcheck The clients do not look inside the file, they merely look to see if the file exists. Hence “mnt check”

the /etc/exports file defines what directories are exported. think of this as sharing. In that file, you should have two lines that describe your existing local storage node. Just copy those lines and past them at the end of the file, and change those two pasted lines to describe the new exported directories (wherever you mounted your hdd to). You’ll need to update their IDs. You cannot have duplicate IDs in this file. Then you save your changes, and then reboot.

Does this make sense?

inside of FOG Configuration -> FOG Settings -> Client Service

The “New client” thing must be checked for the new client to work.

Also please note that you should type in your PLAIN TEXT password into the password field, and that your fogcrypt string should go into the legacy field.

Also note that in the hosts menu, any password that you put into the AD Settings fields in there gets re-encrypted when the aforementioned “NEW CLIENT” check-box is checked. So, I’d recommend just clicking the “Clear Fields” and then click the “Join Domain” so that it simply auto-populates.

@Tom-Elliott Amazing. I’ve been wanting this for a while.

Now, if the check sums don’t match, does it re-attempt the downloads? What about checksums for the new client?

@ZINGARO1972
https://wiki.fogproject.org/wiki/index.php?title=Upgrade_to_trunk#Check_what_version_you.27re_running

@Jordonlovik said:

all i have to do is add two new lines with new IDs that correspond with the new node location.

Correct.

Plus the .mntcheck files and dev folder, and the matching stuff in the web interface afterwards.

files in Linux that begin with a period are hidden.

ls lists files.
-a includes hidden files.
-l shows permissions and ownership.
-R is the recursive flag.

So this command would show every single file in /images and it’s sub-directories:
[CODE]ls -laR /images[/CODE]

You could pipe that with grep, which is a powerful searching tool and just search for .mntcheck

[CODE]ls -laR /images | grep .mntcheck[/CODE]
That will only show all instances of .mntcheck inside the /images directory.

There should be two.

Please and thanks.

@Arrowhead-IT said:

because I’m dumb when I’m sleepy.

You’re not the only one. Number 1 piece of advice I give to college kids, athletes, and just every day people is don’t sacrifice your sleep.

Short story - I was going through studying for finals in college one semester, staying up late, getting up early for work. Trying to find time to code a custom price markup management piece of software for a business that wanted to further save more paper. Basically double columns of data per page, like rows 1-80 on the left, 81 through 160 on the right, then on the back of the page, and so on…

I kept screwing it up… couldn’t get the math right. And yes, there’s algebra involved with this problem. I spent days on this. Just couldn’t get it.

Then, instead of continuing to pound at it, I realized I was really really tired, and I needed to sleep. I took a nap for 3 or 4 hours. When I woke up, I solved the problem in 5 minutes.

Sleep… so important. Sleep deprivation makes you dumb. You become mentally exhausted, just as you can physically. Physically, your body will be less strong, able to go less distance, lift less weight. Mental exhaustion means your not as clear, don’t have as good memory, not as good focus or attention to detail, and not so creative and not so good at solving problems.

People brush off sleep like it’s un-necessary. These are the people that consistently unperform, or just barely make par. Really, really value your sleep!

@Jordonlovik

You don’t edit the .mntcheck file. It’s supposed to be a blank file.

You simply create it with touch .mntcheck and that’s it, you are done.

http://www.linfo.org/touch.html

The touch Command
The touch command is the easiest way to create new, empty files.

@Tune389 said:

@ch3i okay thanks for the info. I try now to downgrade my fog version back to 1.2 …

That’s not supported nor advised…
To “downgrade” requires either restoring a previous snapshot (via a virtual machine) or rebuilding your FOG server from scratch…

Then we need to figure out a way for any old client that reports in - to just be told to execute such-n-such to install the new client automatically. This is really important.

@BASURILLABAS2 In your picture below, it’s still trying to use bzimage32 with init.xz. One is 32 bit, the other is 64 bit. They can’t work together. Did you re-run the installer? What version of FOG are you using? Have you specified anything in the kernel parameters for this particular host?

@Jordonlovik I apologize, I should have realized. You do need “super user” permission when editing /etc/exports.

you can either A. change to super user for the duration of your session like sudo su or B. execute only one command with sudo like sudo vi /etc/exports

@Julianh You’re missing one .mntcheck file.

You need one in both images and dev folders

[CODE]touch /images2/.mntcheck
touch /images2/dev/.mntcheck[/CODE]

After that, restart the NFS service and portmap/RPC (or reboot the machine).

Let us know what it does then.