Posts made by jheikkila54

@Tom-Elliott Thank you Tom!!! RPCBIND was not running, I started that service and configured it to run at startup and is now working. Again, thank you very much for the help, it is greatly appreciated.

@Tom-Elliott Yes that is the correct IP address

@Tom-Elliott Oh that it is, sorry I am multitasking excessively currently.

@Tom-Elliott It all flies by so it is a bit difficult to catch, looks to be failing at “Mounting File System” I am not quite sure how to run a debug.

@Tom-Elliott I have preformed a full checkdisk and returned 0 errors. I then created a new image to test, this image failed in the same spot with the same error.

It may have been partclone, I deleted the image and created a new one as a troubleshooting step, it must have defaulted to “partimage” I did just try it with “partclone” with same results. I can boot into Window with no issue, what would you like me to do?

I upgraded from 1.3.5-RC10

Image Settings:
OS - Windows 10
Image Path - /images/Windows10x64_PRO
Image Type - Single Disk - Resizeable
Partition - Everything
Compression - 6
Image Manager - Partimage

I am not sure what you mean by “box model” but this is a virtual machine that has 1 disk. I have been using this VM to update my image for about 1.5 years now with 0 issues, until now.

Server

• FOG Version: 1.4.2
• OS: CentOS 6.9

Client

• Service Version:
• OS: Windows 10 Pro 1607

Description

I recently updated FOG to 1.4.2 and it appears I cannot capture my image anymore and I have searched high and low for an answer with no success. The error I get is:
Could not mount /dev/sda2 (/bin/fog.upload->beginUpload)
Args Passed:
Reason: Run lists overlap. Cannot merge: Numerical result out of range

@Wayne-Workman
Alright good news, I got everything working! First thing, connecting to the mysql server as ‘fogstorage’ on the main server will not work, fogstorage has host access from % (which includes all IP addresses except for localhost.) In order to get this working, this is what I had done (in-case anyone else runs into this)

1. Verify that the node cannot communicate with the main MySQL server
   mysql -u fogstorage -h (your main servers DNS/IP address) -p
   enter your fogstorage password and hit enter
2. If you do not successfully log in, then you need to change your passwords.
3. Go to the webpage of the main fog server and go to Fog Configuration->Fog Settings->Configure Storage Nodes
4. Set the username to fogstorage and the password to whatever you want
5. SSH into the main fog server
6. Connect to the local MySQL server as root
   mysql -u root -p
   enter password (default is a blank password) and hit enter
7. Change the fogstorage user password
   use fog;
   UPDATE mysql.user SET Password=PASSWORD(‘the new passord’) WHERE User=‘fogstorage’;
   FLUSH PRIVILEGES;
   exit;
8. Test that you can connect to the mysql server by doing step 1 again.
9. If you can connect successfully now, you should be working, if not please try removing and reinstalling fog and ensuring you use the correct mysql username and password during the install phase

@Wayne-Workman Alright, it does not work, with fogstorage or root (root has no password)…

@Tom-Elliott Alright I upgraded my main to 6559, set the fogstorage password via the configuration page, created a new storage node with 6559 and set the mysql user to fogstorage and set the password to the same as the configuration page. I then put the username and password, supplied at the end of the install, into the management credentials when adding the new storage node. The images are replicating now but it appears that they are still not communicating as the boot.php page looks the same as before.

The old_password links below do not apply as the password for user fogstorage is not the “old way.” Any other thoughts?

@Tom-Elliott Ahh, makes sense!

@Tom-Elliott The main replicated the images to the storage node though, is that different from the line of communication you are talking about?

@Tom-Elliott No problem! I appreciate your help with this! I do know that TFTP-server was not installed on the storage node, so that is an obvious key, but how to go about adding it to the install script and config file for Redhat, is the question. The guide on the Wiki for completing that is now invalid.

@Tom-Elliott I used the fogstorage user and password, I believe. I set this up a week ago and followed the instructions in the install script.

@Tom-Elliott
Both are disabled, I have followed your guide religiously and verified everything.

@Tom-Elliott
Hey Tom, I am running the Node and Master on CentOS 6.7 64bit.

@Wayne-Workman

Hey Wayne,
Thanks for replying, I greatly appriciate it! I see this for the storage node boot.php

#!ipxe
set fog-ip
set fog-webroot
set boot-url http://${fog-ip}/${fog-webroot}
cpuid --ext 29 && set arch x86_64 || set arch i386
goto get_console
:console_set
colour --rgb 0x00567a 1 ||
colour --rgb 0x00567a 2 ||
colour --rgb 0x00567a 4 ||
cpair --foreground 7 --background 2 2 ||
goto MENU
:alt_console
cpair --background 0 1 ||
cpair --background 1 2 ||
goto MENU
:get_console
console --picture http:///service/ipxe/bg.png --left 100 --right 80 && goto console_set || goto alt_console
:MENU
menu
colour --rgb 0xff0000 0 ||
cpair --foreground 1 1 ||
cpair --foreground 0 3 ||
cpair --foreground 4 4 ||
item --gap Host is NOT registered!
item --gap – -------------------------------------
choose --default fog.local --timeout 0 target && goto ${target}
:bootme
chain -ar http:///service/ipxe/boot.php##params ||
goto MENU
autoboot

Good Morning,

I have setup FOG 1.2 R6455 at our main branch. We are looking to setup storage nodes at our other branches and to have PXE boot enabled on the storage nodes. I have followed the guide to do so for 1.2, but both files the require adjusting in the latest releases, do not have the locations described in the post. I have a storage node setup and the images replicated, but I cannot PXE boot to that node (yes I have setup the DHCP options, and the computer does try to contact that server.) Everything is on the same subnet, so if I contact the PXE server at the main location and image a computer, will FOG be smart enough to use the local storage node or will it use a random one? I was wondering if there is a new way to do this now? Any help would be greatly appreciated.